Sato Hub
← OpenSea Agent Skill verification record

Score history

OpenSea Agent Skill

Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.

Score today

81

Change over 90d

+1

Days measured

90

Days missed

4

Sato Score, daily

2026-06-11 → 2026-09-13
02550751002026-06-17: Sato Hub changed the scoring method (80 → 81). Not a change by the project.2026-06-25: Sato Hub changed the scoring method (81 → 88). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (88 → 81). Not a change by the project.2026-06-12: 80 (High)2026-06-13: 80 (High)2026-06-14: 80 (High)2026-06-15: 80 (High)2026-06-16: 80 (High)2026-06-17: 81 (High)2026-06-18: 81 (High)2026-06-19: 81 (High)2026-06-20: 81 (High)2026-06-22: 81 (High)2026-06-24: 81 (High)2026-06-25: 88 (High)2026-06-26: 88 (High)2026-06-27: 88 (High)2026-06-30: 88 (High)2026-07-01: 88 (High)2026-07-02: 88 (High)2026-07-03: 88 (High)2026-07-04: 88 (High)2026-07-05: 88 (High)2026-07-06: 88 (High)2026-07-07: 88 (High)2026-07-08: 88 (High)2026-07-09: 88 (High)2026-07-10: 88 (High)2026-07-11: 88 (High)2026-07-12: 88 (High)2026-07-13: 88 (High)2026-07-14: 81 (High)2026-07-15: 81 (High)2026-07-16: 81 (High)2026-07-17: 81 (High)2026-07-18: 81 (High)2026-07-19: 81 (High)2026-07-20: 81 (High)2026-07-21: 81 (High)2026-07-22: 81 (High)2026-07-23: 81 (High)2026-07-24: 81 (High)2026-07-25: 81 (High)2026-07-26: 81 (High)2026-07-27: 81 (High)2026-07-28: 81 (High)2026-07-29: 81 (High)2026-07-30: 81 (High)2026-07-31: 81 (High)2026-08-01: 81 (High)2026-08-02: 81 (High)2026-08-03: 81 (High)2026-08-04: 81 (High)2026-08-05: 81 (High)2026-08-06: 81 (High)2026-08-07: 81 (High)2026-08-08: 81 (High)2026-08-09: 81 (High)2026-08-10: 81 (High)2026-08-11: 81 (High)2026-08-12: 81 (High)2026-08-13: 81 (High)2026-08-14: 81 (High)2026-08-15: 81 (High)2026-08-16: 81 (High)2026-08-17: 81 (High)2026-08-18: 81 (High)2026-08-19: 81 (High)2026-08-20: 81 (High)2026-08-21: 81 (High)2026-08-22: 81 (High)2026-08-23: 81 (High)2026-08-24: 81 (High)2026-08-25: 81 (High)2026-08-26: 81 (High)2026-08-27: 81 (High)2026-08-28: 81 (High)2026-08-29: 81 (High)2026-08-30: 81 (High)2026-08-31: 81 (High)2026-09-01: 81 (High)2026-09-02: 81 (High)2026-09-03: 81 (High)2026-09-04: 81 (High)2026-09-05: 81 (High)2026-09-06: 81 (High)2026-09-07: 81 (High)2026-09-08: 81 (High)2026-09-09: 81 (High)2026-09-10: 81 (High)2026-09-11: 81 (High)2026-09-12: 81 (High)2026-09-13: 81 (High)8088812026-06-122026-09-13

4 days in this span have no reading; the line breaks there rather than joining across them. 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

0 changes attributable to the project, 3 caused by a revision of the scoring method.

DateFromToChangeCause
2026-07-148881-7Sato Hub changed the scoring method
2026-06-258188+7Sato Hub changed the scoring method
2026-06-178081+1Sato Hub changed the scoring method

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.

Maintenance & liveness35/35
35
Code transparency18/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance14/15
15
Independent verification8/10
10

The observed record

98.4% of Sato Hub's own daily checks succeeded over 62 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.

