Kairos Signal Technical Manual
Verifiable DePIN and physical-world data, with cryptographic receipts. Every value carries its source, a timestamp, and a verify_url you can check yourself; DePIN data-API responses (not the credits, engine or analytics routes) carry an ed25519 signature (X-Kairos-Signature, key at /.well-known/kairos-signing-key.json), and each daily batch is Merkle-rooted and anchored to Bitcoin. Three layers: measured data (ground truth), descriptive math computed from it, and delivery over REST, MCP and A2A.
For the full API reference with curl examples, auth details, and response schemas, see Customer API Reference.
Live Numbers (restamped nightly from the warehouse)
These numbers are measured live from our ClickHouse warehouse and the /v1/networks API endpoint. You can verify them yourself at kairossignal.com/v1/networks (free, no key required).
Provenance-First Methodology
In a world drowning in AI slop and made-up numbers, we bring receipts. Every single value in our system carries:
| Field | What it means |
|---|---|
source | The exact data source name (e.g. akash_console, solana_rpc, CoinGecko /coins/markets) |
as_of | UTC timestamp when the value was measured — not when we stored it |
verify_url | A URL pointing to the upstream API endpoint a buyer can call themselves to check the number |
freshness | fresh / stale / dead — based on expected refresh cadence per source |
Each daily batch is Merkle-rooted and anchored to Bitcoin via OpenTimestamps, so you can cryptographically verify that a value existed at a specific time.
Network Coverage
Our catalog holds 733 entries (superseded and Bittensor subnet rows included) across compute, storage, wireless, sensor, AI, and other categories. 447 symbols (318 networks plus 129 Bittensor subnets) have live data flowing. Each network is classified into one of three telemetry tiers:
| Tier | Count | What it means |
|---|---|---|
| first_party_telemetry | 288 | Network's own API or chain is being read directly — node counts, committed CPU/GPU, storage, leases, staking, coverage, token supply via RPC |
| onchain_only | 30 | We read network data that is not a market price (a contract, chain or project-published count) from a source outside our first-party list. Price, market cap, volume, GitHub statistics and status pages alone never place a network here |
| catalog_only | 72 | The project is catalogued (name, website, category) but no data is flowing yet |
The distinction between first-party and commodity data is the product. Anyone can pull CoinGecko prices. We read the network's own API or blockchain directly — that's the scarce, differentiating layer.
Counting correction, 2026-10-24: networks are now counted by identity, their public ticker or, for a project with no resolved ticker, its internal reference. Before this date FliteGrid, LayerDrone and NetSepio carried first-party telemetry but were left out of every network count because they have no ticker (their series were always in the series counts), and M3tering's own subgraph data was left out the same way. A hosted service's status page no longer makes a network count as live (GitHub statistics already did not), so Storacha, Huddle01 and Prime Intellect left the live tiers, as did Copute, whose only feed is an AI-agent picks board rather than its compute layer. 4DSKY's map feed, which one collector had stored under a second key, is now filed under its single catalog entry. Their data is still served; earlier dated figures are not rewritten.
Data Sources (the main ones)
| Source | Type | What it reads |
|---|---|---|
CoinGecko /coins/markets | Market (commodity) | Price, market cap, volume, circulating supply |
subtensor_rpc | First-party (chain) | Bittensor subnet registered UIDs (129 subnets + TAO) |
evm_blockscout | First-party (chain) | Holders, transfers, gas, contract stats |
github | Dev velocity | Stars, open issues, forks, repos |
bsc_rpc | First-party (chain) | BSC ERC-20 totalSupply, burn balance |
solana_rpc | First-party (chain) | Solana L1: epoch, supply, inflation, validators, nodes, TPS |
first_party_api | First-party (API) | Per-network stats APIs (Akash, Helium, Storj, Filecoin, etc.) |
ethereum_rpc | First-party (chain) | Ethereum ERC-20 totalSupply |
ethereum_blockscout | First-party (chain) | Ethereum holders, transfers, gas |
DefiLlama /protocols | Revenue | Protocol TVL |
DefiLlama /overview/fees | Revenue | Protocol fees and revenue as DefiLlama reports them (24h/7d/30d/all-time; aggregator figures, labelled) |
bsc_deep_stats | First-party (chain) | BSC token supply + circulating |
cosmos_lcd | First-party (chain) | Cosmos validators, bonded stake, supply |
DefiLlama /v2/chains | Market | Chain-level TVL |
polygon_rpc | First-party (chain) | Polygon ERC-20 totalSupply |
How many networks each source covers changes daily, so it is not typed here: every served value names its source, and GET /v1/provenance lists them live. 147 distinct sources total (sources that wrote in the last 7 days). Every source is named on every value. First-party sources (the network's own API or chain node) are flagged — commodity sources (CoinGecko, DefiLlama) are labeled as such.
Telemetry Tier Classification
Each network is assigned a tier based on what data is actually flowing — not what we plan to collect:
TIER LOGIC
IF the catalog row names a successor (superseded_by) → superseded
ELIF a scope ruling applies (data/network_scope_rulings.json) → its ruling: not_depin / defunct / superseded
ELIF a first-party source (the network's own API or chain) wrote a metric in the last 7 days → first_party_telemetry
ELIF an eligible non-market, non-aggregator row was written in the last 7 days → onchain_only
ELIF only market rows exist (price, market cap, volume: CoinGecko or DEX) → market_data_only
ELSE → catalog_only (project known but no data flowing)
A registered stats API is metadata only; it never makes a network first_party_telemetry.
Counted as "networks with live data": first_party_telemetry + onchain_only.
Outside the counted tiers: market_data_only, catalog_only, superseded, not_depin, defunct, and no_live_data (an on-chain symbol with no catalog row and no eligible rows).
No enrichment is invented. A tier only reflects data that actually exists.
REST API (23 endpoints, all live)
The primary delivery mechanism. All endpoints return JSON. Base URL: https://api.kairossignal.com (proxied at https://kairossignal.com/v1/).
/v1/networks
Free
Full network list with telemetry tiers, coverage, and provenance. Returns the catalog's 733 entries, plus on-chain-only symbols outside the catalog, each with its tier classification (free and agent keys receive a sample).
/v1/network/<SYM>
Free
Single network detail — all metrics, sources, and verify_urls for one ticker.
/v1/supply
Free
First-party supply telemetry (the scarce tier). Every value from a network's own API or chain, with verify_url.
/v1/market
Free
Market data — price, market cap, volume, circulating/total/max supply from CoinGecko.
/v1/revenue
Free
DefiLlama fee and revenue figures (REV_24H/REV_30D = DefiLlama fees total24h/total30d; DL_FEES_* 24h/7d/30d/all-time and DL_REV_* 24h/7d/30d where DefiLlama has them), each labelled as an aggregator’s figure. Free callers get every network it serves; TVL is in /v1/market.
/v1/provenance
Free
Source registry — every data source with its description and verify_url template.
/v1/correlations
Paid
Cross-network correlation matrix.
/v1/correlations/lead-lag
Paid
Hourly lead-lag correlations between driver series (physical and network telemetry, a DePIN price index, and three hourly statistics of the untrained DAG encoder’s tick batches: curvature, curvature_d and lyapunov, which are encoder statistics, not measurements) and BTC/ETH/SOL hourly returns, the DePIN index return and BTC’s absolute return, in the same hour and one hour later. Significance is counted within each hourly run.
/v1/indicators
Paid
SMA-20, EMA-12, RSI-14 and MACD(12,26,9) on hourly closes for 14 crypto assets, as Polygon (Massive) computes them. The upstream updates once a UTC day, so the newest value per asset is the previous day’s last hourly bar. as_of_kind says what as_of is: that bar’s time on rows written since 2026-10-24 08:01Z, our first poll time on older rows (the bar time was not stored then). No OHLCV bar or VWAP is served.
/v1/signals
Paid
The paper traders' recorded entry signals (paper trading only; no orders are placed), one row per paper position opened, with timestamps. Only the rows written 2026-06-14..2026-08-02 carry a chain_hash/prev_hash; the rows written since 2026-08-17 carry neither, and no row is signed, so this is not a tamper-evident ledger. These records do not establish trading performance.
/v1/digest
Paid
Daily digest of material changes across the estate.
/v1/changes
Paid
Recent changes and movements in network metrics.
/v1/compare?metric=<canonical>
Paid
Compare all networks on a single canonical metric.
/v1/history?network=<SYM>&metric=<M>&days=<N>
Free
Historical daily series for a network+metric over N days. The free tier serves a 7-day window; Pro and Enterprise serve the full history held.
/v1/health-profile/<SYM>
Paid
Health profile for one network: market cap, FDV/MC, price, GitHub activity, first-party metric count, with missing_fields naming every absent input (null, never 0). The paid SKU depin_health_profile is fixed to AKT; the same record is free inside /v1/network/<SYM>.
/v1/grades
Paid
Network grade rows. Every letter grade whose inputs are unmeasured is withheld, and none currently carries one, so the depin_grades SKU is withdrawn (a purchase is refused, not charged).
/v1/enrichment/<SYM>
Paid
One-time 2026-08-20 snapshot of upstream reads (token contract, chain RPC, first-party API), each with verify_url, built_at and provenance_class. The depin_enrichment purchase delivers the bulk set (all records); the per-network slice is here.
/v1/ai-intel
Paid
Rule-generated per-network summaries (fixed text templates over live values, no language model) with heuristic rung scores only where every input is live; moat withdrawn.
/v1/network-signals
Paid
Descriptive mathematical decomposition of observed network data (paid engines tier). When the worker defers on its health gate, the last complete run is served and labeled as such.
/v1/revisions?symbol=<SYM>&kind=<K>&since=<YYYY-MM-DD>
Free
Machine-detected upstream restatements: each row records an upstream source replacing a value for (network, metric, date) it had already published, with the before and after values.
/v1/attestations
Free
The daily Merkle batches of published values, each root OpenTimestamps-stamped for Bitcoin anchoring, with each batch's Bitcoin status (pending until a block confirms it) and the backfilled batches labeled.
/v1/attest?symbol=<SYM>&metric=<M>&date=<YYYYMMDD>
Free
Inclusion proof for one (symbol, metric, date) row in an anchored batch, naming the batch; a row that is in no anchored batch gets an honest miss, never a synthesized proof.
/health
Free
API health check.
/health, /v1/networks, /v1/network/<SYM>, /v1/supply, /v1/market, /v1/revenue, /v1/provenance, /v1/history (7-day window), /v1/revisions, /v1/attestations, /v1/attest.Paid endpoints require an
X-API-Key header. Without a valid key, they return 402 payment_required.
Analytical Engines (:6035)
Paid analytical endpoints that compute derived intelligence from the raw data:
| Endpoint | Shape | What it computes |
|---|---|---|
/v1/node-quality | raw / active / dead counts, ratio, grade, as_of per row | Raw vs active node counts; an A–F grade only where an active count is measured, else UNGRADED |
/v1/sector-health | one index per category (count in the response) | Category coverage-and-market index (not a health measure) |
/v1/competitive-landscape | share and HHI per category (count in the response) | CoinGecko market-cap share and HHI within a hand-coded category list |
/v1/gpu-supply-demand | io_net, akash, golem and cross_network blocks | io.net GPUs by model, Akash GPU/CPU/storage totals, Golem only when live |
Engines are available on Design Partner, Watchtower, Pro and Enterprise. They return 402 payment_required without a valid paid API key.
MCP Server & Agent Tools
We expose a Model Context Protocol server for AI agents at https://kairossignal.com/mcp/: 21 tools, 5 of them paid analytics tools charged in credits per answered call (each tool's description states its cost). The read-only edition at https://kairossignal.com/mcp/public serves 10 tools and has no account, purchase or payment tools. tools/list on either endpoint returns the current set.
We also publish an A2A agent card at https://a2a.kairossignal.com/.well-known/agent-card.json for agent-to-agent discovery per the A2A protocol.
DAG Manifold API
A 63-layer encoder with untrained (initialization) weights, a fixed random-feature map of each tick’s symbol-name, sector and price-magnitude hashes, log price and hour/day features; distances between symbols are not correlations, and /lyapunov/alert and /wilson/curvature return the batch log top singular value and batch half-norm ratio (encoder-batch statistics, no alerts). All 63 layers execute over a 256-wide state across a 191-edge topology; the weights are a pinned initialization, not trained; 32 dimensions published) available as a separate product at dag.kairossignal.com. Pricing: $99 for 30 days (one-time 30-day access key via dag_manifold_30d). On the record: the terminal node has 42 layers in the terminal layer’s ancestry; the other 21 compute each pass and are discarded, because they are not ancestors of the terminal layer. Layer 51 draws fresh stochastic-differential-equation noise on every pass, so two passes on identical input are not bit-identical. A second, explicitly versioned vector, encoder v2, is served only when a request asks for it with ?basis=v2: its noise is seeded from each input, so identical input gives a bit-identical v2 vector. It runs on the same untrained initialization weights and is never mixed with the default vector; ?basis=oja_v1 serves a versioned Oja-QR projection of the default encoder’s internal state.
Encodes each market tick (selected by sector from market_ticks) through the untrained DAG, which holds no correlation or co-movement content, using Clarke subdifferential (∂C) or ReQU activations, Green’s-function and wavelet terms on layers 18-27 and a stochastic-differential-equation step at layer 51; the published 32-dim vector is the leading slice of its terminal state. Nearest-neighbour and distance queries on that vector are what the product returns.
Plans & Pricing
| Plan | Price | What you get | Requests / day |
|---|---|---|---|
| Verify Free | $0 | Browse /v1/networks, /v1/supply, /v1/provenance with verify_urls. No key needed. | 1,000 |
| Design Partner | $199/mo | All networks, 30 days of daily history, the engines and cross-network views (Watchtower, bulk exports and alert webhooks not included). Rate locked for as long as the subscription stays active. | 100,000 |
| Watchtower | $249/mo | Everything in Design Partner plus material-change detection across a 10-network watchlist and the weekly IC Pack. | 100,000 |
| Pro | $499/mo | Everything in Watchtower (the analytical engines are already in Design Partner) plus a 40-network watchlist, unlimited history and bulk CSV/NDJSON export. Alert webhooks are Enterprise-only. | 500,000 |
| Enterprise | from $2,000/mo | Custom schemas, SLA, dedicated support, due diligence packages, revision-restatement webhooks (one alert type, revision_restate, checked daily at 01:35 UTC). | 5,000,000 |
Budgets are exact and reset at 00:00 UTC; anonymous callers are
counted per IP. /health, /try, /v1/world,
/v1/brief and /v1/key/by-session are never counted.
Over budget returns 429 with your daily_limit. Full
detail: Request budgets.
Additional products:
- DAG Manifold API — $99 for 30 days, one-time key (dag.kairossignal.com)
Authentication
Free endpoints require no authentication. Paid endpoints require an API key passed via the X-API-Key header:
CURL EXAMPLE — PAID ENDPOINTcurl -H "X-API-Key: your-key-here" \
https://api.kairossignal.com/v1/correlations
API keys are obtained through the self-serve credit system at checkout.kairossignal.com (Stripe) or by registering an account and requesting a USDC quote (unique amount with no wallet signature, or a verified wallet).
Without a valid key, paid endpoints return HTTP 402 Payment Required — not an error, but a clear signal that payment is needed.
USDC on Base
Register an account, verify your sending wallet with a signed challenge, and request a current quote before sending. Credit requires the exact quoted native USDC amount and a finalized Base transfer.
USDC quotes (unique amount or verified wallet) and receipts · Current availability
Kairos Signal · DePIN Intelligence Platform · Customer API Reference →
Coverage figures are snapshots. Check individual source timestamps in API responses. Verify free at /v1/networks.
Questions: [email protected]