← Back to kairossignal.com

KAIROS Signal Customer Technical Manual

The comprehensive, verifiable dataset for decentralized physical infrastructure networks (DePIN). Every value is measured live, every value carries proof. Delivered over REST, MCP, and A2A — this manual documents the full API surface, pricing, and provenance model.

Platform status: Live and production-ready.
Primary delivery: REST API (HTTP/JSON)
Agent delivery: MCP server + A2A agent card
Version: v1
Updated: 2026-08-25
457
Networks w/ live data
383
First-party telemetry
78
On-chain market only
800
Total cataloged
11,061
Live series
69
Distinct data sources
665K
Rows in ClickHouse
19
Live REST endpoints

What KAIROS measures

KAIROS Signal tracks the operating health, supply, revenue, and market position of decentralized physical infrastructure networks across every major blockchain. We do not guess, model, or interpolate. We read the network's own telemetry, chain state, and markets — and we show you the receipts.

Of the 800 networks we have cataloged, 457 currently return live data. Of those, 383 are served by first-party telemetry read directly from the network's own API or chain, 78 are on-chain market only, and 339 remain catalog-only (metadata, no live series). We maintain 11,061 live time series sourced from 69 distinct upstream sources, stored in 665K rows in ClickHouse.

Coverage & Scale

Metric Value Meaning
networks_live457Networks with live telemetry flowing today
first_party383Networks read from their own API or chain
market_only78Networks with on-chain market data only
catalog_only339Cataloged but no live data yet
catalog_total800Total cataloged networks
live_series11,061Individual live time series
data_sources69Distinct upstream data sources
rows_clickhouse665KRows in our ClickHouse store
endpoints19Live REST API endpoints

Quick Start

The fastest path: hit a public endpoint, no key required. Network list, first-party supply, and the source registry are free to browse.

CURL — Health Checkcurl https://api.kairossignal.com/health
CURL — Network List (no key)curl https://api.kairossignal.com/v1/networks
CURL — Single Network (no key)curl https://api.kairossignal.com/v1/network/HELIUM
CURL — With API Keycurl -H "X-API-Key: your_key_here" \
  https://api.kairossignal.com/v1/market
Prefer a proxy? Every endpoint is also served at https://kairossignal.com (e.g. https://kairossignal.com/v1/networks). Use whichever fits your network policy.

Base URL & Versioning

Channel Base URL Notes
REST (primary)https://api.kairossignal.comVersioned under /v1
REST (proxy)https://kairossignal.comSame endpoints
Engines (paid)https://api.kairossignal.com port :6035Node-quality, sector-health, bot-detection, competitive-landscape, gpu-supply-demand
MCP serverhttps://kairossignal.com/mcp/10 tools, agent-ready
A2A agent cardhttps://a2a.kairossignal.com/.well-known/agent-card.jsonAgent-to-Agent discovery
DAG Manifold APIhttps://dag.kairossignal.comCorrelation/analytics manifold
GPU compute APIhttps://gpu.kairossignal.comToken-billed inference

Versioning is path-based (/v1/...). Breaking changes ship under a new major version (/v2/...) with a documented migration window. Minor additive changes (new fields) do not bump the version.

Authentication

Authentication uses a single API key passed in the X-API-Key header. Keys are issued from /v1/credits or via Stripe checkout. There is no OAuth, no session tokens, and no per-request signing.

AUTH — API Keycurl -H "X-API-Key: ks_live_xxxxxxxxxxxxxxxx" \
  https://api.kairossignal.com/v1/signals

Key tiers & behavior

Tier Key required? Free endpoints Paid endpoints
Verify Free No /v1/networks, /v1/supply, /v1/provenance 402 payment_required
Paid (Design Partner / Pro / Enterprise) Yes All free + paid Full access
Free endpoints need no key. But if you attach a key that is unpaid, paid endpoints return 402 payment_required with a message telling you how to upgrade. Public endpoints (/v1/networks, /v1/supply, /v1/provenance) always respond with or without a key.
CURL — Payment Required Responsecurl -i https://api.kairossignal.com/v1/signals

HTTP/1.1 402 Payment Required
Content-Type: application/json

{"error": "payment_required", "message": "Valid X-API-Key required for this endpoint",
 "plan": "pro", "upgrade_url": "https://kairossignal.com/#access"}

