Inside x402's Breakout Traction

x402 had a busy June.

Transactions spiked, settling into a baseline roughly 2x above May, as a clear use case emerged: activity clustered around a single seller (the inference router BlockRun). Enterprise adoption continued as Amazon integrated the protocol and Cloudflare announced its Content Monetization Gateway. Technical upgrades leave x402 more robust and more attributable heading into summer, the qualities it needs to survive the trial Cloudflare is about to put it through.

Let's catch up on what's new, what's working, and what's still unproven.

More sellers are coming online

If you're using x402, this section's for you.

In June, Apify joined x402, letting buyers access its library of web automation and scraping tools using USDC on Base (still the protocol's overwhelming home). You can now scrape Twitter, Reddit, TikTok, and Facebook with stablecoins, though not all of its "Actors," Apify's name for these scripts, are created equal.

Next, Exa, the AI search engine, extended x402 support to Solana, so web and content search can be paid for there. I recommend it for quality research, especially when scoping out a project.

Then there's Seal, a personal assistant platform that released Hacks: custom agent skills that bundle API calls into a single task. It's built as a marketplace with x402 underneath, a use case that hits close to home and one I hoped for in “My x402 Wishlist.” Good to see it live, and I'm keen to try it.

Finally, the Merit Systems team keeps bringing new data feeds online, usable inside Poncho, its x402-augmented chat app.

The rails got more practical

At the protocol level, two updates stand out.

• Builder Codes — An x402 payment can now carry a record of which app, client, or facilitator originated it, enabling the referral and revenue-sharing loops that make marketplaces possible.
• Batch settlement — Instead of settling every tiny request onchain one at a time, buyers fund an account once, sign off on repeated purchases, and let the seller collect in batches later. For inference, search, or any flow where a buyer makes hundreds of micro-payments, settling one by one would be too slow and expensive to bother. That makes the high-frequency case viable.

Beyond that, x402 now works across more languages and chains, which mostly means it's getting easier to integrate wherever a seller already builds.

Distribution shows up

The updates that matter most came from outside crypto.

AWS added a way to charge AI traffic at the edge. When a buyer requests a protected resource, AWS can return a price and payment terms, verify payment, then serve access. Any publisher or API sitting behind AWS can now treat agents as paying customers.

Then the headliner: Cloudflare. On July 1st it opened the waitlist for its Monetization Gateway, which will let customers charge for anything behind Cloudflare: pages, datasets, APIs, tools. Payments settle in stablecoins over x402, verified at the edge. Content monetization is the use case x402 was heralded for, the one meant to fix an internet whose economics broke once bots became the primary source of traffic. Bots read the content, no ad clicks follow, and publishers eat it: costs up, revenue down. Cloudflare sits in front of roughly 20% of the web, which makes its gateway the first real test of charging bots for what they take.

The open question is scale. On our podcast, Cloudflare's CEO championed x402 as the fix but flagged the catch himself: blockchains can't yet move the volume this needs. Monetizing even a slice of Cloudflare's traffic would demand millions of transactions per second, well beyond what any chain he tested delivers. That gap has to close first.

Which use case wins

A few use cases have emerged for x402. 

Inference routing appears the biggest, with BlockRun proving buyers want a way into these services without juggling subscriptions. Premium data is close behind, since buyers pay for better inputs and better inputs improve what they produce.

Both are durable, though neither have the reliable revenue that would make x402 a necessary piece of the new internet. Content monetization, on the other hand, does. If agents are going to pay for the web they consume, that's the use case that turns x402 from useful into ubiquitous. Cloudflare will be where we find out whether it holds.