Head to head · Product search for shoppers · October 2026 research run

Amazon Creators API vs Zinc

Zinc scores 69.9 (B) on agent readiness against Amazon Creators API's 5 (F), and leads in every scored category. Both do product search for shoppers.

Best shopping and order APIs for AI agents buying for a person · All 50 shopping comparisons

Which one, for what

Amazon Creators API F

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Its documentation and terms host refuses our reader, so nothing about operations, limits, errors or credentials could be graded

Zinc B

Best for Agents that need to buy physical goods from US retailers for a person, with machine payment and no account.

Ahead on

  • Reliability, 55 against 5
  • Schema & documentation, 92 against 0
  • Agent ergonomics, 86 against 0
  • Security & auth, 57 against 0
  • Payments & pricing, 98 against 0
  • Maintenance & community, 83 against 0
  • Transparency & trust, 60 against 46

Also in its favour

  • Free to start without a card

Watch for

By default orders run on retailer accounts Zinc runs, and its docs index lists a guide to Amazon's anti-bot pages and one on proxies "for account protection"

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Zinc +98

Amazon Creators API 0

No x402, MPP or L402 found (0 of 40). The absence of a per-call fee, the eligibility rule of 10 qualifying sales and the browser signup were read on 14 October 2026 only on affiliate-program.amazon.com, which answered our robots.txt request on 4 November 2026 with HTTP 404 and an Associates Central page saying "Access Denied! You do not have permission to perform the requested operation". An access-denied body is a refusal whatever its status code (us.zohostatus.com for zoho-crm and zoho-desk), so those readings are struck (0, 0, 0). 0 + 0 + 0 + 0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Zinc 98

