x402 vs AP2: what is the difference?
Short answer
They solve different problems and can be used together. x402 moves money for a single HTTP request. AP2, the Agent Payments Protocol started by Google, proves that a person authorized an agent to make a purchase, using signed records called mandates. AP2 does not use HTTP 402 and was donated to the FIDO Alliance in April 2026.
Side by side
| x402 | AP2 | |
|---|---|---|
| Full name | x402 | Agent Payments Protocol |
| Started by | Coinbase, May 2025 | Google, announced September 16, 2025 |
| Governed by | x402 Foundation (Linux Foundation) | FIDO Alliance, since April 28, 2026 |
| Main question it answers | How does this request get paid for? | Did the person really authorize this purchase? |
| How | A 402 reply and a signed token transfer | Signed mandates, issued as verifiable credentials |
| Uses HTTP 402 | Yes | No |
| Travels over | HTTP, MCP, A2A | An extension for A2A and MCP |
| Pays with | Blockchain tokens | Cards first. Digital currencies are on the roadmap |
| Typical purchase | A fraction of a cent for an API call | A shopping order placed by an agent |
The problem each one solves
x402 is about settlement. A server names a price, a client pays it, and the money moves. The protocol does not ask who the client is or whether a person approved the spend. That is left to the wallet and its limits.
AP2 is about authorization and accountability. When an agent buys something on a person's behalf, the merchant, the card network and the bank all want evidence that the person asked for it. AP2 provides that with mandates: signed records of what the person approved, such as a Checkout Mandate and a Payment Mandate. If there is a dispute later, the mandates show who agreed to what.
So AP2 sits a layer above the payment. It says a purchase is authorized. Something else still has to move the money.
How they fit together
They are designed to combine. An agent can hold an AP2 mandate that proves its user approved a purchase, and then settle that purchase with x402. Google's agentic commerce organization publishes an extension that carries x402 payments over the A2A protocol, and AP2 ships an x402 sample.
When each matters
- An agent calling paid APIs and tools: x402. The amounts are tiny, the buyer is software, and a spending limit on the wallet is enough control.
- An agent placing an order with a merchant on a card: AP2-style authorization matters, because card payments can be disputed and someone has to show consent.
- Both at once: an agent that shops on your behalf and pays in stablecoins would use AP2 for the consent record and x402 for the transfer.
Related work
AP2 version 0.2 was published alongside the donation to FIDO. Verifiable Intent, a related specification co-developed by Mastercard and Google, was donated to FIDO at the same time.
Sources
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.