Bankless Claimables API
One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.
Score today
34
Change over 45d
+3
Days measured
45
Days missed
0
Sato Score, daily
2026-09-22 → 2026-11-05Every day in this span has a reading. A dashed vertical mark (┆) is a day Sato Hub changed the scoring method — movement on those days is ours, not the project’s.
Every day the score moved
2 changes attributable to the project, 0 caused by a revision of the scoring method.
| Date | From | To | Change | Cause |
|---|---|---|---|---|
| 2026-10-20 | 32 | 34 | +2 | the project |
| 2026-10-05 | 31 | 32 | +1 | the project |
What moved, component by component
Six charts, six axes — each scaled to its own maximum weight. They are never stacked on one axis: a component worth 10 points and one worth 35 would not be comparable on a shared scale, and the small one is usually the one that moved.
The observed record
100% of 45 daily checks since 2026-09-22 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.
- answered
- host answered with an error
- failed on our side
- failed, unattributable
Every reading
The table the charts are drawn from. A missing day is missing from this table too — nothing is filled in.
| Date | Score | Tier | Status | Our check |
|---|---|---|---|---|
| 2026-11-05 | 34 | Low | Active | up |
| 2026-11-04 | 34 | Low | Active | up |
| 2026-11-03 | 34 | Low | Active | up |
| 2026-11-02 | 34 | Low | Active | up |
| 2026-11-01 | 34 | Low | Active | up |
| 2026-10-31 | 34 | Low | Active | up |
| 2026-10-30 | 34 | Low | Active | up |
| 2026-10-29 | 34 | Low | Active | up |
| 2026-10-28 | 34 | Low | Active | up |
| 2026-10-27 | 34 | Low | Active | up |
| 2026-10-26 | 34 | Low | Active | up |
| 2026-10-25 | 34 | Low | Active | up |
| 2026-10-24 | 34 | Low | Active | up |
| 2026-10-23 | 34 | Low | Active | up |
| 2026-10-22 | 34 | Low | Active | up |
| 2026-10-21 | 34 | Low | Active | up |
| 2026-10-20 | 34 | Low | Active | up |
| 2026-10-19 | 32 | Low | Active | up |
| 2026-10-18 | 32 | Low | Active | up |
| 2026-10-17 | 32 | Low | Active | up |
| 2026-10-16 | 32 | Low | Active | up |
| 2026-10-15 | 32 | Low | Active | up |
| 2026-10-14 | 32 | Low | Active | up |
| 2026-10-13 | 32 | Low | Active | up |
| 2026-10-12 | 32 | Low | Active | up |
| 2026-10-11 | 32 | Low | Active | up |
| 2026-10-10 | 32 | Low | Active | up |
| 2026-10-09 | 32 | Low | Active | up |
| 2026-10-08 | 32 | Low | Active | up |
| 2026-10-07 | 32 | Low | Active | up |
| 2026-10-06 | 32 | Low | Active | up |
| 2026-10-05 | 32 | Low | Active | up |
| 2026-10-04 | 31 | Low | Active | up |
| 2026-10-03 | 31 | Low | Active | up |
| 2026-10-02 | 31 | Low | Active | up |
| 2026-10-01 | 31 | Low | Active | up |
| 2026-09-30 | 31 | Low | Active | up |
| 2026-09-29 | 31 | Low | Active | up |
| 2026-09-28 | 31 | Low | Active | up |
| 2026-09-27 | 31 | Low | Active | up |
| 2026-09-26 | 31 | Low | Active | up |
| 2026-09-25 | 31 | Low | Active | up |
| 2026-09-24 | 31 | Low | Active | up |
| 2026-09-23 | 31 | Low | Active | up |
| 2026-09-22 | 31 | Low | Active | up |
What happened alongside it
Releases, status changes, applied corrections and answered disputes, on the same dates — so a movement in the line can be read against an event rather than guessed at.
- Sep 22, 2026Listed on Sato Hub
- Sep 22, 2026Sato Hub began tracking this listing
How to read this
- · Every point is one UTC day. A day we did not capture is drawn as a gap, never joined across.
- · A change on a marked methodology day is ours, not the project’s.
- · The score says how open, active and verifiable the project is. It is not a safety, quality or returns grade.
- · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.