x402 (v2, USDC on Base and Solana) and MPP (Tempo, and Link with a Shared Payment Token) on POST /agent/orders and the /agent/* data endpoints. Returns, cases, managed accounts and webhooks need an API key (8 of 10). $1 per successful order plus the item, $0.25 for tracking links and emails, $0.10 per item over 10, and $0.01 per data call, published without login (30). A sandbox needs no account or card, and a device-approved live key comes with a $5 starter credit (30). An agent can pay per order with no account, or mint a sandbox key with one unauthenticated call (30). 8 + 30 + 30 + 30 = 98.

Schema & documentation Zinc +92

Amazon Creators API 0

Every schema reading (no OpenAPI file, no llms.txt, the operation pages, typed parameters, examples, the error page and the versioned path) was read on 14 October 2026 only on affiliate-program.amazon.com, which answered our robots.txt request on 4 November 2026 with HTTP 404 and an Associates Central page saying "Access Denied! You do not have permission to perform the requested operation". An access-denied body is a refusal whatever its status code (us.zohostatus.com for zoho-crm and zoho-desk), so those readings are struck. No readable page states the contract today. 0 + 0 + 0 + 0 + 0 + 0 = 0.

Zinc 92

A public OpenAPI 3.1 file at api.zinc.com/openapi.json, version 2026-10-30, with 45 paths and 53 operations, 49 of them described (25). llms.txt, llms-full.txt, section indexes and Accept: text/markdown on every page (10). Pages say when to use each route, such as checking a retailer before ordering and using the offers endpoint rather than product details for a price (17 of 20). Typed request bodies with required fields, prices in integer cents and enumerated payment methods (14 of 15). Examples on every page and a long table of error codes with recovery steps, but the metered data endpoints return a different 402 shape and the MCP connector's tool schemas weren't read (11 of 15). Dated API versions (CalVer, 30 versions listed back to 24 November 2025) and a weekly changelog (15). 25 + 10 + 17 + 14 + 11 + 15 = 92.

Agent ergonomics Zinc +86

Amazon Creators API 0

Field selection, paging and filters, error reasons, read-only operations and defaults were read on 14 October 2026 only on affiliate-program.amazon.com, which answered our robots.txt request on 4 November 2026 with HTTP 404 and an Associates Central page saying "Access Denied! You do not have permission to perform the requested operation". An access-denied body is a refusal whatever its status code (us.zohostatus.com for zoho-crm and zoho-desk), so those readings are struck. No readable page states them today. 0 + 0 + 0 + 0 + 0 = 0.

Zinc 86

Search returns up to 20 results, best first, and data and order calls are separate routes, so responses stay small. No field selection found (20 of 25). List and export endpoints take filters, and orders can be listed, exported and followed by webhook (18 of 20). Errors carry a stable code, a message and details, including details.fund_with on insufficient_funds and RFC 8628 hints in the device flow (20). Idempotency keys on orders, agent orders and top-ups, a 409 that names the existing order, and an MCP spending tool that needs a confirmation token only a person's click produces. MCP annotations weren't read (18 of 20). Few required fields, and an official npm SDK (zinc, CalVer from the live spec). No second official SDK was confirmed (10 of 15). 20 + 18 + 20 + 18 + 10 = 86.

Maintenance & community Zinc +83

Amazon Creators API 0

The SDK changelog (last entry 1.3.0, 21 August 2026), the support route, the SDK downloads and the package-health reading were read on 14 October 2026 only on affiliate-program.amazon.com, which answered our robots.txt request on 4 November 2026 with HTTP 404 and an Associates Central page saying "Access Denied! You do not have permission to perform the requested operation". An access-denied body is a refusal whatever its status code (us.zohostatus.com for zoho-crm and zoho-desk), so those readings are struck. No other dated source of Amazon's for this API was found, so recency and the 90-day line are 0, and support, SDKs and package health score 0. 0 + 0 + 0 + 0 + 0 = 0.

Zinc 83

The changelog's latest entry is dated 13 November 2026, and the npm SDK's latest version is 2026.10.30 (30). Weekly dated changelog entries, 13 since 20 August 2026 (20). A public weekly changelog and a support address (support@zinc.com) that the contact page says gets a person. GitHub issue response wasn't checked (10 of 25). The MCP connector is in the official MCP registry as com.zinc.www/mcp, published 28 October 2026 under Zinc's domain namespace, and the npm SDK is current (15). The npm SDK is generated from the live spec and published with provenance attestations (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.

Security & auth Zinc +57

Amazon Creators API 0

The credential model, the read-only scope of the operations, the seller-written content and the reporting were read on 14 October 2026 only on affiliate-program.amazon.com, which answered our robots.txt request on 4 November 2026 with HTTP 404 and an Associates Central page saying "Access Denied! You do not have permission to perform the requested operation". An access-denied body is a refusal whatever its status code (us.zohostatus.com for zoho-crm and zoho-desk), so those readings are struck (0, 0, 0, 0). The security programme line was already 0: security.txt on www.amazon.com was not read because its robots.txt disallows our crawler, and no other programme reading stands (0 of 20). 0 + 0 + 0 + 0 + 0 = 0.

Zinc 57

Bearer API keys, zn_test_ for sandbox and zn_live_ for live, and each agent can get its own live key by device-code approval. No scopes or rotation steps were found (18 of 30). Sandbox keys can't spend, every order carries a max_price cap, a person approves a live key in the browser, and the MCP connector's place-order needs a confirmation token withheld from the model (17 of 20). The MCP docs explain that the token is there so a prompt injection in a page can't become a purchase. Product data from retailers is untrusted text (12 of 15). Order timelines, a usage endpoint, CSV export and the dashboard show every order (10 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001 found (0). 18 + 17 + 12 + 10 + 0 = 57.

Reliability Zinc +50

Amazon Creators API 5

No status page for the Creators API was found (0 of 20). No readable incident history, so the line takes the unread 5 (5 of 30). The rate limits, the 429 and 500 retry guidance and the API's general availability were read on 14 October 2026 only on affiliate-program.amazon.com, which answered our robots.txt request on 4 November 2026 with HTTP 404 and an Associates Central page saying "Access Denied! You do not have permission to perform the requested operation". An access-denied body is a refusal whatever its status code (us.zohostatus.com for zoho-crm and zoho-desk), so those readings are struck and the lines score 0 (0 of 15, 0 of 15, 0 of 10). No SLA found (0 of 10). 0 + 5 + 0 + 0 + 0 + 0 = 5.

Zinc 55

Zinc's own status page (www.zinc.com/status) shows five components (Ordering, Tracking, Product Data, API, Dashboard) with 90-day uptime bars (20). On 18 November 2026 it showed 99.1 per cent uptime for Ordering and 99.57 per cent for the API over 90 days, both recovered from a degradation that day. The page has no incident write-ups, and 99.1 per cent over 90 days is about 19 hours, so at least one major interruption is implied (10 of 30). No numeric request rate limits found, apart from 5 sandbox key mints per IP address a day (5 of 15). 429 carries rate_limit_exceeded with guidance to back off and retry, responses carry RateLimit and RateLimit-Policy headers (changelog, August 2026), and orders and top-ups take idempotency keys (15). No SLA found (0). Orders are generally available. Cross-retailer search and the Zinc 2.0 announcement carry a beta label (5 of 10). 20 + 10 + 5 + 15 + 0 + 5 = 55.

Score by category

CategoryWeightAmazon Creators APIZincEdge
Reliability16%555Zinc +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%092Zinc +92
Agent ergonomics13%086Zinc +86
Security & auth14%057Zinc +57
Payments & pricing10%098Zinc +98
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%083Zinc +83
Transparency & trust7%4660Zinc +14
Negative events≤1500
TotalF 5/100B 69.9/100

Facts side by side

FactAmazon Creators APIZinc
KindHTTP APIHTTP API
VendorAmazonZinc
Hosted endpointhttps://creatorsapi.amazon/catalog/v1https://mcp.zinc.com/mcp
TransportsHTTPStreamable HTTP
AuthOAuthOAuth or key
PricingFreePay per use
x402noon some endpoints
LicenceProprietary service under the Amazon Associates Program Operating Agreement and its IP Licence for each localeProprietary service, agent skills MIT
Tools exposednone8
Read-only variant documentedyesno
llms.txtnoyes
MCP registrynot listedcom.zinc.www/mcp
Last release2026-08-212026-11-13
Terms last updated2025-10-152026-10-12
Privacy policy last updated2026-06-302026-10-06
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesyes

How the scores have moved

Verdicts

Amazon Creators API

Amazon's product catalogue API for Associates affiliates, graded on almost nothing. Its documentation and terms host answered our robots.txt request with an access-denied page on 4 November 2026, so the earlier readings of operations, limits, errors and credentials are withdrawn, and www.amazon.com disallows our crawler. Only the published terms still count.

Zinc

An agent can mint a sandbox key with no signup and pay for real orders by x402, MPP or Link with no account, at $1 an order plus the item, with idempotency keys and a public OpenAPI file. Orders run on Zinc's own retailer accounts by default, and no security programme or numeric rate limits were found.

Before you call either

Amazon Creators API

  1. Read Amazon's current Creators API documentation and Associates terms before calling, since this listing carries no current reading of them

Zinc

  1. Call GET /retailers/check with the product URL and country before ordering, since unsupported retailers and countries fail predictably
  2. Set max_price and an idempotency_key on every order. If a retry returns 409, read the existing order id from error.details.order_id
  3. If your HTTP client merges WWW-Authenticate headers, add ?method=x402, ?method=tempo or ?method=stripe to get one payment challenge
  4. Store the X-Api-Key returned with a paid agent order. It is the only way to follow that order without paying again
  5. Persist a sandbox key across runs. It expires after 7 days without use, and minting is limited to 5 a day per IP address

Questions

Which is better for AI agents, Amazon Creators API or Zinc?

Zinc scores 69.9 (B) on agent readiness against Amazon Creators API's 5 (F), and leads in every scored category.

Do Amazon Creators API and Zinc need an API key?

Amazon Creators API uses an OAuth sign-in. Zinc takes an API key or an OAuth sign-in.

Can an agent call Amazon Creators API and Zinc without installing anything?

Yes. Amazon Creators API has a hosted endpoint at https://creatorsapi.amazon/catalog/v1 and Zinc at https://mcp.zinc.com/mcp.

Other comparisons with Amazon Creators API or Zinc

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.