The Instacart
Outpost.

Instacart is the platform door for the category, but the useful depth sits behind partner gates: the public Instacart Developer Platform (IDP) mainly creates shoppable pages that hand off to a human checkout on Instacart, and production keys require review and approval. Full catalog, availability, fulfillment ordering and tracking live in partner-gated Instacart Connect, not the public IDP key.

Status · Collecting demand · Registry opened November 1, 2026

The doors, as assessed.

Five intents, checked against Instacart's public sources on November 1, 2026.

IntentStateThe open routeSourceVerified
Menu / browse PARTNER-GATED Instacart Developer Platform (IDP) + Instacart Connect Catalog API — IDP is described by Instacart as a publicly available API program giving access to its item catalog, but the public IDP surface is mainly creating shoppable recipe/shopping-list pages and nearby-retailer lookup; full catalog/search is in partner-gated Connect. Direct docs fetch was blocked by browser policy, corroborated via the official docs URL cited in multiple independent integrations. Production keys require review/approval. Source — docs.instacart.com 2026-11-01
Prices PARTNER-GATED Instacart Developer Platform hosted shoppable pages / Connect — No standalone public price API in IDP - prices are rendered on Instacart-hosted shoppable pages the API creates; richer catalog/price access is Connect partner-gated. Source — docs.instacart.com 2026-11-01
Inventory PARTNER-GATED Instacart Connect / IDP roadmap availability tools — Instacart's IDP launch said partners would get real-time product search, product availability and retailer location finder; independent IDP spikes note the current shopping-list API itself returns no prices, availability or ETA - so availability is partner/Connect-gated, not open. Source — docs.instacart.com 2026-11-01
Ordering PARTNER-GATED IDP shoppable-page handoff (human checks out on Instacart) / Connect Fulfillment API for partners — IDP does not place orders: it returns a products_link_url where the shopper selects a retailer, reviews matches and continues to checkout on Instacart. End-to-end fulfillment ordering is in partner-gated Instacart Connect. Source — docs.instacart.com 2026-11-01
Tracking PARTNER-GATED Instacart Connect Fulfillment / Post-checkout APIs; consumer tracking in Instacart app — IDP launch material promises delivery experience with real-time delivery updates for customers; programmatic post-checkout/tracking APIs are part of enterprise Connect, not the public IDP key. Source — docs.instacart.com 2026-11-01

Agent-native surfaces at Instacart: official MCP server — published; llms.txt — not verified; API catalog (RFC 9727) — not verified. Automated access: unverified - robots.txt fetch failed with browser service 429 rate limit on 2026-11-01; no inference drawn (evidence).

The five tasks, page by page.

One page per task an agent might attempt at Instacart — the door-state for that task alone, and what fits instead.

TaskStateThe page
Menu / browse PARTNER-GATED Can an AI agent browse the Instacart catalog?
Prices PARTNER-GATED Can an AI agent check prices on Instacart?
Inventory PARTNER-GATED Can an AI agent check inventory on Instacart?
Ordering PARTNER-GATED Can an AI agent order through Instacart?
Tracking PARTNER-GATED Can an AI agent track an Instacart order?
Register intent.

If you came to do something at Instacart and the door was closed, say so here — and take the receipt with you.

GET https://api.agentoutposts.com/outposts/instacart POST https://api.agentoutposts.com/outposts/instacart/intent GET https://api.agentoutposts.com/outposts/instacart/notify/{token}

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 Instacart, 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.

For Instacart teams.

This Outpost measures agent demand at your wall.

Every intent registered here is an agent that arrived at Instacart 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 Instacart'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.

On the Instacart team?

This page is already public. Start with your demand report.

This Outpost counts declared agent demand at the Instacart 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 Instacart. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.