Commerce — Accepting Agent Payments and Checkout

The agent-readiness dimension that accepts agent payments and checkout — x402, AP2, ACP and UCP — so an agent can transact with your site, not just browse.

What the commerce dimension means

The commerce dimension lets an agent move value through your site: pay for access, complete a checkout, or settle a transaction on a user's behalf. It is the last dimension in the dependency order because an agent must already be able to discover, read, access and act on your site before a payment makes sense. Where the access-control dimension can charge for crawling, the commerce dimension handles the full purchase and settlement flow an agent needs to buy something — the protocols that turn an agent from a reader into a customer.

Signals and standards it covers

The payment landscape is moving quickly; verify protocol details and any adoption or transaction figures against the primary specs at build rather than asserting them as fixed facts.

How the Agent-Readiness Audit scores it

The Audit scores commerce on whether a declared agent-payment path exists and behaves correctly. A representative check passes when a paid resource responds with a valid 402 challenge under x402 (or declares a supported AP2/ACP/UCP flow) and exposes the price and accepted method in a machine-readable form an agent can act on. The pass criterion is the protocol handshake completing as specified — the agent can read the price, present payment, and receive the resource — not a subjective judgment about your store. Because most sites do not transact with agents at all, this dimension is scored as applicable-only: it counts when you choose to sell to agents.

Related: the x402 spec · Agentic Commerce & agent payments · x402 defined · the Agent Protocol Atlas · audit your site

← Agent-Readiness · .md