Grubhub documents a full diner API — menus, availability, carts, checkout and delivery tracking — but it is a partner-integration program for point-of-sale and online-ordering providers, with credentials flowing through partner onboarding. There is no self-serve consumer agent door and no agent-native surface.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Grubhub's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | PARTNER-GATED | Grubhub diner/Partner APIs (documented at Grubhub Developers, Zendesk) — restaurants endpoint — Docs show GET /restaurants returning menus, but the developer portal frames access as partner integration (POS / online-ordering providers); no self-serve consumer signup found. Docs also state Grubhub provides no restaurant search — partners use a provided data feed. | Source — grubhub-developers.zendesk.com | 2026-11-01 |
| Prices | PARTNER-GATED | Grubhub diner API — menu item prices and cart bill token (partner access) — Menu payloads include item prices, delivery fees, minimums and tax, and checkout uses a bill token — all inside the partner-gated API, not an open consumer API. | Source — grubhub-developers.zendesk.com | 2026-11-01 |
| Inventory | PARTNER-GATED | Grubhub diner API — GET /restaurants/availability_summaries (partner access) — Availability summaries report open / available_for_delivery / available_for_pickup for up to 30 restaurant IDs per call, for API partners only. | Source — grubhub-developers.zendesk.com | 2026-11-01 |
| Ordering | PARTNER-GATED | Grubhub diner API — carts and checkout (partner access) — Homepage frames the offer as 'Grubhub's Partner Integration API enables a merchant's Point-of-sale, third-party online-ordering provider, or the merchant themselves' to manage menus and orders. Diner cart/checkout endpoints exist in docs but credentials flow through partner onboarding, not self-serve signup. | Source — grubhub-developers.zendesk.com | 2026-11-01 |
| Tracking | PARTNER-GATED | Grubhub API — orders order-status and Deliveries endpoints (partner access) — Delivery API 'lets you track the location of a courier' with status, driver assignment and ~60s location updates — documented for partners, no open consumer access found. | Source — grubhub-developers.zendesk.com | 2026-11-01 |
Agent-native surfaces at Grubhub: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: robots.txt disallows /search, /checkout/, /account/, /oauth2/, /my-bag and restaurant menu-item/choice paths for all agents; llms.txt and /.well-known/api-catalog returned HTML (SPA fallback), not machine-readable agent files, on 2026-11-01. (evidence).
One page per task an agent might attempt at Grubhub — the door-state for that task alone, and what fits instead.
| Task | State | The page |
|---|---|---|
| Menu / browse | PARTNER-GATED | Can an AI agent browse restaurants on Grubhub? |
| Prices | PARTNER-GATED | Can an AI agent check prices on Grubhub? |
| Inventory | PARTNER-GATED | Can an AI agent check availability on Grubhub? |
| Ordering | PARTNER-GATED | Can an AI agent order through Grubhub? |
| Tracking | PARTNER-GATED | Can an AI agent track a Grubhub order? |
If you came to do something at Grubhub 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 Grubhub, 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 Grubhub 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 Grubhub'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 Grubhub 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 Grubhub. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.