Head to head · Affiliate product APIs · October 2026 research run

CartAI vs Instacart Developer Platform API + MCP

Instacart Developer Platform API + MCP scores 45.8 (E) on agent readiness against CartAI's 34.9 (F), and leads in 6 of 7 scored categories. Both do affiliate product apis.

Best shopping and order APIs for AI agents buying for a person · All 61 shopping comparisons

Best recipe, nutrition and meal planning APIs for AI agents · All 31 cooking comparisons

Which one, for what

CartAI F

Best for Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

No public prices. Production fees are basis points on order value, shown only in the dashboard

Instacart Developer Platform API + MCP E

Best for Grocery list and recipe hand-off for meal planning and recipe agents in the US and Canada.

Ahead on

  • Agent ergonomics, 61 against 49
  • Security & auth, 66 against 43
  • Transparency & trust, 53 against 45

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where CartAI loses 3 points for them

Watch for

No product search, price, order, order status or return endpoint. The person picks the store and checks out on Instacart

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Instacart Developer Platform API + MCP +23

CartAI 43

One API key per request in a header, revocable and regenerated in the portal, with no scopes or rotation guidance found (20 of 30). No read-only key. A checkout can wait for the customer's confirmation, and production payments run through hosted Visa Intelligent Commerce or Mastercard Agent Pay sessions the customer authorises. The MCP server places orders with no confirmation of its own (10 of 20). Product search and details return merchant page content with no prompt-injection guidance, and the create_payment_session tool description tells the model to present the payment link "without asking the user first" (3 of 15). Each task has a status history with timestamps and credits, a live preview URL and webhooks for every status (10 of 15). No security.txt (404), disclosure policy, bug bounty or certification found. The known limitations page says test-mode card data is not tokenised and could appear in logs (0 of 20). 20 + 10 + 3 + 10 + 0 = 43.

Instacart Developer Platform API + MCP 66

Per the 14 October check, not re-read on 4 November (the developer terms bar scraping the developer portal, so docs.instacart.com is paused). Revocable API keys with read-only, read-write and admin levels, separate development and production keys, and a documented rotation procedure (25 of 30). The API only creates pages. The person chooses the store and checks out on Instacart, so an agent cannot spend money (18 of 20). The API returns a link and retailer names, with no free text from third parties (10 of 15). The dashboard shows each key's creation, last use and usage statistics (8 of 15). On 4 November HackerOne's page for Instacart, as served, is titled "Instacart - Bug Bounty Program", so a public bounty programme exists; its policy and scope load by script and were not read, and www.instacart.com's security.txt is disallowed by robots.txt (0 to 5, scope unconfirmed, as voyage-ai). Total 66.

Agent ergonomics Instacart Developer Platform API + MCP +12

CartAI 49

The MCP server has 8 tools with compact descriptions, but each result appends the full JSON response, and the REST API has no field selection (22 of 25). Product search takes a query and an optional merchant to prioritise, with no limit, page or filter parameters found (6 of 20). A documented 401 body with an error code and message, 400 on every operation, and 403, 404 and 409 on interactive inputs. Error bodies for failed checkouts are not described beyond the FAILED status (10 of 20). No idempotency key on writes, and the docs say a resubmit creates a duplicate. A confirmation step (verifyBeforePlacement, PENDING_CONFIRMATION) and a cancel call exist, and the MCP tools carry no readOnlyHint or destructiveHint (6 of 20). A checkout needs a full customer object with contact, two addresses, shipping strategy and payment. No official SDK, and the MCP server runs from a clone, in Node.js only (5 of 15). 22 + 6 + 10 + 6 + 5 = 49.

Instacart Developer Platform API + MCP 61

Per the 14 October check, not re-read on 4 November (the developer terms bar scraping the developer portal, so docs.instacart.com is paused). The 14 October context-cost credit (two compact MCP tools) rested on the struck tools/list answer. Read as an API, two of the three endpoints return a single page URL and the retailer list takes only postal and country code filters, with no field selection or limit (25 to 15). Line items take brand and health filters (15 of 20). Errors carry an internal code and a meta key that names the failing field (18 of 20). No idempotency keys. Repeating a call creates another page, which costs nothing but a new link, and the docs advise caching links (5 of 20). Two required fields per call. No official SDKs (8 of 15). Total 61.

Transparency & trust Instacart Developer Platform API + MCP +8

CartAI 45

