The DePIN Data Problem
Decentralized Physical Infrastructure Networks (DePIN) represent one of the fastest-growing sectors in crypto, but the data infrastructure supporting them remains fragmented and unreliable. Most DePIN dashboards and aggregators present derived or modeled estimates without verifiable provenance — making it impossible for researchers, investors, and AI agents to trust the numbers.
At Kairos Signal, we catalog DePIN networks and label which carry live data and which have first-party supply telemetry we read directly from their own API endpoints. Every value we publish carries a verify_url pointing to the exact upstream source, so any data point can be independently checked.
What We Found
Supply Telemetry Coverage
Our catalog separates:
- networks that expose first-party supply telemetry (registered capacity, active capacity, utilization)
- networks with on-chain data only (revenue, TVL, market data)
- networks with on-chain market data (price, market cap, liquidity)
- catalog-only networks — no public data feed exists
The Verification Gap
Most DePIN data aggregators present numbers without any way to verify them. When a dashboard says "io.net has 50,000 GPUs," there's no link to the source. When a report claims "Filecoin has 18 EiB of storage," you can't check when that was measured or where it came from.
We solve this by attaching a verify_url to every single value. For io.net supply data, the verify_url points to io.net's own API. For Filecoin storage metrics, it points to the Filecoin chain explorer. For market data, it points to CoinGecko or DefiLlama.
Bitcoin-Anchored Provenance
Each daily data batch is Merkle-rooted and timestamped to Bitcoin via OpenTimestamps. This creates a cryptographic proof that a specific set of data existed at a specific time — without trusting us or any third party. The Merkle root is embedded in a Bitcoin transaction, and anyone can verify that a specific data point was part of a specific batch.
Why This Matters
For AI agents: Autonomous agents need machine-readable, verifiable data to make decisions. Without verify_urls, an agent has no way to assess data quality. With them, an agent can programmatically check any value before acting on it.
For investors: DePIN investment decisions based on unverified supply metrics are speculative. Verifiable, timestamped data reduces information asymmetry and enables evidence-based allocation.
For developers: Building on a DePIN network requires understanding its actual capacity and utilization. First-party telemetry is the ground truth; everything else is hearsay.
A Minimal Query Flow
The fastest way to get a verifiable supply number is three calls: discover, fetch, verify.
# 1. Discover what's live
curl "https://api.kairossignal.com/v1/networks" -H "X-API-Key: *"
2. Fetch supply telemetry for one network
curl "https://api.kairossignal.com/v1/supply?network=akash" -H "X-API-Key: *"
3. Verify a value at its source
curl "https://api.kairossignal.com/v1/provenance" -H "X-API-Key: *"
Every response returns source, as_of, verify_url, and freshness_verdict. The last field is critical: it tells you whether a value is fresh, stale, or missing — and missing values are never zero-filled. A stale value is flagged so your pipeline can decide whether to use it, rather than silently consuming a number past its freshness window.
Canonical Concepts Across Networks
The value of a programmatic supply query compounds when it is canonical. Instead of reverse-engineering each network's native schema — active_providers on Akash, active_devices on io.net, online_hotspots on Helium — you query one concept and get comparable, unit-declared answers across every network. We map 89 native field names into 38 canonical concepts, so your integration code is written once and works everywhere.
From REST to MCP
The same supply data is available to autonomous agents through our MCP server. An agent that speaks Model Context Protocol can discover, query, verify, and even purchase data end to end — no human in the loop. The MCP tool surface mirrors the REST endpoints, so the canonical schema is consistent whether a human or an agent is doing the querying.
Try It
Query our API directly:
# Full network catalog
curl https://kairossignal.com/try
Supply telemetry (free sample)
curl https://kairossignal.com/samples/depin-sample-pack.json
New registrants get $5 in free credits — no credit card required. Full API access starts at $0.99 for the network catalog and $4.99 for complete supply telemetry across every network with first-party supply data.
Get a free API key →---
This is a data product. Kairos Signal publishes no trading signals, performance returns, win rates, or accuracy claims. All values are measured facts with verifiable provenance. Measured 2026-08-17.---
Try it yourself
Query the live catalog, supply telemetry, and provenance receipts directly: /v1/networks, /v1/supply on the REST API.
Related reading: the DePIN developer guide · how to query DePIN data with curl · depin data documentation · DePIN RPC endpoints across chains
Start with a free API key — $5 in credits, no credit card — and query live network data and the MCP server. Try the API free → · See pricing
---
Get Started With DePIN Intelligence
Kairos Signal provides verifiable, provenance-first telemetry for DePIN networks, with first-party supply data read directly from each network's own API or blockchain. Current counts are published live at /v1/networks. Every value carries a verify_url you can check yourself, and each daily batch is Merkle-rooted and anchored to Bitcoin.
Every API response is signed with ed25519 and timestamped. You can prove what was served and when, months later. That is what we mean by provenance-first.
Related reading: DePIN Intelligence Guide · DePIN Telemetry · How to Query DePIN Data · DePIN Data Verification · Pricing Correction 2026-09-25: this post called our catalog entry count a count of DePIN networks; that count includes superseded rows and Bittensor subnet rows. It has been removed, together with some present-tense coverage counts written beside it. Current coverage figures: /v1/networks.