On August 16, Circle shipped an Agent Marketplace — a curated catalog of x402-compatible services that accept USDC, browsable at agents.circle.com/services and queryable through a Discovery API that needs no key, no account, and no registration. It is the clearest signal yet that agent payment rails are done being the hard part.
I curled the API to see what's actually in it, because the launch post and the data usually disagree. The catalog is live and small enough to read: 1,055 resources as of this morning, each carrying 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.
Circle's launch did not 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 built 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, not on whether it works. x402 is now infrastructure.
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 (Stripe, Circle).
When the rails are a commodity war, whoever owns the rails is not where the durable value lives. What's left over is the layer that answers two questions no giant's custody 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.
Circle's own 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 is no self-serve endpoint yet — a POST to the Discovery API returns 404, and submission is a manual-review intake form. "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 actual 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.