checkout-registry v0.1

The registry of /checkout infrastructure.

The buy-side checkout APIs that complete a purchase at any merchant — callable from any app or agent. Every one in a single registry, each capability sourced from the provider's docs, tested against their APIs.

registry ~ $ registry list --status=verified

Registry

6 checkout agents · click a row to expand
#AgentCoverageExecutionProtocolsStatusVerification
01 CartAI
CartAI
Universal Browser REST Live claimed
websitewww.cartai.ai docsdocs.cartai.ai/ coverageUniversal — any web property executionHeadless browser automation (async, background) paymentCaller passes payment creds; retailer is merchant of record authCaller-supplied customer + payment credentials protocolsREST (POST /checkout) + webhooks discoveryCaller supplies product URL returnsnot stated regionsnot stated pricingTransaction fee (not detailed) sandboxYes (sandbox: true) statusLive
02 Agentic Checkout
Crossmint
Universal + API + Browser x402MPP Live claimed
websitewww.crossmint.com/products/agentic-checkout docsdocs.crossmint.com/solutions/ai-agents/introduction coverageAmazon, Shopify, 1B+ products, flights; + any site via browser executionFast Checkout (single API call) + browser automation paymentCrossmint issues virtual cards / wallet / stablecoin; spending rules authAgent identity + card verification ceremony protocolsx402, MPP, EVM wallets; Visa VIC, Mastercard Agent Pay discoveryCaller supplies product (API-driven) returnsYes — order refunds supported regionsGlobal (with restricted countries) pricingPer-transaction, tiered by volume; convenience fee typically charged to users (rates via sales) sandboxYes (staging, USDXM testnet) statusLive
03 Firmly.ai
Firmly
11M+ merchants API UCPACPMCPAP2 Live claimed
websitewww.firmly.ai docsdevelopers.firmly.ai/introduction coverage11M+ merchants / $900B+ GMV via one integration (Shopify, BigCommerce, Magento); 32K products live executionCart API + 1-Step Checkout (single integration) paymentCompletes checkout with encrypted payment; Klarna express; PCI-compliant authAccess token for Cart API (backend) protocolsUCP, ACP, MCP, AP2, TAP discoveryBuilt-in product search across merchant catalogs returnsYes — exposes returns/refunds status from the merchant regionsnot stated pricingnot stated sandboxnot stated statusLive
04 Henry
Henry Labs
Multi-merchant SDK REST Live claimed
websitewww.henrylabs.ai docsdocs.henrylabs.ai/ coverageMulti-merchant (with per-merchant success rate + latency) executionSDK/REST; async default or sync (≤30s); headless or hosted frame paymentCard tokenization via isolated iframe authAPI key (server-side) protocolsREST + JS SDK + webhooks discoveryBuilt-in text & image product search returnsnot stated regionsnot stated pricingPer-request credits, tiered plans sandboxYes (test cards) statusLive (updated 02/2026)
05 Universal Checkout API
Rye
Universal Browser ACPUCP Live claimed
websiterye.com/products/universal-checkout-api docsrye.com/docs coverageUniversal — any product URL, ~15,000+ merchants executionBrowser automation; no merchant integration required paymentCaller supplies tokenized payment; Rye handles pricing/tax/shipping/order authAPI key (Basic auth) protocolsREST; ACP, UCP (claimed on site) discoveryCaller supplies product URL returnsYes — open a return against a completed order, track to refund regionsUS primary pricingDeveloper $149/mo ($50 free credits, $0.05/order, $0.02/product fetch, no markup on platform costs); Enterprise custom sandboxYes (staging.api.rye.com) statusLive
06 Zinc API
Zinc
50+ retailers API RESTMPP Live claimed
websitewww.zinc.com docswww.zinc.com/docs coverageAmazon, Walmart, Target, Best Buy + 50; global retailers executionProgrammatic order automation paymentPrepaid balance, Stripe Connect, or Machine Payments Protocol authAPI key protocolsREST; Machine Payments Protocol (HTTP 402) discoveryBuilt-in product search + details returnsYes — return requests supported regionsGlobal pricingPer-order fee (drawn from balance) sandboxYes statusLive (v2 API, spec 2026-06)

Every capability is claimed from the vendor's own docs. Verified means we ran it ourselves — verification in progress.

The benchmark

coming soon

What we test

Every agent runs against the same frozen set of storefronts we control — Shopify, WooCommerce, headless, and one deliberately hostile checkout. Reproducible, no real money, no merchant ToS exposure. A rotating hidden holdout keeps anyone from optimizing to the test.

Scored on: success rate · site-coverage breadth · latency · price accuracy · variant & coupon handling · returns/refunds · protocol support.

Verified vs. claimed

Every capability carries a marker for how we know it:

verified tested by us against the suite
claimed stated in docs, not yet run
spec / unverified no runnable agent

Agent-readable

available as JSON, JSON-LD, and llms.txt

JSON API

Every row on this page is a static, crawlable record and a JSON endpoint. No auth to read.

# the registry, machine-readable
$ curl https://checkoutregistry.com/api/v1/agents

{
  "registry": "Checkout Registry",
  "count": 6,
  "agents": [
    { "vendor": "Rye", "verification": "claimed",
      "capabilities": { "coverage": "Universal — any product URL", ... } },
    ...
  ]
}

Built for LLM discovery

Structured data in the markup, plus a JSON API and an agent guide at the root:

# structured data, in the served HTML
‹script type="application/ld+json"
  "@type": "Dataset"
‹/script›

# machine-readable, at the root
GET /api/v1/agents
GET /llms.txt

The registry is served as static HTML and JSON, so a model fetching this page reads all 6 listings straight from the markup.

FAQ

What is a checkout agent?

Software that completes a purchase on behalf of a person or an AI agent, taking a product selection through to a confirmed order. They range from APIs you call programmatically, to consumer agents that buy inside a chat interface, to browser agents that drive a storefront's UI, to the payment rails and protocols underneath.

What is Checkout Registry?

An independent registry of agentic checkout infrastructure — the buy-side APIs that complete a purchase at a merchant, callable from any app or agent (not just AI). It tracks each one's vendor, capabilities, protocols, and auth, sourced from their own docs, with independent testing planned. It deliberately excludes consumer shopping surfaces, general browser agents, and merchant platforms.

How are capabilities verified?

Every agent runs against the same frozen set of storefronts we control — Shopify, WooCommerce, headless, and a deliberately hostile checkout. Runs are reproducible, use no real money, and carry no merchant ToS exposure. A rotating hidden holdout keeps agents from optimizing to the test.

What do "verified" and "claimed" mean?

Verified means we tested the capability against our suite. Claimed means it is stated in the vendor's documentation but not yet run. Spec / unverified means there is no runnable agent to test. Every capability in the registry carries one of these markers.

Which protocols does the registry track?

Agents across the emerging agentic-commerce protocols — including ACP, AP2, UCP, x402, and MCP — alongside API-only and browser-driven agents that use no shared protocol.

How do I get an agent listed?

Agent submission opens soon. Once it is live, you can submit an agent to be indexed and verified against the public benchmark.

Is the registry free to access?

Yes. Every listing is served as static HTML and as a machine-readable JSON endpoint at /api/v1/agents, with no authentication required to read. An llms.txt is also available for AI agents.

Run a checkout agent?

Submit it to the registry. Get your capabilities verified against the public benchmark.

Register an agent · coming soon Read the methodology