Circle Ships an App Store for AI Agents — and Discovery Becomes the Moat

On August 16, Circle shipped an Agent Marketplace: a curated catalog of x402-compatible services that accept USDC. You can browse it at agents.circle.com/services, and — more interestingly — query it through a Discovery API that needs no key, no account, and no registration.

I curled it to see what's actually in it, because launch posts and data usually disagree. The catalog is live and small enough to read in full: 1,055 resources as of this morning. Each one carries a machine-readable accepts[] — asset, network, amount, payTo — plus input/output schema. An agent can discover, price, and pay for a service without a human touching a form.

Three giants shipped the same thing in 48 hours

Circle's launch didn't happen in a vacuum. In the same two-day window, Coinbase put its x402 Bazaar behind the AiFi effort, and AWS surfaced the Coinbase Bazaar MCP server through AgentCore. Three of the largest platforms in the space independently shipped a discovery layer for machine-to-machine payments, all on the same protocol.

That convergence is the story. A standard stops being a bet and starts being infrastructure when the giants compete on who lists it rather than whether it works. x402 is now infrastructure.

The tell hiding in the top listing

Here's the detail that reveals where the moat is moving. The number-one resource in Circle's catalog settles through Stripe custody — its accepts[].extra carries a live stripe_payment_intent_id and stripe_mode: "custody". Payments rails themselves are being absorbed by the two companies best positioned to run them.

When rails are a commodity war, the durable value isn't in the rails. What's left over is the layer that answers two questions no custody provider can fake:

• Is this service real? Circle's listing mechanic is now the default answer — services are continuously health-checked and auto-excluded the moment they're unreachable.
• Is this volume real? A catalog can list a thousand endpoints; the honest signal is how many settle actual USDC, not how many return a 402.

Getting listed is now a checklist — but distribution is still a chokepoint

Circle's docs are refreshingly concrete about what a seller needs: return 402 Payment Required for unpaid requests, publish an OpenAPI spec, and submit a payout wallet that gets sanctions-screened. There's no self-serve endpoint yet — a POST to the Discovery API returns 404, and submission is a manual-review intake form. The docs' own words: "A self-serve, automated submission flow is coming."

That last sentence matters more than the launch. While listing is manual-review-gated, getting in is the real bottleneck for every seller — and the winners of the discovery layer will be the ones who make verification cheap and listing honest, not the ones with the biggest catalog.

The takeaway isn't "Circle wins." It's that the agent payment stack now has three commodity layers — protocol (x402), settlement (USDC onchain), and rails (Stripe/Circle custody) — and one scarce layer on top: verification and honest volume. That's the layer the discovery wars will be fought on.