June Trading Volume Doubles: x402 Ecosystem Continues to Expand, Content Monetization Narrative Faces Key Test

BlockRun ignites demand, AWS and Cloudflare enter the fray; what does x402 still need for widespread adoption?

Written by: David Christopher

Compiled by: Saoirse, Foresight News

x402 experienced rapid business growth in June.

The protocol's trading volume surged significantly, stabilizing at about twice the level of May's trading volume, revealing a clear practical scenario: the vast majority of trading activities are concentrated on a single service provider—BlockRun, a reasoning routing project. Enterprises continue to adopt it: Amazon has completed the protocol integration, and Cloudflare has officially announced the launch of a content monetization gateway. A series of technical upgrades have greatly enhanced the stability and traceability of transactions for x402 as it enters summer, and these features are essential for the practical tests that Cloudflare is about to bring.

Next, we will outline the latest developments, the validated feasible directions, and the hypotheses that still need verification.

x402scan platform's selected service rankings (statistics from the past 30 days), showcasing the activity, transaction amounts, number of transactions, buyer counts, and operational metrics of AI data/gateway service providers BlockRun, twit.sh, and StableEnrich based on usage billing.

More Service Providers Connect to the Ecosystem

If you are using x402, this section is worth paying special attention to.

In June, Apify announced its integration with x402. Developers can utilize its web automation and data scraping toolset based on the USDC stablecoin on the Base chain (which remains the primary operating network for the protocol). Users can now scrape data from platforms like Twitter (X), Reddit, TikTok, and Facebook using stablecoins, although the quality of various automation scripts (which Apify calls Actors) varies.

Following closely, the AI search engine Exa expanded x402 payment support to the Solana chain, allowing users to pay for web retrieval and content search services on this public chain. This is particularly suitable for in-depth research, especially for due diligence on new projects.

The personal AI assistant platform Seal launched a feature module called Hacks: it allows multiple API requests to be bundled into a single automated task as a custom intelligent agent capability. This product is built on the x402 trading market, which is precisely the practical scenario I eagerly anticipated in my previous article "My Vision List for x402 Development." I am pleased to see the product officially launched, and I plan to experience it myself.

Additionally, the Merit Systems team continues to launch a new data information stream available for its chat application Poncho, which is equipped with the x402 protocol.

Kevin Leffew, co-author of the x402 white paper, shares his thoughts on Seal's Hacks feature based on x402: users can create AI intelligent agent automation skills for sale simply by describing them in text, earning revenue per call; Kevin believes this direction has great potential.

Significant Enhancement of Payment Infrastructure Usability

Two major updates at the protocol level are particularly crucial:

• Builder Codes: x402 payment transactions can now be tagged with the application, client, or service intermediary that initiated the payment. This feature enables the establishment of distribution commission and revenue-sharing systems, clearing obstacles for various trading market ecosystems.
• Batch Settlement: There is no need to settle each small request on-chain individually. Buyers only need to pre-load their accounts and authorize multiple continuous purchasing actions, allowing service providers to subsequently aggregate funds in bulk. For high-frequency small payments like AI reasoning and information retrieval, settling each transaction on-chain is not feasible due to cost and delay; batch settlement makes high-frequency micropayment models a reality.

In addition, x402 has added support for more programming languages and multiple blockchains, effectively lowering the integration threshold for various service providers.

DukeOphir, a core member and actual maintainer of the x402 ecosystem, announces project development progress, with code submissions exceeding 1,000 and over 300 developers involved; the scale of technical support for v2 has expanded exponentially within six months.

External Mainstream Internet Giants Bring Channel Benefits

The most impactful progress does not come from the native crypto industry.

AWS has launched an AI traffic billing solution for edge nodes. When users request protected resources, AWS edge nodes can return pricing and payment terms, verify payment credentials, and then grant access to resources. Any content site or API deployed on AWS can now treat AI intelligent agents as paying customers.

The main event comes from Cloudflare. On July 1, its content monetization gateway officially opened for applications. With this gateway, customers can charge for all resources hosted on Cloudflare: web content, datasets, various APIs, and tool services can all be included in the billing scope. Transactions are settled using stablecoins through x402, with payment verification completed at the edge nodes.

Content monetization is precisely the core application scenario that initially attracted external interest in x402. The current internet business model is already imbalanced: various scraping bots occupy the vast majority of access traffic, scraping content without generating ad clicks, leaving website operators to bear bandwidth costs without revenue compensation. Cloudflare handles about 20% of global website traffic, so this gateway will be the first large-scale real test for the paid scraping of internet content by bots.

The biggest question at this stage is performance scaling. The CEO of Cloudflare publicly endorsed x402 as a solution in a podcast but also pointed out the core bottleneck: the existing blockchain throughput cannot currently support the required transaction scale. Even monetizing just a small portion of Cloudflare's traffic requires processing capabilities of millions of transactions per second, far exceeding the performance of all public chains he has tested. This performance gap must be bridged first.

Source: Cloudflare co-founder and CEO Matthew Prince's interview on Bankless.

Which Application Track Will Ultimately Prevail?

Currently, multiple practical tracks have emerged for x402.

The AI reasoning routing seems to be leading in scale, as BlockRun has validated market demand: users want a one-stop call for various reasoning services without having to separately open and manage multiple subscription accounts. The premium data payment track follows closely, as developers are willing to spend money on high-quality input data, which can significantly enhance the output effects of large models.

Both tracks have real and sustainable demand, but relying solely on these two is insufficient for x402 to become an indispensable foundational component of the next-generation internet. In contrast, the content monetization track possesses this potential. If various AI intelligent agents need to pay for the web content they scrape, this scenario will push x402 from being a useful tool to widespread adoption. The practical implementation of the Cloudflare gateway will test whether this path can be successfully navigated.