Header reference

HeaderRequiredDescription
X-API-KeyPaid endpointsYour live API key
AcceptNoapplication/json (default)

Pricing & Tiers

Tier Price What you get Term
Verify Free $0 Browse /v1/networks, /v1/supply, /v1/provenance with verify_url Forever
Design Partner $199/mo Locked 12-month rate, full API access 12-month lock
Pro $499/mo Full API + all 5 engines (node-quality, sector-health, bot-detection, competitive-landscape, gpu-supply-demand) at :6035 Monthly
Enterprise from $2,000/mo Custom schemas, SLA, dedicated support Custom
Design Partner rate: $199/mo locks your 12-month rate. If you're building on top of KAIROS before the wider rollout, this is the entry point for full API access with a price guarantee.
Pro adds the engines. Engine endpoints live on port :6035 and require a Pro (or higher) key. See the Engines section for details.
Start free. The Verify Free tier is fully functional for verification use cases — you can confirm a network's live supply and follow its verify_url back to the source at zero cost.

Credits & Deposits

Beyond monthly plans, KAIROS runs a self-serve agent credit system. You purchase credits up front via Stripe or USDC on Base, and credits are drawn against usage (especially for agent-facing and GPU compute workloads).

Payment rails

MethodDetail
Card (Stripe)Self-serve at checkout; issues API key immediately
USDC on BaseDeposit to 0x2AaE65Fd8D80de18583590DbE0A17758889a89d0
CURL — Get Credits / Keycurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/credits
Crypto deposits: Only USDC on Base is accepted at the address above. 0x2AaE65Fd8D80de18583590DbE0b17758889a89d0. Deposits on other networks or tokens may be lost — verify the network before sending.

Other billed services

ServiceBase URLBilling
DAG Manifold APIhttps://dag.kairossignal.com$99/mo per customer
GPU compute APIhttps://gpu.kairossignal.com$0.002 / 1K input tokens · $0.004 / 1K output tokens

Endpoint Index

All 19 endpoints are live. None are "coming soon." Base URL: https://api.kairossignal.com (or https://kairossignal.com).

#MethodEndpointDescriptionAuth
1GET/healthAPI health check
2GET/v1/networksFull network list with telemetry tiersFree
3GET/v1/network/<SYM>Single network detailKey
4GET/v1/supplyFirst-party supply telemetry (scarce tier)Free
5GET/v1/marketPrice, mcap, volume (CoinGecko/DefiLlama)Key
6GET/v1/revenueProtocol revenue / feesKey
7GET/v1/provenanceSource registry with verify_url per sourceFree
8GET/v1/correlationsCross-network correlation matrixKey
9GET/v1/correlations/lead-lagLead-lag analysisKey
10GET/v1/indicatorsTechnical indicatorsKey
11GET/v1/signalsTrading signalsKey
12GET/v1/digestDaily digest of changesKey
13GET/v1/changesRecent changes / movementsKey
14GET/v1/compare?metric=<canonical>Compare networks on a metricKey
15GET/v1/history?network=<SYM>&metric=<M>&days=<N>Historical time seriesKey
16GET/v1/health-profile/<SYM>Network health profileKey
17GET/v1/gradesNetwork gradesKey
18GET/v1/enrichment/<SYM>Enrichment data per networkKey
19GET/v1/ai-intelAI intelligence layerKey
GET /health

API health check. Returns service status and version. No key required.

CURL — Healthcurl https://api.kairossignal.com/health
RESPONSE{"status": "ok", "version": "v1", "time": "2026-08-25T12:00:00Z"}
GET /v1/networks

Full network list with telemetry tiers. This is the free browsing surface — no key required. Each entry tells you whether the network is first-party, market-only, or catalog-only.

CURL — Network Listcurl https://api.kairossignal.com/v1/networks
RESPONSE (abridged){
  "count": 800,
  "live": 457,
  "networks": [
    {"symbol": "IO", "name": "io.net", "tier": "first_party", "chain": "solana"},
    {"symbol": "HELIUM", "name": "Helium", "tier": "first_party", "chain": "solana"},
    {"symbol": "FIL", "name": "Filecoin", "tier": "onchain_market", "chain": "evm"},
    {"symbol": "X", "name": "Catalog-only network", "tier": "catalog_only"}
  ]
}

