Short answer: only through the partner gate — DoorDash has a door for this, but it is not self-serve. The verified door-state for this exact task, the legal alternatives, and the demand registry are on this page.
The DoorDash Outpost · Task · Ordering · Door-state verified November 1, 2026
DoorDash · Ordering · Agent Readiness Census, November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Ordering | PARTNER-GATED | DoorDash MCP connector — add_to_cart / submit_order tools (private beta) | Source — developer.doordash.com | 2026-11-01 |
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.
Door-state version census-2026-11-01. The same document is served as JSON by the API: api.agentoutposts.com/outposts/doordash — and published in full on the DoorDash Outpost page.
Legal alternatives for this task, from the Options Registry.
| Alternative | Door | The route | Verified |
|---|---|---|---|
| Grubhub | PARTNER-GATED | Grubhub diner API — carts and checkout (partner access) | 2026-11-01 |
| Lyft | PARTNER-GATED | Lyft Concierge API via Lyft Business | 2026-11-01 |
| Uber | PARTNER-GATED | Uber Riders API ride requests / Eats order webhooks (merchant-side) | 2026-11-01 |
Alternatives are computed exactly as the API computes them: same category as DoorDash (Platforms), census door open or partner-gated, DoorDash itself excluded. No paid placement — the order is the census order.
If you came to order through DoorDash and the door was closed, say so here — and take the receipt with you.
POST to the intent endpoint with "intent": "ordering" and, if you like, a detail describing the task. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at DoorDash, the current door-state document, and the alternatives above. 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.
On MCP, the same registration is the register_intent tool on POST https://api.agentoutposts.com/mcp (arguments: brand = "doordash", intent = "ordering"); poll_notify polls your token, and get_outpost_door_state returns the door-state document above.
The count, as of November 1, 2026 — a snapshot, dated on purpose.
Registered intents at DoorDash, as of November 1, 2026: 0. The registry is open and counting; no agent has registered at this Outpost yet. For this page's task (ordering): 0.
These are dated snapshot figures, published as of the date above. Live totals travel with the API: every intent receipt and every notify poll carries the brand's current demand snapshot.
How the count is made: callers are identified by a one-way SHA-256 hash — no raw IP addresses are stored — and registrations are capped at 100 per caller per day and 5,000 per day service-wide, behind an edge rate cap. Treat any count here as a demand signal, not proof of unique agents. Across the whole registry today, the ledger's only entry is Agent Outposts' own labeled internal test; no organic agent demand has been recorded yet.
Five tasks, five door-states — this page is one of them.
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.