Niches · Agent checkout protocols

Recognise a trusted agent and check its credential before accepting the order

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
4companies, fit with a limit
32companies carry the tag
14share of the category's work
4first-hand accounts

What counts as done

The merchant verifies the signature against the published key directory, records which agent and platform placed the order, and rejects stale or replayed signatures, using test vectors the spec publishes.

How agents ask for it: is this bot a real agent, accept orders only from verified agents, check the agent signature

Does the job, with a limit 4

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.

ListingWhy
Agent Payments Protocol (AP2) C
Google LLC
Merchants verify mandate signatures by key id, and one merchant publishes discovery and JWKS files for v0.2 (acc-09). The repository has no signature test vectors or conformance suite, and agent identity signatures over HTTP are left to other specs. source
Mastercard Agent Pay E
Mastercard
Certified agents sign requests with RFC 9421 Web Bot Auth keys registered in payment-network directories, which merchants or edge providers verify. No Mastercard directory URL, test vectors or versioned spec were found in the guides read. source
Universal Commerce Protocol (UCP) BB
UCP Authors (Google, Shopify and co-developers)
Requests are signed per RFC 9421 with keys published in /.well-known/ucp, keyid as the JWK thumbprint, created and expires required and a nonce recommended, with Web Bot Auth compatibility. No signature test vectors were found in the spec or the conformance suite. source
Visa Intelligent Commerce D
Visa Inc.
TAP signs requests with created and expires at most 8 minutes apart and a nonce the merchant records to block reuse, with keys from a retrieval service. The spec has no version or test vectors (acc-15), and the reference proxy rejects the RFC 9421 keyid spelling (acc-14); both are open. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Agentic Commerce Protocol (ACP) C
OpenAI and Stripe
Clients SHOULD sign requests with a Signature and Timestamp header, but algorithms are published out of band, there is no key directory or test vectors, and no required field names the agent (acc-07). source
American Express Agentic Commerce Experiences (ACE) F
American Express Company
The Agent Registration specification, which would let a merchant or Amex verify an agent, is still under development per the ACE page; no key directory or test vectors are published. source

What stops agents finishing

  • reference implementation rejects the RFC spelling
  • no public API contract or sandbox for the card programmes

Around it

Before: agent-auth.sign-request. After: checkout-protocols.buy-for-person, checkout-protocols.dispute-evidence.

Where this comes from

Weight 14 of 100 in Agent checkout protocols: 4 of 18 accounts (acc-07, acc-14, acc-15, acc-17); Visa and Mastercard programmes have no other first-hand reports

The same as data: /api/v1/use-cases/checkout-protocols.verify-agent.json, or the MCP tool get_use_case with id checkout-protocols.verify-agent. Other jobs in this category: /api/v1/niches?category=checkout-protocols.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.