Niches · Agent checkout protocols
Buy later, while the person is away, inside limits they signed
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The purchase matches every signed constraint, the mandate is used no more times than allowed, it expires and can be revoked, and the merchant or issuer can verify it, as the spec and SDK document.
How agents ask for it: buy concert tickets when they go on sale, up to 200
, reorder coffee when it is under 15
, book the flight if it drops below 400
Does the job, with a limit 5
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.
| Listing | Why |
|---|---|
| American Express Agentic Commerce Experiences (ACE) F American Express Company | Intent Intelligence captures purchase intent for authentication, authorisation and disputes, and Amex says Card Members get spend and intent controls. Mandate fields, expiry and revocation sit in specifications behind a confidentiality agreement. source |
| Agent Payments Protocol (AP2) C Google LLC | Open mandates carry exp and constraints for merchants, line items, amount range, budget, recurrence and execution date, and unknown constraints fail. Open issues report verifiers never consuming a closed mandate so one consent paid twice (acc-10), SDK checks that pass negative amounts (acc-12), and no revocation path (acc-13). source |
| Mastercard Agent Pay E Mastercard | Verifiable Intent v0.1 lets the user sign autonomous-mode constraints (products, merchants, amount) with lifetimes of 24 hours to 30 days, verified by merchant or network, with a test suite for constraint checking. It has no credential revocation protocol beyond removing a key from JWKS, and no commit since 2026-04-20. source |
| Universal Commerce Protocol (UCP) BB UCP Authors (Google, Shopify and co-developers) | The AP2 mandates extension carries signed mandates, canonicalised with JCS so they verify later, but it inherits AP2's gaps: no revocation path for open mandates and verifiers that don't consume closed ones. source |
| Visa Intelligent Commerce D Visa Inc. | Purchase instructions carry consumer-set limits, can be created, updated and cancelled through the VIC APIs and MCP tools, and network controls enforce merchant and amount. The APIs are restricted to onboarded agents, and the instruction schema is not public. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Agentic Commerce Protocol (ACP) C OpenAI and Stripe | The delegated payment allowance MUST be reason one_time, bound to one checkout session with a max_amount and expires_at; there is no standing mandate for a later purchase and no revocation. source |
What stops agents finishing
- no documented way to revoke an open mandate
- SDK constraint checks that pass bad amounts
- access needs a card-network or issuer partnership
Around it
Before: scheduling.trigger, checkout-protocols.find-and-cart. After: checkout-protocols.dispute-evidence, notifications.notify-person.
Where this comes from
Weight 20 of 100 in Agent checkout protocols: 5 of 18 accounts (acc-09, acc-10, acc-12, acc-13, acc-16); mostly implementers testing AP2 and Verifiable Intent, no person-away purchase reported in production
The same as data: /api/v1/use-cases/checkout-protocols.delegated-purchase.json, or the MCP tool get_use_case with id checkout-protocols.delegated-purchase. Other jobs in this category: /api/v1/niches?category=checkout-protocols.
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.