2026-07-14: answered our check2026-07-15: answered our check2026-07-16: answered our check2026-07-17: answered our check2026-07-18: answered our check2026-07-19: answered our check2026-07-20: answered our check2026-07-21: answered our check2026-07-22: answered our check2026-07-23: answered our check2026-07-24: answered our check2026-07-25: answered our check2026-07-26: answered our check2026-07-27: answered our check2026-07-28: answered our check2026-07-29: answered our check2026-07-30: answered our check2026-07-31: answered our check2026-08-01: answered our check2026-08-02: answered our check2026-08-03: answered our check2026-08-04: answered our check2026-08-05: answered our check2026-08-06: answered our check2026-08-07: answered our check2026-08-08: answered our check2026-08-09: answered our check2026-08-10: answered our check2026-08-11: answered our check2026-08-12: answered our check2026-08-13: answered our check2026-08-14: answered our check2026-08-15: answered our check2026-08-16: answered our check2026-08-17: answered our check2026-08-18: answered our check2026-08-19: answered our check2026-08-20: answered our check2026-08-21: answered our check2026-08-22: answered our check2026-08-23: answered our check2026-08-24: answered our check2026-08-25: answered our check2026-08-26: answered our check2026-08-27: answered our check2026-08-28: answered our check2026-08-29: answered our check2026-08-30: answered our check2026-08-31: answered our check2026-09-01: answered our check2026-09-02: answered our check2026-09-03: answered our check2026-09-04: answered our check2026-09-05: answered our check2026-09-06: answered our check2026-09-07: answered our check2026-09-08: answered our check2026-09-09: answered our check2026-09-10: answered our check2026-09-11: answered our check2026-09-12: answered our check2026-09-13: the host answered with an error
  • 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.

DateScoreTierStatusOur check
2026-09-1381HighActivedown
2026-09-1281HighActiveup
2026-09-1181HighActiveup
2026-09-1081HighActiveup
2026-09-0981HighActiveup
2026-09-0881HighActiveup
2026-09-0781HighActiveup
2026-09-0681HighActiveup
2026-09-0581HighActiveup
2026-09-0481HighActiveup
2026-09-0381HighActiveup
2026-09-0281HighActiveup
2026-09-0181HighActiveup
2026-08-3181HighActiveup
2026-08-3081HighActiveup
2026-08-2981HighActiveup
2026-08-2881HighActiveup
2026-08-2781HighActiveup
2026-08-2681HighActiveup
2026-08-2581HighActiveup
2026-08-2481HighActiveup
2026-08-2381HighActiveup
2026-08-2281HighActiveup
2026-08-2181HighActiveup
2026-08-2081HighActiveup
2026-08-1981HighActiveup
2026-08-1881HighActiveup
2026-08-1781HighActiveup
2026-08-1681HighActiveup
2026-08-1581HighActiveup
2026-08-1481HighActiveup
2026-08-1381HighActiveup
2026-08-1281HighActiveup
2026-08-1181HighActiveup
2026-08-1081HighActiveup
2026-08-0981HighActiveup
2026-08-0881HighActiveup
2026-08-0781HighActiveup
2026-08-0681HighActiveup
2026-08-0581HighActiveup
2026-08-0481HighActiveup
2026-08-0381HighActiveup
2026-08-0281HighActiveup
2026-08-0181HighActiveup
2026-07-3181HighActiveup
2026-07-3081HighActiveup
2026-07-2981HighActiveup
2026-07-2881HighActiveup
2026-07-2781HighActiveup
2026-07-2681HighActiveup
2026-07-2581HighActiveup
2026-07-2481HighActiveup
2026-07-2381HighActiveup
2026-07-2281HighActiveup
2026-07-2181HighActiveup
2026-07-2081HighActiveup
2026-07-1981HighActiveup
2026-07-1881HighActiveup
2026-07-1781HighActiveup
2026-07-1681HighActiveup
2026-07-1581HighActiveup
2026-07-1481HighActiveup
2026-07-1388HighActivenot checked
2026-07-1288HighActivenot checked
2026-07-1188HighActivenot checked
2026-07-1088HighActivenot checked
2026-07-0988HighActivenot checked
2026-07-0888HighActivenot checked
2026-07-0788HighActivenot checked
2026-07-0688HighActivenot checked
2026-07-0588HighActivenot checked
2026-07-0488HighActivenot checked
2026-07-0388HighActivenot checked
2026-07-0288HighActivenot checked
2026-07-0188HighActivenot checked
2026-06-3088HighActivenot checked
2026-06-2788HighActivenot checked
2026-06-2688HighActivenot checked
2026-06-2588HighActivenot checked
2026-06-2481HighActivenot checked
2026-06-2281HighActivenot checked
2026-06-2081HighActivenot checked
2026-06-1981HighActivenot checked
2026-06-1881HighActivenot checked
2026-06-1781HighActivenot checked
2026-06-1680HighActivenot checked
2026-06-1580HighActivenot checked
2026-06-1480HighActivenot checked
2026-06-1380HighActivenot checked
2026-06-1280HighActivenot checked
2026-06-11unknown—Activenot checked

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.

  1. Sep 1, 2026
    New release published
  2. Aug 23, 2026
    New release published
  3. Jun 25, 2026
    Enriched: agent type, has pricing
  4. Jun 25, 2026
    Auto-enriched: creator name, creator profile url, supported integrations, deployment options +1 more
  5. Jun 17, 2026
    11 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  6. Jun 16, 2026
    Edited: deploy spec
  7. Jun 12, 2026
    Sato 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.
← Verification recordThis week’s moversDispute this score