Sato Hub
Alchemy AgentPay verification record

Score history

Alchemy AgentPay

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

37

Change over 78d

+24

Days measured

78

Days missed

2

Sato Score, daily

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

2 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-09-013437+3Sato Hub changed the scoring method
2026-07-203034+4Sato Hub changed the scoring method
2026-07-141330+17Sato 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 & liveness20/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance10/15
15
Independent verification7/10
10

The observed record

100% 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: answered our check
  • 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-1337LowBetaup
2026-09-1237LowBetaup
2026-09-1137LowBetaup
2026-09-1037LowBetaup
2026-09-0937LowBetaup
2026-09-0837LowBetaup
2026-09-0737LowBetaup
2026-09-0637LowBetaup
2026-09-0537LowBetaup
2026-09-0437LowBetaup
2026-09-0337LowBetaup
2026-09-0237LowBetaup
2026-09-0137LowBetaup
2026-08-3134LowBetaup
2026-08-3034LowBetaup
2026-08-2934LowBetaup
2026-08-2834LowBetaup
2026-08-2734LowBetaup
2026-08-2634LowBetaup
2026-08-2534LowBetaup
2026-08-2434LowBetaup
2026-08-2334LowBetaup
2026-08-2234LowBetaup
2026-08-2134LowBetaup
2026-08-2034LowBetaup
2026-08-1934LowBetaup
2026-08-1834LowBetaup
2026-08-1734LowBetaup
2026-08-1634LowBetaup
2026-08-1534LowBetaup
2026-08-1434LowBetaup
2026-08-1334LowBetaup
2026-08-1234LowBetaup
2026-08-1134LowBetaup
2026-08-1034LowBetaup
2026-08-0934LowBetaup
2026-08-0834LowBetaup
2026-08-0734LowBetaup
2026-08-0634LowBetaup
2026-08-0534LowBetaup
2026-08-0434LowBetaup
2026-08-0334LowBetaup
2026-08-0234LowBetaup
2026-08-0134LowBetaup
2026-07-3134LowBetaup
2026-07-3034LowBetaup
2026-07-2934LowBetaup
2026-07-2834LowBetaup
2026-07-2734LowBetaup
2026-07-2634LowBetaup
2026-07-2534LowBetaup
2026-07-2434LowBetaup
2026-07-2334LowBetaup
2026-07-2234LowBetaup
2026-07-2134LowBetaup
2026-07-2034LowBetaup
2026-07-1930LowBetaup
2026-07-1830LowBetaup
2026-07-1730LowBetaup
2026-07-1630LowBetaup
2026-07-1530LowBetaup
2026-07-1430LowBetaup
2026-07-1313LowBetanot checked
2026-07-1213LowBetanot checked
2026-07-1113LowBetanot checked
2026-07-1013LowBetanot checked
2026-07-0913LowBetanot checked
2026-07-0813LowBetanot checked
2026-07-0713LowBetanot checked
2026-07-0613LowBetanot checked
2026-07-0513LowBetanot checked
2026-07-0413LowBetanot checked
2026-07-0313LowBetanot checked
2026-07-0213LowBetanot checked
2026-07-0113LowBetanot checked
2026-06-3013LowBetanot checked
2026-06-2713LowBetanot checked
2026-06-2613LowBetanot 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. Jul 14, 2026
    Enriched: supported integrations, deployment options, tags
  2. Jun 26, 2026
    Sato Hub began tracking this listing
  3. Jun 25, 2026
    Listed on Sato Hub

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.