Closed service with published terms naming CartAI, LLC under Texas law, updated 13 May 2026, and an Apache 2.0 MCP server (15 of 30). The privacy policy (13 May 2026) describes card vaulting through a partner and says raw card numbers never reach CartAI systems, but the docs say test-mode card data is not tokenised and could appear in logs. Retention is "as long as necessary" with no periods, and no DPA was found (12 of 30). No API deprecation policy. The terms let CartAI change or discontinue parts of the Services without liability and promise notice only for material changes to the terms and to pricing (0 of 20). The privacy policy names Visa Intelligent Commerce and Mastercard AgentPay and other providers by kind, and the terms name Cloudflare, HUMAN and Fingerprint as bot-mitigation partners. Processing is in the US and other countries, with no subprocessor list (6 of 20). 15 + 12 + 0 + 6 = 33.

Instacart Developer Platform API + MCP 53

Closed service with dated developer terms (re-read on 4 November, still last updated 3 July 2024) that are clear on restrictions and termination (15 of 30). The terms set security and privacy obligations for the developer, refer to the privacy policy on www.instacart.com, which robots.txt keeps us from reading, and name a data processing addendum on Instacart's SafeBase trust portal, not read (8 of 30). Per the 14 October check, the 18 March 2026 deprecation of quantity and unit was announced with a replacement but no removal date, and the terms allow changes without notice (5 of 20). No subprocessor list or data locations were found for the Developer Platform (0 of 20). Total 28.

Score by category

CategoryWeightCartAIInstacart Developer Platform API + MCPEdge
Reliability16%1822Instacart Developer Platform API + MCP +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5960Instacart Developer Platform API + MCP +1
Agent ergonomics13%4961Instacart Developer Platform API + MCP +12
Security & auth14%4366Instacart Developer Platform API + MCP +23
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1820Instacart Developer Platform API + MCP +2
Transparency & trust7%4553Instacart Developer Platform API + MCP +8
Negative events≤15-30
TotalF 34.9/100E 45.8/100

Facts side by side

FactCartAIInstacart Developer Platform API + MCP
KindHTTP APIHTTP API
VendorCartAIMaplebear Inc. (Instacart)
Hosted endpointno (local only)https://mcp.instacart.com/mcp
TransportsstdioHTTP
AuthAPI keyAPI key
PricingFreemiumFree
x402nono
LicencenoneProprietary service under the Instacart Developer Platform Terms and Conditions
Tools exposed82
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-202026-06-18
Terms last updated2026-05-13couldn't be read
Privacy policy last updated2026-05-13couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read

How the scores have moved

Verdicts

CartAI

CartAI lets a platform buy from US merchants' own sites through one asynchronous API, with a public OpenAPI file, Markdown docs, webhooks and an optional customer confirmation step. There is no public price list, status page, rate limit or idempotency key, and the home page's retry-safe and Hosted Cart claims go further than the docs.

Instacart Developer Platform API + MCP

A small REST API and a hosted MCP server with structured errors turn a list or recipe into an Instacart cart link. The agent cannot search products, see prices, place an order or follow one, and production keys need a demo review Instacart puts at 30 to 40 days. No public status page or rate figure was found.

Before you call either

CartAI

  1. Never resend POST /checkout after a 201 or a timeout. Look up the task with GET /checkout/{taskId} first, because a resubmit creates a duplicate order
  2. Use only the test card 4242 4242 4242 4242 until the account is in production mode, since test mode does not tokenise card data
  3. Set verifyBeforePlacement and show derivedDetails.pricing to the customer at PENDING_CONFIRMATION before the order is placed
  4. Poll a task no more than once every 5 to 10 seconds when webhooks are unavailable
  5. Give selectedVariant labels as the merchant's page shows them, and use US merchants, addresses and phone numbers only

Instacart Developer Platform API + MCP

  1. Connect to https://mcp.instacart.com/mcp over Streamable HTTP with Authorization: Bearer and an Instacart Developer Platform key. Test against https://mcp.dev.instacart.tools/mcp with a development key
  2. Give the person the returned products_link_url to choose a store and check out. No call places or tracks an order
  3. Cache each generated link and create a new one only when the list changes, as the docs advise
  4. Send line_item_measurements rather than quantity and unit on the REST shopping list endpoint, since those fields are deprecated
  5. Do not show priced items from more than one retailer on one screen or move items between retailer baskets. The developer terms forbid both

Questions

Which is better for AI agents, CartAI or Instacart Developer Platform API + MCP?

Instacart Developer Platform API + MCP scores 45.8 (E) on agent readiness against CartAI's 34.9 (F), and leads in 6 of 7 scored categories.

Do CartAI and Instacart Developer Platform API + MCP need an API key?

Both need an API key.

Can an agent call CartAI and Instacart Developer Platform API + MCP without installing anything?

CartAI runs on your own machine, with no hosted endpoint listed. Instacart Developer Platform API + MCP has a hosted endpoint at https://mcp.instacart.com/mcp.

Other comparisons with CartAI or Instacart Developer Platform API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.