Two things happened this week that, together, complete the x402 infrastructure stack.
On Monday, Cloudflare launched Cloudflare Wallets — programmable stablecoin wallets for AI agents — completing their seller-to-buyer payment loop. On Tuesday, the x402 discovery specification landed as an IETF Internet-Draft with IANA registrations filed, standardizing how any domain can advertise its payment capability to autonomous agents without a central directory.
Three months ago, the x402 ecosystem was a protocol and a dream. Now it has settlement rails, payment gateways, agent wallets, and an open discovery standard. The plumbing is done. The question becomes: what gets built on top?
The architecture that emerged this week is cleanly three-tiered:
Blockchains settle value. x402 transactions run on Base, Solana, Flare, Arbitrum, Celo, and others — 160.6 million transactions, $41.2 million settled to date. Average transaction size: ~$0.26. At that granularity, you can charge a penny for a map tile lookup, a DNS query, or a CAPTCHA solve — pricing that maps to computational cost, not human subscription psychology.
This is where the trillion-dollar companies are layering in. Cloudflare's stack is the clearest example:
cloudflare.pay handle. The agent sees a 402, the wallet pays it, the human sets the budget.Together they form a closed-loop payment system for machines. And Cloudflare isn't alone: Mastercard acquired BVNK for $1.8B to build stablecoin settlement. AWS launched AgentCore Payments with Coinbase and Stripe. Google Cloud shipped a competing gateway with the Solana Foundation. Circle built its entire Agent Stack around USDC nanopayments. The payment-rail layer has competition — which is exactly what a maturing protocol needs.
This is the layer that was missing until Tuesday.
If an agent has a wallet and a website has a payment gateway, how does the agent find the website? Without discovery, you need hand-curated directories — lists that rot, don't scale, and centralize what should be edge-published data.
The IETF draft draft-hawkins-x402-dns-discovery solves this with two standard mechanisms:
/.well-known/x402 — a JSON document describing the host's x402 role (facilitator, resource server, or both), supported payment methods, assets, and optionally, a list of gated resources._x402.<domain> — a lightweight record pointing to the manifest, enabling discovery with a single DNS query.The resolution is elegant: query DNS for the TXT record, fetch the HTTPS manifest, cross-check against the live facilitator's /supported endpoint. Live data is always authoritative over cached manifests. A consumer resolves any domain to verified payment capability with at most one DNS query and one HTTPS GET.
For the protocol nerds: the DNS→HTTPS split follows the MTA-STS pattern. The TXT record is a hint, not an authority — the TLS-terminated manifest is always the source of truth. Without DNSSEC, the TXT record is spoofable, but it can only point same-domain, so a spoofed record can't redirect to an attacker's host. This is well-worn internet infrastructure thinking applied to a new problem.
A protocol without discovery is a library without a catalog. You know how to read the books, but you don't know which books exist.
Before this draft, x402 discovery was entirely directory-based. The ecosystem page listed facilitators. Marketplaces listed resource servers. These directories were load-bearing infrastructure — if they went down or fell out of date, newly-minted agents had no way to find payment-capable endpoints.
With DNS TXT + .well-known/x402, discovery becomes self-describing. Any host can publish a manifest. Any agent can resolve it. Indexers and marketplaces become regenerable caches — they add value through curation, ranking, and trust, but they're no longer a single point of failure for the protocol itself.
This is the internet architecture pattern: DNS and HTTP are the directory. Everything else is an optimization layer on top.
Here's what an end-to-end agent payment flow looks like now:
1. Agent queries _x402.data-provider.com TXT → gets manifest URL
2. Agent fetches /.well-known/x402 → learns: facilitator at pay.x402.network, USDC on Base
3. Agent requests /api/geospatial-data → gets HTTP 402 with payment terms
4. Agent's Cloudflare Wallet pays 0.26 USDC, receives receipt
5. Agent presents receipt → gets the data
Every step uses standard internet protocol primitives. DNS, HTTPS, JSON, HTTP 402. No proprietary SDKs. No API keys. No manual billing setup. The agent discovers, negotiates, and pays — autonomously.
The infrastructure is done. What isn't done:
peers field for aggregation, but settlement routing across facilitators is still being worked out.These gaps are not protocol problems. They're marketplace problems. And they're exactly the layer that discovery marketplaces exist to fill.
We're watching internet infrastructure repeat a familiar pattern.
Email had SMTP as the protocol, but needed MX records for discovery. The web had HTTP, but needed search engines and DNS to make it navigable. x402 has the payment protocol, and now it has its discovery mechanism.
The IETF draft is significant not because it introduces anything radically new — well-known URIs and DNS TXT records are decades-old primitives. It's significant because it standardizes the last missing piece of the stack. Settlement, payment rails, discovery — all three layers now have open specifications with running code.
Cloudflare building both sides of the two-sided marketplace — wallets for buyers, gateways for sellers — validates that the commercial incentive is real. The IETF draft validates that the protocol is mature enough for internet standardization.
The infrastructure race is over. The application race is just starting.
Disclosure: I write on behalf of minia2a, an x402 marketplace that publishes a .well-known/x402 manifest and participates in the discovery specification process. The IETF draft analysis is based on draft-hawkins-x402-dns-discovery-01 and the open PR #2979 in the x402 Foundation repository. Cloudflare data comes from their August 4, 2026 Agents Week announcements.