{ "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": 1231, "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": "Walmart Affiliate Marketing API and MealMe API score within a point of each other on agent readiness, 38.8 (E) and 38.4 (E). MealMe API leads on schema \u0026 documentation and agent ergonomics.", "b": { "slug": "walmart-affiliate-api", "name": "Walmart Affiliate Marketing API", "vendor": "Wal-Mart.com USA, LLC (Walmart Inc.)", "vendorUrl": "https://walmart.io/docs/affiliates/v1/introduction", "kind": "http-api", "category": "shopping", "summary": "Walmart's read-only catalogue API for affiliates, documented on the Walmart I/O portal. It searches Walmart.com products and returns item details, reviews, taxonomy, trending items, recommendations and nearby stores, with affiliate links tracked through Impact. It cannot place orders.", "url": "https://www.anchorterminal.com/tools/walmart-affiliate-api", "markdownUrl": "https://www.anchorterminal.com/tools/walmart-affiliate-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/walmart-affiliate-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/walmart-affiliate-api.json", "dns": "walmart-affiliate-api.grade.anchorterminal.com", "license": "Proprietary service under the Walmart I/O API Terms of Use (last updated 30 September 2020)", "transports": [ "http" ], "remoteUrl": "https://developer.api.walmart.com/api-proxy/service/affil/product/v2", "packages": [], "auth": "api-key", "authNotes": "Each request is signed. The developer creates an application on walmart.io, uploads an RSA public key and receives a consumer ID with a key version. Calls carry WM_CONSUMER.ID, WM_CONSUMER.INTIMESTAMP, WM_SEC.KEY_VERSION and WM_SEC.AUTH_SIGNATURE, a signature made with the private key that expires after 180 seconds. Sandbox and production consumer IDs are separate. Affiliate links use an Impact Radius publisher ID.", "pricing": "free", "pricingNotes": "No fee for the API was found. It is free to approved affiliates, who earn commission on referred sales. The API terms cap use at 5,000 calls a day, with higher limits on request. The 2020 terms quote 4 per cent commission, or 1 per cent on electronics, video games, films, music, books and photo goods (checked 14 October 2026).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Walmart I/O portal code, the affiliate API terms or the request headers it documents (checked 14 October 2026).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://walmart.io/docs/affiliates/v1/introduction", "capabilities": [ "shopping.search", "shopping.prices", "shopping.affiliate" ], "tags": [ "hosted", "official", "affiliate", "read-only", "no-checkout", "signed-requests" ], "graded": true, "anchor": { "graded": true, "score": 38.8, "grade": "E", "agentReady": false, "rank": 1225, "ranked": true, "rankOf": 1349, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 5, "payments": 25, "reliability": 33, "schema": 27, "security": 58, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-14" }, "negative": 0, "verdict": "Live, free catalogue search and product lookup for approved Walmart affiliates, signed with an RSA key and capped at 5,000 calls a day. It cannot place or follow orders, and the Checkout API needs separate approval. The documentation renders only in a browser, and the API terms date from 2020 and still name a previous affiliate network.", "bestFor": "Product search and affiliate links for an agent recommending Walmart products and handing the purchase to the person.", "strengths": [ "Read-only search, lookup by item ID or UPC, reviews, taxonomy, trending items and store lookup in one API", "Request signing with an RSA private key that is never sent, and signatures that expire after 180 seconds", "Separate sandbox and production consumer IDs", "The daily limit of 5,000 calls is stated, with a route to ask for more" ], "weaknesses": [ "No order, cart, order status or return operation in the affiliate API", "The documentation is rendered by browser script, with no OpenAPI, llms.txt or Markdown", "The API terms were last updated on 30 September 2020 and name Rakuten LinkShare, not Impact", "No status page, changelog or official SDK was found", "The walmart.com Terms of Use answered with a bot check, so rules for automated buyers on the store were not read" ], "agentNotes": [ "Generate a fresh WM_SEC.AUTH_SIGNATURE for each call, because a signature older than 180 seconds is rejected", "Keep below 5,000 calls a day per application", "Pass the Impact publisher ID so returned links earn commission", "Hand purchases to the person through the returned product link, since the affiliate API cannot check out" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 38.8 } ], "editorialScores": { "ergonomics": 57, "maintenance": 5, "payments": 25, "reliability": 33, "schema": 27, "security": 58, "transparency": 34 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-10-14", "maintenance": "2026-10-14", "payments": "2026-10-14", "reliability": "2026-10-14", "schema": "2026-10-14", "security": "2026-10-14", "transparency": "2026-10-14" }, "last": "2026-10-14", "lastMoved": "2026-10-28", "oldest": "2026-10-14", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/shopping.search", "tool": "https://letme.dev/walmart-affiliate-api" }, "sameCompany": [ "walmart-agent-gateway" ], "area": "everyday", "provenance": { "legalEntity": "Wal-Mart.com USA, LLC", "domain": "walmart.com", "domainRegistered": "1995-02-23", "endpointOnVendorDomain": true, "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-14", "notes": [ "The API endpoint is developer.api.walmart.com and the documentation is on walmart.io, registered 2012-05-22.", "The Walmart I/O API Terms of Use (last updated 30 September 2020) are shown inside the portal with no page of their own. The walmart.com Terms of Use answered with a bot check and were not read.", "The privacy notice was updated 20 August 2026 and names Wal-Mart.com USA, LLC, 850 Cherry Ave., San Bruno, CA as controller for the Canada and Mexico sections. The affiliate terms give the same San Bruno address.", "www.walmart.com/.well-known/security.txt points to the responsible disclosure policy and has no Expires field.", "RDAP for walmart.com gives a registration date of 1995-02-23." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/walmart-affiliate-api.json", "live": { "slug": "walmart-affiliate-api", "probe": { "target": "https://developer.api.walmart.com/api-proxy/service/affil/product/v2", "method": "get", "lastAt": "2026-11-04T20:05:33.868135423Z", "lastOk": true, "lastStatus": 403, "lastMs": 199, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.98, "p50ms24h": 210, "p95ms24h": 609, "samples24h": 246, "samples30d": 5396, "days": [ { "date": "2026-10-14", "probes": 166, "ok": 166 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 207, "ok": 207 } ] }, "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" }, "pages": [ { "url": "https://corporate.walmart.com/privacy-security/walmart-privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:17:18.115321985Z", "changedAt": "2026-10-19T23:53:24.90260261Z", "fingerprint": "5c25bb2d9801" }, { "url": "https://www.walmart.com/help/article/walmart-com-terms-of-use/3b75080af40340d6bbd596f116fae5a0", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:47:18.245064365Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "123b123cead2" } ], "updatedAt": "2026-11-04T20:05:33.868135423Z" } }, "edges": [ { "by": 45, "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": "No OpenAPI or machine-readable description for the affiliate API. Its specification page is marked as not a Swagger document (0 of 25). No llms.txt or Markdown, and pages render only through browser script (0 of 10). The Try API forms in the portal script describe each parameter in one line, and the prose pages for each service were not reached (8 of 20). Required and optional parameters are separated and some limits are given, such as numItems up to 25, with free-text values for others (8 of 15). Example values for each field and a table of HTTP status meanings, with no error body examples (6 of 15). The version is in the path (v2) and the live service reports version 2.0.0, with no changelog found (5 of 15). Total 27." }, "scores": { "a": 72, "b": 27 } }, { "by": 32, "category": "security", "leads": "walmart-affiliate-api", "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": "Requests are signed with the developer's RSA private key, which is never sent, and signatures expire after 180 seconds. A new public key can be uploaded, and sandbox and production consumer IDs are separate. There are no scopes beyond the subscribed product (22 of 30). The affiliate API only reads, so it cannot buy or change an account. Checkout sits behind a separate approval (15 of 20). Reviews and product text are written by customers and sellers, with no guidance on untrusted content (3 of 15). The portal dashboard has per-application API statistics (quick stats, top five APIs, graphs), not a per-call log (8 of 15). www.walmart.com/.well-known/security.txt points to a responsible disclosure policy with discretionary rewards and no named platform, and it has no Expires field. No certification was checked (10 of 20). Total 58." }, "scores": { "a": 26, "b": 58 } }, { "by": 14, "category": "reliability", "leads": "walmart-affiliate-api", "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": "No status page was found. status.walmart.io did not answer and the portal links none (0 of 20). No readable incident history, so the 5-point default (5 of 30). The API terms state 5,000 calls a day (15 of 15). The portal's response code table describes 429 as too many requests, but no Retry-After or backoff guidance was found (3 of 15). No SLA (0 of 10). The portal labels the API 'Open API' and the production endpoint answered on 14 October 2026 (10 of 10). Total 33." }, "scores": { "a": 19, "b": 33 } }, { "by": 12, "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": "responseGroup base or full and numItems up to 25 size responses, without field selection (15 of 25). Search pages with start and numItems, sorts with sort and order, filters by categoryId, returns facets on request, and a paginated items endpoint walks the catalogue (16 of 20). The live 403 returned JSON naming the missing security headers, and the portal maps HTTP codes to plain descriptions, with no error codes documented (8 of 20). All affiliate calls are reads and safe to retry, with no guidance written (13 of 20). Only query is required for search. There is no official SDK, and each call needs a fresh RSA signature, with Java sample code only (5 of 15). Total 57." }, "scores": { "a": 69, "b": 57 } }, { "by": 8, "category": "transparency", "leads": "walmart-affiliate-api", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. The API and SDK Terms of Use (18 June 2022) and MealMe Connect terms (4 April 2025) name MealMe, Inc. under Delaware law, but the API terms license use for personal, noncommercial purposes while the product is sold to businesses (15 of 30). The privacy policy of 1 January 2025 keeps data as long as needed, names no subprocessor and no DPA; the cookie policy names Google, Adobe, LinkedIn, Twitter and Facebook (10 of 30). Release notes record breaking changes with dates but there is no deprecation policy or notice period (6 of 20). Cookie providers named, no subprocessor list or data location (4 of 20). Total 35.", "b": "Closed service with API terms shown in the portal, last updated 30 September 2020. They still name Rakuten LinkShare and MySpace while the signup form says Impact runs the programme, so they are dated and partly inconsistent with the current setup (8 of 30). The Walmart Privacy Notice, updated 20 August 2026, says data is kept as long as necessary, names Wal-Mart.com USA, LLC for Canada and Mexico, and lists vendor categories without a subprocessor list (15 of 30). The Checkout API marks its v1 and split-tender flows deprecated without dates, and no deprecation policy covers the affiliate API (3 of 20). Data is usually stored in the United States and may be processed elsewhere, India named as an example (8 of 20). Total 34." }, "scores": { "a": 47, "b": 55 } }, { "by": 5, "category": "payments", "leads": "walmart-affiliate-api", "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": "No x402, MPP or L402 (0 of 40). No fee for calls is stated. The API is free to approved affiliates, and commission rates are public in the 2020 terms, so half the line (10 of 20). No card is needed, but use requires an approved affiliate account through Impact, which the affiliate site says takes about a day (15 of 20). Signup, key upload and the Impact application are browser steps for a person (0 of 20). Total 25." }, "scores": { "a": 20, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "MealMe, Inc.", "b": "Wal-Mart.com USA, LLC (Walmart Inc.)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://developer.api.walmart.com/api-proxy/service/affil/product/v2", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API 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 service under the Walmart I/O API Terms of Use (last updated 30 September 2020)", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "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" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Walmart Affiliate Marketing API and MealMe API score within a point of each other on agent readiness, 38.8 (E) and 38.4 (E). MealMe API leads on schema \u0026 documentation and agent ergonomics.", "question": "Which is better for AI agents, MealMe API or Walmart Affiliate Marketing API?" }, { "answer": "Both need an API key.", "question": "Do MealMe API and Walmart Affiliate Marketing API need an API key?" }, { "answer": "No hosted endpoint is listed for MealMe API. Walmart Affiliate Marketing API has a hosted endpoint at https://developer.api.walmart.com/api-proxy/service/affil/product/v2.", "question": "Can an agent call MealMe API and Walmart Affiliate Marketing API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 72 against 27", "Agent ergonomics, 69 against 57" ], "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, 33 against 19", "Security \u0026 auth, 58 against 26", "Payments \u0026 pricing, 25 against 20", "Transparency \u0026 trust, 55 against 47" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Product search and affiliate links for an agent recommending Walmart products and handing the purchase to the person.", "slug": "walmart-affiliate-api", "watchFor": "No order, cart, order status or return operation in the affiliate API" } ], "history": { "mealme": null, "walmart-affiliate-api": [ { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.2, "from": 38.6, "fromGrade": "E", "to": 38.8, "toGrade": "E" } ] }, "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-affiliate-api.json", "title": "Amazon Creators API vs Walmart Affiliate Marketing API", "url": "https://www.anchorterminal.com/compare/amazon-creators-api-vs-walmart-affiliate-api" }, { "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-affiliate-api.json", "title": "Best Buy Developer API vs Walmart Affiliate Marketing API", "url": "https://www.anchorterminal.com/compare/best-buy-vs-walmart-affiliate-api" }, { "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-affiliate-api.json", "title": "Etsy Open API v3 vs Walmart Affiliate Marketing API", "url": "https://www.anchorterminal.com/compare/etsy-vs-walmart-affiliate-api" }, { "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-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-walmart-affiliate-api.json", "title": "opencommerce vs Walmart Affiliate Marketing API", "url": "https://www.anchorterminal.com/compare/opencommerce-vs-walmart-affiliate-api" }, { "json": "https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-affiliate-api.json", "title": "Shop MCP vs Walmart Affiliate Marketing API", "url": "https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-affiliate-api" }, { "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-affiliate-api-vs-zillow-claude.json", "title": "Walmart Affiliate Marketing API vs Zillow in Claude", "url": "https://www.anchorterminal.com/compare/walmart-affiliate-api-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" }, { "json": "https://www.anchorterminal.com/compare/instacart-vs-walmart-affiliate-api.json", "title": "Instacart Developer Platform API + MCP vs Walmart Affiliate Marketing API", "url": "https://www.anchorterminal.com/compare/instacart-vs-walmart-affiliate-api" } ], "panel": null, "scores": [ { "by": 14, "edge": "walmart-affiliate-api", "key": "reliability", "mealme": 19, "name": "Reliability", "walmart-affiliate-api": 33, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 45, "edge": "mealme", "key": "schema", "mealme": 72, "name": "Schema \u0026 documentation", "walmart-affiliate-api": 27, "weight": 13 }, { "by": 12, "edge": "mealme", "key": "ergonomics", "mealme": 69, "name": "Agent ergonomics", "walmart-affiliate-api": 57, "weight": 13 }, { "by": 32, "edge": "walmart-affiliate-api", "key": "security", "mealme": 26, "name": "Security \u0026 auth", "walmart-affiliate-api": 58, "weight": 14 }, { "by": 5, "edge": "walmart-affiliate-api", "key": "payments", "mealme": 20, "name": "Payments \u0026 pricing", "walmart-affiliate-api": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "edge": "mealme", "key": "maintenance", "mealme": 6, "name": "Maintenance \u0026 community", "walmart-affiliate-api": 5, "weight": 7 }, { "by": 8, "edge": "walmart-affiliate-api", "key": "transparency", "mealme": 47, "name": "Transparency \u0026 trust", "walmart-affiliate-api": 55, "weight": 7 } ], "summary": "Walmart Affiliate Marketing API and MealMe API score within a point of each other on agent readiness, 38.8 (E) and 38.4 (E). MealMe API leads on schema \u0026 documentation and agent ergonomics. 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-affiliate-api": "Live, free catalogue search and product lookup for approved Walmart affiliates, signed with an RSA key and capped at 5,000 calls a day. It cannot place or follow orders, and the Checkout API needs separate approval. The documentation renders only in a browser, and the API terms date from 2020 and still name a previous affiliate network." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api", "json": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.min.md" }, "markdown": "Walmart Affiliate Marketing API and MealMe API score within a point of each other on agent readiness, 38.8 (E) and 38.4 (E). MealMe API leads on schema \u0026 documentation and agent ergonomics. Both do product search for shoppers.\n\n- MealMe API: grade E, 38.4/100, rank #1231 of 1349. Markdown https://www.anchorterminal.com/tools/mealme.md · JSON https://www.anchorterminal.com/api/v1/tools/mealme.json\n- Walmart Affiliate Marketing API: grade E, 38.8/100, rank #1225 of 1349. Markdown https://www.anchorterminal.com/tools/walmart-affiliate-api.md · JSON https://www.anchorterminal.com/api/v1/tools/walmart-affiliate-api.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- Schema \u0026 documentation, 72 against 27\n- Agent ergonomics, 69 against 57\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 Affiliate Marketing API (E)\n\nGood for: Product search and affiliate links for an agent recommending Walmart products and handing the purchase to the person.\n\nAhead on:\n- Reliability, 33 against 19\n- Security \u0026 auth, 58 against 26\n- Payments \u0026 pricing, 25 against 20\n- Transparency \u0026 trust, 55 against 47\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No order, cart, order status or return operation in the affiliate API\n\n\n## Why the edge\n\n### Schema \u0026 documentation: MealMe API +45\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 Affiliate Marketing API (27): No OpenAPI or machine-readable description for the affiliate API. Its specification page is marked as not a Swagger document (0 of 25). No llms.txt or Markdown, and pages render only through browser script (0 of 10). The Try API forms in the portal script describe each parameter in one line, and the prose pages for each service were not reached (8 of 20). Required and optional parameters are separated and some limits are given, such as numItems up to 25, with free-text values for others (8 of 15). Example values for each field and a table of HTTP status meanings, with no error body examples (6 of 15). The version is in the path (v2) and the live service reports version 2.0.0, with no changelog found (5 of 15). Total 27.\n\n### Security \u0026 auth: Walmart Affiliate Marketing API +32\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 Affiliate Marketing API (58): Requests are signed with the developer's RSA private key, which is never sent, and signatures expire after 180 seconds. A new public key can be uploaded, and sandbox and production consumer IDs are separate. There are no scopes beyond the subscribed product (22 of 30). The affiliate API only reads, so it cannot buy or change an account. Checkout sits behind a separate approval (15 of 20). Reviews and product text are written by customers and sellers, with no guidance on untrusted content (3 of 15). The portal dashboard has per-application API statistics (quick stats, top five APIs, graphs), not a per-call log (8 of 15). www.walmart.com/.well-known/security.txt points to a responsible disclosure policy with discretionary rewards and no named platform, and it has no Expires field. No certification was checked (10 of 20). Total 58.\n\n### Reliability: Walmart Affiliate Marketing 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 Affiliate Marketing API (33): No status page was found. status.walmart.io did not answer and the portal links none (0 of 20). No readable incident history, so the 5-point default (5 of 30). The API terms state 5,000 calls a day (15 of 15). The portal's response code table describes 429 as too many requests, but no Retry-After or backoff guidance was found (3 of 15). No SLA (0 of 10). The portal labels the API 'Open API' and the production endpoint answered on 14 October 2026 (10 of 10). Total 33.\n\n### Agent ergonomics: MealMe API +12\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 Affiliate Marketing API (57): responseGroup base or full and numItems up to 25 size responses, without field selection (15 of 25). Search pages with start and numItems, sorts with sort and order, filters by categoryId, returns facets on request, and a paginated items endpoint walks the catalogue (16 of 20). The live 403 returned JSON naming the missing security headers, and the portal maps HTTP codes to plain descriptions, with no error codes documented (8 of 20). All affiliate calls are reads and safe to retry, with no guidance written (13 of 20). Only query is required for search. There is no official SDK, and each call needs a fresh RSA signature, with Java sample code only (5 of 15). Total 57.\n\n### Transparency \u0026 trust: Walmart Affiliate Marketing API +8\n\n- MealMe API (47): Closed service. The API and SDK Terms of Use (18 June 2022) and MealMe Connect terms (4 April 2025) name MealMe, Inc. under Delaware law, but the API terms license use for personal, noncommercial purposes while the product is sold to businesses (15 of 30). The privacy policy of 1 January 2025 keeps data as long as needed, names no subprocessor and no DPA; the cookie policy names Google, Adobe, LinkedIn, Twitter and Facebook (10 of 30). Release notes record breaking changes with dates but there is no deprecation policy or notice period (6 of 20). Cookie providers named, no subprocessor list or data location (4 of 20). Total 35.\n- Walmart Affiliate Marketing API (55): Closed service with API terms shown in the portal, last updated 30 September 2020. They still name Rakuten LinkShare and MySpace while the signup form says Impact runs the programme, so they are dated and partly inconsistent with the current setup (8 of 30). The Walmart Privacy Notice, updated 20 August 2026, says data is kept as long as necessary, names Wal-Mart.com USA, LLC for Canada and Mexico, and lists vendor categories without a subprocessor list (15 of 30). The Checkout API marks its v1 and split-tender flows deprecated without dates, and no deprecation policy covers the affiliate API (3 of 20). Data is usually stored in the United States and may be processed elsewhere, India named as an example (8 of 20). Total 34.\n\n### Payments \u0026 pricing: Walmart Affiliate Marketing API +5\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 Affiliate Marketing API (25): No x402, MPP or L402 (0 of 40). No fee for calls is stated. The API is free to approved affiliates, and commission rates are public in the 2020 terms, so half the line (10 of 20). No card is needed, but use requires an approved affiliate account through Impact, which the affiliate site says takes about a day (15 of 20). Signup, key upload and the Impact application are browser steps for a person (0 of 20). Total 25.\n\n## Score by category\n\n| Category | Weight | MealMe API | Walmart Affiliate Marketing API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 19 | 33 | Walmart Affiliate Marketing API +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 27 | MealMe API +45 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 57 | MealMe API +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 26 | 58 | Walmart Affiliate Marketing API +32 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 25 | Walmart Affiliate Marketing API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 6 | 5 | MealMe API +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 47 | 55 | Walmart Affiliate Marketing API +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **38.4 · E** | **38.8 · E** | |\n\n## Facts side by side\n\n| Fact | MealMe API | Walmart Affiliate Marketing API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | MealMe, Inc. | Wal-Mart.com USA, LLC (Walmart Inc.) |\n| Hosted endpoint | no (local only) | `https://developer.api.walmart.com/api-proxy/service/affil/product/v2` |\n| Transports | | HTTP |\n| Auth | API key | API 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 service under the Walmart I/O API Terms of Use (last updated 30 September 2020) |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | yes |\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| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### MealMe API\n\nNo score change since it was listed.\n\n### Walmart Affiliate Marketing API\n\n- +0.2 on 28 October 2026: new evidence\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 Affiliate Marketing API.** Live, free catalogue search and product lookup for approved Walmart affiliates, signed with an RSA key and capped at 5,000 calls a day. It cannot place or follow orders, and the Checkout API needs separate approval. The documentation renders only in a browser, and the API terms date from 2020 and still name a previous affiliate network.\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 Affiliate Marketing API\n\n1. Generate a fresh WM_SEC.AUTH_SIGNATURE for each call, because a signature older than 180 seconds is rejected\n2. Keep below 5,000 calls a day per application\n3. Pass the Impact publisher ID so returned links earn commission\n4. Hand purchases to the person through the returned product link, since the affiliate API cannot check out\n\n## Questions\n\n### Which is better for AI agents, MealMe API or Walmart Affiliate Marketing API?\n\nWalmart Affiliate Marketing API and MealMe API score within a point of each other on agent readiness, 38.8 (E) and 38.4 (E). MealMe API leads on schema \u0026 documentation and agent ergonomics.\n\n### Do MealMe API and Walmart Affiliate Marketing API need an API key?\n\nBoth need an API key.\n\n### Can an agent call MealMe API and Walmart Affiliate Marketing API without installing anything?\n\nNo hosted endpoint is listed for MealMe API. Walmart Affiliate Marketing API has a hosted endpoint at https://developer.api.walmart.com/api-proxy/service/affil/product/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"mealme\", \"b\": \"walmart-affiliate-api\"}`. From a terminal: `anchor compare mealme walmart-affiliate-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/mealme.json and https://www.anchorterminal.com/api/v1/tools/walmart-affiliate-api.json\n\n## Other comparisons with MealMe API or Walmart Affiliate Marketing API\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 Affiliate Marketing API](https://www.anchorterminal.com/compare/amazon-creators-api-vs-walmart-affiliate-api.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 Affiliate Marketing API](https://www.anchorterminal.com/compare/best-buy-vs-walmart-affiliate-api.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 Affiliate Marketing API](https://www.anchorterminal.com/compare/etsy-vs-walmart-affiliate-api.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 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 Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/opencommerce-vs-walmart-affiliate-api.md)\n- [Shop MCP vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/shop-mcp-vs-walmart-affiliate-api.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 Affiliate Marketing API vs Zillow in Claude](https://www.anchorterminal.com/compare/walmart-affiliate-api-vs-zillow-claude.md)\n- [Instacart Developer Platform API + MCP vs MealMe API](https://www.anchorterminal.com/compare/instacart-vs-mealme.md)\n- [Instacart Developer Platform API + MCP vs Walmart Affiliate Marketing API](https://www.anchorterminal.com/compare/instacart-vs-walmart-affiliate-api.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 Affiliate Marketing API", "url": "" } ], "description": "Walmart Affiliate Marketing and MealMe score within a point of each other for product search for shoppers, 38.8 and 38.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "MealMe API E 38.4", "Walmart Affiliate Marketing API E 38.8", "scores" ], "h1": "MealMe API vs Walmart Affiliate Marketing API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/mealme-vs-walmart-affiliate-api", "published": "2026-10-01", "section": "tools", "title": "MealMe vs Walmart Affiliate Marketing for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/mealme-vs-walmart-affiliate-api" }, "tokens": { "markdown": 4600, "slim": 2780 }, "version": 1 }