How many accounts hold at least 0.1 / 1 / 10 / 100 / 1k / 10k TAO, per UTC day
https://api.bittensor.ai/api/v2/accounts/holder-thresholds- Status
- Beta
- Auth
- API key or OAuth access token
- Scope
data:read- Rate limit
plan
The distribution of holders over time: per UTC day (at its close), the accounts holding at least 0.1, 1, 10, 100, 1,000 and 10,000 TAO in measure (total: free + reserved + staked, the default; free; staked), the accounts holding any, and the sum over every account.
Full description
The distribution of holders over time: per UTC day (at its close), the accounts holding at least 0.1, 1, 10, 100, 1,000 and 10,000 TAO in measure (total: free + reserved + staked, the default; free; staked), the accounts holding any, and the sum over every account. Each count includes the higher thresholds' accounts (holders_ge_0_1 >= holders_ge_1 >= ... >= holders_ge_10k). Free and reserved are the account's System.Account balance at the day's close (carried forward from its last change). Staked is its alpha holdings as a coldkey on every subnet, root included, valued in TAO at each pool's close price that day. Unclaimed root dividends and liquidity-provider positions are not in these balances. Protocol accounts are pallet / module accounts (their 32 bytes start with modl): subnet accounts, escrows, the treasury. They hold TAO for the protocol, not for a holder, and are left out by default (exclude_protocol=true). The window is from_day..to_day (UTC days, inclusive), or the days ending at to_day (default the 30 days ending on the newest available day), at most 400 days; it is clamped to the available days (meta.from_day / meta.to_day). Read from the analytics store only: it computes each UTC day after it closes, so the newest day is meta.through_day. A day more than 6 hours overdue (at most 36) is still served, labelled by meta.through_day, with the response headers X-BTAI-Data-Through: <YYYY-MM-DD> and X-BTAI-Overdue-S: <seconds> (cached as slow); a store more than 36 hours overdue is a 503 SOURCE_NOT_READY with Retry-After, as is one still computing the day. meta.sources names the store. Where this deployment does not serve the rich list the route is a 503 SOURCE_NOT_READY. A pinned window served as asked is cached as settled, anything else as slow. Errors are application/problem+json: INVALID_DAY, INVALID_DAYS, INVALID_RANGE, RANGE_TOO_LARGE (over 400 days), INVALID_MEASURE, INVALID_BOOLEAN, UNKNOWN_PARAMETER, SOURCE_TIMEOUT (503), SOURCE_NOT_READY (503), SERVICE_UNAVAILABLE (503), BAD_GATEWAY (502: the store's answer broke its contract).
Beta: this route may change with one release's notice in the v2 changelog; additive changes need none (x-stability: beta).
Query parameters
- from_dayquery· string (date)
The first UTC day,
YYYY-MM-DD, inclusive (not withdays: a 400INVALID_RANGE). Not a date: a 400INVALID_DAY.- Format: date, YYYY-MM-DD
- to_dayquery· string (date)
The last UTC day,
YYYY-MM-DD, inclusive (default: the newest available day). Beforefrom_day: a 400INVALID_RANGE; more than 400 days after it: a 400RANGE_TOO_LARGE.- Format: date, YYYY-MM-DD
- daysquery· integer · 1 to 400
The window's length in days ending at
to_day, 1..400 (default 30 withoutfrom_day). Anything else is a 400INVALID_DAYS.- measurequery· enum · one of total, free, staked · default total
The balance counted:
total(free + reserved + staked, the default),freeorstaked. Anything else is a 400INVALID_MEASURE.- exclude_protocolquery· enum · one of true, false · default true
true(the default): leave protocol accounts (pallet / module accounts: subnet accounts, escrows, the treasury) out.false: rank and count them too. Lower-case; anything else is a 400INVALID_BOOLEAN.
Response
data is a list of objects with these fields. Amounts are integer strings in their base unit, and null means unknown, never zero (see Units and formats). meta.at names the block the answer was read at.
One row per available day in meta.from_day..meta.to_day, oldest first; [] when none.
- daystring (date)
The UTC day, at its close.
- Format: date, YYYY-MM-DD
- is_completeboolean
True when the day's counts are whole. False when the window starts before the counts' coverage: every figure is then null and
unavailable_reasonsays why (never a partial count).- holders_ge_0_1integer · unit count · can be null
Accounts holding at least 0.1 TAO in
meta.measure. Null exactly whenis_completeis false.- holders_ge_1integer · unit count · can be null
Accounts holding at least 1 TAO. Null exactly when
is_completeis false.- holders_ge_10integer · unit count · can be null
Accounts holding at least 10 TAO. Null exactly when
is_completeis false.- holders_ge_100integer · unit count · can be null
Accounts holding at least 100 TAO. Null exactly when
is_completeis false.- holders_ge_1kinteger · unit count · can be null
Accounts holding at least 1,000 TAO. Null exactly when
is_completeis false.- holders_ge_10kinteger · unit count · can be null
Accounts holding at least 10,000 TAO. Null exactly when
is_completeis false.- holders_nonzerointeger · unit count · can be null
Accounts holding any units in the measure (TAO or alpha), whatever their value; an account whose only holding is worth 0 at spot counts. Null exactly when
is_completeis false.- sum_raostring · unit rao (÷1e9) · can be null
The sum of
meta.measureover every account in scope, rao. Null exactly whenis_completeis false.- Format: whole number, as a string · on chain: u64
Response headers
10 headers: ETag, Cache-Control, CDN-Cache-Control, X-BTAI-Stale, X-BTAI-Stale-As-Of, RateLimit-Policy, RateLimit, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
- ETag
Strong validator of this answer. Send it back as
If-None-Match: an unchanged answer is a 304 Not Modified without a body. A settled answer's validator leaves the chain head out, so it stays valid as the head moves.- Cache-Control
One of three classes: settled
public, max-age=3600, stale-while-revalidate=86400(pinned to a block that cannot move), slowpublic, max-age=300, stale-while-revalidate=600(state that moves in minutes or days) or tippublic, max-age=6, stale-while-revalidate=12(follows the chain head); the label routes are cached until the next nightly copy (public, max-age=<seconds>, stale-while-revalidate=60). Neverimmutable.no-storeon an earlier answer served because the data source failed (X-BTAI-Stale).- CDN-Cache-Control
The same class for shared caches (RFC 9213; browsers ignore it): settled 24 h, slow 300 s, tip 6 s, each with
stale-while-revalidateandstale-if-error;no-storewithX-BTAI-Stale.- X-BTAI-Stale
Present only when the data source failed to answer (it timed out or was unavailable) and an earlier answer to the same request is served instead of a 503 (stale if error, RFC 5861). Then
if-error, withX-BTAI-Stale-As-Of,Age(its seconds since then) andWarning: 110 - "Response is Stale", andCache-Control: no-store: the answer is never kept as fresh, and a later request reads again. Prices and quotes are never served this way.- X-BTAI-Stale-As-Of
With
X-BTAI-Stale: when the earlier answer served was produced, an RFC 3339 UTC time (2026-10-21T12:00:00Z).- RateLimit-Policy
The tier's request quota of the current window (IETF draft), e.g.
"tier";q=600.- RateLimit
Requests left in the current window and the seconds until it resets (IETF draft), e.g.
"tier";r=597;t=42.- X-RateLimit-Limit
The tier's request quota of the current window.
- X-RateLimit-Remaining
Requests left in the current window.
- X-RateLimit-Reset
When the current window resets, Unix seconds.
Status codes
200 · 304 · 400 · 401 · 402 · 403 · 404 · 429 · 500 · 502 · 503
304 Not Modified: the If-None-Match validator still matches; no body.
Error codes
The codes this endpoint can return. Each links to what it means and what to do.
- AMBIGUOUS_CREDENTIALS
- BAD_GATEWAY
- BILLING_UNAVAILABLE
- BUDGET_EXCEEDED
- CONCURRENCY_LIMIT
- INSUFFICIENT_PERMISSIONS
- INTERNAL_ERROR
- INVALID_BOOLEAN
- INVALID_DAY
- INVALID_DAYS
- INVALID_MEASURE
- INVALID_RANGE
- PAYMENT_REQUIRED
- PLAN_REQUIRED
- RANGE_TOO_LARGE
- RATE_LIMITED
- REPEATED_PARAMETER
- SERVICE_UNAVAILABLE
- SOURCE_BUSY
- SOURCE_NOT_READY
- SOURCE_TIMEOUT
- UNAUTHORIZED
- UNKNOWN_PARAMETER
- VALIDATION_ERROR
From the API's published specification, version 1.165.0.