Urgent.News

What's breaking now, across thousands of outlets.

Tech

Cloudflare Put a 402 Paywall Behind Every Domain. The Rail Was Never the Hard Part.

On 2026-09-30 Cloudflare opened a closed beta of its Monetization Gateway . It lets a domain owner charge agents per request over HTTP 402, settled in USDC on Base, through Coinbase's x402 Facilitator. We have settled on exactly that rail since we launched. So the interesting question is not whether the rail works — it plainly does — but what is left to build on top of it. What actually shipped,…

On September 30, 2026, Cloudflare launched a closed beta of its Monetization Gateway, which allows domain owners to charge agents per request over HTTP 402. The payment is settled in USDC on Base through Coinbase's x402 Facilitator. This is not a competing rail, but rather a payment method that can be used by any wallet that accepts USDC on Base.

The buyer side of the announcement is more interesting, as U.S. Cloudflare customers can pay per inference at request time by sending PAYMENT-METHOD: x402. This opens up a pay-per-call economy, where the buyer side is quieter and harder to integrate with. Cloudflare's gateway does not handle four key aspects of a marketplace: cross-seller discovery, first contact, accountability when delivery is bad, and provenance of the numbers.

The company publishes the split of settled payments versus total volume, acknowledging that most buyers' funds are funded by sellers themselves. Cloudflare owns key components of a marketplace, but lacks a catalog and a directory. The gating factor for sellers is the opening of the beta and the introduction of a fee.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Is Open Source no longer exciting!?

This blog has been a little while coming, but I guess today just makes for a good time to ask this funny question, following an announcement by Sindre about closing pull requests to external…

Relocating High-Performance Server to Networking Closet for Improved Setup and Functionality

Introduction: The Imperative of Strategic Relocation Consider a high-performance server such as the HP DL360 , equipped with 8TB SSD , 256 threads , 512GB DDR4 , and 1GbE networking , currently housed…

  • Server relocated from desk to networking closet to improve performance
  • Thermal management compromised on non-engineered surfaces
  • Networking closet ensures uniform weight distribution and airflow

More from Friday 2 October →