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

Amazon Creators API vs CartAI

CartAI scores 34.9 (F) on agent readiness against Amazon Creators API's 5 (F), and leads in 6 of 7 scored categories. Both do product search for shoppers.

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

Which one, for what

Amazon Creators API F

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where CartAI loses 3 points for them

Watch for

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

CartAI F

Best for Platforms that show products (rewards apps, publishers, vertical AI apps) and want to complete purchases on US merchants' own sites without merchant integrations.

Ahead on

  • Reliability, 18 against 5
  • Schema & documentation, 59 against 0
  • Agent ergonomics, 49 against 0
  • Security & auth, 43 against 0
  • Payments & pricing, 30 against 0
  • Maintenance & community, 18 against 0

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

No public prices. Production fees are basis points on order value, shown only in the dashboard

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.

Schema & documentation CartAI +59

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.

CartAI 59

A public OpenAPI 3.0 file at docs.cartai.ai/openapi/latest.yml with 13 operations. It declares no security scheme, and the key header is spelt X-Api-Key on some paths and x-api-key on others, which CartAI's own auth.md points out (20 of 25). llms.txt on both hosts and a Markdown twin of every docs page (10). Reference pages say when to use each call, such as a table of when to use webhooks or polling for a task, and the MCP tool descriptions say which call comes next (14 of 20). Required fields and patterns for phone and postal code, but only two enums in the spec, shippingMethod.strategy is a free string, and payment.data is typed as a string in one table while the examples send an object (7 of 15). Request and response examples on each page and a 401 body, but most operations document only 400, and a link to the task lifecycle section points to an anchor that is missing (8 of 15). No changelog and no API versioning beyond 1.0.0 in the spec (0). 20 + 10 + 14 + 7 + 8 + 0 = 59.

Agent ergonomics CartAI +49

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.

CartAI 49

The MCP server has 8 tools with compact descriptions, but each result appends the full JSON response, and the REST API has no field selection (22 of 25). Product search takes a query and an optional merchant to prioritise, with no limit, page or filter parameters found (6 of 20). A documented 401 body with an error code and message, 400 on every operation, and 403, 404 and 409 on interactive inputs. Error bodies for failed checkouts are not described beyond the FAILED status (10 of 20). No idempotency key on writes, and the docs say a resubmit creates a duplicate. A confirmation step (verifyBeforePlacement, PENDING_CONFIRMATION) and a cancel call exist, and the MCP tools carry no readOnlyHint or destructiveHint (6 of 20). A checkout needs a full customer object with contact, two addresses, shipping strategy and payment. No official SDK, and the MCP server runs from a clone, in Node.js only (5 of 15). 22 + 6 + 10 + 6 + 5 = 49.

Security & auth CartAI +43

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.

CartAI 43

One API key per request in a header, revocable and regenerated in the portal, with no scopes or rotation guidance found (20 of 30). No read-only key. A checkout can wait for the customer's confirmation, and production payments run through hosted Visa Intelligent Commerce or Mastercard Agent Pay sessions the customer authorises. The MCP server places orders with no confirmation of its own (10 of 20). Product search and details return merchant page content with no prompt-injection guidance, and the create_payment_session tool description tells the model to present the payment link "without asking the user first" (3 of 15). Each task has a status history with timestamps and credits, a live preview URL and webhooks for every status (10 of 15). No security.txt (404), disclosure policy, bug bounty or certification found. The known limitations page says test-mode card data is not tokenised and could appear in logs (0 of 20). 20 + 10 + 3 + 10 + 0 = 43.

Payments & pricing CartAI +30

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.

CartAI 30

No x402, MPP or L402. The card sessions pay merchants for customers' orders, not CartAI (0 of 10). No price list without a login. The terms say production fees are basis points on order value and other usage metrics, shown in the dashboard or agreed separately, and credits have no published price (0 of 30). Every new account gets 5 free credits, about 500 Catalog API calls or at least 10 test checkouts, and the signup asks for name, email and password with no card (30). A person signs up in a browser to get a key, and production needs a Go Live review (0). 0 + 0 + 30 + 0 = 30.

