The hype cycle around AI agents is finally maturing into infrastructure. A new breakdown from DEV.to maps the five core protocols powering agentic commerce: MCP, x402, AP2, ACP, and EAS. Each protocol solves a specific bottleneck in the agent-to-business interaction loop, but none of them alone creates a durable commercial record. This is not just about connecting tools; it is about defining who pays, who authorizes, and who keeps the receipt when the agent crashes.
The Payment and Access Layers
Anthropicβs Model Context Protocol (MCP), introduced in November 2024, acts as the 'USB-C for AI,' standardizing how models call external tools. However, MCP does not handle the business logic that follows a tool call. Enter Coinbaseβs x402, announced in May 2025, which turns payment into a native HTTP operation. By mid-2026, x402 processed 165 million agent transactions, backed by a foundation including Visa and Mastercard. While x402 ensures money moves via USDC on Base, it remains silent on whether the delivered service actually matched the agreement.
Authorization and Checkout Protocols
Googleβs Agent Payments Protocol (AP2), launched in September 2025 with over 60 partners like PayPal and American Express, addresses the 'who allowed this' question. AP2 uses Verifiable Credentials to capture user intent and payment mandates cryptographically. In 2026, Google donated AP2 to the FIDO Alliance for stewardship. Meanwhile, the Agentic Commerce Protocol (ACP), co-developed by OpenAI, Stripe, and Meta, defines the checkout flow itself. ACP powers features like Instant Checkout in ChatGPT, but it does not specify what happens if fulfillment fails after the checkout completes.
The Missing Commitment Layer
The Ethereum Attestation Service (EAS) provides the final piece: verifiable records that survive the systems that created them. EAS allows parties to register schemas and issue attestations on-chain or off-chain, anchoring evidence like delivery notes or verification results. However, EAS does not define commerce semantics on its own; it only proves a statement was signed. The critical gap in the current stack is the 'commitment layer'βa structured record of parties, terms, and recovery policies that exists before the transaction and persists after. The source article highlights the SAAX implementation as a potential solution to this gap.
Key Takeaways
- MCP standardizes tool access but does not handle payment or dispute resolution.
- x402 enables HTTP-native payments but does not verify service delivery quality.
- AP2 provides cryptographic user authorization via mandates but lacks full commercial terms.
- ACP defines the checkout flow but leaves post-checkout failure recovery undefined.
- EAS creates verifiable records but does not inherently define contract fulfillment logic.
The Bottom Line
We have standardized execution, authorization, and checkout, but we are still missing the durable agreement record. Until that layer is solidified, agentic commerce remains a convenient demo rather than a reliable business infrastructure.