# Instacart Developer Platform API + MCP vs MealMe API

> Instacart Developer Platform scores 48.5 (D) to MealMe's 38.4 (E) for commerce cart. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/instacart-vs-mealme
- Markdown: https://www.anchorterminal.com/compare/instacart-vs-mealme.md (~3,750 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-03

Instacart Developer Platform API + MCP scores 48.5 (D) on agent readiness against MealMe API's 38.4 (E), and leads in 6 of 7 scored categories. Both do commerce cart.

- Instacart Developer Platform API + MCP: grade D, 48.5/100, rank #1067 of 1349. Markdown https://www.anchorterminal.com/tools/instacart.md · JSON https://www.anchorterminal.com/api/v1/tools/instacart.json
- MealMe API: grade E, 38.4/100, rank #1231 of 1349. Markdown https://www.anchorterminal.com/tools/mealme.md · JSON https://www.anchorterminal.com/api/v1/tools/mealme.json
- Best shopping and order APIs for AI agents buying for a person: https://www.anchorterminal.com/best/shopping/index.md
- All 41 shopping comparisons: https://www.anchorterminal.com/compare/shopping/index.md
- Best recipe, nutrition and meal planning APIs for AI agents: https://www.anchorterminal.com/best/cooking/index.md
- All 28 cooking comparisons: https://www.anchorterminal.com/compare/cooking/index.md

## Which one, for what

### Instacart Developer Platform API + MCP (D)

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

Ahead on:
- Schema & documentation, 80 against 72
- Security & auth, 61 against 26
- Maintenance & community, 20 against 6
- Transparency & trust, 53 against 47

Also in its favour:
- A hosted endpoint, with nothing to install

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

### MealMe API (E)

Good for: Agents that must place a real restaurant or grocery order in the US or Canada, or compare live prices across stores, and can hold a card on the account.

Watch for: One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header


## Why the edge

### Security & auth: Instacart Developer Platform API + MCP +35

- Instacart Developer Platform API + MCP (61): 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 tools only create 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). docs.instacart.com has no security.txt, and the one on www.instacart.com could not be read because robots.txt disallows our crawler. No disclosure programme was confirmed (0 of 20). Total 61. The MCP server answered the MCP handshake and tools/list without a key. Tool calls were not tested.
- MealMe API (26): One API key per account in a custom Id-Token header, with no scopes, expiry, rotation or revocation documented (10 of 30). place_order defaults to false and charge_user can be turned off, so an agent can quote without buying, but there is no read-only key (8 of 20). Store descriptions, menus and support-chat messages are untrusted content with no guidance (3 of 15). Get Orders and a tracking webhook give order history; no per-call log for the operator is documented (5 of 15). No security.txt (400), disclosure policy, bug bounty or certification found; the Enterprise plan names a security review (0 of 20). Total 26.

### Maintenance & community: Instacart Developer Platform API + MCP +14

- Instacart Developer Platform API + MCP (20): The newest changelog entry is 18 June 2026, 118 days before this check (10 of 30). No entries in the last 90 days (0 of 20). A dated changelog, a developer support address and an Atlassian service desk (10 of 15). No Instacart server in the official MCP registry, which lists only a community server, and no official SDKs (0 of 15). No public package or repository to assess (0 of 10). Total 20.
- MealMe API (6): Read as a closed service. The newest dated change is the release note of 6 May 2025 (Get Inventory v4), more than 180 days before 3 November 2026; the pricing and dashboard pages carry no date (0 of 30). No dated change in the last 90 days (0 of 20). A support address, release notes and no community channel (6 of 15). No official SDKs (0). No package to judge (0). Total 6.

### Schema & documentation: Instacart Developer Platform API + MCP +8

- Instacart Developer Platform API + MCP (80): No public OpenAPI file was found for the Developer Platform API. Both MCP tools have typed JSON Schema inputs with required fields and additionalProperties false (20 of 25). llms.txt and a Markdown version of every page on docs.instacart.com (10 of 10). The REST reference explains each endpoint and its matching rules. The MCP descriptions are one line each and say nothing on when to use them (10 of 20). Required fields, minItems, enums for health filters and a 365-day cap on expires_in. MCP units are free text (11 of 15). Examples in curl, Java, Python and Go, and per-endpoint error tables with codes (14 of 15). Versioned paths (/idp/v1) and a dated changelog (15 of 15). Total 80.
- MealMe API (72): The reference pages are generated from an API description with operation ids (get_search_store_v3), named response schemas (Product_Search_Output) and typed parameters, but no spec file URL was found on the docs, llms.txt or the site (15 of 25). llms.txt at mealmeapi.readme.io and mealme.ai, and every page as Markdown (10). Each operation states its purpose and coverage; several descriptions are truncated in the index and none says when not to use it (12 of 20). Enums on sort, store_type, user_country and search_focus, required flags on latitude and longitude, conditional requirements written in prose (11 of 15). Request and response examples per endpoint, a Create Order errors page with 17 entries, and 400, 401 and 429 schemas on each operation (12 of 15). Versioned paths (v2 to v4) and dated release notes that call out breaking changes, the newest of 6 May 2025 (12 of 15). Total 72.

### Transparency & trust: Instacart Developer Platform API + MCP +6

