Peet's is the proof it can be done: it publishes an official llms.txt and a live UCP profile whose MCP shopping endpoint gives agents catalog, pricing, availability, checkout and order tracking — self-serve, no enrollment. The open door covers the peets.com retail store (packaged coffee, tea, merchandise); made-to-order coffeebar drinks remain human app / aggregator only, and checkout requires buyer authorization.
Industry Leader · The door is open · Census checked November 1, 2026
Five intents, checked against Peet's Coffee's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | OPEN API | Peet's UCP MCP (Shopify Universal Commerce Protocol) — Official llms.txt ('Agent Instructions — Peet's Coffee') documents UCP product discovery via the MCP endpoint advertised at https://www.peets.com/.well-known/ucp (verified live 2026-11-01: catalog.search and catalog.lookup capabilities, MCP transport). SCOPE CAVEAT: this covers the peets.com retail catalog (packaged coffee, tea, merch), NOT made-to-order coffeebar drinks — the coffeebar menu at peets.com/pages/menu is human web/app, with coffeebar delivery via DoorDash/Uber Eats. | Source — www.peets.com | 2026-11-01 |
| Prices | OPEN API | Peet's UCP MCP (Shopify Universal Commerce Protocol) — UCP catalog/cart/checkout tools return pricing; llms.txt instructs agents to 'Use the buyer's country and currency where supported by the tool schemas for accurate pricing and availability.' Retail scope only, as in menu_browse note. | Source — www.peets.com | 2026-11-01 |
| Inventory | OPEN API | Peet's UCP MCP (Shopify Universal Commerce Protocol) — Availability is exposed through the UCP catalog/fulfillment capabilities in the live /.well-known/ucp profile (dev.ucp.shopping.fulfillment, catalog search/lookup). This is retail product availability, not per-coffeebar drink/item stock, for which no API was found. | Source — www.peets.com | 2026-11-01 |
| Ordering | OPEN API | Peet's UCP MCP (Shopify Universal Commerce Protocol) — Llms.txt: 'Use those tools to find products, manage carts, prepare checkout, and complete buyer-authorized purchases' via UCP checkout (dev.ucp.shopping.checkout/cart in the UCP profile), with Shop Pay / card handlers. Buyer authorization is required. Coffeebar Order Ahead remains human app-only. | Source — www.peets.com | 2026-11-01 |
| Tracking | OPEN API | Peet's UCP MCP / Shop — Llms.txt Shop skill section: 'Orders: search your user's order history for purchases from this store, track deliveries, and reorder products,' and the UCP profile includes the dev.ucp.shopping.order capability. Retail e-commerce tracking only; coffeebar/delivery tracking would be via the aggregator used. | Source — www.peets.com | 2026-11-01 |
Agent-native surfaces at Peet's Coffee: official MCP server — published; llms.txt — published; API catalog (RFC 9727) — none published. Automated access: Shopify-standard with explicit agent rules: robots.txt Allow: / for * but Disallow /checkout, /cart/, /orders and /account; llms.txt requires agents to identify as agent-initiated, use Web Bot Auth / WebMCP tools, and back off on 429 (evidence).
One page per task an agent might attempt at Peet's Coffee — the door-state for that task alone, and what fits instead.
| Task | State | The page |
|---|---|---|
| Menu / browse | OPEN API | Can an AI agent browse the Peet's Coffee retail catalog? |
| Prices | OPEN API | Can an AI agent check prices at Peet's Coffee? |
| Inventory | OPEN API | Can an AI agent check availability at Peet's Coffee? |
| Ordering | OPEN API | Can an AI agent order from Peet's Coffee? |
| Tracking | OPEN API | Can an AI agent track a Peet's Coffee order? |
No registration is taken here — an agent goes straight to Peet's Coffee's own door.
Peet's UCP MCP shopping endpoint (Shopify Universal Commerce Protocol). Self-serve through the MCP endpoint advertised in Peet's official llms.txt and its /.well-known/ucp profile (catalog search/lookup, cart, checkout, order capabilities). Agents must identify as agent-initiated under the llms.txt rules, and checkout completes only with buyer authorization (Shop Pay / card handlers). Retail store only — not coffeebar drinks.
Peet's coffeebar — app / web, delivery via DoorDash and Uber Eats. Made-to-order coffeebar drinks have no agent door: the coffeebar menu is human web/app, Order Ahead is app-only, and coffeebar delivery runs through DoorDash and Uber Eats.
The verified door-state document is served as JSON by the API: api.agentoutposts.com/outposts/peetscoffee. A POST to the intent endpoint records nothing — it returns the open-door pointer (status door_open) — because the demand ledger counts demand only where a wall keeps agents out.
The proof it can be done.
Peet's Coffee opened a sanctioned door for agents itself — the thing every Outpost in this registry is asking its brand to do. Agent Outposts lists it as an Industry Leader: assessed on the same census, against the same five intents, from the same public sources.
No demand is registered at an Industry Leader, because there is no wall to count demand against. Agent Outposts re-checks this door on a standing sweep; if it ever closes, this listing becomes a demand registry and the counting starts.
You are listed as an Industry Leader — this page documents the door you opened.
Your door is the standard the census measures the other brands against. It is re-checked on a standing weekly sweep; if it ever closes, this listing converts into a demand registry and the counting starts. The census · Talk to us about your listing
Agent Outposts is not affiliated with Peet's Coffee. This Industry Leader listing documents a door Peet's Coffee opened itself; door-states are assessed from public sources, linked, and dated.