Tier values: first_party (383), onchain_market (78), catalog_only (339).

GET /v1/network/<SYM>

Single network detail. Use the network symbol (e.g. IO, HELIUM). Requires a valid key.

CURL — Network Detailcurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/network/IO

Returns symbol, name, chain, tier, live series list, last update, and linked provenance.

GET /v1/supply

First-party supply telemetry — the scarce tier. This is real circulating supply read from each network's own API or chain, not a CoinGecko estimate. Free to browse.

CURL — Supply (no key)curl https://api.kairossignal.com/v1/supply
RESPONSE (abridged){
  "series": 11061,
  "networks": 383,
  "supply": [
    {"network": "IO", "total_supply": 123456789, "circulating": 98765432,
     "source": "solana_rpc", "as_of": "2026-08-25T11:00:00Z",
     "verify_url": "https://api.mainnet-beta.solana.com/...", "freshness": "fresh"}
  ]
}
GET /v1/market

Market data — price, market cap, volume — sourced from CoinGecko and DefiLlama. Requires key.

CURL — Marketcurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/market
GET /v1/revenue

Protocol revenue / fees. Real fee capture per network. Requires key.

CURL — Revenuecurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/revenue
GET /v1/provenance

Source registry — every source we read from, with a verify_url per source. This is how you confirm the data yourself. Free to browse.

CURL — Provenance (no key)curl https://api.kairossignal.com/v1/provenance
RESPONSE (abridged){
  "sources": 69,
  "sources": [
    {"name": "CoinGecko", "kind": "commodity", "networks": 288,
     "verify_url": "https://api.coingecko.com/api/v3/coins/markets"},
    {"name": "bittensor_subtensor_rpc", "networks": 130,
     "verify_url": "https://...subtensor..."},
    {"name": "evm_blockscout", "networks": 118,
     "verify_url": "https://.../api/v2/"}
  ]
}
GET /v1/correlations

Cross-network correlation matrix. Requires key.

CURL — Correlationscurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/correlations
GET /v1/correlations/lead-lag

Lead-lag analysis — which series leads, which lags, and the lag horizon. Requires key.

CURL — Lead-Lagcurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/correlations/lead-lag
GET /v1/indicators

Technical indicators computed over live series. Requires key.

CURL — Indicatorscurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/indicators
GET /v1/signals

Trading signals derived from the indicator layer. Requires key.

CURL — Signalscurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/signals
GET /v1/digest

Daily digest of changes across networks. Requires key.

CURL — Digestcurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/digest
GET /v1/changes

Recent changes and movements across the dataset. Requires key.

CURL — Changescurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/changes
GET /v1/compare?metric=<canonical>

Compare multiple networks on a single canonical metric. Requires key.

CURL — Comparecurl -H "X-API-Key: your_key" \
  "https://api.kairossignal.com/v1/compare?metric=circulating_supply"

Use canonical metric names from /v1/provenance.

GET /v1/history?network=<SYM>&metric=<M>&days=<N>

Historical time series for one network and metric over N days. Requires key.

CURL — Historycurl -H "X-API-Key: your_key" \
  "https://api.kairossignal.com/v1/history?network=IO&metric=circulating_supply&days=30"
RESPONSE (abridged){
  "network": "IO", "metric": "circulating_supply", "days": 30,
  "points": [{"ts": "2026-08-25T00:00:00Z", "value": 98765432}, ...]
}
GET /v1/health-profile/<SYM>

Network health profile — the composite operating-health view. Requires key.

CURL — Health Profilecurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/health-profile/HELIUM
GET /v1/grades

Network grades across the catalog. Requires key.

CURL — Gradescurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/grades
GET /v1/enrichment/<SYM>

Enrichment data per network — supplementary derived fields. Requires key.

CURL — Enrichmentcurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/enrichment/IO
GET /v1/ai-intel

AI intelligence layer — the agent-facing analytical surface. Requires key.

CURL — AI Intelcurl -H "X-API-Key: your_key" \
  https://api.kairossignal.com/v1/ai-intel

Engines (Paid — Pro & Enterprise)

Engines run on the same API host on port :6035. They require a Pro ($499/mo) or higher key. There are five engines.

