ProtocolProtocol profile
Agent Payments Protocol
Protocol using verifiable credentials and payment mandates for agent commerce.
Official link: ap2-protocol.org (opens in a new tab)Sources checked November 13, 2026
Source-linked research and editorial guidance. Capabilities are not independently tested unless a profile explicitly includes a reproducible test record. Sources checked November 13, 2026.
Evidence status
- Description
- Source summary — not runtime-tested
- Testing
- Not runtime-tested No runtime test, payment test or security audit was performed for this release. A source shows that something is documented, not that it was independently tested.
- Identity
- Candidate record; identity not fully resolved
- Evidence note
- Published description inspected; no execution, interoperability, security, payment or performance test performed.
- Version or lifecycle
- Google announced v0.2 and donation to FIDO Alliance on 2026-04-28; release announcement is not proof that every implementation runs v0.2.
Agent Payments Protocol explained
Source-based explanation with an editorial checklist
- Layer
- Payment authorization
AP2 describes payment mandates and verifiable credentials for agent commerce. Model the authorization evidence separately from the payment service and its settlement mechanism.
Limitations
Protocol membership or an announcement does not prove that a particular merchant supports a particular release.
Version and lifecycle
Google announced v0.2 and donation to FIDO Alliance on 2026-04-28; release announcement is not proof that every implementation runs v0.2.
Implementation checklist Editorial
- Record mandate type, issuer, scope, expiry, implementation release and the evidence connecting authorization to a payment
Sources: ap2-protocol.org (opens in a new tab), blog.google/products-and-platforms/platforms/google-pay/agent… (opens in a new tab)
What it does
Description
Source summaryProtocol using verifiable credentials and payment mandates for agent commerce.
Source: ap2-protocol.org (opens in a new tab) (observed November 13, 2026)
Evidence gaps
What the inspected sources did not establish. Unknown does not mean absent or unsupported.
- Pricing: Not established by the inspected sources
- Documented interfaces (MCP or other): Not established by the inspected sources
- People, organization and funding: Not established by the inspected sources
- Repository: Not established by the inspected sources
Verification backlog High priority
- Approval policy
- Runtime compatibility
- Independent task results
- Recheck volatile prices and versions at publication
Related records to investigate
Linked by topic; not a ranking or a verified compatibility claim.
Category: Agent payments and commerce
Compared in: x402, AP2, ERC-8004 and ERC-8183: payments, authority, identity and jobs
x402
HTTP payment protocol for charging clients for internet resources.Agentic Commerce Protocol (OpenAI and Stripe)
Commerce interaction model connecting buyers, agents and businesses for checkout and delegated payments.Agent Commerce Protocol (Virtuals)
Framework for agreements and commerce among autonomous agents.ERC-8183 Agentic Commerce
Proposed job escrow interface with client, provider and evaluator roles.Universal Commerce Protocol
Commerce building blocks spanning discovery, checkout and subsequent interactions.Sources
- ap2-protocol.org (opens in a new tab)
- blog.google/products-and-platforms/platforms/google-pay/agent… (opens in a new tab)
Spotted something out of date? Suggest a correction