{ "data": { "a": { "slug": "mealme", "name": "MealMe API", "vendor": "MealMe, Inc.", "vendorUrl": "https://www.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": 38.4, "grade": "E", "agentReady": false, "rank": 1229, "ranked": true, "rankOf": 1349, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 6, "payments": 20, "reliability": 19, "schema": 72, "security": 26, "transparency": 47 }, "pending": [ "performance", "tasks" ], "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": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 38.4 } ], "editorialScores": { "ergonomics": 69, "maintenance": 6, "payments": 20, "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", "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-04T15:53:11.510847421Z" }, "updatedAt": "2026-11-04T15:53:11.510847421Z" } }, "answer": "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.", "b": { "slug": "walmart-agent-gateway", "name": "Walmart Agent Gateway", "vendor": "Walmart Inc.", "vendorUrl": "https://corporate.walmart.com/news/2026/10/Making-It-Possible-for-Agents-to-Shop-on-Behalf-of-Customers", "kind": "mcp", "category": "shopping", "summary": "Walmart Agent Gateway is Walmart's announced MCP interface for AI agents that shop Walmart and Sam's Club for a customer. Announced on 21 October 2026, it starts as a beta by request for companies and developers, with no public endpoint.", "url": "https://www.anchorterminal.com/tools/walmart-agent-gateway", "markdownUrl": "https://www.anchorterminal.com/tools/walmart-agent-gateway.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/walmart-agent-gateway.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/walmart-agent-gateway.json", "dns": "walmart-agent-gateway.grade.anchorterminal.com", "license": "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", "transports": [], "packages": [], "auth": "mixed", "authNotes": "No credential model is published. Walmart's post says the gateway begins with a beta for companies and developers, reached through a link to www.walmart.com/agents, which answered with a bot check and was not read. For Agent Profiles, announced for about November 2026, the post says Walmart creates a profile the first time an agent shops through the gateway and the customer links it by signing in to their Walmart account. Today, per the post, an agent shopping for a customer signs in with the customer's own account (https://corporate.walmart.com/news/2026/10/Making-It-Possible-for-Agents-to-Shop-on-Behalf-of-Customers).", "pricing": "free", "pricingNotes": "No charge to agent developers is named on any page we could read. The post says agents see the same prices a person sees on Walmart.com, with applicable discounts and fees shown before purchase. Terms of the beta were not read (checked 2026-10-25).", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in Walmart's announcement of 21 October 2026, and no public endpoint to carry one. The post says agents don't receive payment-card information and can't add or change payment methods (checked 2026-10-25).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-25" }, "docsUrl": "https://corporate.walmart.com/news/2026/10/Making-It-Possible-for-Agents-to-Shop-on-Behalf-of-Customers", "capabilities": [ "shopping.orders", "shopping.search", "shopping.prices" ], "tags": [ "official", "hosted", "mcp", "closed-source", "beta", "early-access", "announced", "security-txt", "new" ], "graded": true, "anchor": { "graded": true, "score": 8.5, "grade": "F", "agentReady": false, "rank": 1341, "ranked": true, "rankOf": 1349, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 0, "payments": 10, "reliability": 5, "schema": 0, "security": 10, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-25" }, "negative": 0, "verdict": "Walmart has published terms for agents shopping its sites, including customer approval of purchases by default, no access to payment cards and blocking of agents that break them. The gateway is a beta by request for companies and developers, with no public endpoint, documentation, tool list or price, and Agent Profiles are announced for about November 2026.", "bestFor": "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.", "strengths": [ "Walmart's published terms require customer approval of agent purchases by default and let Walmart ask for more approvals within a limit", "Agents don't receive payment-card details and can't add or change a customer's payment methods, per the terms of 21 October 2026", "Walmart's returns process applies to agent purchases, including when an agent doesn't act as intended", "Walmart states agents see the same prices as people on Walmart.com, with fees shown before purchase" ], "weaknesses": [ "No public MCP endpoint, tool list, developer documentation or price was found on 25 October 2026", "Access is a beta for companies and developers by request; the beta page sits behind a bot check and its conditions were not read", "Agent Profiles, with per-agent spending limits and separate purchase history, are announced for about November 2026 and not live", "The full terms for AI agents were not found as a readable page; only the post's summary of them was read", "No status page, changelog, rate limits or MCP registry entry for the gateway was found" ], "agentNotes": [ "Don't look for a public endpoint; Walmart hasn't published one, and the gateway starts as a beta for approved companies and developers", "Ask your human for approval before any Walmart purchase; Walmart's terms require it by default and block agents that act beyond the shopper's intent", "Don't request or store the customer's card details; Walmart's terms bar agents from payment-card data and payment-method changes", "Treat claims that ChatGPT, Gemini or Muse already connect through the gateway as Reuters's reporting; Walmart's own post doesn't say so" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 8.5 } ], "editorialScores": { "ergonomics": 0, "maintenance": 0, "payments": 10, "reliability": 5, "schema": 0, "security": 10, "transparency": 31 }, "provenanceScore": 71, "checked": { "categories": { "ergonomics": "2026-10-25", "maintenance": "2026-10-25", "payments": "2026-10-25", "reliability": "2026-10-25", "schema": "2026-10-25", "security": "2026-10-25", "transparency": "2026-10-25" }, "last": "2026-10-25", "lastMoved": "2026-10-28", "oldest": "2026-10-25", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/shopping.orders", "tool": "https://letme.dev/walmart-agent-gateway" }, "sameCompany": [ "walmart-affiliate-api" ], "area": "everyday", "provenance": { "legalEntity": "Walmart Inc.", "domain": "walmart.com", "domainRegistered": "1995-02-23", "endpointOnVendorDomain": null, "terms": "https://www.walmart.com/help/article/walmart-com-terms-of-use/3b75080af40340d6bbd596f116fae5a0", "privacy": "https://corporate.walmart.com/privacy-security/walmart-privacy-notice", "statusPage": "", "changelog": "", "securityTxt": "valid", "checked": "2026-10-25", "notes": [ "The announcement's footer reads © 2026 Walmart Inc. No page read names the legal entity that runs the gateway or its beta. The walmart-affiliate-api listing names Wal-Mart.com USA, LLC for walmart.com's API terms.", "The terms URL is the walmart.com Terms of Use recorded on the walmart-affiliate-api listing on 14 October 2026. www.walmart.com answers our reader with a bot check, so it was not read today. The terms for AI agents exist only as the summary in the post; no full document was found.", "The Walmart Customer Privacy Notice (Online and In-Store) shows Updated August 20, 2026. It says nothing about agents or the gateway. The post says the agent's own privacy policy covers what the agent receives and Walmart's Privacy Notice covers what the agent gives Walmart.", "www.walmart.com/.well-known/security.txt gives a Contact (the responsible disclosure policy on corporate.walmart.com), a Policy, a Canonical and Preferred-Languages, with no Expires field. Recorded as valid, as on the walmart-affiliate-api listing.", "No endpoint is published, so endpointOnVendorDomain is left empty. No status page or changelog for the gateway was found.", "RDAP for walmart.com gives a registration date of 23 February 1995.", "robots.txt was read first on corporate.walmart.com (allows ClaudeBot on the post), www.walmart.com (allows /agents), developer.walmart.com and www.ksl.com. www.walmart.com/agents answered with a bot check, which we did not try to get past." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/walmart-agent-gateway.json", "live": { "slug": "walmart-agent-gateway", "securityTxt": { "url": "https://walmart.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:54:44.16026327Z" }, "domain": { "domain": "walmart.com", "registered": "1995-02-23", "source": "https://rdap.verisign.com/com/v1/domain/walmart.com", "checkedAt": "2026-11-01T14:20:47.071777296Z" }, "updatedAt": "2026-11-04T15:54:44.16026327Z" } }, "edges": [ { "by": 72, "category": "schema", "leads": "mealme", "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": "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." }, "scores": { "a": 72, "b": 0 } }, { "by": 69, "category": "ergonomics", "leads": "mealme", "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": "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." }, "scores": { "a": 69, "b": 0 } }, { "by": 16, "category": "security", "leads": "mealme", "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": "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." }, "scores": { "a": 26, "b": 10 } }, { "by": 14, "category": "reliability", "leads": "mealme", "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": "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." }, "scores": { "a": 19, "b": 5 } }, { "by": 10, "category": "payments", "leads": "mealme", "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.", "b": "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." }, "scores": { "a": 20, "b": 10 } }, { "by": 6, "category": "maintenance", "leads": "mealme", "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": "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." }, "scores": { "a": 6, "b": 0 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "MealMe, Inc.", "b": "Walmart Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the MealMe API and SDK Terms of Use", "b": "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", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2025-05-06", "b": "none", "name": "Last release" }, { "a": "2025-04-04", "b": "2026-09-09", "name": "Terms last updated" }, { "a": "2025-04-04", "b": "2026-08-20", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "MealMe API scores 38.4 (E) on agent readiness against Walmart Agent Gateway's 8.5 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, MealMe API or Walmart Agent Gateway?" }, { "answer": "MealMe API needs an API key. Walmart Agent Gateway takes an API key or an OAuth sign-in.", "question": "Do MealMe API and Walmart Agent Gateway need an API key?" }, { "answer": "No hosted endpoint is listed for MealMe API. No hosted endpoint is listed for Walmart Agent Gateway.", "question": "Can an agent call MealMe API and Walmart Agent Gateway without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 19 against 5", "Schema \u0026 documentation, 72 against 0", "Agent ergonomics, 69 against 0", "Security \u0026 auth, 26 against 10", "Payments \u0026 pricing, 20 against 10", "Maintenance \u0026 community, 6 against 0" ], "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": null, "also": null, "goodFor": "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.", "slug": "walmart-agent-gateway", "watchFor": "No public MCP endpoint, tool list, developer documentation or price was found on 25 October 2026" } ], "history": { "mealme": null, "walmart-agent-gateway": [ { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 8.4, "fromGrade": "F", "to": 8.5, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 8.3, "fromGrade": "F", "to": 8.4, "toGrade": "F" } ] }, "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-walmart-agent-gateway.json", "title": "Amazon Creators API vs Walmart Agent Gateway", "url": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-walmart-agent-gateway" }, { "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-walmart-agent-gateway.json", "title": "Best Buy Developer API vs Walmart Agent Gateway", "url": "https://www.anchorterminal.com/compare/best-buy-vs-walmart-agent-gateway" }, { "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-walmart-agent-gateway.json", "title": "Etsy Open API v3 vs Walmart Agent Gateway", "url": "https://www.anchorterminal.com/compare/etsy-vs-walmart-agent-gateway" }, { "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-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-walmart-agent-gateway.json", "title": "opencommerce vs Walmart Agent Gateway", "url": "https://www.anchorterminal.com/compare/opencommerce-vs-walmart-agent-gateway" }, { "json": "https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-agent-gateway.json", "title": "Shop MCP vs Walmart Agent Gateway", "url": "https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-agent-gateway" }, { "json": "https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-walmart-agent-gateway.json", "title": "Walmart Affiliate Marketing API vs Walmart Agent Gateway", "url": "https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-walmart-agent-gateway" }, { "json": "https://www.anchorterminal.com/compare/walmart-agent-gateway-vs-zillow-claude.json", "title": "Walmart Agent Gateway vs Zillow in Claude", "url": "https://www.anchorterminal.com/compare/walmart-agent-gateway-vs-zillow-claude" }, { "json": "https://www.anchorterminal.com/compare/instacart-vs-mealme.json", "title": "Instacart Developer Platform API + MCP vs MealMe API", "url": "https://www.anchorterminal.com/compare/instacart-vs-mealme" } ], "panel": null, "scores": [ { "by": 14, "edge": "mealme", "key": "reliability", "mealme": 19, "name": "Reliability", "walmart-agent-gateway": 5, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 72, "edge": "mealme", "key": "schema", "mealme": 72, "name": "Schema \u0026 documentation", "walmart-agent-gateway": 0, "weight": 13 }, { "by": 69, "edge": "mealme", "key": "ergonomics", "mealme": 69, "name": "Agent ergonomics", "walmart-agent-gateway": 0, "weight": 13 }, { "by": 16, "edge": "mealme", "key": "security", "mealme": 26, "name": "Security \u0026 auth", "walmart-agent-gateway": 10, "weight": 14 }, { "by": 10, "edge": "mealme", "key": "payments", "mealme": 20, "name": "Payments \u0026 pricing", "walmart-agent-gateway": 10, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "mealme", "key": "maintenance", "mealme": 6, "name": "Maintenance \u0026 community", "walmart-agent-gateway": 0, "weight": 7 }, { "by": 4, "edge": "walmart-agent-gateway", "key": "transparency", "mealme": 47, "name": "Transparency \u0026 trust", "walmart-agent-gateway": 51, "weight": 7 } ], "summary": "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.", "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.", "walmart-agent-gateway": "Walmart has published terms for agents shopping its sites, including customer approval of purchases by default, no access to payment cards and blocking of agents that break them. The gateway is a beta by request for companies and developers, with no public endpoint, documentation, tool list or price, and Agent Profiles are announced for about November 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway", "json": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.min.md" }, "markdown": "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.\n\n- MealMe API: grade E, 38.4/100, rank #1229 of 1349. Markdown https://www.anchorterminal.com/tools/mealme.md · JSON https://www.anchorterminal.com/api/v1/tools/mealme.json\n- Walmart Agent Gateway: grade F, 8.5/100, rank #1341 of 1349. Markdown https://www.anchorterminal.com/tools/walmart-agent-gateway.md · JSON https://www.anchorterminal.com/api/v1/tools/walmart-agent-gateway.json\n- Best shopping and order APIs for AI agents buying for a person: https://www.anchorterminal.com/best/shopping/index.md\n- All 41 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 28 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\nAhead on:\n- Reliability, 19 against 5\n- Schema \u0026 documentation, 72 against 0\n- Agent ergonomics, 69 against 0\n- Security \u0026 auth, 26 against 10\n- Payments \u0026 pricing, 20 against 10\n- Maintenance \u0026 community, 6 against 0\n\nWatch for: One key with no scopes, read-only mode, expiry or rotation documented, sent in a custom Id-Token header\n\n### Walmart Agent Gateway (F)\n\nGood 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.\n\nWatch for: No public MCP endpoint, tool list, developer documentation or price was found on 25 October 2026\n\n\n## Why the edge\n\n### Schema \u0026 documentation: MealMe API +72\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- 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.\n\n### Agent ergonomics: MealMe API +69\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- 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.\n\n### Security \u0026 auth: MealMe API +16\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- 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.\n\n### Reliability: MealMe API +14\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- 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.\n\n### Payments \u0026 pricing: MealMe API +10\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: MealMe API +6\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- 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.\n\n## Score by category\n\n| Category | Weight | MealMe API | Walmart Agent Gateway | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 19 | 5 | MealMe API +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 0 | MealMe API +72 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 0 | MealMe API +69 |\n| Security \u0026 auth | 14% (17.5 this run) | 26 | 10 | MealMe API +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 10 | MealMe API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 6 | 0 | MealMe API +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 47 | 51 | Walmart Agent Gateway +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **38.4 · E** | **8.5 · F** | |\n\n## Facts side by side\n\n| Fact | MealMe API | Walmart Agent Gateway |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | MealMe, Inc. | Walmart Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2025-05-06 | none |\n| Terms last updated | 2025-04-04 | 2026-09-09 |\n| Privacy policy last updated | 2025-04-04 | 2026-08-20 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n\n## How the scores have moved\n\n### MealMe API\n\nNo score change since it was listed.\n\n### Walmart Agent Gateway\n\n- +0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\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**Walmart Agent Gateway.** Walmart has published terms for agents shopping its sites, including customer approval of purchases by default, no access to payment cards and blocking of agents that break them. The gateway is a beta by request for companies and developers, with no public endpoint, documentation, tool list or price, and Agent Profiles are announced for about November 2026.\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### Walmart Agent Gateway\n\n1. Don't look for a public endpoint; Walmart hasn't published one, and the gateway starts as a beta for approved companies and developers\n2. Ask your human for approval before any Walmart purchase; Walmart's terms require it by default and block agents that act beyond the shopper's intent\n3. Don't request or store the customer's card details; Walmart's terms bar agents from payment-card data and payment-method changes\n4. Treat claims that ChatGPT, Gemini or Muse already connect through the gateway as Reuters's reporting; Walmart's own post doesn't say so\n\n## Questions\n\n### Which is better for AI agents, MealMe API or Walmart Agent Gateway?\n\nMealMe API scores 38.4 (E) on agent readiness against Walmart Agent Gateway's 8.5 (F), and leads in 6 of 7 scored categories.\n\n### Do MealMe API and Walmart Agent Gateway need an API key?\n\nMealMe API needs an API key. Walmart Agent Gateway takes an API key or an OAuth sign-in.\n\n### Can an agent call MealMe API and Walmart Agent Gateway without installing anything?\n\nNo hosted endpoint is listed for MealMe API. No hosted endpoint is listed for Walmart Agent Gateway.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mealme\", \"b\": \"walmart-agent-gateway\"}`. From a terminal: `anchor compare mealme walmart-agent-gateway`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mealme.json and https://www.anchorterminal.com/api/v1/tools/walmart-agent-gateway.json\n\n## Other comparisons with MealMe API or Walmart Agent Gateway\n\n- [Amazon Creators API vs MealMe API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-mealme.md)\n- [Amazon Creators API vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/amazon-creators-api-vs-walmart-agent-gateway.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 Walmart Agent Gateway](https://www.anchorterminal.com/compare/best-buy-vs-walmart-agent-gateway.md)\n- [Etsy Open API v3 vs MealMe API](https://www.anchorterminal.com/compare/etsy-vs-mealme.md)\n- [Etsy Open API v3 vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/etsy-vs-walmart-agent-gateway.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 Zillow in Claude](https://www.anchorterminal.com/compare/mealme-vs-zillow-claude.md)\n- [opencommerce vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/opencommerce-vs-walmart-agent-gateway.md)\n- [Shop MCP vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-agent-gateway.md)\n- [Walmart Affiliate Marketing API vs Walmart Agent Gateway](https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-walmart-agent-gateway.md)\n- [Walmart Agent Gateway vs Zillow in Claude](https://www.anchorterminal.com/compare/walmart-agent-gateway-vs-zillow-claude.md)\n- [Instacart Developer Platform API + MCP vs MealMe API](https://www.anchorterminal.com/compare/instacart-vs-mealme.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "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 Walmart Agent Gateway", "url": "" } ], "description": "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.", "facts": [ "MealMe API E 38.4", "Walmart Agent Gateway F 8.5", "scores" ], "h1": "MealMe API vs Walmart Agent Gateway", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/mealme-vs-walmart-agent-gateway", "published": "2026-10-01", "section": "tools", "title": "MealMe vs Walmart Agent Gateway for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/mealme-vs-walmart-agent-gateway" }, "tokens": { "markdown": 4250, "slim": 2430 }, "version": 1 }