Short answer: yes — Peet's Coffee runs an open, self-serve API for this. The verified door-state for this exact task, the legal alternatives, and the demand registry are on this page.
The Peet's Coffee Outpost · Task · Ordering · Door-state verified November 1, 2026
Peet's Coffee · Ordering · Agent Readiness Census, November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Ordering | OPEN API | Peet's UCP MCP (Shopify Universal Commerce Protocol) | Source — www.peets.com | 2026-11-01 |
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.
Door-state version census-2026-11-01. The same document is served as JSON by the API: api.agentoutposts.com/outposts/peetscoffee — and published in full on the Peet's Coffee Outpost page.
Legal alternatives for this task, from the Options Registry.
Nothing fits today. No other business in the Coffee category has an open or partner-gated door for ordering in the census, so there is no sanctioned alternative to offer. That is exactly the case the registry below exists for: register the intent, take the receipt, and the demand is logged where the Peet's Coffee team can see it in aggregate.
Peet's Coffee is an Industry Leader — its door for agents is open, so there is no registry here, because there is no wall.
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 this pointer (status door_open) — because the demand ledger counts demand only where a wall keeps agents out.
The door is open — there is nothing to count.
Agent Outposts keeps a demand registry only where a wall keeps agents out. At Peet's Coffee, an agent goes straight in, so no intents are collected, no queue forms, and no demand count is published for this listing. If this door ever closes, this listing converts into a demand registry and the counting starts.
Five tasks, five door-states — this page is one of them.
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.