Cloudflare's AI Wallets Unlock Stablecoin Spend-but NET's 18% Shock Shows the Market Wants Revenue, Not Hype

Cloudflare targets machine payments, but investors are focused on monetization

Cloudflare is aiming at a real bottleneck: agents lack a native way to pay for APIs, and around 57% of web traffic consists of bots. Its response is stablecoin wallets for AI agents with allowances, approved-merchant lists, and maximum transaction sizes. As a payment-rail design, that is coherent. The harder question for investors is whether a new rail will convert into visible revenue soon enough to matter.

The earnings reaction put that question in sharp relief

Cloudflare reported first-quarter earnings that beat expectations, but shares still fell 18% in extended trading after the company disclosed a 20% workforce reduction affecting more than 1,100 employees globally. That reaction suggests investors were not willing to look through cost actions just because the quarter beat.

Why the stock still needs proof

The bullish case is easy to see: the Monetization Gateway plus wallets could create a path toward usage-based pricing as agents become more prominent on the internet. The bearish case is simpler: if customer adoption has to come first, the story is still too early for a market that wants clearer revenue visibility now.

How Cloudflare's agent-pay stack is supposed to work

The key constraint is not whether AI can reason. It is whether an AI can complete a transaction. Cloudflare is addressing that with two pieces that only matter together: Cloudflare Wallets for AI agents on the buyer side and the Monetization Gateway on the seller side. The traffic backdrop matters too, because around 57% of web traffic consists of bots.

Payment is the credential

Right now, agents hitting a paywall often run into a login page designed for humans, need a human to add a payment method, and then wait for API key generation. Cloudflare's approach is to make payment the credential. Buyers get spending control through Account Wallets or delegated Virtual Wallets with a hard spend cap. Sellers use the Monetization Gateway to decide what can be charged: web pages, datasets, APIs, or MCP tools.

x402 attaches payment directly to HTTP

Then x402 handles the payment flow inside HTTP. The client requests a resource, and the server replies with 402 Payment Required plus price, token, network, and merchant address. The client retries with a signed payment payload. The server verifies the payment, settles the transaction on-chain, and returns the resource. No signup, no session, no preexisting relationship, no accounts, credentials, or session tokens.

The mechanism is clear; commercial proof is not

That design could make access a programmable commerce event, letting agents discover, test, and consume endpoints with less human friction. But mechanism is not the same as installed base. Wallets payments are still "coming soon," and the Gateway opened as a waitlist. The real test is whether merchants put valuable endpoints behind paywalls and whether agents transact reliably at scale.

What matters for NET from here

Scotiabank's $300 price target points to roughly 5 percentage points of upside to second-half estimates if traffic keeps leading revenue. That matters because the last report still produced a sharp post-earnings selloff after the layoff disclosure. The message from the market appears to be this: traffic can support the thesis, but monetization still has to start showing up.

Bull case: traffic could turn into revenue before it shows up in reports

The tradable setup is an estimate reset, not just a story rerating. If Cloudflare becomes infrastructure for machine spend, usage could improve before reported revenue fully catches up. The setup is still early, but it is real enough to trade: Monetization Gateway waitlist plus Cloudflare Wallets for AI agents give the company a plausible path to sit in the flow of agent transactions at the edge.

Bear case: early-access products are not yet revenue

The cleanest bear objection is straightforward: waitlists and wallet architecture are not reported monetization. Those products can remain relevant for quarters without showing up clearly in earnings. After the market rejected a headline beat, that distinction matters more.

What would change the view

This framework gets weaker if products that are still in early-access or waitlist form remain stuck there, if agents still break at adding a payment method, or if traffic continues to improve without any disclosed monetization bridge.