A subnet's share of the network's TAO emission per day
https://api.bittensor.ai/api/v2/subnets/{netuid}/emission-share- Status
- Beta
- Auth
- API key or OAuth access token
- Scope
data:read- Rate limit
plan
Per UTC day, oldest first.
Full description
Per UTC day, oldest first: the TAO emitted into the subnet's pool (SubtensorModule.SubnetTaoInEmission summed over the day), the same over every subnet, the subnet's share of it (share_ratio) and its rank that day; and the day's whole TAO block emission to subnets (injected TAO + the chain's excess buy) with the subnet's share of THAT (share_of_block_emission_ratio, null on a day the protocol emission record does not cover yet). Default: the 90 days ending at the last available day (days counts back from to_day). The range is clamped to the days available so far (meta.history_from_day on; earlier history is still being prepared): meta.from_day / meta.to_day say what was served. A range that ends before the first day available is a 400 INVALID_RANGE. Day window: from_day / to_day (inclusive UTC days), or days back from to_day (not both days and from_day); no ceiling: a range longer than meta.page.limit_days pages by cursor (meta.page.next_cursor), oldest days first, and meta.range states the whole request (from_day raised to the first available day says so). An explicit to_day is never answered with an earlier day: one not available yet is a 503 NOT_READY. While paged day windows are not available yet, from_day, to_day and cursor are a 503 SOURCE_NOT_READY (a days-only request is unchanged). One life: a netuid is a slot and a re-registered subnet is a new life; the series covers the subnet's CURRENT life only, from its first whole UTC day (meta.generation, meta.life_start_height, meta.life_first_day; a life with no whole day yet answers no rows). While per-life series are not available yet, the series is not limited to one life and those members are null. A pinned, closed range is cached as settled. Errors are application/problem+json: INVALID_DAY, INVALID_DAYS, INVALID_RANGE, INVALID_CURSOR, UNKNOWN_PARAMETER, NOT_READY (503), SOURCE_TIMEOUT (503), SOURCE_NOT_READY (503).
Beta: this route may change with one release's notice in the v2 changelog; additive changes need none (x-stability: beta).
Path parameters
- netuidpath, required· integer · 0 to 65535
Subnet slot (0 = root).
Query parameters
- from_dayquery· string (date)
First UTC day,
YYYY-MM-DD, inclusive. Default:days(else 90) - 1 beforeto_day.- Format: date, YYYY-MM-DD
- to_dayquery· string (date)
Last UTC day,
YYYY-MM-DD, inclusive. Default: the last available day. Never answered with an earlier day: one not available yet is a 503NOT_READY; today is a 503NOT_READY, a later day a 400INVALID_RANGE.- Format: date, YYYY-MM-DD
- daysquery· integer · at least 1
How many days end at
to_day, 1..1,000,000 (no page ceiling: a long range pages bycursor). Not withfrom_day(both: a 400INVALID_RANGE). Outside 1..1,000,000: a 400INVALID_DAYS.- cursorquery· string · up to 200 characters
meta.page.next_cursorof the previous page: the next days of a range longer than one page, sent back unchanged with the same other parameters (a changed or altered one is a 400INVALID_CURSOR). While paged day windows are not available yet: 503SOURCE_NOT_READY.
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.
- Format: date, YYYY-MM-DD
- day_end_heightinteger · unit block
The day's last block the figures are summed through.
- tao_in_raostring · unit rao (÷1e9)
SubtensorModule.SubnetTaoInEmission summed over the UTC day: TAO emitted into the pool, rao.
- Format: whole number, as a string · on chain: u64
- network_tao_in_raostring · unit rao (÷1e9)
The same summed over every subnet that day, rao.
- Format: whole number, as a string · on chain: u64
- rankinteger · unit count
The subnet's rank by
tao_in_raothat day (1 = the largest; ties share).- network_block_emission_tao_raostring · unit rao (÷1e9) · can be null
The day's whole TAO block emission to subnets: every subnet's injected TAO plus the chain's excess buy (SubtensorModule.SubnetExcessTao), per block, rao. Null while the day's protocol flows aren't available yet, and on an older data version's answer.
- 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_CURSOR
- INVALID_DAY
- INVALID_DAYS
- INVALID_NETUID
- INVALID_RANGE
- NOT_READY
- PAYMENT_REQUIRED
- PLAN_REQUIRED
- 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.