Learn / What is AP2 (Agent Payments Protocol)?
What is AP2 (Agent Payments Protocol)?
AP2 (Agent Payments Protocol) is an open protocol led by Google that focuses on the authorization side of agent payments: cryptographically verifiable mandates that prove an AI agent is allowed to spend on a person's or company's behalf. Where x402 answers "how does an agent pay?", AP2 answers "who said this agent may pay, and up to how much?"
How a mandate works
A user grants their agent a signed mandate — for example, "this agent may spend up to $50 per month on data APIs." Merchants and payment rails can verify the mandate before accepting an agent-initiated transaction, creating an audit trail of intent that survives disputes.
Rail-agnostic by design
AP2 deliberately does not pick a settlement rail. A mandate can authorize spending over card networks, bank transfers, or stablecoin rails like x402 — which is why the two protocols are increasingly described as complementary layers rather than competitors.
Where it stands
AP2 is an emerging spec with growing wallet and merchant interest, but as of mid-2026 it has far less production volume than x402. Its natural role is becoming the authorization layer that the x402 Foundation stack still lacks.
Frequently asked questions
Is AP2 a competitor to x402?
Mostly no. x402 handles per-request payment execution; AP2 handles authorization and spending mandates. An agent can present an AP2 mandate and settle the actual payment over x402.
Who created AP2?
Google introduced AP2 as an open specification, with input from payments and wallet partners.
What problem does AP2 solve?
Trust. Merchants need proof that an autonomous agent is acting with its principal's consent and within limits — AP2's verifiable mandates provide that proof.
Live, curated, and machine-readable.
Compare all three standards