Bring supported DePIN observations into your research workflow through REST or MCP. Inspect network coverage, metric definitions, source attribution, freshness, and available history before integrating. Live supply, revenue, market and on-chain telemetry across 370 networks (499 symbols incl. 129 subnets) — Akash, Filecoin, io.net, WeatherXM, Flux and more. Every provenance-stamped value carries a verify_url pointing to its named upstream source, and each daily batch is anchored to Bitcoin. Nothing to take on faith.
This is a data product. No trading signals, no performance claims — measured facts with provenance attached.
Most crypto data feeds ask you to trust the number. Ours hands you the receipt with it. Three things make the difference.
370 networks with live telemetry (499 symbols including 129 Bittensor subnets), 18,931 live series, and a coverage catalog of 731 entries — including networks we deliberately don't cover yet.
Not one price per token. Up to 41 live metrics on a single network — supply, revenue, market and node-level telemetry — read straight from the source that owns it.
Every stamped value carries its source and a verify_url you can open right now. Each daily batch is Merkle-rooted and timestamped to the Bitcoin blockchain.
Compute, storage, wireless, sensing, bandwidth, oracles — the DePIN map, measured.
When a network has no free, checkable feed, we say so and leave the cell empty — we never invent a number to fill a gap. The coverage catalog names all 731 entries and marks exactly which ones carry live telemetry today and which don't. You always know what you're buying, and what you aren't.
A sample of live metric breadth per network, measured on 2026-08-09. This is telemetry, not a single ticker.
| Network | Symbol | Category | Live metrics |
|---|---|---|---|
| Akash | AKT | Compute | |
| WeatherXM | WXM | Weather | |
| ThreeFold | TFT | Cloud / Compute | |
| Filecoin | FIL | Storage | |
| io.net | IO | GPU Compute | |
| Flux | FLUX | Compute | |
| Storj | STORJ | Storage | |
| Internet Computer | ICP | Compute | |
| Arweave | AR | Storage | |
| Aethir | ATH | GPU Compute | |
| Nosana | NOS | GPU Compute | |
| Chainlink | LINK | Oracle | |
| Grass | GRASS | Bandwidth |
Metric counts are a snapshot of per-network breadth, measured 2026-08-22, not a live view. The full 441-network list is available on request.
Two independent proofs travel with every number. One says it's real. The other says we didn't touch it.
9cd92fde04…987318b7) and timestamped to
the Bitcoin blockchain via OpenTimestamps, submitted to four independent
calendars. If a value were altered after the fact, the root wouldn't match. A public
per-value inclusion-proof endpoint ships with the API.
{
"symbol": "AKT",
"metric": "circulating_supply",
"value": 383502056.718427,
"unit": "tokens",
"source": "CoinGecko /coins/markets",
"verify_url": "https://www.coingecko.com/en/coins/akash-network",
"as_of": "2026-08-09T17:15:20Z"
}| Source | Series | What it is |
|---|---|---|
| First-party | 595 | network's own API / chain |
| CoinGecko | 58 | price / mcap / supply |
| DefiLlama | 51 | TVL + fees / revenue |
| GitHub | 14 | dev-activity telemetry |
| Akash Console | 13 | provider / lease telemetry |
| WeatherXM API | 10 | station telemetry |
| Flux API | 7 | node telemetry |
We don't call it all first-party. The source label on each value tells you exactly where it came from.
If your work has to survive a second look, provenance isn't a nicety — it's the point.
The same provenance, shaped for code. Endpoints return structured rows with a source and verify_url on every field.
An MCP endpoint and an agent-credit rail let an autonomous buyer discover, price and pull exactly the rows it needs — metered per query (on the order of $0.005 for a provenance or networks lookup, $0.02 for a supply or revenue query). The endpoints are self-service — register and your key works immediately; usage limits and billing units are shown per plan.
Access is self-serve — register and your key works immediately. Begin free, prove the data to yourself, then grow.
Not sure which tier fits? Start on Verify — open a verify_url, check a number against its source, and decide from there.
Get API key