Kairos Signal Technical Manual

Verifiable DePIN supply-side telemetry. Every value carries its source, a timestamp, and a verify_url you can check yourself. Provenance-first: we bring receipts.

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:

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 731 entries (superseded and Bittensor subnet rows included) across compute, storage, wireless, sensor, AI, and other categories. 501 symbols (372 networks plus 129 Bittensor subnets) have live data flowing. Each network is classified into one of three telemetry tiers:

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.

Data Sources (top 15 by network count)

154 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 network has a first-party stats API registered → first_party_telemetry
ELIF live supply telemetry is flowing (from any chain-direct source) → first_party_telemetry
ELIF on-chain market data exists (price, supply from CoinGecko) → onchain_only
ELSE → catalog_only (project known but no data flowing)

No enrichment is invented. A tier only reflects data that actually exists.

REST API (19 endpoints, all live)

The primary delivery mechanism. All endpoints return JSON. Base URL: https://api.kairossignal.com (proxied at https://kairossignal.com/v1/).

Analytical Engines (:6035)

Paid analytical endpoints that compute derived intelligence from the raw data:

Engines are available on the Pro plan ($499/mo) and above. 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/. 10 tools available, agent-ready.

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 Correlation Engine

A neural correlation encoder (all 63 layers execute over a 256-wide state; 32 dimensions published) available as a separate product at dag.kairossignal.com. Pricing: $99/mo per customer. On the record: the published vector draws on the 42 layers in the terminal layer’s ancestry; the other 21 compute each pass but do not feed it. Layers 51–52 draw unseeded noise, so the vector is not bit-reproducible across calls.

Computes cross-network correlation manifolds from the same provenance-stamped telemetry: the encoder is a learned map, not a symplectic integrator, and the published vector is the first 32 dimensions of its state. Nearest-neighbour and distance queries on that vector are what the product returns.

Plans & Pricing

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/mo (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 before the verified-wallet USDC top-up flow.

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.

Wallet verification, quotes 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]