{
  "data": {
    "a": {
      "slug": "cartai",
      "name": "CartAI",
      "vendor": "CartAI",
      "vendorUrl": "https://www.cartai.ai",
      "company": "cartai.ai",
      "kind": "http-api",
      "category": "shopping",
      "summary": "CartAI is a REST API from CartAI, LLC that places orders on US merchants' own websites for a platform's customers. An AI agent runs each checkout in the background, with product search, cost estimates, hosted card sessions and webhooks.",
      "url": "https://www.anchorterminal.com/tools/cartai",
      "markdownUrl": "https://www.anchorterminal.com/tools/cartai.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cartai.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/cartai.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cartai.json",
      "dns": "cartai.grade.anchorterminal.com",
      "repo": "https://github.com/TheCartAI/cartai-mcp-server",
      "transports": [
        "stdio"
      ],
      "packages": [],
      "auth": "api-key",
      "authNotes": "One API key in the `X-API-Key` header, generated in the portal at portal.cartai.ai after a browser signup with name, email and password. Keys can be revoked and regenerated in the portal. No scopes or expiry found. Production card handling (tokenisation and Visa Intelligent Commerce flows) needs a Request Go Live review by CartAI staff. Some reference pages still say to contact the account management team for access.",
      "pricing": "freemium",
      "pricingNotes": "No public price list. Every new account gets 5 free credits, which llms.txt says is enough for 500 Catalog API calls and the known limitations page says covers at least 10 test checkouts. Credits are consumed per agent step. Production fees are basis points on order value (GMV) and other usage metrics, shown in the account dashboard or agreed separately, per the terms of 13 May 2026. Signup asks for no card.",
      "priceSummary": "Freemium",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs, OpenAPI file, llms.txt, agents files or terms (checked 2026-11-20). Visa Intelligent Commerce and Mastercard Agent Pay sessions pay the merchant for the customer's order and are not a way to pay CartAI.",
        "endpoints": []
      },
      "toolCount": 8,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-20"
      },
      "docsUrl": "https://docs.cartai.ai/reference/",
      "llmsTxt": "https://docs.cartai.ai/llms.txt",
      "openapi": "https://docs.cartai.ai/openapi/latest.yml",
      "capabilities": [
        "shopping.orders",
        "shopping.search",
        "shopping.prices",
        "shopping.affiliate",
        "commerce.checkout"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "freemium",
        "free-tier",
        "no-card",
        "mcp",
        "stdio",
        "llms-txt",
        "openapi",
        "webhooks",
        "browser-agent",
        "us-only",
        "new"
      ],
      "lastRelease": "2026-07-20",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 34.9,
        "grade": "F",
        "agentReady": false,
        "rank": 1438,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 49,
          "maintenance": 18,
          "payments": 30,
          "reliability": 18,
          "schema": 59,
          "security": 43,
          "transparency": 45
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-20"
        },
        "negative": -3,
        "negativeNotes": [
          "2026-11-20: a misleading claim on the vendor's own home page (-3). It says the API is \"Idempotent, retry-safe by design\" and shows a Hosted Cart as one of three ways to integrate, while the Create Checkout Task reference says a resubmitted payload creates a duplicate checkout and llms.txt says the Hosted Cart is coming soon and not generally available. Sources: https://www.cartai.ai/, https://docs.cartai.ai/reference/create-checkout-task.md, https://www.cartai.ai/llms.txt"
        ],
        "verdict": "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.",
        "bestFor": "Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.",
        "strengths": [
          "Public OpenAPI 3.0 file with 13 operations, llms.txt on both hosts and a Markdown twin of each docs page",
          "Webhooks for every checkout status, plus a status history per task with timestamps and credits consumed",
          "A confirmation flow (`PENDING_CONFIRMATION`) lets the customer see merchant pricing before the order is placed",
          "Production payments go through hosted Visa Intelligent Commerce or Mastercard Agent Pay sessions the customer authorises",
          "Operator named in the terms as CartAI, LLC, a Texas company with a Plano address, and founders named on the about page"
        ],
        "weaknesses": [
          "No public prices. Production fees are basis points on order value, shown only in the dashboard",
          "No status page, SLA, numeric rate limits, security.txt, disclosure policy or certification found",
          "No idempotency key on `POST /checkout`, and the docs say a resubmitted payload creates a duplicate order",
          "Test mode sends raw card numbers that the docs say are not tokenised and could appear in logs",
          "No changelog or API versioning, and the MCP server is not packaged or in the official registry"
        ],
        "agentNotes": [
          "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",
          "Use only the test card 4242 4242 4242 4242 until the account is in production mode, since test mode does not tokenise card data",
          "Set `verifyBeforePlacement` and show `derivedDetails.pricing` to the customer at `PENDING_CONFIRMATION` before the order is placed",
          "Poll a task no more than once every 5 to 10 seconds when webhooks are unavailable",
          "Give `selectedVariant` labels as the merchant's page shows them, and use US merchants, addresses and phone numbers only"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 34.9
          }
        ],
        "editorialScores": {
          "ergonomics": 49,
          "maintenance": 18,
          "payments": 30,
          "reliability": 18,
          "schema": 59,
          "security": 43,
          "transparency": 33
        },
        "provenanceScore": 57,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-20",
            "maintenance": "2026-11-20",
            "payments": "2026-11-20",
            "reliability": "2026-11-20",
            "schema": "2026-11-20",
            "security": "2026-11-20",
            "transparency": "2026-11-20"
          },
          "last": "2026-11-20",
          "oldest": "2026-11-20",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "git clone https://github.com/TheCartAI/cartai-mcp-server \u0026\u0026 cd cartai-mcp-server \u0026\u0026 npm install",
        "http": "curl -X POST https://api.cartai.ai/product/search -H \"X-API-Key: $CARTAI_API_KEY\" -H \"Content-Type: application/json\" -d '{\"name\": \"white linen shirt\"}'",
        "claudeCode": "claude mcp add cartai -e CARTAI_API_KEY=YOUR_CARTAI_API_KEY -- node /absolute/path/to/cartai-mcp-server/src/index.js",
        "config": {
          "mcpServers": {
            "cartai": {
              "args": [
                "/absolute/path/to/cartai-mcp-server/src/index.js"
              ],
              "command": "node",
              "env": {
                "CARTAI_API_KEY": "YOUR_CARTAI_API_KEY"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/shopping.orders",
        "tool": "https://letme.dev/cartai"
      },
      "area": "everyday",
      "provenance": {
        "legalEntity": "CartAI, LLC",
        "domain": "cartai.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.cartai.ai/terms",
        "privacy": "https://www.cartai.ai/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-20",
        "notes": [
          "The terms name CartAI, LLC, a Texas limited liability company, at 6009 W Parker Rd, #149-380, Plano, TX 75093, with Texas law and JAMS arbitration. Terms and privacy policy were both last updated on 13 May 2026.",
          "The terms forbid scraping, crawling or harvesting data from the Services except through authorised APIs. Recorded as a fact, with no deduction.",
          "cartai.ai/robots.txt allows all agents with `Content-Signal: search=yes, ai-input=yes`. docs.cartai.ai/robots.txt allows all apart from edit, login and `api-next` paths, with `Content-Signal: ai-train=yes, search=yes, ai-input=yes`.",
          "www.cartai.ai/.well-known/security.txt returned 404. No status page or changelog was linked from any page read.",
          "RDAP for cartai.ai was not read, so the domain's registration date is not recorded."
        ],
        "score": 57
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/cartai.json",
      "live": {
        "slug": "cartai",
        "githubStars": 1,
        "securityTxt": {
          "url": "https://cartai.ai/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:35:46.934117008Z"
        },
        "llmsTxt": {
          "url": "https://docs.cartai.ai/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-20T16:21:47.394304634Z"
        },
        "updatedAt": "2026-11-20T20:18:47.995341714Z"
      }
    },
    "answer": "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 \u0026 auth and maintenance \u0026 community.",
    "b": {
      "slug": "mealme",
      "name": "MealMe API",
      "vendor": "MealMe, Inc.",
      "vendorUrl": "https://www.mealme.ai/",
      "company": "mealme.ai",
      "kind": "http-api",
      "category": "shopping",
      "summary": "MealMe is a REST API from MealMe, Inc. that searches restaurants, grocery stores and products across the US and Canada, returns menus and inventory with live quotes, and places pickup or delivery orders with tracking and support chat.",
      "url": "https://www.anchorterminal.com/tools/mealme",
      "markdownUrl": "https://www.anchorterminal.com/tools/mealme.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mealme.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/mealme.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mealme.json",
      "dns": "mealme.grade.anchorterminal.com",
      "license": "Proprietary service under the MealMe API and SDK Terms of Use",
      "transports": [],
      "packages": [],
      "auth": "api-key",
      "authNotes": "One API key per account, sent in the Id-Token header on every call. A person creates an account with email and password at https://mealmeai.vercel.app/dashboard, adds a card, then creates the key; the docs also say to request a key through account setup on mealme.ai. No scopes, key expiry or rotation are documented. The embedded SDK uses a separate SDK key issued after a meeting and a licence agreement.",
      "pricing": "usage",
      "pricingNotes": "$0.10 per successful API call on the Developer plan with no monthly minimum, invoiced daily; $250 a month for unlimited successful calls on the Unlimited plan; Enterprise at a custom price for 250,000 or more calls a month. A card is required before API access. No free tier or credits found (https://mealmeai.vercel.app/pricing, checked 3 November 2026).",
      "priceSummary": "$0.10 / call",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API reference, llms.txt, pricing page or API terms (checked 3 November 2026).",
        "endpoints": []
      },
      "toolCount": 0,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://docs.mealme.ai/reference/environments",
      "llmsTxt": "https://mealmeapi.readme.io/llms.txt",
      "capabilities": [
        "shopping.search",
        "shopping.orders",
        "shopping.prices",
        "cooking.grocery",
        "commerce.cart",
        "commerce.checkout"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "api-key",
        "usage-priced",
        "card-required",
        "llms-txt",
        "rest",
        "webhooks",
        "sandbox",
        "no-status-page"
      ],
      "lastRelease": "2025-05-06",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 39.7,
        "grade": "E",
        "agentReady": false,
        "rank": 1390,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 7,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 6,
          "payments": 30,
          "reliability": 19,
          "schema": 72,
          "security": 26,
          "transparency": 47
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "Search, inventory, cart, order, payment, tracking webhook and support chat in one API, covering restaurants and grocery stores in the US and Canada",
          "Per-call price published without login, $0.10 a successful call with no monthly minimum, or $250 a month unlimited",
          "Store search takes a projections list to size responses and pages through next_page; product search accepts UPC codes",
          "Orders can be quoted first (place_order false returns 202 with the final quote) and placed in a second call",
          "Seventeen Create Order errors are listed with their status codes, and each endpoint page documents 400, 401 and 429"
        ],
        "weaknesses": [
          "One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header",
          "No status page, SLA or rate limit figures; the 429 schema shows only an example message",
          "No idempotency key on Create Order, so a retried call can place a second order",
          "A card is required before any call, and there is no free tier or trial",
          "The newest release note is dated 6 May 2025, and the API and SDK terms of 18 June 2022 license use for personal, noncommercial purposes"
        ],
        "agentNotes": [
          "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",
          "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",
          "Set projections on store search to the fields you need; fetch_quotes greatly increases response time per the docs",
          "Keep use_new_db the same across store search, Get Inventory and Get MealMe Store, or the store ids will not match",
          "Treat 406 (store closed, out of range, no delivery), 420 (product unavailable) and 422 (checkout error) as fixes to make, not transient failures"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 39.7
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 6,
          "payments": 30,
          "reliability": 19,
          "schema": 72,
          "security": 26,
          "transparency": 35
        },
        "provenanceScore": 59,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-03",
            "maintenance": "2026-11-03",
            "payments": "2026-11-03",
            "reliability": "2026-11-03",
            "schema": "2026-11-03",
            "security": "2026-11-03",
            "transparency": "2026-11-03"
          },
          "last": "2026-11-03",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-03",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl 'https://api.mealme.ai/search/store/v3?latitude=37.7786357\u0026longitude=-122.3918135\u0026store_type=grocery' -H 'Id-Token: YOUR_API_KEY'"
      },
      "letme": {
        "capability": "https://letme.dev/shopping.search",
        "tool": "https://letme.dev/mealme"
      },
      "alsoIn": [
        "cooking"
      ],
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Successful API call, Developer plan",
          "unit": "call",
          "usd": 0.1,
          "note": "No monthly minimum, invoiced daily; https://mealmeai.vercel.app/pricing"
        },
        {
          "item": "Unlimited plan",
          "unit": "month",
          "usd": 250,
          "note": "Unlimited successful calls, cancel any time"
        }
      ],
      "provenance": {
        "legalEntity": "MealMe, Inc.",
        "domain": "mealme.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.mealme.ai/privacy",
        "privacy": "https://www.mealme.ai/privacy",
        "statusPage": "",
        "changelog": "https://docs.mealme.ai/reference/release-notes",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "One page at mealme.ai/privacy holds the MealMe Connect Terms of Service (4 April 2025), the Privacy Policy (1 January 2025), the API and SDK Terms of Use (18 June 2022) and the Cookie Policy (1 January 2020). All name MealMe, Inc.; the Connect terms give a Wilmington, Delaware address and the API terms a Scottdale, Georgia notice address.",
          "The API and SDK terms forbid any robot, spider, scraper or other automatic or manual means to access the services or copy content, and the Connect terms forbid automated data extraction without written permission. Recorded as a fact; public pages were read within robots.txt.",
          "www.mealme.ai/robots.txt allows all crawlers except URLs with ?lightbox=; docs.mealme.ai/robots.txt allows all except /api-next, /edit/, /login and /logout, and points to mealmeapi.readme.io/llms.txt.",
          "The dashboard, signup and pricing pages are served from mealmeai.vercel.app, not mealme.ai.",
          "/.well-known/security.txt on www.mealme.ai returns 400. No status page found; status.mealme.ai does not resolve.",
          "RDAP for mealme.ai (rdap.nic.ai) returned no readable record, so no registration date is recorded."
        ],
        "score": 59
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/mealme.json",
      "live": {
        "slug": "mealme",
        "securityTxt": {
          "url": "https://mealme.ai/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:36:19.269833535Z"
        },
        "llmsTxt": {
          "url": "https://mealmeapi.readme.io/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-20T16:23:16.317068235Z"
        },
        "domain": {
          "domain": "mealme.ai",
          "registered": "2020-05-22",
          "source": "https://rdap.identitydigital.services/rdap/domain/mealme.ai",
          "checkedAt": "2026-11-15T15:17:37.129069617Z"
        },
        "pages": [
          {
            "url": "https://docs.mealme.ai/reference/release-notes",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-19T22:21:43.014156083Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "2834b165dfc8"
          },
          {
            "url": "https://mealmeai.vercel.app/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-19T22:29:14.453565057Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "825ce9abec8b"
          },
          {
            "url": "https://www.mealme.ai/privacy",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-19T22:46:53.741126619Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "eb325cb1665a"
          }
        ],
        "updatedAt": "2026-11-20T16:36:19.269833535Z"
      }
    },
    "edges": [
      {
        "by": 20,
        "category": "ergonomics",
        "leads": "mealme",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 49,
          "b": 69
        }
      },
      {
        "by": 17,
        "category": "security",
        "leads": "cartai",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 43,
          "b": 26
        }
      },
      {
        "by": 13,
        "category": "schema",
        "leads": "mealme",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 59,
          "b": 72
        }
      },
      {
        "by": 12,
        "category": "maintenance",
        "leads": "cartai",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 18,
          "b": 6
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "CartAI",
        "b": "MealMe, Inc.",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio",
        "b": "",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "Proprietary service under the MealMe API and SDK Terms of Use",
        "name": "Licence"
      },
      {
        "a": "8",
        "b": "0",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-07-20",
        "b": "2025-05-06",
        "name": "Last release"
      },
      {
        "a": "2026-05-13",
        "b": "2025-04-04",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-13",
        "b": "2025-04-04",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 auth and maintenance \u0026 community.",
        "question": "Which is better for AI agents, CartAI or MealMe API?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do CartAI and MealMe API need an API key?"
      },
      {
        "answer": "CartAI runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for MealMe API.",
        "question": "Can an agent call CartAI and MealMe API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 43 against 26",
          "Maintenance \u0026 community, 18 against 6"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.",
        "slug": "cartai",
        "watchFor": "No public prices. Production fees are basis points on order value, shown only in the dashboard"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 72 against 59",
          "Agent ergonomics, 69 against 49"
        ],
        "also": [
          "No incidents deducted, where CartAI loses 3 points for them"
        ],
        "goodFor": "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.",
        "slug": "mealme",
        "watchFor": "One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header"
      }
    ],
    "history": {
      "cartai": null,
      "mealme": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.3,
          "from": 38.4,
          "fromGrade": "E",
          "to": 39.7,
          "toGrade": "E"
        }
      ]
    },
    "job": {
      "capability": "shopping.orders",
      "name": "Placing and tracking orders"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-cartai.json",
        "title": "Amazon Creators API vs CartAI",
        "url": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-cartai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme.json",
        "title": "Amazon Creators API vs MealMe API",
        "url": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme"
      },
      {
        "json": "https://www.anchorterminal.com/compare/best-buy-vs-cartai.json",
        "title": "Best Buy Developer API vs CartAI",
        "url": "https://www.anchorterminal.com/compare/best-buy-vs-cartai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/best-buy-vs-mealme.json",
        "title": "Best Buy Developer API vs MealMe API",
        "url": "https://www.anchorterminal.com/compare/best-buy-vs-mealme"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-etsy.json",
        "title": "CartAI vs Etsy Open API v3",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-etsy"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-walmart-affiliate-api.json",
        "title": "CartAI vs Walmart Affiliate Marketing API",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-walmart-affiliate-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-zillow-claude.json",
        "title": "CartAI vs Zillow in Claude",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-zillow-claude"
      },
      {
        "json": "https://www.anchorterminal.com/compare/etsy-vs-mealme.json",
        "title": "Etsy Open API v3 vs MealMe API",
        "url": "https://www.anchorterminal.com/compare/etsy-vs-mealme"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mealme-vs-opencommerce.json",
        "title": "MealMe API vs opencommerce",
        "url": "https://www.anchorterminal.com/compare/mealme-vs-opencommerce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mealme-vs-shop-mcp.json",
        "title": "MealMe API vs Shop MCP",
        "url": "https://www.anchorterminal.com/compare/mealme-vs-shop-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.json",
        "title": "MealMe API vs Walmart Affiliate Marketing API",
        "url": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.json",
        "title": "MealMe API vs Walmart Agent Gateway",
        "url": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mealme-vs-zillow-claude.json",
        "title": "MealMe API vs Zillow in Claude",
        "url": "https://www.anchorterminal.com/compare/mealme-vs-zillow-claude"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mealme-vs-zinc.json",
        "title": "MealMe API vs Zinc",
        "url": "https://www.anchorterminal.com/compare/mealme-vs-zinc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-opencommerce.json",
        "title": "CartAI vs opencommerce",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-opencommerce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.json",
        "title": "CartAI vs Shop MCP",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-shop-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-walmart-agent-gateway.json",
        "title": "CartAI vs Walmart Agent Gateway",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-walmart-agent-gateway"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-zinc.json",
        "title": "CartAI vs Zinc",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-zinc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cartai-vs-instacart.json",
        "title": "CartAI vs Instacart Developer Platform API + MCP",
        "url": "https://www.anchorterminal.com/compare/cartai-vs-instacart"
      },
      {
        "json": "https://www.anchorterminal.com/compare/instacart-vs-mealme.json",
        "title": "Instacart Developer Platform API + MCP vs MealMe API",
        "url": "https://www.anchorterminal.com/compare/instacart-vs-mealme"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 1,
        "cartai": 18,
        "edge": "mealme",
        "key": "reliability",
        "mealme": 19,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 13,
        "cartai": 59,
        "edge": "mealme",
        "key": "schema",
        "mealme": 72,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 20,
        "cartai": 49,
        "edge": "mealme",
        "key": "ergonomics",
        "mealme": 69,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 17,
        "cartai": 43,
        "edge": "cartai",
        "key": "security",
        "mealme": 26,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 0,
        "cartai": 30,
        "edge": "",
        "key": "payments",
        "mealme": 30,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 12,
        "cartai": 18,
        "edge": "cartai",
        "key": "maintenance",
        "mealme": 6,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 2,
        "cartai": 45,
        "edge": "mealme",
        "key": "transparency",
        "mealme": 47,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "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 \u0026 auth and maintenance \u0026 community. Both do placing and tracking orders.",
    "tasks": null,
    "tutorials": [],
    "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": "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/cartai-vs-mealme",
    "json": "https://www.anchorterminal.com/compare/cartai-vs-mealme.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/cartai-vs-mealme.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/cartai-vs-mealme.min.md"
  },
  "markdown": "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 \u0026 auth and maintenance \u0026 community. Both do placing and tracking orders.\n\n- CartAI: grade F, 34.9/100, rank #1438 of 1563. Markdown https://www.anchorterminal.com/tools/cartai.md · JSON https://www.anchorterminal.com/api/v1/tools/cartai.json\n- MealMe API: grade E, 39.7/100, rank #1390 of 1563. Markdown https://www.anchorterminal.com/tools/mealme.md · JSON https://www.anchorterminal.com/api/v1/tools/mealme.json\n- Best shopping and order APIs for AI agents buying for a person: https://www.anchorterminal.com/best/shopping/index.md\n- All 61 shopping comparisons: https://www.anchorterminal.com/compare/shopping/index.md\n- Best recipe, nutrition and meal planning APIs for AI agents: https://www.anchorterminal.com/best/cooking/index.md\n- All 31 cooking comparisons: https://www.anchorterminal.com/compare/cooking/index.md\n\n## Which one, for what\n\n### CartAI (F)\n\nGood for: Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.\n\nAhead on:\n- Security \u0026 auth, 43 against 26\n- Maintenance \u0026 community, 18 against 6\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No public prices. Production fees are basis points on order value, shown only in the dashboard\n\n### MealMe API (E)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 72 against 59\n- Agent ergonomics, 69 against 49\n\nAlso in its favour:\n- No incidents deducted, where CartAI loses 3 points for them\n\nWatch for: One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header\n\n\n## Why the edge\n\n### Agent ergonomics: MealMe API +20\n\n- 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.\n- 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.\n\n### Security \u0026 auth: CartAI +17\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: MealMe API +13\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: CartAI +12\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | CartAI | MealMe API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 18 | 19 | MealMe API +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 59 | 72 | MealMe API +13 |\n| Agent ergonomics | 13% | 49 | 69 | MealMe API +20 |\n| Security \u0026 auth | 14% | 43 | 26 | CartAI +17 |\n| Payments \u0026 pricing | 10% | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 18 | 6 | CartAI +12 |\n| Transparency \u0026 trust | 7% | 45 | 47 | MealMe API +2 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **34.9 · F** | **39.7 · E** | |\n\n## Facts side by side\n\n| Fact | CartAI | MealMe API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | CartAI | MealMe, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio |  |\n| Auth | API key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under the MealMe API and SDK Terms of Use |\n| Tools exposed | 8 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-07-20 | 2025-05-06 |\n| Terms last updated | 2026-05-13 | 2025-04-04 |\n| Privacy policy last updated | 2026-05-13 | 2025-04-04 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | yes |\n\n## How the scores have moved\n\n### CartAI\n\nNo score change since it was listed.\n\n### MealMe API\n\n- +1.3 on 13 November 2026: checklist\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### CartAI\n\n1. 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\n2. Use only the test card 4242 4242 4242 4242 until the account is in production mode, since test mode does not tokenise card data\n3. Set `verifyBeforePlacement` and show `derivedDetails.pricing` to the customer at `PENDING_CONFIRMATION` before the order is placed\n4. Poll a task no more than once every 5 to 10 seconds when webhooks are unavailable\n5. Give `selectedVariant` labels as the merchant's page shows them, and use US merchants, addresses and phone numbers only\n\n### MealMe API\n\n1. 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\n2. 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\n3. Set projections on store search to the fields you need; fetch_quotes greatly increases response time per the docs\n4. Keep use_new_db the same across store search, Get Inventory and Get MealMe Store, or the store ids will not match\n5. Treat 406 (store closed, out of range, no delivery), 420 (product unavailable) and 422 (checkout error) as fixes to make, not transient failures\n\n## Questions\n\n### Which is better for AI agents, CartAI or MealMe API?\n\nMealMe 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 \u0026 auth and maintenance \u0026 community.\n\n### Do CartAI and MealMe API need an API key?\n\nBoth need an API key.\n\n### Can an agent call CartAI and MealMe API without installing anything?\n\nCartAI runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for MealMe API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cartai-vs-mealme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cartai-vs-mealme.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cartai\", \"b\": \"mealme\"}`. From a terminal: `anchor compare cartai mealme`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cartai.json and https://www.anchorterminal.com/api/v1/tools/mealme.json\n\n## Other comparisons with CartAI or MealMe API\n\n- [Amazon Creators API vs CartAI](https://www.anchorterminal.com/compare/amazon-creators-api-vs-cartai.md)\n- [Amazon Creators API vs MealMe API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme.md)\n- [Best Buy Developer API vs CartAI](https://www.anchorterminal.com/compare/best-buy-vs-cartai.md)\n- [Best Buy Developer API vs MealMe API](https://www.anchorterminal.com/compare/best-buy-vs-mealme.md)\n- [CartAI vs Etsy Open API v3](https://www.anchorterminal.com/compare/cartai-vs-etsy.md)\n- [CartAI vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/cartai-vs-walmart-affiliate-api.md)\n- [CartAI vs Zillow in Claude](https://www.anchorterminal.com/compare/cartai-vs-zillow-claude.md)\n- [Etsy Open API v3 vs MealMe API](https://www.anchorterminal.com/compare/etsy-vs-mealme.md)\n- [MealMe API vs opencommerce](https://www.anchorterminal.com/compare/mealme-vs-opencommerce.md)\n- [MealMe API vs Shop MCP](https://www.anchorterminal.com/compare/mealme-vs-shop-mcp.md)\n- [MealMe API vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.md)\n- [MealMe API vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.md)\n- [MealMe API vs Zillow in Claude](https://www.anchorterminal.com/compare/mealme-vs-zillow-claude.md)\n- [MealMe API vs Zinc](https://www.anchorterminal.com/compare/mealme-vs-zinc.md)\n- [CartAI vs opencommerce](https://www.anchorterminal.com/compare/cartai-vs-opencommerce.md)\n- [CartAI vs Shop MCP](https://www.anchorterminal.com/compare/cartai-vs-shop-mcp.md)\n- [CartAI vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/cartai-vs-walmart-agent-gateway.md)\n- [CartAI vs Zinc](https://www.anchorterminal.com/compare/cartai-vs-zinc.md)\n- [CartAI vs Instacart Developer Platform API + MCP](https://www.anchorterminal.com/compare/cartai-vs-instacart.md)\n- [Instacart Developer Platform API + MCP vs MealMe API](https://www.anchorterminal.com/compare/instacart-vs-mealme.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-20",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "CartAI vs MealMe API",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": [
      "CartAI F 34.9",
      "MealMe API E 39.7",
      "scores"
    ],
    "h1": "CartAI vs MealMe API",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/cartai-vs-mealme",
    "published": "2026-10-01",
    "section": "tools",
    "title": "CartAI vs MealMe for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-20",
    "url": "https://www.anchorterminal.com/compare/cartai-vs-mealme"
  },
  "tokens": {
    "markdown": 4100,
    "slim": 880
  },
  "version": 1
}
