TOLL

What software pays for, recorded every six hours.

Snapshot
2026-11-01 21:59 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
52,265

Facilitators probed

TOLL reads two catalogues and there are more. This is every facilitator it has probed, what each one answered, and the rule that decides which are indexed. The refusals are here beside the answers, because a coverage page that listed only what was found would be the thing it is meant to prevent.

probed 2026-09-15 09:44 UTC · method

19 facilitators probed, from the public directory at facilitators.x402.watch. 4 serve the bazaar discovery extension at the standard path without a key; 9 answered without it; 3 did not answer at all; and 3 publish a settlement address and no service URL, so there was nothing to probe. TOLL reads 1 of them today.

The rule

the first inclusion rule this site has stated

  1. TOLL indexes every facilitator that serves the bazaar discovery extension at the standard path without authentication.
  2. Every facilitator probed is published here with what it returned, including the ones that returned nothing.
  3. A facilitator that starts serving discovery is added at the next pull. One that stops is recorded as stopped, never quietly dropped.

Inclusion is a property of the facilitator’s own conduct rather than an opinion TOLL holds about it. Serving the extension openly is a thing a facilitator does or does not do, and the request that establishes it is the one printed below, which anyone can repeat and check against this page. Everywhere else this site refuses to make quality judgements about what it measures; deciding which catalogues to read on the basis of reputation would be the same judgement, moved one step earlier and made invisible.

What the rule costs, stated so it is not discovered later:

  • It does not permit leaving out a catalogue for being concentrated in one seller.
  • It does not permit dropping entries that look like noise; they are counted and described.
  • It admits facilitators TOLL knows nothing else about, which is the point: knowing something else about them would be the judgement this rule exists to avoid.

The request

repeat it and compare

One request per facilitator, a stated user agent, a stated timeout, taken once on 2026-09-15 09:44 UTC. The site never probes on a page render.

curl -sS -A 'TOLL-index/0.1 (+https://tollindex.com; coverage survey)' \
  --max-time 15 \
  '<facilitator base>/discovery/resources?limit=2'

What each one answered

19 probed

Every facilitator probed, with the result of the request
facilitatorbase probedresultdetailresourcescounters
Polygon Facilitatorhttps://x402.polygon.technologyno discovery hereHTTP 404——
Coinbase read by TOLLhttps://api.cdp.coinbase.com/platform/v2/x402The directory's host does not resolve. The catalogue is served at the standard path on another host, which is the one TOLL reads.serves discoveryHTTP 200, 15,590 resources listed15,590yes
Questflow—nothing to probethe directory lists a settlement address and no service URL, so there is nothing to probe——
Heuristhttps://facilitator.heurist.xyzno discovery hereHTTP 404, text/html——
X402rshttps://facilitator.x402.rsno discovery hereHTTP 200, text/html——
PayAIhttps://facilitator.payai.networkserves discoveryHTTP 200, 28,662 resources listed28,662no
CodeNuthttps://facilitator.codenut.aino answerUND_ERR_CONNECT_TIMEOUT — Connect Timeout Error (attempted address: facilitator.codenut.ai:443, timeout: 10000ms)——
AurraCloud—nothing to probethe directory lists a settlement address and no service URL, so there is nothing to probe——
OpenX402https://open.x402.hostno answerERR_TLS_CERT_ALTNAME_INVALID — Hostname/IP does not match certificate's altnames: Host: open.x402.host. is not in the cert's altnames: DNS:*.up.railway.app, DNS:up.railway.app——
KAMIYOhttps://kamiyo.ai/api/v1/x402no discovery hereHTTP 503, text/html——
Thirdwebhttps://api.thirdweb.com/v1/payments/x402serves discoveryHTTP 200, 713 resources listed713no
Daydreamshttps://facilitator.daydreams.systemsno discovery hereHTTP 404, text/plain——
Ultravioleta DAO—nothing to probethe directory lists a settlement address and no service URL, so there is nothing to probe——
Corbitshttps://facilitator.corbits.devno answerENOTFOUND — getaddrinfo ENOTFOUND facilitator.corbits.dev——
Dexterhttps://facilitator.dexter.cashserves discoveryHTTP 200, 3,328 resources listed3,328no
Mogamihttps://facilitator.mogami.techno discovery hereHTTP 404, text/html——
402104https://x402.load.networkno discovery hereHTTP 404——
xEchohttps://www.xechoai.xyzno discovery hereHTTP 402, application/json——
Virtuals Protocolhttps://acpx.virtuals.iono discovery hereHTTP 404, application/json——

