# Make a store buyable by agents

> Make a store buyable by agents: 1 companies fully do it, 1 with a limit, 48 carry the tag. Every listing in Agent checkout protocols with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/checkout-protocols.make-store-agent-ready/
- Markdown: https://www.anchorterminal.com/niches/checkout-protocols.make-store-agent-ready/index.md (~950 tokens)
- Slim: https://www.anchorterminal.com/niches/checkout-protocols.make-store-agent-ready/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/checkout-protocols.make-store-agent-ready/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 1 | 48 | 22 | 6 |

## What counts as done

The store publishes a profile or feed an agent can discover, implements catalogue, checkout and order calls that validate against the published schema, and a stated agent platform can complete a test order, with the build steps and any approval documented.

How agents ask for it: let ChatGPT sell my products; add UCP to my store; can agents check out on my site; get my shop into agent checkout

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Universal Commerce Protocol (UCP) (UCP Authors (Google, Shopify and co-developers))**: A business publishes /.well-known/ucp with versions and capabilities, implements catalogue, checkout and order over REST, MCP or A2A, and the conformance repository tests checkout, idempotency, totals and orders against a Google platform profile; a WooCommerce store took a test order (acc-02).

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Agentic Commerce Protocol (ACP) (OpenAI and Stripe)**: A seller publishes /.well-known/acp.json (unreleased RFC), a product feed and the checkout API, with capability negotiation returning the intersection. The 2026-04-17 OpenAPI rejects six fields its JSON Schema declares (acc-08), and no public list says which agent platforms complete ACP orders (acc-06); both issues are open.

- not this job: American Express Agentic Commerce Experiences (ACE) (American Express Company): No merchant-side catalogue, checkout or order contract; ACE is for agent platforms paying with Amex credentials.
- not this job: Agent Payments Protocol (AP2) (Google LLC): No catalogue, checkout or order calls for a store; AP2 is the mandate layer a checkout protocol carries.
- not this job: Mastercard Agent Pay (Mastercard): Agent Pay gives merchants token acceptance and Web Bot Auth guidance, not a catalogue, checkout or order contract.
- not this job: Visa Intelligent Commerce (Visa Inc.): TAP lets a merchant recognise agents; Visa publishes no catalogue, checkout or order contract for a store to implement.

## What stops agents finishing

- agent platform approval or partner agreement before any order
- OpenAPI and JSON Schema disagree
- no list of which agent platforms honour the protocol

## Around it

Before: commerce.product-catalogue. After: checkout-protocols.verify-agent, payment-platforms.charge-agents-per-call.

## Where this comes from

Weight 22 of 100 in Agent checkout protocols: 6 of 18 accounts (acc-02, acc-05, acc-06, acc-08, acc-09, acc-18); the most first-hand writing came from merchants and plugin builders

As data: https://www.anchorterminal.com/api/v1/use-cases/checkout-protocols.make-store-agent-ready.json, or the MCP tool get_use_case with id checkout-protocols.make-store-agent-ready. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
