A checkout for AI agents
R2.3Can an agent complete a purchase without a browser?
- Why it matters
- Without one, an AI agent has to hand the purchase back to a person at a browser.
- What Lens looks for
- We checked whether your site declares a checkout for AI agents, through UCP or ACP. We never start one.
- Where it sits
- Purchase · Check 2 of 3
- Needed for
- Transactable
- Builds on
- Order links AI agents can build R2.2
- Needed by
- A way for AI agents to pay R2.4
- Usually fixed by
- Developer · Weeks
What to do
Publish the UCP checkout capability, or ACP's discovery document.
Purchase
Can an agent buy without a browser?
- 1Order links AI agents can buildR2.2
- 2A checkout for AI agentsR2.3
- Transactable needs the first 2
- 3A way for AI agents to payR2.4
The definition
- Definition
- A UCP business profile declares checkout when its capabilities include dev.ucp.shopping.checkout with a service binding the handshake completed against. The checkout tools are create_checkout, get_checkout, update_checkout, complete_checkout and cancel_checkout. An ACP discovery document is /.well-known/acp.json answering 200 with JSON in which
protocol.nameis "acp",protocol.versionandsupported_versionsare present,api_base_urlis an absolute https URL,transportsis a non-empty subset of rest and mcp, andcapabilities.servicesincludes checkout. - Passes when
- Either the profile declares checkout and tools/list advertises all five checkout tools, or the site publishes an ACP discovery document, or a route of R2.4 is met. No checkout is created. A route in lists.routes listed for this rung, or for a higher rung of the same dimension, meets it; the result names the route.
- Decided by
- A rule
- Evidence
- The profile and the tools/list response; or the ACP document
- Steps
- wellknown, ucp.handshake
- Made as
- anon, ucp