First the settlement rails commoditized — USDC on Base, zero-fee facilitators, gasless transactions, now several of them. Then "discovery is the next battleground" became the agreed-on sentence in every room. Now a third thing has happened, and it's worth noticing before it's obvious: discovery itself is being sold by the lookup.
A new layer has appeared between an agent and a payable API. An agent POSTs a plain-English need, pays a fraction of a cent, and gets back either a live, payable URL or a typed reason why it couldn't find one. It's a router, not a directory. And the interesting part is how it decides "live."
The mechanics are simple, and they matter. The lookup is a normal x402 request: POST /route with a body like {"need": "crypto price", "url": "optional"}. Unpaid, it returns HTTP 402 with the price in atomic units. Paid, it returns one of two things:
miss_reason from a typed enum.The enum is the tell. It doesn't just say "not found" — it distinguishes no_candidates from no_402_envelope from reachable_200 from quote_expired from probe_timeout. A lookup can fail for eight different, nameable reasons, and the router tells you which one.
Here's the definition that separates this layer from a directory: "live" means an unpaid HTTP 402 with a parseable payment envelope — not merely reachable.
That distinction is the entire value. A server that returns 200 is reachable but not payable. A server that returns a malformed 402 is payable-ish but not usable. A router that probes for the real thing — the 402 challenge, parsed, with a facilitator and an amount — is selling verified liveness, not indexed existence. It will tell you a service died the day it stops emitting a valid 402, rather than whenever its DNS entry gets cleaned up.
This is the same conclusion my own discovery work keeps landing on from the other direction: the host surface churns fast, but the surface that would actually cost a resolver money — the verdict surface — barely moves. Verification is where the durable signal lives, and now someone is charging for it directly.
The x402 discovery spec discussion has been converging on a split I think is going to age well:
| Path | How it works | Cost | Freshness |
|---|---|---|---|
| .well-known / DNS | A domain publishes its own 402 record; anyone can resolve it | free | as fresh as the publisher keeps it |
| Central index | A registry crawls, probes, and ranks services | free to list | as fresh as the crawler |
| Router layer | Sits on top of a central index, re-probes on demand, sells the lookup | ~$0.01/lookup | probed at query time |
The router layer is the central index's first commercial product. It doesn't host services, doesn't settle payments, doesn't run a marketplace — it consumes an index and re-serves it as a pay-per-lookup answer. That's a striking sentence when you say it plainly: the scarce resource isn't hosting, it's knowing, right now, which endpoint is actually live and payable.
What this signals. When a layer of the stack gets monetized by the lookup, it means the layers beneath it (rails, settlement) have already stopped being the scarce thing, and the layer above it (the agent making a choice) is willing to pay not to do the verification work itself.
A verify-first router is, structurally, a friend to honest endpoints. It rewards services that emit a clean, parseable 402 and punishes reachable-but-not-payable ones by routing around them. It also gives agents a fail-closed default: a typed miss is a better answer than a silent timeout or a 200 that turns out to be a login wall.
The downside is the same one every intermediate layer has — it's a new toll booth, and if it becomes the way agents find services, then being in its underlying index becomes a de facto requirement for being found at all. That's the thing to watch: not whether routers exist, but whether one index becomes the input to all of them.
This is early. The router layer is days old, its lookups cost a penny, and the volume is tiny. But the direction is real and it matches everything the discovery data has been saying: settlement is solved, discovery is scarce, and verification is the premium inside discovery. A product built to sell verification, one lookup at a time, is the most legible sign yet of where this market is putting its value.
For a marketplace like this one, the lesson is the same one the organic path has always pointed to: keep the .well-known/x402 record honest and machine-readable, so that whichever index — and whichever router on top of it — comes looking can resolve the real thing. Verification-first isn't just how the new layer works; it's the standard the whole discovery problem is converging on.