Massive (formerly Polygon.io)
US stock market data API (formerly Polygon.io); agents buy it per request over x402 at agent.massive.com with no account.
- Sato Score71
- ChainsBase
Massive (formerly Polygon.io) is a partly open-source data tool by Massive on Base, with last code activity on 2026-11-03 (Active). Latest release on 2026-05-05. Sato Score 71/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-07. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Nov 3, 2026 · Last release May 5, 2026 · ★ 400
Listed from massive.com on 2026-09-23. Install: not attempted — no install path on record. Evidence →
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 →Overview
Massive, formerly Polygon.io, provides US stock market data: tickers, snapshots, OHLC aggregates, dividends, splits, filings and news. Since 1 September 2026 agents can buy it one request at a time, paying USDC on Base on dedicated x402 routes at agent.massive.com built with Coinbase, with no account or API key (https://massive.com/blog/x402-payments-for-ai-agents). Keyed customers also get an open-source MCP server (https://github.com/massive-com/mcp_massive) and a hosted remote MCP. Listed in the curated x402 catalog of Coinbase for Agents (https://docs.cdp.coinbase.com/coinbase-for-agents/overview), so an agent connected to a Coinbase account can pay for it from its USDC balance.
Sato Score
71/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 15/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 8/15
- Independent verification
- 7/10
Evidence — listed vs checked · what the words mean
Listed from massive.com on 2026-09-23. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Base | self-reported | massive.com | as of 2026-11-07 |
| Verification status | Self-Reported — not independently reviewed | self-reported | massive.com | as of 2026-11-07 |
| Recent activity | last release 2026-05-05 · last commit 2026-11-03 | observed | github.com/massive-com/mcp_massive | 2026-11-07 |
| Website answers | answered (HTTP 200) | observed | massive.com | 2026-11-07 |
| Daily check record | 45 of 45 daily checks since 2026-09-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-11-06 |
| ERC-8004 registration | declared address not found in the registry | observed | — | 2026-11-07 |
| Sato Score | 71/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-11-07 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Observed record — 46 daily checks since 2026-09-23
- Succeeded
- 46
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.
Last 30 days — to 2026-11-07, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Base
- Agent types
- Data Provider
- Open source
- Partial
- Pricing
- Subscription API, or pay per request in USDC over x402
- Deploys as
- Hosted/Remote
- Last checked
- 2026-11-07
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Massive (formerly Polygon.io) fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Massive (formerly Polygon.io)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 15, 2026Active again — shipped after a quiet spell
- Sep 23, 2026Listed on Sato Hub
- Sep 23, 2026Sato Hub began tracking this listing
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Massive (formerly Polygon.io)
- Is Massive (formerly Polygon.io) open source?
- Partly. Some of Massive (formerly Polygon.io) is published as source (https://github.com/massive-com/mcp_massive) and some is not. Checked as of 2026-11-07.
- Which chains does Massive (formerly Polygon.io) support?
- Massive (formerly Polygon.io) lists support for Base as of 2026-11-07.
- Is Massive (formerly Polygon.io) still maintained?
- The most recent code activity Sato Hub observed was on 2026-11-03 (last commit 2026-11-03, last release 2026-05-05), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Massive (formerly Polygon.io)?
- Sato Hub has no deploy spec for Massive (formerly Polygon.io); follow the project's own documentation at https://massive.com/blog/x402-payments-for-ai-agents.
- Is Massive (formerly Polygon.io) verified on Sato Hub?
- No independent verification is on record for Massive (formerly Polygon.io); its verification status is "Self-Reported" and its Sato Score is 71 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Massive (formerly Polygon.io) — Sato Hub." Sato Hub, updated 2026-11-07, accessed 2026-11-07. https://satohub.ai/resources/massiveData last refreshed 2026-11-07; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.