# Greif

> Greif, Inc. (NYSE: GEF) is a global industrial packaging manufacturer headquartered in Delaware,
> Ohio, producing steel, plastic and fibre drums, intermediate bulk containers, jerrycans, closures,
> containerboard, corrugated products, tubes and cores, and adhesives, with reconditioning and
> recycling services. Its customer-facing digital products are the Greif+ customer portal and the
> Greif Green Tool life-cycle-assessment calculator.

This file is generated by API Evangelist (https://apievangelist.com) from the public profile at
https://github.com/api-evangelist/greif. It is not published by Greif.

## API surface

Greif runs no developer program. There is no developer portal, no API documentation, no SDK, no CLI,
no MCP server, no agent card, no security.txt and no status page on any Greif host, and none of
developer.greif.com, developers.greif.com, api.greif.com, docs.greif.com, mcp.greif.com or
status.greif.com resolves in DNS.

One machine-readable contract does exist, and it is more useful than that summary suggests:

- **Greif WordPress REST API** — https://www.greif.com/wp-json (HTTP 200, 554 routes across 39
  namespaces, 182 of them under wp/v2; fetched 2026-09-12). It is the corporate website's CMS
  interface, not a product — undocumented, unsupported, and returning `X-Robots-Tag: noindex` on
  every response. But Greif has registered its OWN business entities for REST, so anonymous callers
  can read:
  - `/wp/v2/product` — the packaging product catalog (10 records observed)
  - `/wp/v2/product_category`, `/product_material`, `/product_capacity`, `/product_attribute`,
    `/product_market`, `/product_tag`, `/regional_availability` — the catalog taxonomies, which are
    also the filters on the product route
  - `/wp/v2/market` (14 records) and `/wp/v2/technology` — markets served and packaging technologies
  - `/wp/v2/sustainability_items` — sustainability programme items and targets
  - `/wp/v2/wpsl_stores`, `/wp/v2/store_location`, `/wp/v2/wpsl_store_category` — the facility and
    distributor locator
  - `/wp/v2/posts` (570), `/wp/v2/search`, `/wp/v2/types`, `/wp/v2/taxonomies`
  Paging is `page`/`per_page` (default 10, hard cap 100, enforced with HTTP 400), with `X-WP-Total`,
  `X-WP-TotalPages` and an RFC 8288 `Link: …; rel="next"` header. `/wp/v2/settings`, `/wp/v2/users`
  and `/wpsl/v1/block-data` return 401, and every write route needs a WordPress account on greif.com,
  which a third party cannot get. Errors use WordPress's `{code, message, data.status}` envelope, not
  RFC 9457.
  A derived OpenAPI 3.1 for this surface (182 paths, 429 operations) lives in this profile at
  `openapi/greif-wordpress-rest-openapi.yml`; Greif publishes no OpenAPI of its own.

What is NOT callable:

- Greif+ customer portal: https://plus.greif.com (also portal.greif.com) — a Next.js application that
  302s every anonymous request to /SignIn. Orders, forecasts, datasheets, certificates, price lists,
  invoices and complaints live behind it, with no API or integration documentation.
- Greif Green Tool 2.0: https://greentool.greif.com — a Nuxt single-page calculator whose bundle calls
  a backend at https://greifgreentoolnew.fahlgrendigital.com/api, operated by Greif's digital agency.
  That host answers 200 with the same SPA shell for every path, including /openapi.json and a random
  control path, so no contract is published.
- EMEA API gateway hostnames api.gw.emea.prd.greif.com and api.gw.emea.tst.greif.com appear in
  Certificate Transparency logs and resolve (157.97.118.114 / .113) but do not answer on 443 from the
  public internet — internal or partner infrastructure with no public contract.
- Machine-to-machine ordering with Greif runs on EDI (ANSI ASC X12, UN/EDIFACT) arranged bilaterally
  through trading-partner networks, not through a Greif-published specification.
- connect.greif.com serves a real security.txt, but it belongs to the vendor: the request redirects to
  https://www.getflip.com/.well-known/security.txt and names infosec@getflip.com. Greif publishes no
  vulnerability-disclosure contact of its own.

## Company

- Website: https://www.greif.com
- Greif+ customer portal: https://www.greif.com/greif-plus/ (sign-in at https://plus.greif.com)
- Green Tool 2.0: https://www.greif.com/life-cycle-assessment-tools/green-tool-2-0/
- Product catalog: https://www.greif.com/product-catalog/
- Services: https://www.greif.com/services/
- Blog: https://www.greif.com/category/blog/ (RSS: https://www.greif.com/feed/)
- Contact / support: https://www.greif.com/contact/
- Sustainability: https://www.greif.com/sustainability/
- Compliance policies: https://www.greif.com/compliance-policies/
- Terms and conditions: https://www.greif.com/terms-and-conditions/
- Privacy policy: https://www.greif.com/privacy-policy/
- Careers: https://www.greif.com/careers/
- LinkedIn: https://www.linkedin.com/company/greif
- YouTube: https://www.youtube.com/channel/UCFa1IzCyPcTp-ckGTcIMwNw

## Crawling and AI access

- https://www.greif.com/robots.txt allows GPTBot, OAI-SearchBot and ChatGPT-User explicitly, disallows
  only /wp-admin/, and sets Crawl-delay: 10.
- Sitemap index: https://www.greif.com/sitemap_index.xml
- No llms.txt is published by Greif on any host. plus.greif.com and portal.greif.com return HTTP 200
  with a zero-byte application/json body for /llms.txt, which is an empty response, not a document.

## Profile artifacts

- apis.yml: https://raw.githubusercontent.com/api-evangelist/greif/refs/heads/main/apis.yml
- OpenAPI (derived): openapi/greif-wordpress-rest-openapi.yml
- Route index (verbatim source): openapi/greif-wp-json-discovery.json
- Overlay: overlays/greif-wordpress-rest-overlay.yaml
- Authentication: authentication/greif-authentication.yml
- Conventions (paging, reversibility, no idempotency): conventions/greif-conventions.yml
- Error catalog (5 codes observed live): errors/greif-problem-types.yml
- Data model: data-model/greif-data-model.yml
- Lifecycle: lifecycle/greif-lifecycle.yml
- Conformance: conformance/greif-conformance.yml
- Agent skills: skills/_index.yml
- MCP candidate tool list (nothing is deployed): mcp/greif-mcp.yml
- Domain security probe: security/greif-domain-security.yml
- Well-known probe (no first-party documents served): well-known/greif-well-known.yml
- Packages / SDKs (none published): packages/greif-packages.yml
- Plans / pricing (none published): plans/greif-plans-pricing.yml
- Rate limits (none published): rate-limits/greif-rate-limits.yml