Six weeks ago, there was one way to pay for an agent API call via x402: Coinbase CDP. Today, there are four. And they're not just copying each other — they're building for fundamentally different use cases.
This is good news for agent developers. But it also creates a new problem: which facilitator should your agent use? And more importantly — how do you discover services without being locked into one payment rail?
An x402 "facilitator" is the component that handles the payment leg of an HTTP 402 exchange. When an agent hits a paid endpoint, the facilitator verifies the payment, settles in stablecoins, and issues a receipt. The service provider never touches the agent's wallet.
As of August 9, 2026, the active facilitators are:
| Facilitator | Launched | Backed By | Settlement | Key Differentiator |
|---|---|---|---|---|
| Coinbase CDP | Jul 2025 | Coinbase (NASDAQ) | USDC on Base | First mover, $50B cumulative volume, CDP SDK integration |
| Cloudflare Wallets | Aug 4, 2026 | Cloudflare (NYSE) | USDC on Base/Solana | CDN-scale, human-readable .pay handles, per-agent spending caps |
| OSL AgentPay | Aug 7, 2026 | OSL Group (HKEX:863) | USDT/USDC/USDGO | Multi-stablecoin, multi-protocol (x402+AP2+MPP), zero gas, fiat ramps |
| Circle | Jul 2026 | Circle Internet Financial | USDC native | USDC issuer itself; deep stablecoin liquidity |
This isn't fragmentation for fragmentation's sake. Each facilitator is optimized for a different part of the agent economy.
Coinbase was first to market, and it shows in the numbers: ~200 million transactions, $50 billion in cumulative volume, ~150,000 merchant endpoints. CDP is deeply integrated into the Coinbase developer ecosystem — if you're already using Coinbase APIs for wallet infrastructure, CDP Facilitator is the path of least resistance.
The trade-off: CDP is USDC on Base only. If your agent needs USDT or multi-chain support, you need something else.
Cloudflare's move is the most strategically interesting. Every domain behind Cloudflare already has a wallet handle (example.cloudflare.pay). The Monetization Gateway (launched July 1) lets any site charge agents via x402 without touching a crypto SDK. Cloudflare abstracts the blockchain layer entirely — sites set a price, agents pay, Cloudflare handles settlement.
The trade-off: Cloudflare is betting that the infrastructure layer is where the value accrues. They're building a closed-loop system: Cloudflare sites → Cloudflare wallets → Cloudflare settlement. Great for Cloudflare customers, less useful if your service runs elsewhere.
OSL's entry is significant because it bridges two worlds that have been separate: traditional finance and agent payments. OSL is a publicly traded, regulated stablecoin platform in Hong Kong. AgentPay supports USDT, USDC, and USDGO — and crucially, it supports multiple payment protocols (x402, AP2, MPP) simultaneously.
The Banxa integration for fiat on/off-ramps is the killer feature: an enterprise that wants agents to pay for API access can receive settlement in fiat without ever touching a crypto exchange. This is the bridge that could bring the Fortune 500 into agent-to-agent payments.
Circle's facilitator is the simplest and potentially the most powerful: as the issuer of USDC, Circle has direct access to the deepest stablecoin liquidity pools. Their facilitator is USDC-native with no bridging, no wrapping, no additional smart contract risk. For high-volume agent payment flows, this matters.
If you're building an agent that needs to pay for API calls, you now have four payment rails to choose from. The good news: competition drives down fees and improves reliability. The catch: each facilitator has its own SDK, its own wallet format, its own receipt format.
This is where facilitator-agnostic tooling becomes critical. Your agent shouldn't need to know whether the service it's calling settles through Coinbase or Cloudflare or OSL. It should just work.
A marketplace that's neutral across facilitators solves a real problem: service providers can register once and accept payments through any facilitator their customers use. Agents can browse one catalog and pay with whatever wallet they already have.
Think of it like the web itself: HTTP doesn't care whether your server runs on AWS, GCP, or bare metal. The protocol abstracts the infrastructure. x402 does the same for payments — the facilitator is the infrastructure layer, and the discovery layer sits above it.
At minia2a, we're building that facilitator-agnostic discovery layer. 324 services, 252 with active trial usage, 11,661 trials served — and growing. Service providers register once. Agents discover once. The payment rail is an implementation detail.
What we're seeing in August 2026 is the formation of a proper technology stack for agent commerce:
| Layer | What it does | Who's building it |
|---|---|---|
| Discovery | Catalog, search, trial, pricing | Marketplaces, MCP directories, agent search engines |
| Protocol | HTTP 402, payment negotiation, receipts | x402 Foundation (Linux Foundation, 40+ members) |
| Facilitation | Wallet, settlement, identity | Coinbase, Cloudflare, OSL, Circle, PayAI |
| Settlement | Stablecoin rails, blockchain finality | Base, Solana, Ethereum L2s |
Each layer is becoming competitive independently. That's the sign of a real technology stack — not a single-vendor solution, but an ecosystem where developers can mix and match.
The facilitator layer differentiating is not a problem — it's proof that the market is real. When multiple publicly traded companies invest in building competing payment infrastructure for the same protocol, it means they've done the math on the addressable market.
For agent developers: build facilitator-agnostic. Your agent's payment rail should be configurable, not hard-coded. The facilitator you pick today might not be the best one in six months.
For service providers: list on facilitator-agnostic marketplaces. Don't tie your revenue to one payment processor. The agent economy is too young for vendor lock-in.
The x402 stack is forming. The protocol layer is standardized. The facilitator layer is competitive. The discovery layer is where agents and services meet. Build for the stack, not for a single vendor.
minia2a is a facilitator-agnostic marketplace for x402 agent services. 324 services, 252 with active trial data, USDC on Base. Browse the catalog →