USDC (USDC)

Cloudflare released something a couple of days ago, called the Monetization Gateway. This is a business model that only makes sense in the AI era, and it might be the real face of Web3. It's not because it's particularly disruptive. It's that it finally captures a problem that has been talked about for years but never materialized, using a particularly dirty and labor‑intensive approach. Simply put: in the future, when AI wants to read your web page, call your API, or use your tool, it won't need to register or obtain a key; it could just be charged a fee, and the money would automatically go into your wallet. Why hasn't this been possible before? Two long‑standing obstacles. One is the payment channel. Traditional channels can't handle transactions below a few cents; charging a 1‑cent fee may cost more in channel fees than the amount itself, and settlement is slow. Below a certain amount, the cost of processing exceeds the payment. The other is that billing systems need to call APIs. If you want usage‑based billing, you have to turn yourself into a half‑payment provider, building a full stack of usage tracking, billing, and reconciliation, which is expensive to implement. So most companies choose the simpler seat‑based pricing. Cloudflare's solution this time is to embed the payment into a normal HTTP request. It uses the hardly‑used 402 status code (Payment Required). The AI sends a request, the server replies that payment is required, quotes 1 cent, and provides a USDC address. The AI agent's built‑in wallet automatically pays, attaches the payment proof to the request, and resends it; a role called the facilitator verifies that the money was indeed paid and then lets the request through. It's like a subway turnstile with no password. Tap the card, the fee is deducted, and you pass without taking out a wallet or being redirected to a checkout page. The money moves via a stablecoin, such as USDC. Settlement is sub‑second, ~0 fees, and there is no chargeback. The x402 protocol is not exclusive to Cloudflare; the earliest reference implementation came from Coinbase, and now it is hosted by the Linux Foundation's x402 Foundation with 25+ industry partners. At first glance this looks like a product for site owners to monetize traffic. But in my view, this is a pivotal shift in Cloudflare's business model and deserves deeper consideration.

First judgment: It turns from a channel and security provider into a combined checkout + ID verification. For the past 30 years, Cloudflare has been a CDN, a security service, an edge network—essentially helping your traffic pass faster and safer. Now it moves payment verification and identity authentication (Web Bot Auth) to its edge nodes in over 330 cities, so a single request validates who you are and whether you have paid before being forwarded to the origin. The origin only cares about setting prices and writing rules. Metering, payment exchange, and settlement are all moved away from the origin. This means Cloudflare shifts from being a toll for traffic to being the infrastructure that takes a cut of transactions. Those are two completely different valuation anchors. Second judgment: It sits at the intersection of AI and crypto, holding more than one card. According to the pattern we’ve observed, the biggest opportunities arise at the convergence of two domains; whoever holds multiple cards gets the foothold. Cloudflare now has three cards: a global edge network (330+ cities), identity/security (Web Bot Auth), and payments (x402). Also, Cloudflare is a partner of Open USD (OUSD). On the other side, USDC last year positioned itself from a trading tool toward an AI‑payment infrastructure. The two fit together perfectly. Cloudflare needs a payment lane that can handle a few cents, and USDC needs real micro‑machine‑to‑machine use cases. If this stack rolls out, stablecoins will truly move from exchanges and DeFi into everyday requests on mainstream web. This is the trend we’ve been watching: stablecoin total supply is already around $315 billion, and its next big use case is likely automated payments by AI agents.

Third judgment, which I think the market has not fully priced in: expectation gap. Currently the market values Cloudflare (NET) as a CDN plus zero‑trust security company. But if it truly becomes the settlement and identity layer for the AI‑agent economy, every wallet‑enabled agent would have to pass through its edge, have its identity verified, and use its payment system. That narrative would have a completely different valuation anchor. I can’t say it will definitely happen, but the trend points that way. However, it’s still in the rollout phase and it’s unclear whether it will prove feasible. First, it is still on a waiting list; the original text describes the functionality but no public pricing page or real large‑scale usage data. There’s a huge gap between a demo and daily real‑world usage. Second, Cloudflare’s role, although it does not handle the money directly or act as a P2P settlement, handles verification and settlement. If Cloudflare is both the edge network and the default orchestrator, it sits on the critical path of all machine‑to‑machine traffic. Even though the protocol is open, the points of trust in practice may remain highly centralized. Third, stable‑coin regulation is always uncertain. USDC is currently the most compliant, but policy remains an unknown. Fourth, from free to paid: when a free web becomes a paywall web, the openness of the internet will be reshuffled. Whether that is good in the long run cannot be answered now. The product is still on a waitlist; don’t treat it as a reality yet. Nevertheless, this rollout is the most recent example I’ve seen of AI automated‑payment commerce being put into practice. It may not win, but the direction is the right one.