Engine base: https://api.kairossignal.com:6035 — send your X-API-Key header exactly as with the main API.
GET :6035/v1/node-quality

Node-quality engine. Returns 5 key metrics per network evaluating node operational health.

CURL — Node Qualitycurl -H "X-API-Key: pro_key" \
  https://api.kairossignal.com:6035/v1/node-quality
GET :6035/v1/sector-health

Sector-health engine. Returns 4 sector-level health indices.

CURL — Sector Healthcurl -H "X-API-Key: pro_key" \
  https://api.kairossignal.com:6035/v1/sector-health
GET :6035/v1/bot-detection

Bot-detection engine. Returns 5 bot-detection signals per network.

CURL — Bot Detectioncurl -H "X-API-Key: pro_key" \
  https://api.kairossignal.com:6035/v1/bot-detection
GET :6035/v1/competitive-landscape

Competitive-landscape engine. Returns 4 competitive metrics.

CURL — Competitive Landscapecurl -H "X-API-Key: pro_key" \
  https://api.kairossignal.com:6035/v1/competitive-landscape
GET :6035/v1/gpu-supply-demand

GPU supply/demand engine. Returns 6 GPU market metrics.

CURL — GPU Supply & Demandcurl -H "X-API-Key: pro_key" \
  https://api.kairossignal.com:6035/v1/gpu-supply-demand

Provenance Model

The KAIROS provenance model is the core promise: every value is attributable and verifiable. Nothing is fabricated, estimated into place, or back-filled. If a metric isn't flowing, it is absent — never filled with zero.

Every value carries four attributes

AttributeTypeDescription
sourceStringThe upstream source name (e.g. solana_rpc, first_party_api)
as_ofISO-8601When the value was measured upstream
verify_urlURLPoints to the upstream API you can call yourself to reproduce the value
freshnessfresh|stale|deadLive freshness verdict

The rules

  • No zero-fill. An absent metric is absent, not zero.
  • No estimates. We report measured values only.
  • No back-fill. Missing history is not invented.
  • Verifiable. verify_url lets you reproduce any figure.
Why this matters. When your models depend on circulating supply, revenue, or node counts, a "zero" from a dead feed will silently poison the signal. KAIROS surfaces the freshness verdict on every value so your pipeline can distinguish real zeros from missing data and act accordingly.

Data Sources

We aggregate from 69 distinct data sources. The table below is the top 15 by network count, covering the majority of live coverage. Every source carries a verify_url in /v1/provenance.

Source Networks Data provided Class
CoinGecko288Market data (price, mcap, volume)COMMODITY
Bittensor subtensor_rpc130Bittensor subnet telemetryfirst_party
evm_blockscout118Holders, transfers, gaschain
github54Dev velocitysocial
bsc_rpc50BSC token supplychain
solana_rpc49Solana L1 + SPL tokenschain
first_party_api44Per-network first-party stats APIsfirst_party
ethereum_rpc32Ethereum token supplychain
ethereum_blockscout27Ethereum block explorerschain
DefiLlama protocols25TVLdefi
DefiLlama fees21Revenue / feesdefi
bsc_deep_stats20BSC token supply + circulatingchain
DefiLlama chains16Chain TVLdefi
cosmos_lcd12Cosmos validators, bonded stakechain
polygon_rpc6Polygon token supplychain
Provenance classes: sources are tagged so you can separate commodity market data (CoinGecko), first-party telemetry (the network's own API/chain), chain reads (RPC/block explorer), defi aggregates (DefiLlama), and social signals (GitHub). Query /v1/provenance for the full 69-source registry with per-source verify_url.

Delivery Channels

Channel Where Status
REST API (HTTP/JSON)https://api.kairossignal.com✅ Live
MCP serverhttps://kairossignal.com/mcp/ — 10 tools, agent-ready✅ Live
A2A agent cardhttps://a2a.kairossignal.com/.well-known/agent-card.json✅ Live
WebSocketNot yet
WebhooksNot yet
Agent-native by design. Beyond REST, KAIROS exposes an MCP server with 10 tools so AI agents can consume the dataset directly, and an A2A agent card for peer-agent discovery. This makes the data reachable from autonomous toolchains without bespoke scraping.

Kairos Signal · [email protected] · Home · Pricing · Internal Docs

Data for informational and research purposes only. Not investment advice.