# CartAI vs MealMe API (slim)

> MealMe scores 39.7 (E) to CartAI's 34.9 (F) for placing and tracking orders. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cartai-vs-mealme.md (~4,100 tokens) · this version ~880 tokens · JSON https://www.anchorterminal.com/compare/cartai-vs-mealme.json · canonical https://www.anchorterminal.com/compare/cartai-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-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MealMe API scores 39.7 (E) on agent readiness against CartAI's 34.9 (F), and leads in 4 of 7 scored categories. CartAI leads on security & auth and maintenance & community. Both do placing and tracking orders.

- CartAI: F 34.9, rank #1438 of 1563 · https://www.anchorterminal.com/tools/cartai.min.md
- MealMe API: E 39.7, rank #1390 of 1563 · https://www.anchorterminal.com/tools/mealme.min.md
- CartAI, good for Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations. Ahead on Security & auth, 43 against 26; Maintenance & community, 18 against 6. Also Runs on your own machine; Free to start without a card.
- 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. Ahead on Schema & documentation, 72 against 59; Agent ergonomics, 69 against 49. Also No incidents deducted, where CartAI loses 3 points for them.

| Category | CartAI | MealMe API |
| --- | --- | --- |
| Reliability (16%) | 18 | 19 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 59 | 72 |
| Agent ergonomics (13%) | 49 | 69 |
| Security & auth (14%) | 43 | 26 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 18 | 6 |
| Transparency & trust (7%) | 45 | 47 |

| Fact (where they differ) | CartAI | MealMe API |
| --- | --- | --- |
| Vendor | CartAI | MealMe, Inc. |
| Transports | stdio |  |
| Pricing | Freemium | Pay per use |
| Licence | none | Proprietary service under the MealMe API and SDK Terms of Use |
| Tools exposed | 8 | 0 |
| Last release | 2026-07-20 | 2025-05-06 |
| Terms last updated | 2026-05-13 | 2025-04-04 |
| Privacy policy last updated | 2026-05-13 | 2025-04-04 |
| Terms or service can change without notice | not found in the text | yes |

Why the edge:
- Agent ergonomics, MealMe API +20: 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).); MealMe API 69 (Store search takes a projections list to choose response fields and a fetch_quotes switch that the docs say greatly increases response time, so responses can be…)
- Security & auth, CartAI +17: 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).); 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).)
- Schema & documentation, MealMe API +13: CartAI 59 (A public OpenAPI 3.0 file at docs.cartai.ai/openapi/latest.yml with 13 operations.); 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 par…)
- Maintenance & community, CartAI +12: CartAI 18 (Closed service with no changelog.); MealMe API 6 (Read as a closed service.)
