Head to head · Placing and tracking orders · October 2026 research run

CartAI vs MealMe API

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.

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.

Ahead on

  • Security & auth, 43 against 26
  • Maintenance & community, 18 against 6

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

MealMe API E

Best 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 in its favour

  • No incidents deducted, where CartAI loses 3 points for them

Watch for

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

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.

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

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 sized (20 of 25). Page and next_page pagination, bounding-box, distance, rating, price, cuisine and open filters, maximum_miles defaults (18 of 20). Distinct status codes, 406 for a closed or out-of-range store, 420 for an unavailable product, 422 for checkout errors, each with a message naming the field or product (16 of 20). No idempotency key; the two-step order (202 quote, then place) and customer_order_id lookup are the safe-retry route (8 of 20). Only latitude and longitude required for search and sensible defaults, but no official SDK in any language, only an iframe embed (7 of 15). Total 69.

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

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.

Schema & documentation MealMe API +13

CartAI 59

A public OpenAPI 3.0 file at docs.cartai.ai/openapi/latest.yml with 13 operations. It declares no security scheme, and the key header is spelt X-Api-Key on some paths and x-api-key on others, which CartAI's own auth.md points out (20 of 25). llms.txt on both hosts and a Markdown twin of every docs page (10). Reference pages say when to use each call, such as a table of when to use webhooks or polling for a task, and the MCP tool descriptions say which call comes next (14 of 20). Required fields and patterns for phone and postal code, but only two enums in the spec, shippingMethod.strategy is a free string, and payment.data is typed as a string in one table while the examples send an object (7 of 15). Request and response examples on each page and a 401 body, but most operations document only 400, and a link to the task lifecycle section points to an anchor that is missing (8 of 15). No changelog and no API versioning beyond 1.0.0 in the spec (0). 20 + 10 + 14 + 7 + 8 + 0 = 59.

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.

Maintenance & community CartAI +12

CartAI 18

Closed service with no changelog. The newest dated release found is the MCP server's last commit on 20 July 2026, 123 days ago (10 of 30). Docs pages show updatedAt dates from 17 to 20 November 2026, but no dated change list, so no releases can be counted in the last 90 days (0 of 20). No public changelog. Support is through a contact page, info@cartai.ai and a portal request for more credits that the docs say is reviewed within one business day. Neither was tested (5 of 25). Not in the official MCP registry, not on npm, and no official SDKs (0 of 15). The MCP server pins @modelcontextprotocol/sdk ^1.0.0 and zod ^3.22.0 with a lockfile and no CI (3 of 10). The earliest first-hand date of a running API is a webhook example of 6 December 2025, and the MCP repository dates from 25 May 2026. 10 + 0 + 5 + 0 + 3 = 18.

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.

Score by category

CategoryWeightCartAIMealMe APIEdge
Reliability16%1819MealMe API +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5972MealMe API +13
Agent ergonomics13%4969MealMe API +20
Security & auth14%4326CartAI +17
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%186CartAI +12
Transparency & trust7%4547MealMe API +2
Negative events≤15-30
TotalF 34.9/100E 39.7/100

Facts side by side

FactCartAIMealMe API
KindHTTP APIHTTP API
VendorCartAIMealMe, Inc.
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicencenoneProprietary service under the MealMe API and SDK Terms of Use
Tools exposed80
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-202025-05-06
Terms last updated2026-05-132025-04-04
Privacy policy last updated2026-05-132025-04-04
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes

How the scores have moved

CartAI

No score change since it was listed.

MealMe API

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.

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

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

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, CartAI or MealMe API?

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.

Do CartAI and MealMe API need an API key?

Both need an API key.

Can an agent call CartAI and MealMe API without installing anything?

CartAI runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for MealMe API.

Other comparisons with CartAI or MealMe API

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.