TOLL

What software pays for, recorded every six hours.

Snapshot
2026-09-15 16:57 UTC
Sweep
daily-2026-09-15 · finished 2026-09-15 07:10 UTC
Listed
16,167

Put them side by side.

Every row is a figure TOLL measured or a field a registry declared, and a row appears only where the same thing was measured the same way for every column. Where a column has no value the cell says which silence it is. Nothing here is a recommendation; the endpoint that reads best on a row is the one the number puts there.

the index, as of 2026-09-15 16:58 UTC · method · live

Add the first from the list beside this table, or start from any endpoint page and press Compare with another.

Then a second, and a third if you want one. Three columns is the most this table takes.

The rows it will fill

11 measures

Declared price, per call method
as the listing declares it; only comparable where the asset's decimals are on file
Calls, trailing 30 days method
the registry's own counter, a trailing sum and not a rate
Unique payers, trailing 30 days method
distinct paying wallets over the same window, as the registry counts them
Calls per payer method
calls divided by payers, and nothing more: it says how concentrated the usage is, not how loyal anyone is
Verdict at the last sweep method
read from the response body of a preflight call, never from its HTTP status
Sweeps passed method
a fraction and never a percentage: between one and five sweeps have run, and a percentage over five observations would imply a precision the record does not have
Networks declared method
the chains the listing says it will take payment on, not the ones it has been paid on
Position in its category method
by calls, among the endpoints in the same category that carry counters
First observed by TOLL method
observation began 10 September 2026; a listing older than that shows that date
Paid to method
the payee on the primary accept, and how many listed endpoints name the same wallet
Listed in method
presence in a registry at the last pull, which is not liveness of the service

What this table will not compare

An uptime percentage is missing because between one and five daily sweeps have finished since observation began on 10 September 2026, and a percentage over five observations would imply a precision the record does not have; the sweeps-passed row shows the fraction instead. Growth over a window is missing because the counters are trailing thirty-day sums as the registry publishes them, so a difference between two of them is not a rate and TOLL will not present it as one. Both arrive when the record is long enough to carry them.