DoorDash is the category's agent leader — an official MCP connector covers search, menus, pricing, ordering and tracking — but it is private-beta and waitlist gated to approved testers and companies. The Drive and Marketplace APIs remain merchant-only and production-restricted, so there is no open consumer door yet.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against DoorDash's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | PARTNER-GATED | DoorDash MCP connector (official, private beta) — find_restaurants / get_restaurant_menu tools — Official MCP docs: 'DoorDash MCP is in private beta. Access is currently limited to approved testers' via waitlist. This is the first genuine consumer-side agent door in this category, but it is not open/self-serve yet. Drive and Marketplace APIs are merchant/delivery-facing, not consumer menu browsing. | Source — developer.doordash.com | 2026-11-01 |
| Prices | PARTNER-GATED | DoorDash MCP connector — preview_order tool — MCP get-started guide shows preview_order 'to see pricing and totals' as part of the private-beta tool set; access requires approval and OAuth provisioning. | Source — developer.doordash.com | 2026-11-01 |
| Inventory | PARTNER-GATED | DoorDash MCP connector (restaurant/item search) / Drive API quotes (merchant delivery) — Official announcement: connector lets agents 'find items on DoorDash, build a cart, place an order, and track its arrival', starting with a limited beta at company level. No open consumer availability API; Drive API is for businesses requesting Dasher delivery of their own orders. | Source — about.doordash.com | 2026-11-01 |
| Ordering | PARTNER-GATED | DoorDash MCP connector — add_to_cart / submit_order tools (private beta) — submit_order charges the consumer's real payment method per official docs, but only for approved beta testers/companies on the waitlist. Drive API ordering is merchant-side delivery creation, and its production access is separately restricted per the Drive overview page. | Source — developer.doordash.com | 2026-11-01 |
| Tracking | PARTNER-GATED | DoorDash MCP connector (order tracking) / Drive API delivery status (merchant) — Tracking is included in the MCP connector's stated capabilities for beta companies; Drive API status endpoints serve the business that created the delivery, not a consumer agent. | Source — about.doordash.com | 2026-11-01 |
Agent-native surfaces at DoorDash: official MCP server — published; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: robots.txt disallows /orders/, /orders/track/*, /order_history/, /consumer/ and /dasher paths for all agents; llms.txt and /.well-known/api-catalog returned 404 on 2026-11-01. Sanctioned agent path is the gated MCP, not crawling. (evidence).
One page per task an agent might attempt at DoorDash — 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 DoorDash? |
| Prices | PARTNER-GATED | Can an AI agent check prices on DoorDash? |
| Inventory | PARTNER-GATED | Can an AI agent check availability on DoorDash? |
| Ordering | PARTNER-GATED | Can an AI agent order through DoorDash? |
| Tracking | PARTNER-GATED | Can an AI agent track a DoorDash order? |
If you came to do something at DoorDash 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 DoorDash, 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 DoorDash 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 DoorDash'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 DoorDash 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 DoorDash. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.