Maintenance & community CartAI +18

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.

CartAI 18

Closed service with no changelog. The newest dated release found is the MCP server's last commit on 20 July 2026, 123 days ago (10 of 30). Docs pages show updatedAt dates from 17 to 20 November 2026, but no dated change list, so no releases can be counted in the last 90 days (0 of 20). No public changelog. Support is through a contact page, info@cartai.ai and a portal request for more credits that the docs say is reviewed within one business day. Neither was tested (5 of 25). Not in the official MCP registry, not on npm, and no official SDKs (0 of 15). The MCP server pins @modelcontextprotocol/sdk ^1.0.0 and zod ^3.22.0 with a lockfile and no CI (3 of 10). The earliest first-hand date of a running API is a webhook example of 6 December 2025, and the MCP repository dates from 25 May 2026. 10 + 0 + 5 + 0 + 3 = 18.

Reliability CartAI +13

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.

CartAI 18

Graded on the hosted REST API at api.cartai.ai. No status page was linked from any page read (0), so there is no incident history to read (5). No numeric rate limits found. The task reference only says polling every second "may trigger rate limits" (0). No 429 or backoff guidance and no idempotency key. The docs give a 5 to 10 second polling interval and warn that a resubmitted checkout creates a duplicate order (3 of 15). The terms put SLA commitments in separate enterprise agreements, with none published (0). The Checkout and Catalog APIs carry no beta label, though production use needs a Go Live review and the Hosted Cart is not generally available (10). 0 + 5 + 0 + 3 + 0 + 10 = 18.

Score by category

CategoryWeightAmazon Creators APICartAIEdge
Reliability16%518CartAI +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%059CartAI +59
Agent ergonomics13%049CartAI +49
Security & auth14%043CartAI +43
Payments & pricing10%030CartAI +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%018CartAI +18
Transparency & trust7%4645Amazon Creators API +1
Negative events≤150-3
TotalF 5/100F 34.9/100

Facts side by side

FactAmazon Creators APICartAI
KindHTTP APIHTTP API
VendorAmazonCartAI
Hosted endpointhttps://creatorsapi.amazon/catalog/v1no (local only)
TransportsHTTPstdio
AuthOAuthAPI key
PricingFreeFreemium
x402nono
LicenceProprietary service under the Amazon Associates Program Operating Agreement and its IP Licence for each localenone
Tools exposednone8
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-08-212026-07-20
Terms last updated2025-10-152026-05-13
Privacy policy last updated2026-06-302026-05-13
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textyes
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.

CartAI

CartAI lets a platform buy from US merchants' own sites through one asynchronous API, with a public OpenAPI file, Markdown docs, webhooks and an optional customer confirmation step. There is no public price list, status page, rate limit or idempotency key, and the home page's retry-safe and Hosted Cart claims go further than the docs.

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

CartAI

  1. Never resend POST /checkout after a 201 or a timeout. Look up the task with GET /checkout/{taskId} first, because a resubmit creates a duplicate order
  2. Use only the test card 4242 4242 4242 4242 until the account is in production mode, since test mode does not tokenise card data
  3. Set verifyBeforePlacement and show derivedDetails.pricing to the customer at PENDING_CONFIRMATION before the order is placed
  4. Poll a task no more than once every 5 to 10 seconds when webhooks are unavailable
  5. Give selectedVariant labels as the merchant's page shows them, and use US merchants, addresses and phone numbers only

Questions

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

CartAI scores 34.9 (F) on agent readiness against Amazon Creators API's 5 (F), and leads in 6 of 7 scored categories.

Do Amazon Creators API and CartAI need an API key?

Amazon Creators API uses an OAuth sign-in. CartAI needs an API key.

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

Amazon Creators API has a hosted endpoint at https://creatorsapi.amazon/catalog/v1. CartAI runs on your own machine, with no hosted endpoint listed.

Other comparisons with Amazon Creators API or CartAI

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.