Amazon has no open door for agents. Catalog data sits behind a partner gate; ordering and tracking are human-only. This Outpost publishes the verified door-state and registers the demand that hits the wall.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Amazon's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | PARTNER-GATED | Amazon Creators API (Amazon Associates) — catalog search and item lookup. The gate: an enrolled Associates account for the target marketplace, plus at least 10 qualifying sales in the past 30 days. The Creators API is the stated successor to PA-API 5.0. | Creators API docs | 2026-11-01 |
| Prices | PARTNER-GATED | Amazon Creators API — returns offers and pricing for affiliate use, under the same Associates gate. No open, self-serve price API was found. | Creators API docs | 2026-11-01 |
| Inventory | PARTNER-GATED | Amazon Creators API — availability appears only as offer data inside item lookups, under the same gate. There is no standalone real-time inventory API for consumers; the seller-side SP-API covers a seller's own listings, not shopping. | Creators API docs | 2026-11-01 |
| Ordering | HUMAN-ONLY | Amazon.com web and app checkout. The Creators API contains no order placement — it links audiences to Amazon. No sanctioned consumer ordering API was found. | Creators API docs | 2026-11-01 |
| Tracking | HUMAN-ONLY | Amazon.com “Your Orders,” signed-in web and app. No consumer order-tracking operation exists in the Creators API. | Creators API docs | 2026-11-01 |
Agent-native surfaces at Amazon: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: Amazon's robots.txt disallows cart, sign-in, and availability paths, and its Conditions of Use prohibit data mining and the collection of listings and prices (robots.txt).
If you came to do something at Amazon 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 Amazon, 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 Amazon with a task — a price to check, an order to place, a delivery to track — and found no sanctioned way through. 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 Amazon'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.
Agent Outposts is not affiliated with Amazon. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.