# MealMe API vs Zinc (slim)

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

- Full: https://www.anchorterminal.com/compare/mealme-vs-zinc.md (~4,450 tokens) · this version ~1,080 tokens · JSON https://www.anchorterminal.com/compare/mealme-vs-zinc.json · canonical https://www.anchorterminal.com/compare/mealme-vs-zinc
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- MealMe API: E 39.7, rank #1386 of 1557 · https://www.anchorterminal.com/tools/mealme.min.md
- Zinc: B 69.9, rank #320 of 1557 · https://www.anchorterminal.com/tools/zinc.min.md
- MealMe API, good for Agents that must place a real restaurant or grocery order in the US or Canada, or compare live prices across stores, and can hold a card on the account.
- Zinc, good 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 A hosted endpoint, with nothing to install; Free to start without a card.

| Category | MealMe API | Zinc |
| --- | --- | --- |
| Reliability (16%) | 19 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 92 |
| Agent ergonomics (13%) | 69 | 86 |
| Security & auth (14%) | 26 | 57 |
| Payments & pricing (10%) | 30 | 98 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 6 | 83 |
| Transparency & trust (7%) | 47 | 60 |

| Fact (where they differ) | MealMe API | Zinc |
| --- | --- | --- |
| Vendor | MealMe, Inc. | Zinc |
| Hosted endpoint | no (local only) | `https://mcp.zinc.com/mcp` |
| Transports |  | Streamable HTTP |
| Auth | API key | OAuth or key |
| 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 |
| 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 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |

Why the edge:
- Maintenance & community, Zinc +77: MealMe API 6 (Read as a closed service.); Zinc 83 (The changelog's latest entry is dated 13 November 2026, and the npm SDK's latest version is 2026.10.30 (30).)
- Payments & pricing, Zinc +68: MealMe API 30 (No x402, MPP or L402 (0).); 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.)
- Reliability, Zinc +36: MealMe API 19 (Read with the hosted lines.); 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).)
- 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).); 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.)
- 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 par…); 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).)
- 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…); Zinc 86 (Search returns up to 20 results, best first, and data and order calls are separate routes, so responses stay small.)
