Kairos Signal / per-network deep dive — AKT (Akash Network, compute) — generated 2026-09-02 12:48 UTC from live ClickHouse

AKT — Akash Network: the full deep dive

Every metric this estate holds for AKT, with the provenance of each cell: which upstream source reported it, when, and the exact URL to check it at the origin. No estimates, no zero-fill, no back-fill — if a metric is not flowing, it is absent from this page, not shown as zero.

Headline readings

The freshest value per headline metric, from whichever held source reported most recently. The verify link goes to the exact upstream endpoint the value came from — open it and the number should be in the same ballpark right now. That is the product.

Full metric inventory — every series we hold, grouped by source

One row per (metric, source): the latest value that source reports, the unit as held, how many rows we archive, the freshest stamp, the verify URL, and the comparability status of the underlying concept. Hover a value for the raw float.

source: CoinGecko /coins/markets — 24 metric series

source: akash_console — 177 metric series

source: cosmos_lcd — 22 metric series

source: first_party_api — 22 metric series

source: github — 6 metric series

Collection history — rows recorded per day, last 30 days

Each bar is one day of collector writes for AKT, straight from the ledger's own timestamps. Days before our collectors first touched AKT are absent, not zero — 2026-08-09 is the first day we hold. A gap would mean the collectors were down; we would publish the gap, not paper over it.

30-day history — headline series, day by day

Each collapsible series is the last observed value per day for one metric, queried live from the ledger. The full per-row archive (every stamp, not just dailies) is what the API serves.

Revision ledger — 0 restatements recorded for AKT

Zero is a finding, not an omission: our detector archives the before-value whenever an upstream source rewrites a number for an already-observed date, and for AKT it has caught nothing so far — no backward revision is recorded in default.depin_revision_ledger (queried live at generation). That is not a promise it never will; Arweave rewrote its own block history by −14.0% before anyone told buyers — see the worked example at /revision-ledger/sample-ar-restatement.html. The full feed is /v1/revisions.

Comparability grades — what each concept can be honestly compared against

Every metric we hold is either mapped to a canonical concept (which carries a comparability grade: question-verified means a human audited that the underlying native metrics answer the same question across networks; unit-verified means units match but semantics are not audited) or left as a native series only. The grade column in the inventory above is produced from the same live module this section summarises.

Unit transform note, live from the canonical-metrics module: Akash reports CPU in millicpu; the canonical layer divides by 1,000 so cross-network comparisons use cores. This page shows the raw held value — the transform is declared, never silent.

Estate grades for AKT (graded 2026-08-20 13:54:15.000)

Served by /v1/network/AKT — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth.

Verify any cell yourself — the exact commands

Everything above is reproducible without an account. Our API, anonymously:

curl -s https://kairossignal.com/v1/network/AKT | python3 -m json.tool | head -40
curl -s "https://kairossignal.com/v1/supply?network=AKT" | python3 -m json.tool | head -40

And the upstream origins themselves — the same endpoints our collectors read:

# bonded / not-bonded tokens, straight from the Akash chain via the Cosmos directory LCD:
curl -s https://rest.cosmos.directory/akash/cosmos/staking/v1beta1/pool | python3 -m json.tool

# provider / CPU / GPU / memory / storage capacity, from Akash's own console API:
curl -s https://console-api.akash.network/v1/network-capacity | python3 -m json.tool | head -40

Every value in the inventory carries its own per-source verify_url — the "check at origin" column — and the curl blocks above are the same fetch a buyer's agent would script. If an origin ever disagrees with what we published, the row's as_of tells you which snapshot we served.

curl -s "https://kairossignal.com/v1/network/AKT"
curl -s "https://kairossignal.com/v1/supply?network=AKT"