Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-01 · high
There's no Stripe integration or billing code to write, just a price and settlement over x402, a protocol already moving $600M a year with zero fees.
Why now: Cloudflare paired this waitlist with its companion Content Independence Day report, arguing the free-crawling era for creators is already ending.
Cloudflare opened a waitlist for its Monetization Gateway, letting any page, API, dataset, or MCP tool behind its network charge per request, per its blog post.
For builders, per-request pricing on APIs, datasets, and tools becomes a config setting. It used to be a project that ate weeks of chargeback and PCI work.
The protocol behind it isn't a demo. x402, which Cloudflare co-governs with Coinbase, has processed more than 119 million transactions on Base and 35 million on Solana. That's close to $600 million a year in volume, with zero protocol fees.
I've built payment flows before. Chargebacks, PCI scope, subscription edge cases, they eat weeks even when the product is simple.
Put a price on a 402 response instead, and Cloudflare settles it in stablecoins over x402. No Stripe integration, no billing logic to write.
That math changes what's worth shipping. A single-purpose MCP tool can charge a fraction of a cent per call and let agents pay for themselves. No subscription tier could justify that on its own.
Cloudflare's companion Content Independence Day report frames the bigger shift: agents are displacing search referrals, and creators are stuck between staying discoverable and getting paid. The gateway is the toll booth for that shift.
Yes, but it's waitlisted and stablecoin-only, so whether human buyers tolerate a crypto paywall like an agent will is still open.
Each link below shares sources, entities, or timing with this story.
Mastercard partners with Cloudflare / Shared entities / Earlier coverage
Linked by a graph relationship (Mastercard partners with Cloudflare); both cover Base, Cloudflare, Coinbase, SaaS; earlier Base coverage from 2026-06-11.
Cloudflare supports MCP / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Cloudflare supports MCP); both cover Cloudflare, MCP; reported by the same outlet (blog.cloudflare.com).
Cloudflare supports MCP / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Cloudflare supports MCP); both cover Cloudflare, MCP, SaaStr; overlapping topics (agent, already, cloudflare).
SaaStr uses Salesforce / Shared entities / Shared topic / What happened next / Tension / Downstream implication
Linked by a graph relationship (SaaStr uses Salesforce); both cover SaaS, SaaStr; overlapping topics (agent, billing, care).
Cloudflare supports MCP / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Cloudflare supports MCP); both cover Cloudflare, Cloudflare Blog; reported by the same outlet (blog.cloudflare.com).
Cloudflare supports MCP / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Cloudflare supports MCP); both cover Cloudflare, MCP, Monetization Gateway; overlapping topics (cloudflare, dataset).
Cloudflare supports MCP / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Cloudflare supports MCP); both cover Cloudflare, MCP, SaaS; reported by the same outlet (blog.cloudflare.com).
Linked by a graph relationship (Cloudflare supports MCP); both cover Cloudflare, HTTP, MCP; reported by the same outlet (blog.cloudflare.com).