Head to head · Product search for shoppers · October 2026 research run
MealMe API vs Zinc
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.
Best shopping and order APIs for AI agents buying for a person · All 50 shopping comparisons
Best recipe, nutrition and meal planning APIs for AI agents · All 29 cooking comparisons
Which one, for what
Best for Agents that must place a real restaurant or grocery order in the US or Canada, or compare live prices across stores, and can hold a card on the account.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header
Zinc B
Best for Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.
Ahead on
- Reliability, 55 against 19
- Schema & documentation, 92 against 72
- Agent ergonomics, 86 against 69
- Security & auth, 57 against 26
- Payments & pricing, 98 against 30
- Maintenance & community, 83 against 6
- Transparency & trust, 60 against 47
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch 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"
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Zinc +77
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.
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.
Payments & pricing Zinc +68
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.
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.
Reliability Zinc +36
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.
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.
Security & auth Zinc +31
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.
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.
Schema & documentation Zinc +20
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.
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.
Agent ergonomics Zinc +17
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.
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.
Score by category
| Category | Weight | MealMe API | Zinc | Edge |
|---|---|---|---|---|
| Reliability | 16% | 19 | 55 | Zinc +36 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 72 | 92 | Zinc +20 |
| Agent ergonomics | 13% | 69 | 86 | Zinc +17 |
| Security & auth | 14% | 26 | 57 | Zinc +31 |
| Payments & pricing | 10% | 30 | 98 | Zinc +68 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 6 | 83 | Zinc +77 |
| Transparency & trust | 7% | 47 | 60 | Zinc +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 39.7/100 | B 69.9/100 |
Facts side by side
| Fact | MealMe API | Zinc |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | MealMe, Inc. | Zinc |
| Hosted endpoint | no (local only) | https://mcp.zinc.com/mcp |
| Transports | Streamable HTTP | |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | on some endpoints |
| Licence | Proprietary service under the MealMe API and SDK Terms of Use | Proprietary service, agent skills MIT |
| Tools exposed | 0 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.zinc.www/mcp |
| Last release | 2025-05-06 | 2026-11-13 |
| Terms last updated | 2025-04-04 | 2026-10-12 |
| Privacy policy last updated | 2025-04-04 | 2026-10-06 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
How the scores have moved
Zinc
No score change since it was listed.
Verdicts
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.
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.
Before you call either
MealMe API
- 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
Zinc
- Call
GET /retailers/checkwith the product URL and country before ordering, since unsupported retailers and countries fail predictably - Set
max_priceand anidempotency_keyon every order. If a retry returns 409, read the existing order id fromerror.details.order_id - If your HTTP client merges
WWW-Authenticateheaders, add?method=x402,?method=tempoor?method=stripeto get one payment challenge - Store the
X-Api-Keyreturned 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
Questions
Which is better for AI agents, MealMe API or Zinc?
Zinc scores 69.9 (B) on agent readiness against MealMe API's 39.7 (E), and leads in every scored category.
Do MealMe API and Zinc need an API key?
MealMe API needs an API key. Zinc takes an API key or an OAuth sign-in.
Can an agent call MealMe API and Zinc without installing anything?
No hosted endpoint is listed for MealMe API. Zinc has a hosted endpoint at https://mcp.zinc.com/mcp.
Other comparisons with MealMe API or Zinc
- Amazon Creators API vs MealMe API
- Amazon Creators API vs Zinc
- Best Buy Developer API vs MealMe API
- Best Buy Developer API vs Zinc
- Etsy Open API v3 vs MealMe API
- Etsy Open API v3 vs Zinc
- MealMe API vs opencommerce
- MealMe API vs Shop MCP
- MealMe API vs Walmart Affiliate Marketing API
- MealMe API vs Walmart Agent Gateway
- MealMe API vs Zillow in Claude
- opencommerce vs Zinc
- Shop MCP vs Zinc
- Walmart Affiliate Marketing API vs Zinc
- Zillow in Claude vs Zinc
- Instacart Developer Platform API + MCP vs MealMe API
- Walmart Agent Gateway vs Zinc
Machine-readable
- This page as Markdown
/compare/mealme-vs-zinc.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mealme.json·/api/v1/tools/zinc.json - From a terminal
anchor compare mealme zinc(the CLI) - Over MCP
compare_tools {"a": "mealme", "b": "zinc"}at/mcp, no key