Menu

Explorer & Settings

Tempo Explorer Submit Project
🗺️ Protocol Overview

AI Agent Payment Protocols

The standards letting AI agents pay for things — x402, MPP, A2A, AP2, ACP, L402 and MCP — across 1.5k tracked open-source projects. What each does, and when to reach for it.

Protocol What it is Best for Projects
x402 Per-request HTTP 402 rail; USDC on Base/EVM/Solana. The default for charging agents per API/MCP call. Paid APIs & MCP tool calls 1.2k
MCP Model Context Protocol; paid MCP servers charge agents per tool call (often via x402). Monetizing agent tools 320
A2A Agent-to-Agent protocol; standardizes how agents discover and pay each other. Multi-agent coordination + payment 194
MPP Machine Payments Protocol — broad agent-to-agent & machine-to-machine settlement standard. Autonomous agent-to-agent settlement 142
AP2 Agent Payments Protocol; the authorization layer — mandates, limits, delegated authority. Delegated payment authorization 34
ACP Agentic Commerce Protocol; end-to-end agent commerce on top of a payment rail. Agent-driven commerce flows 21
L402 Lightning-native HTTP 402; settles BTC over Lightning with macaroon auth. Bitcoin/Lightning micropayments 20

Project counts are live from the mpp.best ecosystem dataset, classified by protocol and sorted by prevalence.

How the stack fits together

These protocols aren't rivals so much as layers. Payment rails like x402 and L402 handle the actual settlement of value. Coordination & authorization layers — MPP, A2A and AP2 — decide who pays whom, how much, and under what mandate. ACP sits higher still, orchestrating full commerce flows, and MCP is the tool-access surface where a lot of agent monetization actually happens.

In practice you'll often combine them: an MPP or AP2 authorization on top, x402 settlement underneath. Read x402 vs MPP for the most common pairing.

Frequently asked questions

What are the main AI agent payment protocols?

The emerging agentic-payments stack includes x402 (per-request HTTP 402 payments in USDC), MPP (Machine Payments Protocol for agent-to-agent settlement), A2A (agent-to-agent coordination), AP2 (Agent Payments Protocol authorization layer), ACP (Agentic Commerce Protocol), L402 (Lightning-native HTTP 402), and MCP (Model Context Protocol, whose paid servers charge per tool call). They operate at different layers and are often combined.

Which agent payment protocol should I use?

For charging agents per API request or MCP tool call, x402 is the most mature. For autonomous agents paying each other, look at MPP and A2A. For delegated authorization and spending mandates, AP2. Many real systems combine them — e.g., MPP or AP2 for authorization with x402 for settlement.

How do these protocols relate to each other?

They stack rather than compete. Higher-level protocols (ACP, AP2, MPP, A2A) handle discovery, authorization and coordination, while payment rails (x402, L402) handle settlement. MCP is the tool-access layer where much agent monetization happens.