Correlation
Pearson’s r between calls and unique payers is the figure the Ledger has published since observation began. It has ranged 0.11 to 0.45 across 28 snapshots. Over the same snapshots the rank correlation held between 0.65 and 0.68. This page shows why the two disagree, and what follows for anyone publishing an aggregate figure about a market this concentrated.
- Correlation between calls and unique payers, Pearson
- 0.45
- The same, on the ranksderived
- 0.68
- The same, outside the top 1% by callsderived
- 0.56
- The same, with the single largest endpoint removedderived
- 0.10
- Endpoints measured at both endsderived
- 13,269
Does the volume an endpoint takes predict how many parties paid it?
Pearson as published; the rank correlation, Spearman on the ranks of the same two columns; Pearson recomputed across every endpoint outside the top 1% by calls; and Pearson across the 13,269 endpoints carrying both counters at the first snapshot and at this one, which is the same set of endpoints throughout and so cannot move because the index changed shape.
| snapshot, UTC | endpoints with both counters | Pearson | rank | Pearson, outside the top 1% | Pearson, same endpoints throughout |
|---|---|---|---|---|---|
| 15,782 | 0.448 | 0.675 | 0.560 | 0.448 | |
| 15,569 | 0.446 | 0.675 | 0.569 | 0.446 | |
| 15,533 | 0.446 | 0.675 | 0.572 | 0.446 | |
| 15,328 | 0.400 | 0.661 | 0.575 | 0.400 | |
| 15,378 | 0.398 | 0.659 | 0.566 | 0.398 | |
| 15,334 | 0.398 | 0.656 | 0.560 | 0.398 | |
| 15,284 | 0.321 | 0.656 | 0.545 | 0.321 | |
| 14,557 | 0.228 | 0.654 | 0.531 | 0.227 | |
| 14,549 | 0.183 | 0.657 | 0.533 | 0.183 | |
| 14,586 | 0.159 | 0.659 | 0.530 | 0.158 | |
| 14,569 | 0.151 | 0.660 | 0.529 | 0.151 | |
| 14,569 | 0.151 | 0.660 | 0.529 | 0.151 | |
| 14,569 | 0.151 | 0.660 | 0.529 | 0.151 | |
| 14,496 | 0.143 | 0.654 | 0.531 | 0.143 | |
| 14,515 | 0.143 | 0.654 | 0.531 | 0.143 | |
| 14,532 | 0.120 | 0.651 | 0.541 | 0.120 | |
| 14,526 | 0.115 | 0.652 | 0.533 | 0.115 | |
| 14,294 | 0.113 | 0.651 | 0.534 | 0.113 | |
| 14,268 | 0.112 | 0.650 | 0.537 | 0.112 | |
| 14,252 | 0.111 | 0.648 | 0.540 | 0.111 | |
| 14,254 | 0.111 | 0.648 | 0.540 | 0.111 | |
| 14,241 | 0.111 | 0.645 | 0.547 | 0.110 | |
| 14,185 | 0.111 | 0.646 | 0.541 | 0.111 | |
| 14,277 | 0.111 | 0.646 | 0.548 | 0.111 | |
| 14,286 | 0.111 | 0.646 | 0.548 | 0.111 | |
| 14,286 | 0.111 | 0.646 | 0.548 | 0.111 | |
| 14,301 | 0.111 | 0.646 | 0.541 | 0.111 | |
| 14,304 | 0.111 | 0.646 | 0.549 | 0.111 |
The last two columns are the two explanations that do not hold. The same 13,269 endpoints, measured at both ends, move from 0.111 to 0.448: the rise is not the index changing composition. Outside the top 1% by calls the figure holds near 0.56 throughout: the rise is not the index as a whole.
Removing the single largest endpoint by calls takes Pearson from 0.45 to 0.10. That endpoint is q verdict resource on www.ax1.vc, paying to 0x7284D4…2d299C. Between and its counters went from 3,147 calls and 246 payers to 64,125 calls and 2,161 payers, 15.6% of all calls counted. It is now the largest endpoint on both axes at once, which is the one arrangement that pulls a linear correlation up.
| snapshot, UTC | calls, 30d | unique payers, 30d | share of all calls counted |
|---|---|---|---|
| 64,125 | 2,161 | 15.6% | |
| 63,319 | 2,160 | 15.5% | |
| 63,221 | 2,160 | 15.5% | |
| 53,821 | 2,006 | 13.6% | |
| 52,679 | 1,987 | 13.4% | |
| 52,038 | 1,985 | 13.3% | |
| 39,055 | 1,759 | 10.3% | |
| 26,341 | 1,308 | 7.2% | |
| 22,254 | 952 | 6.1% | |
| 19,630 | 736 | 5.5% | |
| 17,054 | 734 | 4.8% | |
| 17,054 | 734 | 4.8% | |
| 17,054 | 734 | 4.8% | |
| 13,550 | 717 | 3.8% | |
| 13,550 | 717 | 3.8% | |
| 9,374 | 406 | 2.7% | |
| 8,137 | 322 | 2.3% | |
| 5,982 | 290 | 1.7% | |
| 5,104 | 277 | 1.5% | |
| 4,250 | 255 | 1.2% | |
| 4,250 | 255 | 1.2% | |
| 3,680 | 247 | 1.1% | |
| 3,147 | 246 | 0.9% | |
| 3,147 | 246 | 0.9% | |
| 3,147 | 246 | 0.9% | |
| 3,147 | 246 | 0.9% | |
| 3,147 | 246 | 0.9% | |
| 3,147 | 246 | 0.9% |
What makes it a single point rather than a trend is the endpoints ranked below it. At this snapshot they carry 198, 1 and 1 payers against 2,161.
| endpoint | host | calls, 30d | unique payers, 30d |
|---|---|---|---|
| q verdict resource | www.ax1.vc | 64,125 | 2,161 |
| exa search | stableenrich.dev | 44,974 | 198 |
| operations | agents.chain.link | 38,846 | 1 |
| operations submit | agents.chain.link | 17,226 | 1 |
Pearson’s r measures linear association between two quantities, and each observation enters it weighted by how far it sits from the mean of both. A point at the extreme of both axes therefore contributes more than thousands of ordinary ones. The rank correlation asks a different question, whether endpoints that rank high on calls also rank high on payers, and a single endpoint can move a rank by at most one place. Neither is wrong; they answer different questions, and on these two counters they currently give 0.45 and 0.68.
The consequence is general. 80.7% of all calls counted sit in 1% of endpoints (concentration). In a market shaped like that, a linear correlation across the whole index is hostage to whichever endpoint is currently largest, and it will move when that endpoint’s usage moves whether or not anything else has. An aggregate figure published about this market without a rank or trimmed figure beside it says less about the market than about its biggest participant. TOLL publishes Pearson because it published Pearson from the first snapshot and a published figure is never restated; the other three measurements are published beside it, and the sentence each page states is chosen from the value rather than written once.
A figure moving by more than 0.05 when one endpoint is removed is the threshold at which the pages say so. At this snapshot the move is 0.35.
Every counter on every endpoint at every snapshot is kept and never overwritten. That is what made the fourth column possible: the set of endpoints carrying both counters on could be reconstructed after the question was asked, and the correlation recomputed across only those endpoints at every snapshot in between. None of that was planned for; it fell out of keeping the rows.
A change log cannot answer this question. A log records that a value moved and when, which is enough to notice the rise and nothing more: the rows it would need to recompute a fixed cohort, or to trim the top 1%, or to remove one endpoint and try again, were never kept. The difference between recording that something changed and recording what every value was is the difference between seeing this and not (the comparison).
Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "Correlation", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/ledger/correlation/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-ledger-correlation-2026-09-15T16-57Z,
author = {TOLL},
title = {Correlation},
howpublished = {\url{https://tollindex.com/ledger/correlation/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.