Author: David Christopher
Compiled by: Saoirse, Foresight News
x402 experienced rapid business development in June.
Protocol transaction volume surged significantly, stabilizing at roughly double the level seen in May. A clear use case has emerged: the vast majority of transaction activity is concentrated with a single service provider—the inference routing project BlockRun. Enterprise adoption continues to materialize: Amazon completed integration with the protocol, and Cloudflare officially announced the launch of its content monetization gateway. A series of technical upgrades have substantially improved the stability and transaction traceability of x402 as it enters the summer months. These very features are essential prerequisites for x402 to face the practical test that Cloudflare is poised to bring.
Next, we will review the latest developments, the directions already validated as viable, and the hypotheses yet to be proven.
x402scan platform's featured services rankings (based on 30-day data), showcasing the activity, transaction amount, transaction count, number of buyers, and hosting blockchain for three AI data/gateway service providers charging by call: BlockRun, twit.sh, and StableEnrich.
More Service Providers Continuously Joining the Ecosystem
If you are using x402, this section is worth special attention.
In June, Apify announced its integration with x402. Developers can now use the USDC stablecoin on the Base blockchain (which remains the protocol's primary operating network) to call its web automation and data scraping toolkit. Users can now leverage stablecoins to scrape data from platforms like Twitter (X), Reddit, TikTok, and Facebook, although the quality of various automated scripts (which Apify calls Actors) within the platform is uneven.
Following closely, the AI search engine Exa expanded x402 payment support to the Solana blockchain, allowing users on this public chain to pay for web retrieval and content search services. This is particularly suitable for in-depth information research, especially for due diligence on new projects.
The personal AI assistant platform Seal launched a feature module called Hacks: a customizable agent capability that bundles multiple API requests into a single automated task. This product's underlying marketplace is built using x402, which aligns perfectly with a key application scenario I previously described in my article "My Wishlist for x402's Development." I'm delighted to see the product officially launched and plan to try it myself.
Additionally, the Merit Systems team continues to roll out new data streams, accessible for its conversational application Poncho, which is equipped with the x402 protocol.
Kevin Leffew, co-author of the x402 whitepaper, commented on Seal's Hacks feature built on x402: users can create and sell AI agent automation skills described simply in text, earning revenue per call. Kevin believes this direction has broad prospects.
Significant Enhancement in Practicality of Payment Infrastructure
Two major protocol-level updates are particularly crucial:
- Builder Codes (Developer Identifier Codes): x402 payment transactions can now be tagged with the application, client, or service intermediary that initiated the payment. This feature enables the construction of distribution affiliate and revenue-sharing systems, clearing obstacles for various marketplace ecosystems.
- Batch Settlement: Eliminates the need for separate on-chain settlement for every small payment request. Buyers only need to pre-fund their accounts and authorize a series of consecutive purchases, with service providers later aggregating funds in batches. For high-frequency, small-amount payment scenarios like AI inference and information retrieval, where per-transaction on-chain costs and latency are infeasible, batch settlement makes the high-frequency micro-payment model a reality.
Furthermore, x402 has added support for more programming languages and compatibility with multiple blockchains, essentially lowering the integration barrier for various service providers.
DukeOphir, a core member and de facto maintainer of the x402 ecosystem, announced project development progress: code commits exceeded 1,000, developers surpassed 300, and various technical components have expanded multiple times within half a year of v2's launch.
Channel Boost from External Mainstream Internet Giants
The most impactful developments did not originate from the crypto-native industry.
AWS launched an edge node AI traffic billing solution. When a user requests a protected resource, an AWS edge node can return pricing and payment terms, verify payment credentials, and then grant access to the resource. Any content site or API deployed on AWS can now treat AI agents as paying customers.
The main event, however, comes from Cloudflare. On July 1st, its Content Monetization Gateway officially opened for waitlist applications. Using this gateway, customers can charge for any resource hosted on Cloudflare: web content, datasets, various APIs, and tool services can all be monetized. Transactions are settled using stablecoins via x402, with payment validation occurring at the edge nodes.
Content monetization is precisely the core application scenario that initially made outsiders optimistic about x402. The current internet business model is fundamentally imbalanced: various crawler bots account for the vast majority of traffic. These bots scrape content without generating ad clicks, forcing website operators to bear bandwidth costs without revenue compensation. Cloudflare handles approximately 20% of global website traffic. Therefore, this gateway represents the first large-scale, real-world test for the model where bots pay to scrape internet content.
The biggest question at this stage is performance scaling. Cloudflare's CEO publicly endorsed x402 as the solution in a podcast but also pinpointed the core bottleneck: current blockchain throughput is temporarily insufficient to handle the required transaction volume. Even monetizing just a small fraction of Cloudflare's traffic would require millions of transactions per second, far exceeding the performance of any public chain he has tested. This performance gap must be bridged first.
Source: Bankless interview with Matthew Prince, Co-founder and CEO of Cloudflare.
Which Application Track Will Ultimately Prevail?
Several viable application tracks have already emerged within the x402 ecosystem.
AI inference routing appears to be leading in scale, with BlockRun having validated market demand: users want to access various inference services through a single interface without managing multiple individual subscriptions. The paid high-quality data track follows closely, as developers are willing to pay for superior input data, which significantly enhances large language model output quality.
Both tracks represent real and sustainable demand. However, by themselves, they are unlikely to make x402 an indispensable foundational component of the next-generation internet. In contrast, the content monetization track possesses this potential. If various AI agents need to pay for the web content they scrape, this scenario could propel x402 from being a useful tool to achieving mass adoption. The practical implementation of the Cloudflare gateway will test whether this path is viable.
