Burger King publishes no public API, and its internal BK Gateway is restricted to Burger King, franchisees and authorized providers. Consumers and agents can reach menu, prices and ordering only through the human BK app or through DoorDash, Uber Eats and Grubhub listings.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Burger King's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — No RBI/Burger King public developer portal/API found in search; BK Gateway is restricted to BKC/franchisees/authorized providers. Aggregator presence corroborated by Burger King-certified location listings stating delivery via BK app, Uber Eats, DoorDash, Grubhub. | Source — bkgateway.whopper.com | 2026-11-01 |
| Prices | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Prices shown human-only on bk.com/app and aggregator menus; no price API. Official US terms page not surfaced, so direct-door absence is based on developer-portal + agent-native checks. | Source — bkgateway.whopper.com | 2026-11-01 |
| Inventory | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Only store/item availability proxy on bk.com/app and aggregator listings; no inventory API found. | Source — bkgateway.whopper.com | 2026-11-01 |
| Ordering | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Ordering is via BK app/bk.com (human) or aggregators; franchisee/authorized-only gateway is partner_gated for internal use but is not a consumer ordering door, hence aggregator_only for this intent. | Source — bkgateway.whopper.com | 2026-11-01 |
| Tracking | AGGREGATOR ONLY | DoorDash / Uber Eats / Grubhub — Order tracking follows the channel used (BK app or aggregator app); no tracking API found. | Source — bkgateway.whopper.com | 2026-11-01 |
Agent-native surfaces at Burger King: official MCP server — none found; llms.txt — not verified; API catalog (RFC 9727) — not verified. Automated access: Bot-walled: bk.com fetches alternated between Incapsula block (403) and SPA fallback; BK Gateway is password-protected/authorized-users only; no public automation/API terms found (evidence).
One page per task an agent might attempt at Burger King — the door-state for that task alone, and what fits instead.
| Task | State | The page |
|---|---|---|
| Menu / browse | AGGREGATOR ONLY | Can an AI agent browse the Burger King menu? |
| Prices | AGGREGATOR ONLY | Can an AI agent check prices at Burger King? |
| Inventory | AGGREGATOR ONLY | Can an AI agent check availability at Burger King? |
| Ordering | AGGREGATOR ONLY | Can an AI agent order from Burger King? |
| Tracking | AGGREGATOR ONLY | Can an AI agent track a Burger King order? |
If you came to do something at Burger King 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 Burger King, 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 Burger King with a task — something to browse, a price to check, an order to place, a delivery to follow — and could not complete it through a sanctioned agent door. 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 Burger King'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.
This page is already public. Start with your demand report.
This Outpost counts declared agent demand at the Burger King wall — by intent, in aggregate, never resold as raw data. Your demand report pairs this door-state dossier with that demand shape as it accrues. How claiming works · Talk to us about your Outpost
Agent Outposts is not affiliated with Burger King. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.