Three things happened in the last 72 hours that clarify the agent payment landscape better than any analyst report could:
These three data points reveal the same thing: the payment rails are being commoditized, and the discovery layer is the open battleground.
By August 2026, the agent payment infrastructure has settled into five distinct layers:
| Layer | Function | Key Players | Status |
|---|---|---|---|
| Protocol | Payment request/authorization standard | x402 (Linux Foundation), MPP (Stripe/Tempo) | ✅ Mature |
| Settlement | Blockchain/stablecoin rails | Base, Solana, Polygon, XRPL, Algorand | ✅ Mature |
| Routing | Which model/API, at what cost/latency | OpenRouter (Stripe), AWS Bedrock, Google Vertex | 🔒 Consolidating |
| Banking & Custody | Fund holding, compliance, trust | Catena Labs ($30M a16z), Fireblocks | 🏗️ Building |
| Discovery | Which APIs exist, what they do, are they reliable | Open battleground | 🔴 Fragmented |
Stripe's OpenRouter deal essentially locks up Layer 3 (Routing). The protocols (Layer 1) and settlement chains (Layer 2) are already mature with 169M+ x402 payments processed. Banking (Layer 4) is being built by well-funded startups.
But Layer 5 — Discovery — has no dominant player. And that's the layer that decides which APIs agents actually call.
Right now, there are four competing models for agent API discovery:
Coinbase's x402 registry auto-discovers services by crawling the network. 14,865 services across 1,561 hosts. The upside: exhaustive coverage. The downside: zero curation. No ratings, no health checks, no quality signals. An agent searching for "token security" gets dozens of results with no way to distinguish a reliable endpoint from one that's been down for weeks.
Model: Google-style crawl-and-index. Problem: ranking by raw request volume is gameable. The top results aren't necessarily the best — they're the ones with the most bot traffic.
Tempo's mpp.dev covers MPP services exclusively — high quality, institutional listings including Anthropic, OpenAI, and Dune Analytics. Lightning-focused directories like Satring cover L402. Each is excellent within its protocol but invisible to agents using other payment standards.
Model: Walled garden. Problem: the agent economy won't be single-protocol. Agents will use x402 for some calls, MPP for others, L402 for Lightning-native services.
Cinderwright indexes across x402 (1,457 services), MPP (92), and L402. Offers paid market intelligence endpoints — gap analysis, category deep dives, competitive reports. Satring started as an L402 directory (562 services) and now accepts x402 payments too. Both are moving toward cross-protocol coverage.
Model: Data platform. Problem: indexing services is different from making them discoverable and usable by agents.
300 curated services, every single one with a free trial (15 calls). Agents don't just see a list — they test the endpoint before committing capital. The catalog is smaller than Coinbase Bazaar's 14K but every listing is verified: uptime monitored, schema documented, pricing transparent. EU-hosted (AWS Ireland) for GDPR compliance.
Model: App Store. Problem: curation doesn't scale as fast as auto-indexing. The catalog needs to grow while maintaining quality.
This isn't theoretical — we've seen this movie before:
2009–2012: Payment rails were the bottleneck. Stripe won by making payments easy.
2026: Payment rails are solved. x402, MPP, USDC on Base — the rails work. The new bottleneck is discovery.
When every agent can pay for any API with a single HTTP 402 header, the question stops being "can I pay for this?" and becomes "which of these 14,865 APIs should I pay for?"
The data from minia2a's own platform supports this. Across 6,911 trials from 316 unique agent users:
| Endpoint | Trials | Unique Users | Calls/User |
|---|---|---|---|
| captcha-solve | 822 | 133 | 6.2 |
| gas-price | 473 | 106 | 4.5 |
| recall (memory) | 420 | 29 | 14.5 |
| web-scrape | 304 | 60 | 5.1 |
| fear-greed-index | 115 | 5 | 23.0 |
The pattern is clear: utility endpoints acquire users (captcha: 133 users), data endpoints retain them (recall: 14.5 calls/user, fear-greed: 23.0 calls/user). A discovery layer that only lists APIs without understanding this usage pattern can't guide agents to the right tools.
Based on what's working and what's not across all four models:
Agents don't browse. They query. A discovery layer that forces agents to read documentation before trying an endpoint loses to one that lets them call the endpoint immediately with a free trial. The decision to pay happens after the first successful call, not before.
Coinbase Bazaar's ranking by raw request count is trivially gameable — a service that gets botted looks more popular than a genuinely useful one. Discovery needs multi-dimensional signals: uptime, latency, trial-to-paid conversion, user retention, schema completeness.
The agent economy won't settle on a single payment protocol. x402 dominates today (169M transactions), MPP is growing (Stripe-backed, institutional quality), and L402 has a dedicated Lightning-native community. A discovery layer that only works with one protocol is building on rented land.
If you're building an agent that calls paid APIs:
Here's my prediction for how the discovery layer evolves:
The payment rails are built. The routing layer has its $10B champion. The banking layer is well-funded. The only question left is: who will agents ask when they need to find an API?
Data: minia2a /api/stats, August 4, 2026. 300 services, 6,911 trials, 316 agent users, 342,692 total requests.