- Instacart Developer Platform API + MCP (53): Closed service with dated developer terms that are clear on restrictions and termination (15 of 30). The terms set security and privacy obligations for the developer and refer to a privacy addendum. The privacy policy itself is on www.instacart.com and was not read (8 of 30). 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.
- MealMe API (47): Closed service. The API and SDK Terms of Use (18 June 2022) and MealMe Connect terms (4 April 2025) name MealMe, Inc. under Delaware law, but the API terms license use for personal, noncommercial purposes while the product is sold to businesses (15 of 30). The privacy policy of 1 January 2025 keeps data as long as needed, names no subprocessor and no DPA; the cookie policy names Google, Adobe, LinkedIn, Twitter and Facebook (10 of 30). Release notes record breaking changes with dates but there is no deprecation policy or notice period (6 of 20). Cookie providers named, no subprocessor list or data location (4 of 20). Total 35.

## Score by category

| Category | Weight | Instacart Developer Platform API + MCP | MealMe API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 22 | 19 | Instacart Developer Platform API + MCP +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 72 | Instacart Developer Platform API + MCP +8 |
| Agent ergonomics | 13% (16.2 this run) | 71 | 69 | Instacart Developer Platform API + MCP +2 |
| Security & auth | 14% (17.5 this run) | 61 | 26 | Instacart Developer Platform API + MCP +35 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 20 | 6 | Instacart Developer Platform API + MCP +14 |
| Transparency & trust | 7% (8.8 this run) | 53 | 47 | Instacart Developer Platform API + MCP +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **48.5 · D** | **38.4 · E** | |

## Facts side by side

| Fact | Instacart Developer Platform API + MCP | MealMe API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Maplebear Inc. (Instacart) | MealMe, Inc. |
| Hosted endpoint | `https://mcp.instacart.com/mcp` | no (local only) |
| Transports | HTTP |  |
| Auth | API key | API key |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under the Instacart Developer Platform Terms and Conditions | Proprietary service under the MealMe API and SDK Terms of Use |
| Tools exposed | 2 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-06-18 | 2025-05-06 |
| Terms last updated | couldn't be read | 2025-04-04 |
| Privacy policy last updated | couldn't be read | 2025-04-04 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |

## How the scores have moved

### Instacart Developer Platform API + MCP

- +0.2 on 27 October 2026: checklist

### MealMe API

No score change since it was listed.

## Verdicts

**Instacart Developer Platform API + MCP.** Two compact MCP tools and a small REST API with structured errors let an agent turn a list 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 that Instacart puts at 30 to 40 days. No status page or published rate figure was found.

**MealMe API.** An agent can search stores and products, fetch live quotes and place a real order through one REST API priced at $0.10 a successful call. One all-powerful key, no rate limit figures, no status page, no idempotency key on orders and release notes that stop at 6 May 2025 are the limits.

## Before you call either

### 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

### MealMe API

1. Send the key as the Id-Token header, not Authorization. Only latitude and longitude are required for store search; address fields become required when fetch_quotes is true and pickup is false
2. Call Create Order with place_order false first, read the 202 final quote, then place it; keep your own customer_order_id and look it up before any retry, since no idempotency key exists
3. Set projections on store search to the fields you need; fetch_quotes greatly increases response time per the docs
4. Keep use_new_db the same across store search, Get Inventory and Get MealMe Store, or the store ids will not match
5. Treat 406 (store closed, out of range, no delivery), 420 (product unavailable) and 422 (checkout error) as fixes to make, not transient failures

## Questions

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

Instacart Developer Platform API + MCP scores 48.5 (D) on agent readiness against MealMe API's 38.4 (E), and leads in 6 of 7 scored categories.

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

Both need an API key.

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

Instacart Developer Platform API + MCP has a hosted endpoint at https://mcp.instacart.com/mcp. No hosted endpoint is listed for MealMe API.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/instacart-vs-mealme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/instacart-vs-mealme.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "instacart", "b": "mealme"}`. From a terminal: `anchor compare instacart mealme`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/instacart.json and https://www.anchorterminal.com/api/v1/tools/mealme.json

## Other comparisons with Instacart Developer Platform API + MCP or MealMe API

- [Amazon Creators API vs MealMe API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme.md)
- [Best Buy Developer API vs MealMe API](https://www.anchorterminal.com/compare/best-buy-vs-mealme.md)
- [Etsy Open API v3 vs MealMe API](https://www.anchorterminal.com/compare/etsy-vs-mealme.md)
- [MealMe API vs opencommerce](https://www.anchorterminal.com/compare/mealme-vs-opencommerce.md)
- [MealMe API vs Shop MCP](https://www.anchorterminal.com/compare/mealme-vs-shop-mcp.md)
- [MealMe API vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.md)
- [MealMe API vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.md)
- [MealMe API vs Zillow in Claude](https://www.anchorterminal.com/compare/mealme-vs-zillow-claude.md)
- [Instacart Developer Platform API + MCP vs opencommerce](https://www.anchorterminal.com/compare/instacart-vs-opencommerce.md)
- [Instacart Developer Platform API + MCP vs Shop MCP](https://www.anchorterminal.com/compare/instacart-vs-shop-mcp.md)
- [Amazon Creators API vs Instacart Developer Platform API + MCP](https://www.anchorterminal.com/compare/amazon-creators-api-vs-instacart.md)
- [Instacart Developer Platform API + MCP vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/instacart-vs-walmart-affiliate-api.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp