The agent payment stack is converging
A year ago, “AI agents that pay for things” was a handful of demos. In 2026 it’s a layered stack — and the layers are starting to snap together.
If you’re building agents today you keep hearing four acronyms: x402, A2A, AP2, and ACP. They are not competitors fighting for the same slot. They sit at different layers of the same problem: how does one piece of software discover, negotiate with, and pay another piece of software — with no human in the loop?
This guide explains how the pieces fit, and points you at the real, active open-source projects implementing each layer right now.
Why trust the project picks below? Every repository referenced here is tracked in the mpp.best directory of 1,400+ agent-payment projects. We surface what is actually being shipped — not press releases.
The four layers, in plain English
Think of an autonomous agent buying a service from another agent. Four things have to happen:
| Layer | Question it answers | Protocol |
|---|---|---|
| Discovery & messaging | How do two agents find and talk to each other? | A2A (Agent2Agent) |
| Commerce / intent | What is being bought, at what price, with what authorization? | AP2 & ACP |
| Payment transport | How is “pay me first” expressed over the wire? | x402 |
| Settlement | What money actually moves, on what rail? | USDC / stablecoins on Base, Solana, etc. |
The big 2026 story is that these layers are interoperating. The clearest proof is Google’s google-agentic-commerce/a2a-x402 extension, which bridges crypto payments (x402) directly into the A2A messaging layer. When the discovery layer and the payment layer ship a joint extension, the stack is real.
Layer 1 — x402: the payment transport
x402 repurposes the dormant HTTP 402 “Payment Required” status code into a full payment handshake. An agent requests a resource, the server replies 402 with payment terms, the agent pays, and retries with proof. No accounts, no API keys, no dashboards.
It’s the transport layer of agent payments — the part that says “you must pay to continue” in a way both humans and machines understand.
Real projects shipping x402 today:
coinbase/x402— the reference protocol and the gravitational center of the ecosystem.Merit-Systems/x402scan— an ecosystem explorer for x402 activity.- Middleware that turns any endpoint into a paid one: lightweight SDKs and “402-compatible” wrappers are one of the fastest-growing categories — see our tools hub for builders and converters.
If you only learn one layer, learn this one — it’s the connective tissue. Start with our x402 pillar guide.
Layer 2 — A2A: how agents find and talk to each other
A2A (Agent2Agent) is the messaging and discovery layer: a standard way for agents to advertise capabilities (“agent cards”), send tasks, and stream results. It answers “who can do this job, and how do I ask them?” — not “how do I pay?”
That payment gap is exactly why the a2a-x402 extension exists: it lets an A2A task carry an x402 payment requirement, so discovery and payment happen in one flow.
Real A2A projects:
a2aproject/a2a-go— a Go SDK for the A2A protocol.google-agentic-commerce/a2a-x402— the crypto-payment extension that ties A2A to x402.
A2A is the single most-referenced protocol across the projects we track — a strong signal that the messaging layer is consolidating around it.
Layer 3 — AP2 & ACP: the commerce layer
This is where intent and authorization live. Two efforts are shaping it:
- AP2 (Agent Payments Protocol) — a standard for expressing a verifiable payment mandate: what the agent is authorized to buy, up to what amount, and on whose behalf. It’s the “permission + intent” layer that sits above raw payment transport.
- ACP (Agentic Commerce Protocol) — the commerce-flow standard pushed from the mainstream-payments side (the OpenAI/Stripe orbit), focused on checkout, catalogs, and merchant integration for agents.
The mental model: AP2/ACP decide what and whether; x402 carries the pay-now; stablecoins do the settling. A robust agent stack will likely speak ACP/AP2 to express commercial intent and fall back to x402 for the actual on-chain settlement.
See our protocol comparison page for a side-by-side of where each one fits.
Layer 4 — settlement: USDC, Base, and Solana
None of the upper layers matter without money moving. In practice that money is USDC (and other stablecoins), and the two dominant rails are:
- Base — the most common chain in agent-payment projects we track, driven by Coinbase’s x402 work.
- Solana — the fastest-growing second rail, favored for low-latency micropayments. Projects like
ProwlFi/ProwlFiare building “private rails for the agentic economy on Solana.”
For developers choosing a rail, the trade-off is ecosystem gravity (Base) vs. latency/cost (Solana). Either way, USDC is the de-facto settlement currency — see our USDC payments guide.
How to actually build on this stack today
You don’t need all four layers on day one. A pragmatic path:
- Gate your service with x402. Wrap an existing API or MCP server so it returns
402with USDC terms. This is the fastest way to earn per-request revenue. (Use our x402 builder.) - Give your agent a wallet. Agent-wallet projects (the category behind repos like Coinbase-adjacent spend SDKs and autonomous “agent with a wallet” tools) let your agent hold and spend USDC under policy limits.
- Speak A2A if your agent needs to discover and hire other agents — and adopt the
a2a-x402extension so payment rides along. - Layer in AP2/ACP when you need verifiable mandates and merchant-grade checkout.
Browse implementations of every layer in the full directory or jump to our curated tools hub.
Where the money is being made
The reason this stack matters commercially: each layer has a business model that’s already being tested.
- Facilitators take a small cut of each x402 settlement.
- Paywall / middleware SaaS charges developers to gate their APIs.
- Agent wallets monetize spend infrastructure.
- Routers take a margin on each routed call + payment.
- Marketplaces take a cut when agents hire agents.
- Data / explorers sell access to ecosystem activity.
If you’re picking where to build, the under-served, high-demand slots in 2026 are AP2/ACP ↔ x402 bridges and trustworthy facilitators — the connective pieces, not yet another wallet.
FAQ
Is A2A a competitor to x402?
No. A2A is the messaging/discovery layer (how agents talk); x402 is the payment transport layer (how “pay first” is expressed). They’re complementary — Google’s a2a-x402 extension exists specifically to combine them.
What’s the difference between AP2 and ACP?
Both live at the commerce layer. AP2 (Agent Payments Protocol) focuses on verifiable payment mandates — what an agent is authorized to spend. ACP (Agentic Commerce Protocol) focuses on the merchant-facing checkout/commerce flow. In practice they overlap and a full stack may use both.
Do I need all four protocols?
No. Most teams start with x402 to charge per request, add an agent wallet to spend, and only adopt A2A and AP2/ACP when they need agent-to-agent discovery or merchant-grade mandates.
What currency do agents actually pay in?
Overwhelmingly USDC, settled on Base or Solana. Stablecoins are the de-facto unit of account for machine-to-machine payments today.
Where can I find projects for each layer?
The mpp.best directory tracks 1,400+ agent-payment projects across all four layers — x402 facilitators, A2A SDKs, agent wallets, and settlement infrastructure. Start with the tools hub for ready-to-use builders.
The agent payment stack is moving fast. mpp.best tracks every layer in real time — explore the directory or check our protocol comparison.