x402 vs AP2 vs ACP: Which Should My AI Agent Use?
They solve different problems. x402 pays for APIs and web resources in stablecoins, ACP runs checkout inside an AI platform, and AP2 records what the user authorised. Most agents that shop need more than one.
The short answer: they solve different problems, so it's rarely either/or. x402 lets an agent pay for an API or web resource in stablecoins over HTTP. ACP lets an agent complete checkout with merchants that support it inside an AI platform. AP2 is about proving what the user authorised the agent to buy.
x402: paying for things on the web, in stablecoins
x402, created by Coinbase, uses the HTTP 402 "Payment Required" status code. A server replies 402 with a price, and the agent pays in stablecoins and retries. It suits machine-to-machine payments: API calls, data, compute, pay-per-request content. It isn't designed for buying a pair of shoes from an ordinary online shop.
ACP: checkout inside an AI platform
The Agentic Commerce Protocol, from OpenAI and Stripe, lets an AI platform complete checkout with merchants that have implemented it. It works well where the merchant has integrated, but your agent can only use it with those merchants.
AP2: proving what the user authorised
Google's Agent Payments Protocol focuses on authorisation. It uses signed "mandates" to record what the user asked for and approved, so merchants, payment providers and the user can verify an agent's purchase afterwards. It's designed to work across payment methods rather than replace them.
So which should your agent use?
| If your agent needs to… | Look at |
|---|---|
| Pay per call for APIs, data or compute | x402 |
| Check out with merchants inside an AI platform that supports it | ACP |
| Prove what the user authorised for a purchase | AP2 |
| Buy from any ordinary online shop today | A one-time virtual card from a wallet |
That last row is the gap. Much of the web still runs on a normal card checkout, and many merchants haven't adopted an agent protocol yet. An agent that shops broadly needs a card it can use safely at any checkout.
Where Agent Pay Safe fits
Agent Pay Safe works today at ordinary online checkouts: your agent gets a one-time virtual card for each approved purchase, checked against your spending mandate. One MCP connection covers any MCP-compatible agent, so you don't build a separate payment integration for each platform. Non-custodial x402 stablecoin payments are coming soon, in the same wallet.
For more on the protocol landscape, read UCP, ACP and AP2: why AI agent payments have three competing protocols.