Short answer: only through the partner gate — Papa John's 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 Papa John's Outpost · Task · Ordering · Door-state verified November 1, 2026
Papa John's · Ordering · Agent Readiness Census, November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Ordering | PARTNER-GATED | Papa John's Commerce Platform for integration partners; otherwise DoorDash | Source — www.papajohns.com | 2026-11-01 |
Official ordering page describes human flow: papajohns.com/app, sign in/guest, address/carryout, pay, then PapaTrack. Partner API integrations to third-party delivery providers are documented by Kong; consumers/agents without partnership must use human site or DoorDash.
Door-state version census-2026-11-01. The same document is served as JSON by the API: api.agentoutposts.com/outposts/papajohns — and published in full on the Papa John's Outpost page.
Legal alternatives for this task, from the Options Registry.
Nothing fits today. No other business in the Pizza category has an open or partner-gated door for ordering in the census, so there is no sanctioned alternative to offer. That is exactly the case the registry below exists for: register the intent, take the receipt, and the demand is logged where the Papa John's team can see it in aggregate.
If you came to order from Papa John's 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 Papa John's, 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 = "papajohns", 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 Papa John's, 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 Papa John's. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.