# MealMe API vs Walmart Agent Gateway (slim)

> MealMe scores 38.4 (E) to Walmart Agent Gateway's 8.5 (F) for product search for shoppers. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.md (~4,250 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.json · canonical https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway
- 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-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MealMe API scores 38.4 (E) on agent readiness against Walmart Agent Gateway's 8.5 (F), and leads in 6 of 7 scored categories. Both do product search for shoppers.

- MealMe API: E 38.4, rank #1229 of 1349 · https://www.anchorterminal.com/tools/mealme.min.md
- Walmart Agent Gateway: F 8.5, rank #1341 of 1349 · https://www.anchorterminal.com/tools/walmart-agent-gateway.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. Ahead on Reliability, 19 against 5; Schema & documentation, 72 against 0; Agent ergonomics, 69 against 0; Security & auth, 26 against 10; Payments & pricing, 20 against 10; Maintenance & community, 6 against 0.
- Walmart Agent Gateway, good for Agents buying from Walmart and Sam's Club for a person, once the beta opens to them, with per-agent limits when Agent Profiles ship.

| Category | MealMe API | Walmart Agent Gateway |
| --- | --- | --- |
| Reliability (16%) | 19 | 5 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 0 |
| Agent ergonomics (13%) | 69 | 0 |
| Security & auth (14%) | 26 | 10 |
| Payments & pricing (10%) | 20 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 6 | 0 |
| Transparency & trust (7%) | 47 | 51 |

| Fact (where they differ) | MealMe API | Walmart Agent Gateway |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | MealMe, Inc. | Walmart Inc. |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Free |
| Licence | Proprietary service under the MealMe API and SDK Terms of Use | Proprietary hosted service. Walmart's terms for AI agents are summarised in its announcement of 21 October 2026; no full terms document was found on a page we could read |
| Tools exposed | 0 | none |
| llms.txt | yes | no |
| Last release | 2025-05-06 | none |
| Terms last updated | 2025-04-04 | 2026-09-09 |
| Privacy policy last updated | 2025-04-04 | 2026-08-20 |
| Customer content may train models | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |

Why the edge:
- Schema & documentation, MealMe API +72: 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.); Walmart Agent Gateway 0 (Every line needs a published contract or documentation, and none exists that we could read. No endpoint, tool list, JSON Schema or OpenAPI file (0 of 25). No llms.txt or Markdown docs for the gateway. The beta page at www.walmart.com/agents answered with a bot check and was not read (0 of 10). No tool descriptions (0 of 20), typed inputs (0 of 15), examples or error responses (0 of 15), versions or changelog (0 of 15). The post describes the product's purpose, which is not a tool description. Total 0.)
- Agent ergonomics, MealMe API +69: 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.); Walmart Agent Gateway 0 (Every line needs a tool list or documentation. With no published tools, context cost, pagination and output controls, errors, retries and annotations, and defaults or SDKs have nothing to score (0 on each line), the reading Claude Duet got on 24 October for an interface outside agents can't reach. Total 0.)
- Security & auth, MealMe API +16: 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.); Walmart Agent Gateway 10 (Graded on the interface an outside agent can call, the reading Claude Duet got. With no published endpoint or credential model, the credential, least-privilege, injection and audit lines score nothing (0 of 30, 0 of 20, 0 of 15, 0 of 15). Walmart's terms for agents (approval by default, no card data, no payment-method changes, least information, blocking) and the announced Agent Profile controls are in forReviewers, unverified. The security programme line doesn't need an interface. www.walmart.com/.well-known/security.txt points to a responsible disclosure policy with safe harbour, discretionary rewards and a submission form hosted by HackerOne, and has no Expires field. No certification was checked. The walmart-affiliate-api dossier gave the same record 10 (10 of 20). 0 + 0 + 0 + 0 + 10 = 10.)
- Reliability, MealMe API +14: 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.); Walmart Agent Gateway 5 (Read with the hosted lines, on what can be read today, which is Walmart's announcement of 21 October 2026. No status page for the gateway was found (0 of 20). With no page there is no readable incident history (5 of 30). No rate limits published (0 of 15). No 429, retry or idempotency guidance (0 of 15). No SLA (0 of 10). Walmart says it is building the gateway and starting with a beta for companies and developers, so not generally available (0 of 10). Total 5.)
- Payments & pricing, MealMe API +10: MealMe API 20 (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.); Walmart Agent Gateway 10 (Read with the hosted rule. No x402, MPP or L402, and no endpoint to carry one (0 of 40). No charge to developers is named; the post says agents see Walmart.com prices with fees shown before purchase. Nothing says the gateway is free either, the Zillow in Claude reading (10 of 20). Access is a beta by request whose terms weren't read, so no free tier without a card can be shown (0 of 20). A company or developer has to request beta access and a customer has to sign in to Walmart, so no autonomous onboarding (0 of 20). 0 + 10 + 0 + 0 = 10.)
- Maintenance & community, MealMe API +6: 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.); Walmart Agent Gateway 0 (Read as a closed service. No release, version, published API change or release note for the gateway was found. The announcement of 21 October 2026 is recorded but isn't a release, and the line would score once the gateway or Agent Profiles ship (0 of 30). No dated entries in the last 90 days (0 of 20). No changelog, developer forum or support channel for the gateway was found. The beta page was unread (0 of 15). No Walmart-owned entry in the official MCP registry on 25 October 2026, only third-party Walmart servers, and no SDK (0 of 15). No package, repository or CI (0 of 10). Total 0.)