Walmart built real APIs — for affiliates and sellers. An agent shopping on a customer's behalf gets product data behind an approval gate, and no door at all for checkout or order tracking. 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 Walmart's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | PARTNER-GATED | The Walmart Affiliate API via Walmart I/O — Walmart says affiliates can access the full range of information and metadata about products on Walmart.com through custom API calls. Access requires becoming a Walmart Affiliate; it is not a self-serve consumer API. | Walmart I/O | 2026-11-01 |
| Prices | PARTNER-GATED | The Walmart Affiliate API — product and price data is exposed to approved affiliates. The Marketplace APIs on the same portal are seller-side price management, not a public consumer price API. | Walmart I/O | 2026-11-01 |
| Inventory | PARTNER-GATED | Partner-gated, and seller-flavored: walmart.io lists sellers managing items, orders, prices and inventory via Marketplace APIs — a seller's own stock. No consumer-facing availability API was found; consumer availability checks are Walmart.com and app only. | Walmart I/O | 2026-11-01 |
| Ordering | HUMAN-ONLY | Walmart.com and the Walmart app, human checkout. No consumer shopping or checkout API exists; Walmart I/O's Immersive Commerce is for approved partners integrating commerce into games and apps, and Marketplace order management is for sellers. | Walmart I/O | 2026-11-01 |
| Tracking | HUMAN-ONLY | Walmart.com and the Walmart app. The developer portal's order APIs are seller order-management; no consumer order-tracking API was found. | Walmart I/O | 2026-11-01 |
Agent-native surfaces at Walmart: official MCP server — none found; llms.txt — not verified (the census fetch was rate-limited; no inference drawn); API catalog (RFC 9727) — not verified. Automated access: not assessed — the census could not retrieve walmart.com's robots.txt on 2026-11-01 (robots.txt).
If you came to do something at Walmart 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 Walmart, 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 Walmart with a task — a product to price, a cart to build, an order to track — and found business APIs behind approval gates, and no consumer door at all for checkout. 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 Walmart'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 Walmart. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.