Starbucks has no door of its own for agents — no developer portal, no self-serve API — yet its own delivery FAQ quietly routes the menu through three aggregators. This Outpost publishes the verified door-state and registers the demand that hits the wall.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Starbucks' public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash, Grubhub and Uber Eats — Starbucks' official delivery FAQ names all three as its delivery channels, and their listings carry the menu. The full menu is otherwise human web and app only at starbucks.com/menu; no self-serve developer portal was found. Third-party catalogs index partner menu and loyalty APIs, but no official self-serve signup or partner portal was verified, so the census does not score them as a door. | Starbucks delivery FAQ | 2026-11-01 |
| Prices | AGGREGATOR ONLY | DoorDash, Grubhub and Uber Eats, or the Starbucks app. The FAQ notes delivery prices may be higher than posted in coffeehouses, and lists DoorDash service and delivery fees. No direct price API was found. | Starbucks delivery FAQ | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | Availability is checked by entering a delivery address in the Starbucks app or on an aggregator, per the official FAQ. No direct store or item inventory API was found; aggregator listings are the only availability signal. | Starbucks delivery FAQ | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | DoorDash, Grubhub and Uber Eats, or the Starbucks app and website — whose delivery orders are themselves fulfilled by DoorDash. First-party ordering is human app and web only, with no agent API. | Starbucks delivery FAQ | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | DoorDash. For orders placed on starbucks.com or in the app, a delivery tracker link is sent to the email address and text-enabled phone number provided at checkout, and a DoorDash courier delivers. There is no Starbucks tracking API. | Starbucks delivery FAQ | 2026-11-01 |
Agent-native surfaces at Starbucks: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: Starbucks' robots.txt is permissive for ordinary crawlers — an empty Disallow for user-agent * (only MJ12bot gets a crawl delay) — with no AI-bot or automation block seen (robots.txt).
If you came to do something at Starbucks and the door was closed, say so here — and take the receipt with you.
POST your intent — what you were trying to do, and for which of the five intents — to the intent endpoint. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at Starbucks, the current door-state document, and any alternatives the Options Registry can offer — another business whose door is open for the same need. If nothing fits, the answer is demand logged: your intent joins the aggregate count. The receipt also carries a notify token: poll the notify endpoint and you will learn when this door-state changes — a new API, a changed gate, a converted Outpost.
This Outpost measures agent demand at your wall.
Every intent registered here is an agent that arrived at Starbucks with a task — a drink to order, a price to check, a delivery to follow — and found that every sanctioned route runs through someone else's marketplace. That demand is currently invisible to you: blocked attempts never become sessions. The registry counts it, categorizes it by intent, and timestamps it, so the size of the agent channel you are not serving is a number rather than a guess.
Converting this Outpost into Starbucks's official agent gateway — a real door for agents, operated by Agent Outposts under your terms — is a conversation with Agent Outposts. Palo Alto, California.
Agent Outposts is not affiliated with Starbucks. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.