# Instacart Developer Platform API + MCP vs MealMe API (slim)

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

- Full: https://www.anchorterminal.com/compare/instacart-vs-mealme.md (~3,750 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/compare/instacart-vs-mealme.json · canonical https://www.anchorterminal.com/compare/instacart-vs-mealme
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: D 48.5, rank #1067 of 1349 · https://www.anchorterminal.com/tools/instacart.min.md
- MealMe API: E 38.4, rank #1231 of 1349 · https://www.anchorterminal.com/tools/mealme.min.md
- Instacart Developer Platform API + MCP, 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 A hosted endpoint, with nothing to install.
- MealMe API, 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.

| Category | Instacart Developer Platform API + MCP | MealMe API |
| --- | --- | --- |
| Reliability (16%) | 22 | 19 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 72 |
| Agent ergonomics (13%) | 71 | 69 |
| Security & auth (14%) | 61 | 26 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 20 | 6 |
| Transparency & trust (7%) | 53 | 47 |

| Fact (where they differ) | Instacart Developer Platform API + MCP | MealMe API |
| --- | --- | --- |
| Vendor | Maplebear Inc. (Instacart) | MealMe, Inc. |
| Hosted endpoint | `https://mcp.instacart.com/mcp` | no (local only) |
| Transports | HTTP |  |
| Pricing | Free | Pay per use |
| 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 |
| 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 |

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.)