Verification record
Massive (formerly Polygon.io)
Its Sato Hub Sato Score and verification record — how open, active, and verifiable this product is, scored from observed evidence. Not a safety, quality, or returns grade.
Sato Score
53/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 15/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 8/15
- Independent verification
- 4/10
Next step
Watch Massive (formerly Polygon.io)
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on massive-com/mcp_massive before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Anchored
2026-09-23 · 432 listingsThis score was committed to a single Merkle root along with every other score we published that day. The root is signed, published, and archivable by anyone — so if we changed this number tomorrow and said it had always been this, the commitment would contradict us. It proves what we published, not that the score is right.
- Leaf
17580df5b923a41402c73a7f0341a588638240cda498eee81bed74d6f1a57fb9- Preimage
satohub-score-leaf/v1|2026-09-23|massive|53|Medium- Proof
- 9 siblings
- Root
b193800c4efd5ef9f4def0a5f5c16cf1a9c24fe106be47c1ddacb936565b6583- Root signature
- Ed25519, kid b04bd38b
- On-chain
- not attested on-chain — key absent (ATTEST_PRIVATE_KEY is not set)
Verify this yourself
# 1. The proof: record, leaf, leaf_preimage, proof (sibling digests)
curl -s "https://satohub.ai/api/verify/massive/proof?date=2026-09-23"
# 2. The roots file, fetched separately; take the root for 2026-09-23
curl -s https://satohub.ai/.well-known/sato-score-roots.json
# 3. leaf = SHA-256(leaf_preimage). For each sibling s:
# leaf = SHA-256("satohub-score-node/v1" || min(leaf,s) || max(leaf,s))
# The result must equal the root from step 2.
# 4. Check that root's signature against https://satohub.ai/.well-known/jwks.jsonNo command-line tool is published for score proofs yet; the steps above are the whole check. Compare against the published roots file, not against the root in the proof response — checking a proof only against a root served in the same reply proves nothing. Raw proof: /api/verify/massive/proof. Method: the house rules.
Record
- Last checked
- 2026-09-23
- Last observed activity
- Jun 11, 2026
- Methodology
- Sato Score methodology →
Verification history
A dated, auditable record of every change to this listing's status, verification, and Sato Score.
- Sep 23, 2026Listed on Sato Hub
- Sep 23, 2026Sato Hub began tracking this listing
Embed this badge
[](https://satohub.ai/verify/massive?utm_source=badge&utm_medium=embed)Paste into your README. The badge reflects the live Sato Score and links back to this report. Free to use, no attribution required.
Embed the 90-day history
Live preview[](https://satohub.ai/verify/massive/history?utm_source=badge&utm_medium=embed)Paste into your README. The sparkline is the last 90 days of daily Sato Score readings with the 90-day change; days nobody measured are drawn as gaps, never joined across. It links back to the full dated record. Free to use, no attribution required.
Think this score is wrong?
Check it first: every input behind it is published at /api/export/score-inputs.json and the scorer is a verbatim copy of ours, so the arithmetic can be run on your own machine — reproduce this score. If you maintain Massive (formerly Polygon.io) and still disagree, say so in public: a dispute is published with your evidence beside our answer, whether or not we agree with it.