# Amazon Creators API vs MealMe API (slim)

> Amazon Creators scores 48.8 (D) to MealMe's 38.4 (E) for product search for shoppers. Prices, MCP, x402, uptime and agent notes side by side.

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

Amazon Creators API scores 48.8 (D) on agent readiness against MealMe API's 38.4 (E), and leads in 5 of 7 scored categories. MealMe API leads on schema & documentation and payments & pricing. Both do product search for shoppers.

- Amazon Creators API: D 48.8, rank #1016 of 1349 · https://www.anchorterminal.com/tools/amazon-creators-api.min.md
- MealMe API: E 38.4, rank #1229 of 1349 · https://www.anchorterminal.com/tools/mealme.min.md
- Amazon Creators API, good for Product search, price checks and affiliate links for an agent that recommends Amazon products and hands the purchase to the person. Ahead on Reliability, 45 against 19; Agent ergonomics, 85 against 69; Security & auth, 48 against 26; Maintenance & community, 41 against 6; Transparency & trust, 53 against 47. Also A hosted endpoint, with nothing to install.
- MealMe API, good for Agents that must place a real restaurant or grocery order in the US or Canada, or compare live prices across stores, and can hold a card on the account. Ahead on Schema & documentation, 72 against 50; Payments & pricing, 20 against 10.

| Category | Amazon Creators API | MealMe API |
| --- | --- | --- |
| Reliability (16%) | 45 | 19 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 72 |
| Agent ergonomics (13%) | 85 | 69 |
| Security & auth (14%) | 48 | 26 |
| Payments & pricing (10%) | 10 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 41 | 6 |
| Transparency & trust (7%) | 53 | 47 |

| Fact (where they differ) | Amazon Creators API | MealMe API |
| --- | --- | --- |
| Vendor | Amazon.com Services LLC | MealMe, Inc. |
| Hosted endpoint | `https://creatorsapi.amazon/catalog/v1` | no (local only) |
| Transports | HTTP |  |
| Auth | OAuth | API key |
| Pricing | Free | Pay per use |
| Licence | Proprietary service under the Amazon Associates Program Operating Agreement and its IP Licence for each locale | Proprietary service under the MealMe API and SDK Terms of Use |
| Tools exposed | none | 0 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-08-21 | 2025-05-06 |
| Terms last updated | 2025-10-15 | 2025-04-04 |
| Privacy policy last updated | 2026-06-30 | 2025-04-04 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |

Why the edge:
- Maintenance & community, Amazon Creators API +35: Amazon Creators API 41 (The latest dated change is SDK 1.3.0 on 21 August 2026, 54 days ago (20 of 30). Only one dated entry falls in the last 90 days (0 of 20). Support is through the Associates contact form, which promises a reply to acceptance requests in 3 to 4 days, and there is no public API changelog or forum (8 of 15). Official SDKs in four languages are current to August 2026, but none is published on npm, PyPI, Packagist or Maven by Amazon (10 of 15). The npm names creatorsapi-nodejs-sdk and amazon-creators-api are held by individuals, and no CI or dependency status is public (3 of 10). Total 41.); 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.)
- Reliability, Amazon Creators API +26: Amazon Creators API 45 (No status page for the Creators API was found in the documentation (0 of 20). No readable incident history, so the line takes the 5-point default (5 of 30). Rate limits are published with numbers, 1 request a second and 8,640 a day at the start, then scaled by shipped revenue up to 10 a second (15 of 15). 429 ThrottleException and 500 InternalServerException both tell clients to retry with exponential backoff, errors can carry retryAfterSeconds, and every operation is a read, so retries are safe (15 of 15). No SLA (0 of 10). The API is the supported successor to PA-API 5 and generally available (10 of 10). Total 45.); 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.)
- Schema & documentation, MealMe API +22: Amazon Creators API 50 (No public OpenAPI or other machine-readable description was found. The SDKs are generated archives behind a download (0 of 25). No llms.txt (/creatorsapi/docs/llms.txt returns 404) and no Markdown twins (0 of 10). Each operation page states its purpose, the parameters that apply to which search indices and when to use a browse node instead of a keyword, without when-not-to-use guidance (14 of 20). Parameters are typed with defaults, ranges (itemCount and itemPage 1 to 10) and required markers, and resources are a fixed enum of dot paths (12 of 15). Examples in cURL and JSON for each operation, and an error page listing every exception with its reason codes and example messages (14 of 15). The API version is in the path (v1) and the SDK changelog is dated, but there is no changelog for the API itself (10 of 15). Total 50.); 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.)
- Security & auth, Amazon Creators API +22: Amazon Creators API 48 (OAuth 2.0 client credentials with tokens that last one hour. Two credentials per application allow rotation, and credentials can be deleted, but there is one scope (creatorsapi::default) and no finer permissions (22 of 30). The API is read-only, so an agent cannot spend money or change an account through it (18 of 20). It returns product titles and feature bullets written by sellers, with no guidance on treating them as untrusted data (5 of 15). The operator sees attributed sales in the Link Type Performance report, not a per-call log (3 of 15). Programme not established. security.txt on www.amazon.com was not read because robots.txt disallows our crawler, affiliate-program.amazon.com has none (404), and the HackerOne page for Amazon's programme did not render, so no point was given (0 of 20). Total 48.); 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.)
- Agent ergonomics, Amazon Creators API +16: Amazon Creators API 85 (The resources parameter returns only the fields requested, and the best practices recommend it to cut payload size (22 of 25). SearchItems pages up to 10 items with itemPage 1 to 10, so 100 results at most, with filters for brand, price range, condition, availability, delivery flags, merchant and sort (17 of 20). Errors have a type, a machine-readable reason, fieldList for validation failures and retryAfterSeconds where relevant, and partial results return an errors array per item (18 of 20). All four operations are reads and safe to retry, though no idempotency mechanism is needed or named (15 of 20). Sensible defaults (search index All, availability Available, itemCount 10) and official SDKs in four languages, though only as archive downloads (13 of 15). Total 85.); 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.)
- Payments & pricing, MealMe API +10: Amazon Creators API 10 (No x402, MPP or L402 (0 of 40). The documentation states no fee for API calls, and usage limits are tied to referred revenue, not a price list. Nothing says the API is free in plain terms, so half the line (10 of 20). There is no free tier in the usual sense. Access needs an accepted Associates account and 10 qualifying sales in the trailing 30 days, so a new developer cannot start (0 of 20). Associates signup, final acceptance and credential creation all happen in a browser by the primary account owner (0 of 20). Total 10.); MealMe API 20 (No x402, MPP or L402 (0). $0.10 per successful call and $250 a month published without login (20). No free tier or trial; a card must be added before the key is created (0). Signup is a browser form with email, password and card (0). Total 20.)