DIMO — the network, measured

Generated 2026-09-02T17:11:55Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,759 observations · 42 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 16:49:30 · 7,759/7,759 rows carry a verify_url. 31 series refreshed in the last 24h (726 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

4 source families feed this network's ledger. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that.

30-day history — headline series (daily last-value, live)

One row per series: latest value, a 30-day sparkline of daily last-known values (scaled to the series' own min→max), day count, and window change. Series absent from the 30-day window are omitted from this table, not zero-filled.

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, diluted valuation, and the published change columns including ATH/ATL. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. The change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. The circulating and total/max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other or against the chain-side contract read in the token section below — different measurements from different endpoints, shown side by side.

Network self-telemetry — DIMO's own identity API, as held (first-party)

First-party reads of DIMO's own public GraphQL API (identity-api.dimo.zone) by this estate's collectors: the network's own counts of registered vehicles, connected vehicles, aftermarket devices, synthetic devices, DCNs, and manufacturers. This is the network's self-reported supply-side telemetry — the strongest provenance class in the ledger: the upstream is the network itself, and each row's verify_url re-executes the same GraphQL query the collector ran (the collector sends { "query": "{ vehicles(first: 1) { totalCount } }" } — every verify command on this page re-runs exactly that shape, probe-verified before this page shipped). connected_vehicles flows near-daily in the archive; the other five counters were collected 2026-08-09 and are shown from their first held row — newer rows are absent from the ledger and that absence is shown, not smoothed. The GraphQL schema has no connectedVehicles field — that metric name is the estate's label for the vehicles(first:1) series.

Token & contract counters — evm_blockscout family, as held

The estate's EVM family reading the DIMO ERC-20 token contract 0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b on eth.blockscout: token counters (holders, transfers, the contract's totalSupply), contract-level address counters (transactions, gas used), and the top holder's balance. The catalog lists DIMO's chains as ethereum,iotex,polygon-pos; the estate holds chain telemetry for the ETHEREUM-side contract only — no IoTeX- or Polygon-native rows exist in the ledger (absence, not zero; no such section exists on this page). Cumulative counters are published raw — never differenced into rates.

Dev velocity — GitHub, as held

Raw GitHub API counters for DIMO-Network — repo-level (DIMO-Network/data-sdk) and one org-level row (public_repos via api.github.com/orgs/DIMO-Network, a different measurement from the repo rows; each keeps its own verify_url). Counters are published raw, never differenced into rates; dev_days_since_push is a raw time delta from the repo's real pushed_at timestamp.

Full metric inventory — 42 measured series, each with provenance

Every series held for DIMO with rows in the last 30 days: latest value, when it was observed, which source observed it, how many rows we hold, how many of the last 30 days it reported, its comparability grade, and the origin link. "days/30" counts distinct dates with at least one row in the window.

Revision ledger — 0 backward revision(s) recorded for DIMO

Backward revisions are values upstream later replaced for a date we had already archived. The before-value is retained — that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

The ledger query ran during generation and returned 0 rows for DIMO. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

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

Served by /v1/network/DIMO — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The dev-velocity and revenue grades are F and data coverage C, and they are published exactly as computed: the estate's dev-velocity engine scores DIMO's GitHub activity against its own window, the estate holds no protocol-revenue adapter rows for DIMO, and the measured-series count this page derives is the coverage engine's input — the unflattering parts ship with the flattering ones, unsmoothed.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–4 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given, id dimo); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields. One polite call per endpoint, no hammering.

# 1) DIMO's OWN identity GraphQL API — the network's self-reported supply-side counts (keyless, as of 2026-09-02T17:11:55Z):
#    (connected vehicles = the collector's vehicles(first:1) series) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"query": "{ vehicles(first: 1) { totalCount } }"}' "https://identity-api.dimo.zone/query"
#    (registered vehicles, same query) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"query": "{ vehicles(first: 1) { totalCount } }"}' "https://identity-api.dimo.zone/query"
#    (aftermarket devices) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"query": "{ aftermarketDevices(first: 1) { totalCount } }"}' "https://identity-api.dimo.zone/query"
#    (synthetic devices) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"query": "{ syntheticDevices(first: 1) { totalCount } }"}' "https://identity-api.dimo.zone/query"
# 2) Token counters on eth.blockscout (holders / transfers for the DIMO ERC-20 contract):\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b" | python3 -m json.tool | head -20
# 2b) Token transfer counter detail:\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b/counters" | python3 -m json.tool
# 2c) Contract ADDRESS counters (transactions, gas used):\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b/counters" | python3 -m json.tool
# 2d) Top holder balance (token holders listing):\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b/holders" | python3 -m json.tool | head -20
# 3) Market reference (CoinGecko public API — the coingecko.com browser\n#    coin page 403s plain curl, so the programmatic endpoint is given):\n# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows) — the coingecko.com browser
# coin page 403s plain curl, so the programmatic endpoint is given
# (id: dimo):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=dimo" | python3 -m json.tool
# 3b) Human-view check of the verify_url target (the browser coin page 403s plain curl — that is the documented 403, the programmatic command above is the verification path):\ncurl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/dimo"
# 4) Dev velocity, repo-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/DIMO-Network/data-sdk" | python3 -m json.tool | head -20
# 4b) Dev velocity, org-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/DIMO-Network" | python3 -c "import json,sys; print('public_repos', json.load(sys.stdin).get('public_repos'))"
# 5) This estate's public API row for DIMO:\ncurl -s "https://kairossignal.com/v1/network/DIMO" | python3 -m json.tool | head -60

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_deep_dive_dimo.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. Comparability grades come from the served canonical-metric system via its own resolver: total_supply maps to token_supply_total (question-verified). The remaining series are DIMO-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "dimo-native (unmapped)". Chain-side rows are Ethereum-side by documented upstream shape: the catalog lists DIMO's chains as ethereum,iotex,polygon-pos, but the estate holds chain telemetry for the ethereum-side token contract only (eth.blockscout) — no IoTeX- or Polygon-native telemetry exists on this page, and that is absence, not zero. The CoinGecko circulating and total/max supply rows are different quantities (circulating vs total vs cap) and are never netted; the ERC-20 contract's totalSupply (blockscout) is a third, chain-side measurement of the token contract, shown side by side and never reconciled into one number. The first-party family reads DIMO's own identity GraphQL API — the network's self-reported counts, labelled as such and never merged with the chain-side or market-reference rows. GitHub rows mix repo-level and org-level counters; both are labelled with their own provenance and never combined, and dev_days_since_push is a raw time delta from a real timestamp. The estate grades are published exactly as the engines served them, unflattering parts included; dev velocity F, revenue F and data coverage C are the engines' own outputs, not derived from any series on this page. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: CoinGecko markets API (dimo) HTTP 200; DIMO identity-api GraphQL (vehicles(first:1) POST) HTTP 200; eth.blockscout token endpoint (dimo contract) HTTP 200; eth.blockscout token counters (dimo contract) HTTP 200; eth.blockscout address counters (dimo contract) HTTP 200; GitHub DIMO-Network/data-sdk HTTP 200; GitHub orgs/DIMO-Network HTTP 200; estate /v1/network/DIMO HTTP 200.