Celo's Dual-Standard Bet: Why Supporting Both x402 and MPP Matters

· · 4 min read · x402MPPCeloM2M

Last month, Celo Core Co. launched x402.celo.org, a native payment facilitator giving AI agents a stablecoin payment rail on Celo. Then, quietly, they added a second standard: MPP (Machine Payments Protocol), backed by Stripe and Tempo. Celo is now the first blockchain to support both major agent payment standards natively — and that dual bet tells us something important about where the M2M economy is heading.

TL;DR: Celo supports x402 (Coinbase ecosystem, 75M July transactions) AND MPP (Stripe ecosystem) on the same facilitator. This means the agent payment standards war isn't settled — and Celo is positioning itself as neutral infrastructure, not a partisan. For developers, it means: build once, accept payments from either standard. For the ecosystem, it means the discovery layer (where minia2a operates) becomes even more important.

The x402 Facilitator: How It Works

Celo's x402 facilitator is a lean, four-endpoint HTTP API that lets AI agents pay for services in stablecoins without accounts, API keys, or human sign-off.

EndpointMethodPurpose
/verifyPOSTOff-chain signature check of a payment payload
/settlePOSTSubmits buyer's authorization on-chain (facilitator pays gas)
/supportedGETLists supported (network, scheme) pairs
/healthGETLiveness probe

The settlement mechanism uses EIP-3009's transferWithAuthorization: the buyer signs a stablecoin authorization off-chain, the facilitator submits it on-chain, and funds move directly from payer to seller. The facilitator never custodies funds — the token contract handles the transfer. Settlement is sub-second, gas costs under $0.001, and supported tokens are USDC and USDT on Celo mainnet.

<$0.001gas per settlement
sub-secondsettlement time
USDC + USDTsupported tokens
non-custodialfunds never held

Then Came MPP: The Dual-Standard Play

Shortly after the x402 launch, Celo added native support for the Machine Payments Protocol (MPP) on the same facilitator infrastructure. MPP is backed by Stripe and Tempo — it's the other major standard competing for the agent payment rail.

This is strategically significant. While x402 has the Coinbase ecosystem and Linux Foundation governance with 40 founding members (Visa, Mastercard, Stripe, AWS, Google, Circle, Ripple), MPP brings Stripe's developer ecosystem and enterprise payment infrastructure. By supporting both, Celo is making a deliberate bet:

The agent payment standards war isn't over. Both x402 and MPP are viable, both have major backers, and both are gaining adoption. Celo's play is to be the Switzerland of agent payments — the chain where developers can accept either standard without choosing sides.

Why This Matters for the M2M Economy

The Celo dual-standard strategy reveals three things about the agent payment market in August 2026:

1. The infrastructure layer is becoming commoditized

Settlement is now available on Base, Casper, XDC, Celo, Algorand, Polygon, and more — each with sub-second, sub-cent transactions. When settlement speed and cost converge to zero across chains, the competitive differentiator shifts up the stack: to discovery, reputation, compliance, and developer experience.

2. Multi-standard is the pragmatic choice

Celo isn't picking sides because developers shouldn't have to either. An agent that needs to call an API shouldn't care whether the API accepts x402 or MPP — it should just work. Celo's facilitator abstracts the standard away from the developer, and that's the direction the market is heading.

3. Discovery becomes the bottleneck

With settlement solved and multiple standards available, the question becomes: how do agents find which APIs to pay for? This is where minia2a operates — 284 x402 services with free trials on every endpoint, 6,447 trials served to 316 agent developers. When every chain supports every standard, discovery is the differentiator.

284services on minia2a
6,447free trials served
316agent developers
75Mx402 July txns

The Bigger Picture: Standards Competition Is Healthy

The fact that both x402 and MPP are thriving — not one crushing the other — is actually good for the ecosystem. It means:

This is also why the x402 Foundation's multi-stakeholder governance under the Linux Foundation matters. With Visa, Mastercard, Stripe, AWS, Google, Circle, Ripple, and others at the table, x402 is evolving from a Coinbase project into an industry standard — but MPP's Stripe backing ensures it won't be the only standard.

What Developers Should Do Now

If you're building AI agents that need to pay for APIs, data, or compute:

  1. Don't bet on one standard. Build your agent to handle x402 AND MPP payment flows. Celo's facilitator shows how both can coexist on one chain.
  2. Use a discovery layer. Don't hardcode API endpoints. Use a directory (like minia2a.uk) that lets your agent discover services at runtime with pricing, trial availability, and payment rails.
  3. Start with free trials. minia2a offers 15 free calls on all 284 services. Your agent can test API quality before committing a single cent.
  4. Watch the regulatory landscape. The EU AI Act (Article 50, effective Aug 2) and Korea's new AI agent payment liability standards mean compliance will become a competitive moat. Choose infrastructure that's hosted in regulated jurisdictions.

Give your AI agents a wallet — they earn, they spend, you stay in control.

284 x402 services · 15 free trials per endpoint · USDC on Base · No KYC

→ Explore minia2a.uk