{
  "data": {
    "a": {
      "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",
      "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": 1386,
        "ranked": true,
        "rankOf": 1557,
        "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": "unknown",
          "checkedAt": "2026-11-18T16:30:17.326973892Z"
        },
        "llmsTxt": {
          "url": "https://mealmeapi.readme.io/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:01.571090102Z"
        },
        "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-18T21:40:49.559451752Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "2834b165dfc8"
          },
          {
            "url": "https://mealmeai.vercel.app/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:48:14.089553191Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "825ce9abec8b"
          },
          {
            "url": "https://www.mealme.ai/privacy",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-18T22:05:51.793144829Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "eb325cb1665a"
          }
        ],
        "updatedAt": "2026-11-18T22:05:51.793144829Z"
      }
    },
    "answer": "Zinc scores 69.9 (B) on agent readiness against MealMe API's 39.7 (E), and leads in every scored category.",
    "b": {
      "slug": "zinc",
      "name": "Zinc",
      "vendor": "Zinc",
      "vendorUrl": "https://www.zinc.com",
      "company": "zinc.com",
      "kind": "http-api",
      "category": "shopping",
      "summary": "Zinc is an API for buying from online retailers such as Amazon, Walmart and Target, covering product search, orders, tracking and returns. Agents can pay per order by x402, MPP or Link without an account.",
      "url": "https://www.anchorterminal.com/tools/zinc",
      "markdownUrl": "https://www.anchorterminal.com/tools/zinc.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zinc.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zinc.json",
      "dns": "zinc.grade.anchorterminal.com",
      "repo": "https://github.com/zincio/skills",
      "license": "Proprietary service, agent skills MIT",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.zinc.com/mcp",
      "packages": [
        {
          "registry": "npm",
          "name": "zinc"
        }
      ],
      "auth": "mixed",
      "authNotes": "Bearer API key (`zn_test_` sandbox, `zn_live_` live). `POST /sandbox/keys` mints a sandbox key with no authentication. A live key for an agent comes from a device-code flow a person approves in a browser. `/agent/*` routes need no key and take payment by x402 or MPP, returning an `X-Api-Key` to follow the order. The MCP connector needs no account to buy.",
      "pricing": "usage",
      "pricingNotes": "$1 per successful order plus the item cost, and $0.01 per data call. Add $0.25 for tracking links and emails, and $0.10 per item over 10. Failed orders aren't billed. Sandbox free with no card, and a $5 starter credit on the first approved live key. Wallet top-ups carry card, ACH or wire fees. Volume pricing from 1,000 orders a month.",
      "priceSummary": "$1 / tx",
      "where": "hosted",
      "x402": {
        "level": "partial",
        "evidence": "`POST /agent/orders` answers 402 with one challenge per rail, x402 v2 in `PAYMENT-REQUIRED` (USDC on Base and Solana, sponsored settlement), and MPP in `WWW-Authenticate` for Tempo and for Link Shared Payment Tokens. The amount is `max_price` plus the $1 fee, and the unused part is refunded. The `/agent/*` data endpoints use the same flow at $0.01 a call on Tempo and x402 only. Other routes need an API key (https://www.zinc.com/docs/v2/agentic-purchases.md, checked 2026-11-18). Not probed.",
        "endpoints": [
          {
            "url": "https://api.zinc.com/agent/orders",
            "priceUsd": null,
            "network": "eip155:8453"
          }
        ]
      },
      "toolCount": 8,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://www.zinc.com/docs",
      "llmsTxt": "https://www.zinc.com/llms.txt",
      "openapi": "https://api.zinc.com/openapi.json",
      "registryName": "com.zinc.www/mcp",
      "capabilities": [
        "shopping.search",
        "shopping.orders",
        "shopping.returns",
        "shopping.prices",
        "payments.x402",
        "payments.protocol"
      ],
      "tags": [
        "hosted",
        "usage",
        "x402",
        "mpp",
        "stablecoin",
        "no-card",
        "sandbox",
        "mcp",
        "remote-mcp",
        "mcp-registry",
        "llms-txt",
        "openapi",
        "typescript"
      ],
      "lastRelease": "2026-11-13",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 69.9,
        "grade": "B",
        "agentReady": false,
        "rank": 320,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 1,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 86,
          "maintenance": 83,
          "payments": 98,
          "reliability": 55,
          "schema": 92,
          "security": 57,
          "transparency": 60
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "warnings": [
          {
            "kind": "operator-unidentified",
            "name": "Operator not identified",
            "text": "Zinc's terms name Zinc Technologies Inc. under California law, with no place of registration, registration number or address. OpenCorporates and SEC EDGAR refused our reader (403), so no register entry was found.",
            "deduct": 0,
            "capGrade": "B",
            "since": "2026-11-18",
            "sources": [
              "https://www.zinc.com/legal/terms",
              "https://www.zinc.com/legal/privacy"
            ]
          }
        ],
        "verdict": "An agent can mint a sandbox key with no signup and pay for real orders by x402, MPP or Link with no account, at $1 an order plus the item, with idempotency keys and a public OpenAPI file. Orders run on Zinc's own retailer accounts by default, and no security programme or numeric rate limits were found.",
        "bestFor": "Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.",
        "strengths": [
          "`POST /agent/orders` takes payment in the request by x402 (USDC on Base or Solana), MPP on Tempo or Link, with no account or key",
          "`POST /sandbox/keys` mints a test key with no authentication, and a person approves a live key by device code in a browser",
          "Public OpenAPI 3.1 file (53 operations), llms.txt, llms-full.txt and Markdown copies of every docs page",
          "$1 per successful order and $0.01 per data call, published without login. Failed orders aren't billed and the unspent `max_price` is refunded",
          "Idempotency keys on orders and wallet top-ups, and a 409 with the existing order's id on a duplicate"
        ],
        "weaknesses": [
          "By default orders run on retailer accounts Zinc runs, and its docs index lists a guide to Amazon's anti-bot pages and one on proxies \"for account protection\"",
          "No security.txt, disclosure policy, bug bounty or certification found",
          "No numeric request rate limits published, apart from 5 sandbox keys per IP address a day",
          "The status page shows 99.1 per cent uptime for ordering and 99.57 per cent for the API over 90 days, with no incident write-ups",
          "Metered data endpoints answer 402 with a bare `detail` string instead of the documented error envelope"
        ],
        "agentNotes": [
          "Call `GET /retailers/check` with the product URL and country before ordering, since unsupported retailers and countries fail predictably",
          "Set `max_price` and an `idempotency_key` on every order. If a retry returns 409, read the existing order id from `error.details.order_id`",
          "If your HTTP client merges `WWW-Authenticate` headers, add `?method=x402`, `?method=tempo` or `?method=stripe` to get one payment challenge",
          "Store the `X-Api-Key` returned with a paid agent order. It is the only way to follow that order without paying again",
          "Persist a sandbox key across runs. It expires after 7 days without use, and minting is limited to 5 a day per IP address"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 69.9
          }
        ],
        "editorialScores": {
          "ergonomics": 86,
          "maintenance": 83,
          "payments": 98,
          "reliability": 55,
          "schema": 92,
          "security": 57,
          "transparency": 46
        },
        "provenanceScore": 73,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm i zinc",
        "http": "curl -X POST https://api.zinc.com/sandbox/keys",
        "claudeCode": "claude mcp add zinc --transport http https://mcp.zinc.com/mcp",
        "config": {
          "mcpServers": {
            "zinc": {
              "url": "https://mcp.zinc.com/mcp"
            }
          }
        },
        "x402": "https://api.zinc.com/agent/orders?method=x402"
      },
      "letme": {
        "capability": "https://letme.dev/shopping.search",
        "tool": "https://letme.dev/zinc"
      },
      "area": "everyday",
      "unitPrices": [
        {
          "item": "Successful order (Zinc fee, item cost extra)",
          "unit": "tx",
          "usd": 1,
          "note": "Failed orders aren't billed"
        },
        {
          "item": "Product data call",
          "unit": "call",
          "usd": 0.01,
          "note": "Search, product details and `offers`, on agent and keyed endpoints"
        },
        {
          "item": "Tracking links and emails add-on",
          "unit": "tx",
          "usd": 0.25,
          "note": "Per order"
        },
        {
          "item": "Extra item over 10 in one order",
          "unit": "tx",
          "usd": 0.1,
          "note": "Per item"
        }
      ],
      "provenance": {
        "legalEntity": "Zinc Technologies Inc.",
        "domain": "zinc.com",
        "domainRegistered": "",
        "domainNote": "Not looked up in this run.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.zinc.com/legal/terms",
        "privacy": "https://www.zinc.com/legal/privacy",
        "statusPage": "https://www.zinc.com/status",
        "changelog": "https://www.zinc.com/docs/changelog",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms (updated 12 October 2026) are with Zinc Technologies Inc., under California law with courts in Los Angeles County. No place of registration, registration number or address appears on the pages read.",
          "www.zinc.com's robots.txt allows all agents and carries Content-Signal ai-train=no, search=yes, ai-input=yes. api.zinc.com's robots.txt answered 404.",
          "www.zinc.com/.well-known/security.txt answered 404 on 18 November 2026.",
          "The terms forbid using the service to violate a retailer's terms \"in a way that harms Zinc or that Retailer\" and say purchases are subject to each retailer's terms."
        ],
        "score": 73
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/zinc.json",
      "live": {
        "slug": "zinc",
        "probe": {
          "target": "https://mcp.zinc.com/mcp",
          "method": "get",
          "lastAt": "2026-11-18T23:14:03.67996308Z",
          "lastOk": true,
          "lastStatus": 204,
          "lastMs": 288,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 473,
          "p95ms24h": 902,
          "samples24h": 16,
          "samples30d": 16,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 16,
              "ok": 16
            }
          ],
          "since": "2026-11-18T21:38:42.096706069Z"
        },
        "vendorStatus": {
          "page": "https://www.zinc.com/status",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T21:41:08.844643791Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.zinc.www/mcp",
            "version": "1.0.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "updatedAt": "2026-11-18T23:14:03.67996308Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 77,
        "category": "maintenance",
        "leads": "zinc",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "The changelog's latest entry is dated 13 November 2026, and the npm SDK's latest version is 2026.10.30 (30). Weekly dated changelog entries, 13 since 20 August 2026 (20). A public weekly changelog and a support address (support@zinc.com) that the contact page says gets a person. GitHub issue response wasn't checked (10 of 25). The MCP connector is in the official MCP registry as `com.zinc.www/mcp`, published 28 October 2026 under Zinc's domain namespace, and the npm SDK is current (15). The npm SDK is generated from the live spec and published with provenance attestations (8 of 10). 30 + 20 + 10 + 15 + 8 = 83."
        },
        "scores": {
          "a": 6,
          "b": 83
        }
      },
      {
        "by": 68,
        "category": "payments",
        "leads": "zinc",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). $0.10 per successful call and $250 a month published without login (20). No free tier or trial; a card must be added before the key is created (0). Signup is a browser form with email, password and card (0). Total 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.",
          "b": "x402 (v2, USDC on Base and Solana) and MPP (Tempo, and Link with a Shared Payment Token) on `POST /agent/orders` and the `/agent/*` data endpoints. Returns, cases, managed accounts and webhooks need an API key (8 of 10). $1 per successful order plus the item, $0.25 for tracking links and emails, $0.10 per item over 10, and $0.01 per data call, published without login (30). A sandbox needs no account or card, and a device-approved live key comes with a $5 starter credit (30). An agent can pay per order with no account, or mint a sandbox key with one unauthenticated call (30). 8 + 30 + 30 + 30 = 98."
        },
        "scores": {
          "a": 30,
          "b": 98
        }
      },
      {
        "by": 36,
        "category": "reliability",
        "leads": "zinc",
        "name": "Reliability",
        "reasons": {
          "a": "Read with the hosted lines. No status page found on mealme.ai, the docs or llms.txt, and status.mealme.ai does not resolve (0). No readable incident history (5). No rate limit figures; each endpoint documents a 429 whose example message is 10 per 1 second(s)!, which the reference itself calls an example (0 of 15). The 429 is documented without Retry-After or backoff guidance, and Create Order has no idempotency key, only an order_id to update an existing order and a caller's customer_order_id to look up (4 of 15). No SLA found (0). The API is in production with versioned endpoints (10). Total 19.",
          "b": "Zinc's own status page (www.zinc.com/status) shows five components (Ordering, Tracking, Product Data, API, Dashboard) with 90-day uptime bars (20). On 18 November 2026 it showed 99.1 per cent uptime for Ordering and 99.57 per cent for the API over 90 days, both recovered from a degradation that day. The page has no incident write-ups, and 99.1 per cent over 90 days is about 19 hours, so at least one major interruption is implied (10 of 30). No numeric request rate limits found, apart from 5 sandbox key mints per IP address a day (5 of 15). 429 carries `rate_limit_exceeded` with guidance to back off and retry, responses carry RateLimit and RateLimit-Policy headers (changelog, August 2026), and orders and top-ups take idempotency keys (15). No SLA found (0). Orders are generally available. Cross-retailer search and the Zinc 2.0 announcement carry a beta label (5 of 10). 20 + 10 + 5 + 15 + 0 + 5 = 55."
        },
        "scores": {
          "a": 19,
          "b": 55
        }
      },
      {
        "by": 31,
        "category": "security",
        "leads": "zinc",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "Bearer API keys, `zn_test_` for sandbox and `zn_live_` for live, and each agent can get its own live key by device-code approval. No scopes or rotation steps were found (18 of 30). Sandbox keys can't spend, every order carries a `max_price` cap, a person approves a live key in the browser, and the MCP connector's `place-order` needs a confirmation token withheld from the model (17 of 20). The MCP docs explain that the token is there so a prompt injection in a page can't become a purchase. Product data from retailers is untrusted text (12 of 15). Order timelines, a usage endpoint, CSV export and the dashboard show every order (10 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001 found (0). 18 + 17 + 12 + 10 + 0 = 57."
        },
        "scores": {
          "a": 26,
          "b": 57
        }
      },
      {
        "by": 20,
        "category": "schema",
        "leads": "zinc",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "A public OpenAPI 3.1 file at api.zinc.com/openapi.json, version 2026-10-30, with 45 paths and 53 operations, 49 of them described (25). llms.txt, llms-full.txt, section indexes and `Accept: text/markdown` on every page (10). Pages say when to use each route, such as checking a retailer before ordering and using the `offers` endpoint rather than product details for a price (17 of 20). Typed request bodies with required fields, prices in integer cents and enumerated payment methods (14 of 15). Examples on every page and a long table of error codes with recovery steps, but the metered data endpoints return a different 402 shape and the MCP connector's tool schemas weren't read (11 of 15). Dated API versions (CalVer, 30 versions listed back to 24 November 2025) and a weekly changelog (15). 25 + 10 + 17 + 14 + 11 + 15 = 92."
        },
        "scores": {
          "a": 72,
          "b": 92
        }
      },
      {
        "by": 17,
        "category": "ergonomics",
        "leads": "zinc",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "Search returns up to 20 results, best first, and data and order calls are separate routes, so responses stay small. No field selection found (20 of 25). List and export endpoints take filters, and orders can be listed, exported and followed by webhook (18 of 20). Errors carry a stable `code`, a message and `details`, including `details.fund_with` on `insufficient_funds` and RFC 8628 hints in the device flow (20). Idempotency keys on orders, agent orders and top-ups, a 409 that names the existing order, and an MCP spending tool that needs a confirmation token only a person's click produces. MCP annotations weren't read (18 of 20). Few required fields, and an official npm SDK (`zinc`, CalVer from the live spec). No second official SDK was confirmed (10 of 15). 20 + 18 + 20 + 18 + 10 = 86."
        },
        "scores": {
          "a": 69,
          "b": 86
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "MealMe, Inc.",
        "b": "Zinc",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://mcp.zinc.com/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "on some endpoints",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the MealMe API and SDK Terms of Use",
        "b": "Proprietary service, agent skills MIT",
        "name": "Licence"
      },
      {
        "a": "0",
        "b": "8",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.zinc.www/mcp",
        "name": "MCP registry"
      },
      {
        "a": "2025-05-06",
        "b": "2026-11-13",
        "name": "Last release"
      },
      {
        "a": "2025-04-04",
        "b": "2026-10-12",
        "name": "Terms last updated"
      },
      {
        "a": "2025-04-04",
        "b": "2026-10-06",
        "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": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Zinc scores 69.9 (B) on agent readiness against MealMe API's 39.7 (E), and leads in every scored category.",
        "question": "Which is better for AI agents, MealMe API or Zinc?"
      },
      {
        "answer": "MealMe API needs an API key. Zinc takes an API key or an OAuth sign-in.",
        "question": "Do MealMe API and Zinc need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for MealMe API. Zinc has a hosted endpoint at https://mcp.zinc.com/mcp.",
        "question": "Can an agent call MealMe API and Zinc without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": null,
        "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"
      },
      {
        "aheadOn": [
          "Reliability, 55 against 19",
          "Schema \u0026 documentation, 92 against 72",
          "Agent ergonomics, 86 against 69",
          "Security \u0026 auth, 57 against 26",
          "Payments \u0026 pricing, 98 against 30",
          "Maintenance \u0026 community, 83 against 6",
          "Transparency \u0026 trust, 60 against 47"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Free to start without a card"
        ],
        "goodFor": "Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.",
        "slug": "zinc",
        "watchFor": "By default orders run on retailer accounts Zinc runs, and its docs index lists a guide to Amazon's anti-bot pages and one on proxies \"for account protection\""
      }
    ],
    "history": {
      "mealme": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.3,
          "from": 38.4,
          "fromGrade": "E",
          "to": 39.7,
          "toGrade": "E"
        }
      ],
      "zinc": null
    },
    "job": {
      "capability": "shopping.search",
      "name": "Product search for shoppers"
    },
    "others": [
      {
        "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/amazon-creators-api-vs-zinc.json",
        "title": "Amazon Creators API vs Zinc",
        "url": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-zinc"
      },
      {
        "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/best-buy-vs-zinc.json",
        "title": "Best Buy Developer API vs Zinc",
        "url": "https://www.anchorterminal.com/compare/best-buy-vs-zinc"
      },
      {
        "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/etsy-vs-zinc.json",
        "title": "Etsy Open API v3 vs Zinc",
        "url": "https://www.anchorterminal.com/compare/etsy-vs-zinc"
      },
      {
        "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/opencommerce-vs-zinc.json",
        "title": "opencommerce vs Zinc",
        "url": "https://www.anchorterminal.com/compare/opencommerce-vs-zinc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/shop-mcp-vs-zinc.json",
        "title": "Shop MCP vs Zinc",
        "url": "https://www.anchorterminal.com/compare/shop-mcp-vs-zinc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-zinc.json",
        "title": "Walmart Affiliate Marketing API vs Zinc",
        "url": "https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-zinc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/zillow-claude-vs-zinc.json",
        "title": "Zillow in Claude vs Zinc",
        "url": "https://www.anchorterminal.com/compare/zillow-claude-vs-zinc"
      },
      {
        "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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/walmart-agent-gateway-vs-zinc.json",
        "title": "Walmart Agent Gateway vs Zinc",
        "url": "https://www.anchorterminal.com/compare/walmart-agent-gateway-vs-zinc"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 36,
        "edge": "zinc",
        "key": "reliability",
        "mealme": 19,
        "name": "Reliability",
        "weight": 16,
        "zinc": 55
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 20,
        "edge": "zinc",
        "key": "schema",
        "mealme": 72,
        "name": "Schema \u0026 documentation",
        "weight": 13,
        "zinc": 92
      },
      {
        "by": 17,
        "edge": "zinc",
        "key": "ergonomics",
        "mealme": 69,
        "name": "Agent ergonomics",
        "weight": 13,
        "zinc": 86
      },
      {
        "by": 31,
        "edge": "zinc",
        "key": "security",
        "mealme": 26,
        "name": "Security \u0026 auth",
        "weight": 14,
        "zinc": 57
      },
      {
        "by": 68,
        "edge": "zinc",
        "key": "payments",
        "mealme": 30,
        "name": "Payments \u0026 pricing",
        "weight": 10,
        "zinc": 98
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 77,
        "edge": "zinc",
        "key": "maintenance",
        "mealme": 6,
        "name": "Maintenance \u0026 community",
        "weight": 7,
        "zinc": 83
      },
      {
        "by": 13,
        "edge": "zinc",
        "key": "transparency",
        "mealme": 47,
        "name": "Transparency \u0026 trust",
        "weight": 7,
        "zinc": 60
      }
    ],
    "summary": "Zinc scores 69.9 (B) on agent readiness against MealMe API's 39.7 (E), and leads in every scored category. Both do product search for shoppers.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "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.",
      "zinc": "An agent can mint a sandbox key with no signup and pay for real orders by x402, MPP or Link with no account, at $1 an order plus the item, with idempotency keys and a public OpenAPI file. Orders run on Zinc's own retailer accounts by default, and no security programme or numeric rate limits were found."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/mealme-vs-zinc",
    "json": "https://www.anchorterminal.com/compare/mealme-vs-zinc.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/mealme-vs-zinc.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/mealme-vs-zinc.min.md"
  },
  "markdown": "Zinc scores 69.9 (B) on agent readiness against MealMe API's 39.7 (E), and leads in every scored category. Both do product search for shoppers.\n\n- MealMe API: grade E, 39.7/100, rank #1386 of 1557. Markdown https://www.anchorterminal.com/tools/mealme.md · JSON https://www.anchorterminal.com/api/v1/tools/mealme.json\n- Zinc: grade B, 69.9/100, rank #320 of 1557. Markdown https://www.anchorterminal.com/tools/zinc.md · JSON https://www.anchorterminal.com/api/v1/tools/zinc.json\n- Best shopping and order APIs for AI agents buying for a person: https://www.anchorterminal.com/best/shopping/index.md\n- All 50 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 29 cooking comparisons: https://www.anchorterminal.com/compare/cooking/index.md\n\n## Which one, for what\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\nWatch for: One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header\n\n### Zinc (B)\n\nGood for: Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.\n\nAhead on:\n- Reliability, 55 against 19\n- Schema \u0026 documentation, 92 against 72\n- Agent ergonomics, 86 against 69\n- Security \u0026 auth, 57 against 26\n- Payments \u0026 pricing, 98 against 30\n- Maintenance \u0026 community, 83 against 6\n- Transparency \u0026 trust, 60 against 47\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: By default orders run on retailer accounts Zinc runs, and its docs index lists a guide to Amazon's anti-bot pages and one on proxies \"for account protection\"\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Zinc +77\n\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- Zinc (83): The changelog's latest entry is dated 13 November 2026, and the npm SDK's latest version is 2026.10.30 (30). Weekly dated changelog entries, 13 since 20 August 2026 (20). A public weekly changelog and a support address (support@zinc.com) that the contact page says gets a person. GitHub issue response wasn't checked (10 of 25). The MCP connector is in the official MCP registry as `com.zinc.www/mcp`, published 28 October 2026 under Zinc's domain namespace, and the npm SDK is current (15). The npm SDK is generated from the live spec and published with provenance attestations (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.\n\n### Payments \u0026 pricing: Zinc +68\n\n- MealMe API (30): No x402, MPP or L402 (0). $0.10 per successful call and $250 a month published without login (20). No free tier or trial; a card must be added before the key is created (0). Signup is a browser form with email, password and card (0). Total 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\n- Zinc (98): x402 (v2, USDC on Base and Solana) and MPP (Tempo, and Link with a Shared Payment Token) on `POST /agent/orders` and the `/agent/*` data endpoints. Returns, cases, managed accounts and webhooks need an API key (8 of 10). $1 per successful order plus the item, $0.25 for tracking links and emails, $0.10 per item over 10, and $0.01 per data call, published without login (30). A sandbox needs no account or card, and a device-approved live key comes with a $5 starter credit (30). An agent can pay per order with no account, or mint a sandbox key with one unauthenticated call (30). 8 + 30 + 30 + 30 = 98.\n\n### Reliability: Zinc +36\n\n- MealMe API (19): Read with the hosted lines. No status page found on mealme.ai, the docs or llms.txt, and status.mealme.ai does not resolve (0). No readable incident history (5). No rate limit figures; each endpoint documents a 429 whose example message is 10 per 1 second(s)!, which the reference itself calls an example (0 of 15). The 429 is documented without Retry-After or backoff guidance, and Create Order has no idempotency key, only an order_id to update an existing order and a caller's customer_order_id to look up (4 of 15). No SLA found (0). The API is in production with versioned endpoints (10). Total 19.\n- Zinc (55): Zinc's own status page (www.zinc.com/status) shows five components (Ordering, Tracking, Product Data, API, Dashboard) with 90-day uptime bars (20). On 18 November 2026 it showed 99.1 per cent uptime for Ordering and 99.57 per cent for the API over 90 days, both recovered from a degradation that day. The page has no incident write-ups, and 99.1 per cent over 90 days is about 19 hours, so at least one major interruption is implied (10 of 30). No numeric request rate limits found, apart from 5 sandbox key mints per IP address a day (5 of 15). 429 carries `rate_limit_exceeded` with guidance to back off and retry, responses carry RateLimit and RateLimit-Policy headers (changelog, August 2026), and orders and top-ups take idempotency keys (15). No SLA found (0). Orders are generally available. Cross-retailer search and the Zinc 2.0 announcement carry a beta label (5 of 10). 20 + 10 + 5 + 15 + 0 + 5 = 55.\n\n### Security \u0026 auth: Zinc +31\n\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- Zinc (57): Bearer API keys, `zn_test_` for sandbox and `zn_live_` for live, and each agent can get its own live key by device-code approval. No scopes or rotation steps were found (18 of 30). Sandbox keys can't spend, every order carries a `max_price` cap, a person approves a live key in the browser, and the MCP connector's `place-order` needs a confirmation token withheld from the model (17 of 20). The MCP docs explain that the token is there so a prompt injection in a page can't become a purchase. Product data from retailers is untrusted text (12 of 15). Order timelines, a usage endpoint, CSV export and the dashboard show every order (10 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001 found (0). 18 + 17 + 12 + 10 + 0 = 57.\n\n### Schema \u0026 documentation: Zinc +20\n\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- Zinc (92): A public OpenAPI 3.1 file at api.zinc.com/openapi.json, version 2026-10-30, with 45 paths and 53 operations, 49 of them described (25). llms.txt, llms-full.txt, section indexes and `Accept: text/markdown` on every page (10). Pages say when to use each route, such as checking a retailer before ordering and using the `offers` endpoint rather than product details for a price (17 of 20). Typed request bodies with required fields, prices in integer cents and enumerated payment methods (14 of 15). Examples on every page and a long table of error codes with recovery steps, but the metered data endpoints return a different 402 shape and the MCP connector's tool schemas weren't read (11 of 15). Dated API versions (CalVer, 30 versions listed back to 24 November 2025) and a weekly changelog (15). 25 + 10 + 17 + 14 + 11 + 15 = 92.\n\n### Agent ergonomics: Zinc +17\n\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- Zinc (86): Search returns up to 20 results, best first, and data and order calls are separate routes, so responses stay small. No field selection found (20 of 25). List and export endpoints take filters, and orders can be listed, exported and followed by webhook (18 of 20). Errors carry a stable `code`, a message and `details`, including `details.fund_with` on `insufficient_funds` and RFC 8628 hints in the device flow (20). Idempotency keys on orders, agent orders and top-ups, a 409 that names the existing order, and an MCP spending tool that needs a confirmation token only a person's click produces. MCP annotations weren't read (18 of 20). Few required fields, and an official npm SDK (`zinc`, CalVer from the live spec). No second official SDK was confirmed (10 of 15). 20 + 18 + 20 + 18 + 10 = 86.\n\n## Score by category\n\n| Category | Weight | MealMe API | Zinc | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 19 | 55 | Zinc +36 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 72 | 92 | Zinc +20 |\n| Agent ergonomics | 13% | 69 | 86 | Zinc +17 |\n| Security \u0026 auth | 14% | 26 | 57 | Zinc +31 |\n| Payments \u0026 pricing | 10% | 30 | 98 | Zinc +68 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 6 | 83 | Zinc +77 |\n| Transparency \u0026 trust | 7% | 47 | 60 | Zinc +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **39.7 · E** | **69.9 · B** | |\n\n## Facts side by side\n\n| Fact | MealMe API | Zinc |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MealMe, Inc. | Zinc |\n| Hosted endpoint | no (local only) | `https://mcp.zinc.com/mcp` |\n| Transports |  | Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | on some endpoints |\n| Licence | Proprietary service under the MealMe API and SDK Terms of Use | Proprietary service, agent skills MIT |\n| Tools exposed | 0 | 8 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.zinc.www/mcp` |\n| Last release | 2025-05-06 | 2026-11-13 |\n| Terms last updated | 2025-04-04 | 2026-10-12 |\n| Privacy policy last updated | 2025-04-04 | 2026-10-06 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n\n## How the scores have moved\n\n### MealMe API\n\n- +1.3 on 13 November 2026: checklist\n\n### Zinc\n\nNo score change since it was listed.\n\n## Verdicts\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**Zinc.** An agent can mint a sandbox key with no signup and pay for real orders by x402, MPP or Link with no account, at $1 an order plus the item, with idempotency keys and a public OpenAPI file. Orders run on Zinc's own retailer accounts by default, and no security programme or numeric rate limits were found.\n\n## Before you call either\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### Zinc\n\n1. Call `GET /retailers/check` with the product URL and country before ordering, since unsupported retailers and countries fail predictably\n2. Set `max_price` and an `idempotency_key` on every order. If a retry returns 409, read the existing order id from `error.details.order_id`\n3. If your HTTP client merges `WWW-Authenticate` headers, add `?method=x402`, `?method=tempo` or `?method=stripe` to get one payment challenge\n4. Store the `X-Api-Key` returned with a paid agent order. It is the only way to follow that order without paying again\n5. Persist a sandbox key across runs. It expires after 7 days without use, and minting is limited to 5 a day per IP address\n\n## Questions\n\n### Which is better for AI agents, MealMe API or Zinc?\n\nZinc scores 69.9 (B) on agent readiness against MealMe API's 39.7 (E), and leads in every scored category.\n\n### Do MealMe API and Zinc need an API key?\n\nMealMe API needs an API key. Zinc takes an API key or an OAuth sign-in.\n\n### Can an agent call MealMe API and Zinc without installing anything?\n\nNo hosted endpoint is listed for MealMe API. Zinc has a hosted endpoint at https://mcp.zinc.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mealme-vs-zinc.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mealme-vs-zinc.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mealme\", \"b\": \"zinc\"}`. From a terminal: `anchor compare mealme zinc`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mealme.json and https://www.anchorterminal.com/api/v1/tools/zinc.json\n\n## Other comparisons with MealMe API or Zinc\n\n- [Amazon Creators API vs MealMe API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme.md)\n- [Amazon Creators API vs Zinc](https://www.anchorterminal.com/compare/amazon-creators-api-vs-zinc.md)\n- [Best Buy Developer API vs MealMe API](https://www.anchorterminal.com/compare/best-buy-vs-mealme.md)\n- [Best Buy Developer API vs Zinc](https://www.anchorterminal.com/compare/best-buy-vs-zinc.md)\n- [Etsy Open API v3 vs MealMe API](https://www.anchorterminal.com/compare/etsy-vs-mealme.md)\n- [Etsy Open API v3 vs Zinc](https://www.anchorterminal.com/compare/etsy-vs-zinc.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- [opencommerce vs Zinc](https://www.anchorterminal.com/compare/opencommerce-vs-zinc.md)\n- [Shop MCP vs Zinc](https://www.anchorterminal.com/compare/shop-mcp-vs-zinc.md)\n- [Walmart Affiliate Marketing API vs Zinc](https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-zinc.md)\n- [Zillow in Claude vs Zinc](https://www.anchorterminal.com/compare/zillow-claude-vs-zinc.md)\n- [Instacart Developer Platform API + MCP vs MealMe API](https://www.anchorterminal.com/compare/instacart-vs-mealme.md)\n- [Walmart Agent Gateway vs Zinc](https://www.anchorterminal.com/compare/walmart-agent-gateway-vs-zinc.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-18",
    "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": "MealMe API vs Zinc",
        "url": ""
      }
    ],
    "description": "Zinc scores 69.9 (B) to MealMe's 39.7 (E) for product search for shoppers. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "MealMe API E 39.7",
      "Zinc B 69.9",
      "scores"
    ],
    "h1": "MealMe API vs Zinc",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/mealme-vs-zinc",
    "published": "2026-10-01",
    "section": "tools",
    "title": "MealMe vs Zinc for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/mealme-vs-zinc"
  },
  "tokens": {
    "markdown": 4450,
    "slim": 1080
  },
  "version": 1
}