A listed resource is not an addressable endpoint

finding

PayAI lists 28,662 resources, which is more than this index holds in total. That number and the number of endpoints a reader could call are not the same number, and the difference is not small. A sample of 800 resources, taken at evenly spread offsets rather than from the head of the catalogue, found 10% whose resource field is not a fetchable URL at all — entries under schemes like monopoly:// with no host — and 50% belonging to a single seller, orbisapi.com. The sample spans 115 hosts in all.

So “28,662 resources” and “28,662 addressable endpoints” are different claims, and only the first is supported. TOLL is not saying the catalogue is wrong: enumerating many paths under one host is a legitimate thing for a seller to do, and a scheme TOLL cannot fetch may be perfectly meaningful to whoever wrote it. It is saying that a headline count carries a shape, and that the shape has to be published with it. The exact figure is unknown until the catalogue is pulled in full, which has not been done.

Of the sample, 38 resources (4.8%) are already in this index by canonical URL, and 14 of its 83 addressable hosts are hosts TOLL already holds. The overlap is small: this would be mostly addition rather than duplication.

The counters are not part of the extension

finding

Every usage figure on this site — calls, unique payers, calls per payer, the concentration ranking, the correlation, the density field, a category position — rests on a quality block carrying a call count, a unique payer count and a last-called time. That block is a Coinbase addition. It is not in the bazaar discovery extension, and of the 4 facilitators serving discovery openly, 1 carries it: Coinbase. The other 3 — PayAI, Thirdweb, Dexter — publish the listing and nothing about its use.

Today 52,065 of 52,265 listed endpoints carry counters, 99.6% of the index. Reading the other three catalogues would add 32,703 resources gross, or about 31,150 after the overlap the sample measured, and the counters would then cover roughly 62% of what the index holds. Nothing about the measurements would change; what would change is what they are measurements of. “Most called” would mean most called among a third of the listings, and every page stating a usage figure would have to say so on the same line.

That is a product question rather than a data one, and it is not decided here. This page exists so the question is visible before an ingestion plan is written rather than after. Nothing from these catalogues has been ingested.

What a directory cannot show

Two limits on this page itself. The directory it starts from is a view of the ecosystem and not a census: Binance B402, the index’s second source, is not listed on it at all, so a rule that read only what the directory carries would inherit the directory’s omissions. And a facilitator is not the only way an endpoint reaches the world — a seller who publishes a manifest at /.well-known/x402 on their own domain appears in no catalogue, and no amount of probing facilitators would find them. The first limit is a decision about sources. The second is a shape this method cannot reach, and it is stated on the method page for that reason.

Probed once, by hand, on 2026-09-15 09:44 UTC. Re-running pnpm tsx scripts/probe-facilitators.ts --sample rewrites this page’s figures and dates them again.

Cite this page

This page is the permanent record and is dated through its changelog, so its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "Facilitators probed". https://tollindex.com/facilitators. Accessed [access date].

BibTeX

@misc{toll-facilitators-2026-09-15,
  author = {TOLL},
  title = {Facilitators probed},
  howpublished = {\url{https://tollindex.com/facilitators}},
  year = {2026},
  month = {9},
  note = {The permanent record, dated through its changelog. Accessed [access date].}
}