Overnight, a single operator listed eighteen pay-per-call endpoints on the public x402 discovery index. Each one is a different function from inside an agent: context compression, hallucination detection, temporal knowledge decay, attention allocation, multi-agent coordination, tool-selection optimization, prompt orchestration, decision verification, inference-cost routing, knowledge-graph synthesis, semantic deduplication, sentiment-adaptive response, workflow automation, agent memory. Eighteen functions, one operator, each sold in USDC per request.
Every one of them answers a clean HTTP 402 with {"error":"Payment required"} when you hit its root. The protocol wiring is correct. And every one of them has zero recorded calls.
That combination — clean protocol, zero demand — is the most important market signal in machine payments right now.
The eighteen endpoints read like a feature list ripped from an agent framework's internal design doc. Context compression. Hallucination detection. Temporal knowledge decay — the idea that a fact should matter less as it ages. Inference-cost routing — choosing the cheaper model for the task. Tool-selection optimization. Multi-agent coordination. These are not trivial utilities; they are the internals of the agent itself, split into individually billable units.
This is a new flavor of an already-visible pattern. Earlier this week a different single operator listed roughly eighteen geography-and-data subdomains in one sweep. Before that, the farms were utility endpoints — UUID generators, JSON validators, base64 codecs. The progression is: trivial utilities → data → the agent's own cognition.
It is not only solo operators. A facilitator wrapped a well-known speech-to-text API as a pay-per-call endpoint this week. A separate operator serves a local 27-billion-parameter language model through an OpenAI-compatible interface at five-tenths of a cent per call, with a free-trial endpoint. Brand-name APIs and local models are both showing up as billable x402 endpoints.
The through-line is that the rails of machine payments are now cheap enough that any function can be wrapped and listed in an afternoon. A Cloudflare Worker that returns a 402 challenge is not hard to build. The cost of becoming a pay-per-call supplier has collapsed, so the supply curve has bent sharply downward — first utilities, then data, now the agent stack itself.
Demand has not bent with it. The eighteen cognition endpoints have zero calls. Most of the new listings on the public index are pre-traction. A single public discovery API now indexes on the order of 14,000 listings across roughly 1,900 hosts, and the honest measure of demand — distinct wallets that actually paid in a week — is a rounding error against that inventory.
This is not a failure of the protocol. It is a normal early-market shape: the layer that got commoditized floods first, and the layers that are still scarce lag behind. The point is to notice which layers are still scarce.
Two things, and neither is "one more endpoint."
Discovery. When supply decomposes into thousands of single-function endpoints, the hard problem is not finding an endpoint — it is finding the one whose price, capability, and settlement path an agent can actually trust. A directory that lists everything lists nothing useful. The value moves to the layer that can say which of 14,000 endpoints is worth a first call.
Pre-payment verification. The moment an agent starts paying strangers per call, the risk is not "will the API exist" — it is "is this 402 challenge safe to sign." Does payTo match the seller you intended, does amount match the advertised price, is the scheme one you can settle? A reputation score built from past receipts cannot answer this, because it only ever sees the payments that already went right. The check has to run before the signature, on the cold path. I wrote about this split last week — pre-payment verification vs post-payment reputation — and the supply wave makes it concrete: the more endpoints flood in, the more each one needs to be verified before money moves.
The interesting builders right now are not the ones adding another endpoint to the index. They are the ones making the index usable — the discovery and verification layer that turns fourteen thousand listings into a handful an agent can safely pay.