AI Agent payment protocols overview · a 7-protocol survey
ConfidenceLikelyUpdated2026-05-26Review by2026-09-22Sources6Machine-translatedOriginal (JA)
Wiki route
This entry sits under agent-economy INDEX. Read it against AI Agent payment 7-protocol layering table for peer / contrast context and payments index for the broader system / regulatory boundary.
Key facts
- The industry shorthand “4 protocols” refers to AP2 + x402 + MCP + A2A — the 4 most frequently cited •
- At the AP2 launch (2025.09) there were already 60+ partners (Coinbase / MetaMask / Salesforce / American Express) •
- x402 is not chain-specific but rides the HTTP standard — any stablecoin, any chain can connect •
- MCP is the LLM ↔ tools protocol released by Anthropic in 2024.11 , followed by OpenAI in 2025 •
- In mid-2026 年 the FIDO Alliance took over AP2 , renaming it AAIF (Agentic AI Identity Federation) •
Mechanism / How it works
The 7 protocols divide labor by layer. The intent layer (where the user expresses “I want to buy Y for X yen”) is handled by AP2 / SPT / ACP, which process the mandate’s 3-layer trust chain (Intent → Cart → Payment), fixed in place with VC + DPK signatures. The transport layer (the actual money transfer) is handled by x402 , which revives the HTTP 402 Payment Required header to realize per-call USDC micropayments; the Lite version has already landed in Cloudflare Agents / Vercel AI SDK. The context layer (how the LLM invokes tools) is handled by MCP, which standardizes the LLM ↔ tools / data-sources interface, while A2A handles agent-to-agent communication. The 3 layers are complementary, not mutually exclusive. A complete agent payment flow usually invokes AP2(intent) + x402(transport) + MCP (context) simultaneously. The lower layer depends on ERC-4337 Overview · Application-Layer Implementation of Account Abstraction and ERC-7702 Overview · The Pectra Upgrade Where EOAs Temporarily Gain SCW Functionality, which provide programmable wallet capability.
Origin & evolution
2024.11 MCP debuted, establishing the de facto standard for the “LLM interface.” 2025.05 Coinbase launched x402 , reviving the 30-year-old HTTP 402 status code and binding it to USDC (for USDC’s role see USD Stablecoin Interchange Market). 2025.09 Google, together with 60+ partners, launched AP2 , positioning it as “the standard for agent payment intent.” Within 2025 年, secondary competing protocols such as SPT (Skyfire) / ACP (Catena Labs · Sequoia-backed) / TAP (xpay) appeared one after another. In mid-2026 年 FIDO took over AP2 and renamed it AAIF; Apple / Microsoft / Mastercard joined and the federation expanded to 100+ — the protocol layer entered the channel of commoditization, analogous to WebAuthn / OAuth / OpenID Connect (for detail see Commoditization of Agent payment protocols and the upward migration of value).
Related
- Wiki Index
- AI Agent payment 7-protocol layering table
- Commoditization of Agent payment protocols and the upward migration of value
- Five-layer unbundling of central-banking functions
Sources
- Google AP2(Agent Payments Protocol · intent-layer mandate) — https://github.com/google-agentic-commerce/AP2
- Coinbase x402(HTTP 402 -native payment · transport layer) — https://github.com/coinbase/x402
- Model Context Protocol (Anthropic · LLM ↔ tools · context layer) — https://github.com/modelcontextprotocol/modelcontextprotocol
- Agent2Agent (A2A) Protocol (agent-to-agent communication) — https://github.com/a2aproject/A2A
- Agent Commerce Kit (Catena Labs · ACK-ID / ACK-Pay) — https://www.agentcommercekit.com/overview/concepts
- BIS Project Agorá (official endorsement of the protocol layer) — https://www.bis.org/about/bisih/topics/fmis/agora.htm
Discovery
Keep reading
Read next
- The current state of AI companies' payment methodsSource note: public billing / payment documentation and public AI-company product pages; cross-border payment implications are framework-level synthesis.
- AI-driven trading regulation · Japan FSA / SESC plus global FCA / SEC / ESMA comparison 2026AI-driven trading regulation in 2026 sits on top of the existing algorithmic-trading regulatory perimeter rather than as a separate "AI trading rule." The Japan FSA + SESC (Securities and Ex...
- AP2 · Google Agent Payments Protocol overviewAP2 extends the traditional user-merchant two-party payment into a user-agent-merchant three-party structure, introducing 4 core components:
Links here
- Agent Payment Infrastructure Research ReportThe current Agent payments space has already formed a 4 -protocol coexistence landscape:
- AI agent legal and tax liability framework · who is liable, how is agent income taxedAs of mid-2026, no major financial regulator (US SEC / CFTC / FinCEN, UK FCA, Japan FSA, Singapore MAS, EU ESMA / EBA) has formally granted AI agents independent legal personhood, and no maj...
- Agent Payment Protocol four-way comparison matrix 2026 · AP2 / x402 / Skyfire / Nevermined plus ERC-7715 + Lit PKPSelecting an agent payment rail in 2026 is not "pick the best protocol" — it is "compose the layer cake correctly so the merchant accepts, the wallet authorizes, and the regulator does not b...
- Agent Protocol Mainnet Adoption · 2026-05 Production-Readiness SnapshotAs of May 2026, the agent-payment protocol stack has bifurcated sharply between mainnet-shipped infrastructure and testnet / consortium-only specs. The production-live tier is dominated by x...
- Commoditization of Agent payment protocols and the upward migration of valueAfter protocol commoditization, take rate cannot be extracted from an open-source standard (one cannot levy an HTTP-protocol fee). Value capture is forced to migrate upward to vertical distr...