The largest restaurant company on earth serves agents only through other companies' apps. McDonald's publishes no public API; its own McDelivery FAQ points to DoorDash, Uber Eats and Grubhub. 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 McDonald's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — the official McDelivery FAQ says menu and availability are viewed in the McDonald's app or on those platforms. No public developer portal or API was found. | McDelivery FAQ | 2026-11-01 |
| Prices | AGGREGATOR ONLY | The aggregator apps — the FAQ notes the delivery prices and fees shown there, which may be higher than in the restaurant. No price API exists. | McDelivery FAQ | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | The app and the aggregators are the only availability proxy: the FAQ says menu items vary by location, and availability is checked there. No inventory API exists. | McDelivery FAQ | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | McDelivery in the McDonald's app — fulfilled by Uber Eats or DoorDash — or directly on DoorDash, Uber Eats and Grubhub. No self-serve ordering API exists. | McDelivery FAQ | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | Track Order in the McDonald's app, or tracking on the aggregator platform where the order was placed, per the FAQ. No tracking API exists. | McDelivery FAQ | 2026-11-01 |
Agent-native surfaces at McDonald's: official MCP server — none found; llms.txt — not verified (the census fetch returned 403, so presence is unconfirmed); API catalog (RFC 9727) — not verified (403). Automated access: McDonald's terms prohibit unauthorized automated systems, spiders, robots and screen scrapers; its robots.txt answers with limited disallows (terms and conditions).
If you came to do something at McDonald's 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 McDonald's, 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 McDonald's with a task — a menu to read, an order to place, a delivery to track — and found that the only routes run through aggregator marketplaces. 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 McDonald's'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 McDonald's. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.