Head to head · Placing and tracking orders · October 2026 research run

CartAI vs Zinc

Zinc scores 69.9 (B) on agent readiness against CartAI's 34.9 (F), and leads in every scored category. Both do placing and tracking orders.

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

Which one, for what

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.

Also in its favour

  • Runs on your own machine

Watch for

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

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 18
  • Schema & documentation, 92 against 59
  • Agent ergonomics, 86 against 49
  • Security & auth, 57 against 43
  • Payments & pricing, 98 against 30
  • Maintenance & community, 83 against 18
  • Transparency & trust, 60 against 45

Also in its favour

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

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 +68

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.

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.

Maintenance & community Zinc +65

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.

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.

Reliability Zinc +37

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.

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.

Agent ergonomics Zinc +37

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.

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.

Schema & documentation Zinc +33

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.

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.

Transparency & trust Zinc +15

CartAI 45

Closed service with published terms naming CartAI, LLC under Texas law, updated 13 May 2026, and an Apache 2.0 MCP server (15 of 30). The privacy policy (13 May 2026) describes card vaulting through a partner and says raw card numbers never reach CartAI systems, but the docs say test-mode card data is not tokenised and could appear in logs. Retention is "as long as necessary" with no periods, and no DPA was found (12 of 30). No API deprecation policy. The terms let CartAI change or discontinue parts of the Services without liability and promise notice only for material changes to the terms and to pricing (0 of 20). The privacy policy names Visa Intelligent Commerce and Mastercard AgentPay and other providers by kind, and the terms name Cloudflare, HUMAN and Fingerprint as bot-mitigation partners. Processing is in the US and other countries, with no subprocessor list (6 of 20). 15 + 12 + 0 + 6 = 33.

Zinc 60

A closed service with clear terms (Zinc Technologies Inc., California law, updated 12 October 2026). The agent skills are MIT (15). The privacy policy (updated 6 October 2026) says Zinc is the processor for end users' order data, doesn't sell personal data and keeps it while the account is active and afterwards for business or legal reasons. No DPA or retention period found (15 of 30). A v1 to v2 migration guide and runbook, and legacy error values marked as no longer returned, but no deprecation policy with dates (8 of 20). The privacy policy names Stripe and Tempo and lists other service providers by kind (hosting, AI model providers, email). No subprocessor list or data location found (8 of 20). 15 + 15 + 8 + 8 = 46.

Score by category

CategoryWeightCartAIZincEdge
Reliability16%1855Zinc +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5992Zinc +33
Agent ergonomics13%4986Zinc +37
Security & auth14%4357Zinc +14
Payments & pricing10%3098Zinc +68
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1883Zinc +65
Transparency & trust7%4560Zinc +15
Negative events≤15-30
TotalF 34.9/100B 69.9/100

Facts side by side

FactCartAIZinc
KindHTTP APIHTTP API
VendorCartAIZinc
Hosted endpointno (local only)https://mcp.zinc.com/mcp
TransportsstdioStreamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumPay per use
Price for placing and tracking ordersnot published$0.10 per transaction
x402noon some endpoints
LicencenoneProprietary service, agent skills MIT
Tools exposed88
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.zinc.www/mcp
Last release2026-07-202026-11-13
Terms last updated2026-05-132026-10-12
Privacy policy last updated2026-05-132026-10-06
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesyes

Verdicts

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.

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

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

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, CartAI or Zinc?

Zinc scores 69.9 (B) on agent readiness against CartAI's 34.9 (F), and leads in every scored category.

Do CartAI and Zinc need an API key?

CartAI needs an API key. Zinc takes an API key or an OAuth sign-in.

Can an agent call CartAI and Zinc without installing anything?

CartAI runs on your own machine, with no hosted endpoint listed. Zinc has a hosted endpoint at https://mcp.zinc.com/mcp.

Other comparisons with CartAI 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.