Idea 23 · Endpoint, a working name

Charge for anything. Get paid the moment it is used.

A price on any web page, dataset, API or MCP tool, paid per request and settled in stablecoins over x402, in seconds. The web is growing a payment layer, and its main customers will be agents.

A scripted demo: a price on a request, a 402 when it arrives without payment, a 200 the moment it settles. The total climbs as the calls land.

The shift.

Cloudflare has opened a waitlist for a Monetization Gateway: charge for any web page, dataset, API or MCP tool behind it, settled in stablecoins over the x402 open protocol. The company in front of a large share of the web is turning "pay per request" into a switch.

x402 revives HTTP 402, "payment required", a status code reserved since the web began and never used. The gap it fills is thirty years old.

Once one resource can charge per call, all of them can: pages, data, APIs, tools. And the caller is increasingly an agent, which arrives with no card and no account but can pay in stablecoins instantly.

Charge for anything, over x402, in stablecoins.

How it works.

01

Put a price on a resource

A page, an endpoint, a dataset, an MCP tool. Per call, per token, per download, your rule.

02

A request meets a 402, pays, and completes

A request arrives without payment and gets a 402: payment required, here is the price. The caller pays, human or agent, and the same request completes.

03

It settles in stablecoins over x402

In seconds, global and near free. You watch the total climb and take out what you want, when you want.

Where the opportunity is.

The rails are being built by the giants at once: Cloudflare's gateway, Coinbase's x402 and settlement, Stripe's stablecoins via Bridge. That is good news. You ride them, you do not build them, and the value moves up. The layer on top is thin and open.

The wedge

Discovery and routing, the buyer side.

As everything becomes a payable endpoint, agents must find, compare and route to the right one on price, quality and latency. The rails help you charge, not choose. Nobody builds the best-execution layer for the agentic web.

Or a vertical

One high-value resource class, done with real trust.

Monetise what the generic gateway skips: datasets with provenance and licensing, or paid MCP tools.

Or the seller's tools

Provider-agnostic seller tooling.

Pricing, metering, receipts, refunds and payouts across providers, not locked to one gateway.

The business.

A cut of the flow, or a fee on discovery and routing, depending on the fit chosen. Volume over ticket size, the model the rails themselves run on.

Questions.

Is this not just Cloudflare, Coinbase or Stripe?

They are the rails; this is the layer on top they do not build: finding and routing, or a vertical, or agnostic seller tooling.

Do buyers need crypto?

Agents pay in stablecoins natively; for people, the wallet step is handled, so they see a price and a receipt.

Is settlement really instant?

On-chain, in seconds, at a fraction of card fees. Moving it to a bank is a separate, optional step.

The giants are laying the rails. The layer on top, finding and routing the agentic web, is open.

All ideas