Documentation / New API reference / Gamma
Get Gamma Subnets
Reference
Last reviewed 2026-11-06
Totals for active subnets, ordered by netuid.
Try it
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
netuid | query | string | Filter by one or more subnet IDs. | |
page | query | integer (int32) | Page number, starting at 1. Default: 1. Bounded window: (page − 1) × limit must be below 1,000,000. | |
limit | query | integer (int32) | Results per page. Default: 50; maximum: 200. |
Responses
200 — Gamma totals for active subnets
| Field | Type | Required | Description |
|---|---|---|---|
data | array | Yes | |
data[].alpha_burned_for_gamma | string | Yes | All-time alpha burned to mint Gamma, in alpha rao. |
data[].alpha_burned_for_gamma_stake_source | string | Yes | Alpha burned for stake-paid Gamma mints, in alpha rao. |
data[].alpha_burned_for_gamma_tao_source | string | Yes | Alpha burned for TAO-paid Gamma mints, in alpha rao. |
data[].deposit_count | string | Yes | Number of open deposits. |
data[].first_mint_block | integer (int32), nullable | Yes | First block containing a Gamma mint, or null when no mint occurred. |
data[].gamma_enabled | boolean, nullable | Yes | Whether Gamma minting is enabled for this subnet, or null before the chain has Gamma state. |
data[].gamma_minted | string | Yes | All-time Gamma minted, in Gamma units. |
data[].gamma_outstanding | string | Yes | Sum of open deposit balances, in Gamma units. |
data[].gamma_price | string, nullable | Yes | Current Gamma price, as a decimal string, or null before Gamma. |
data[].gamma_spent | string | Yes | All-time Gamma spent, in Gamma units. |
data[].gamma_written_off | string | Yes | All-time Gamma written off when deposits were removed by dissolution. |
data[].last_activity_block | integer (int32), nullable | Yes | Most recent block with Gamma activity, or null when there is no activity. |
data[].mint_count | string | Yes | Number of Gamma mints. |
data[].netuid | integer (int32) | Yes | Subnet ID. |
data[].price | string | Yes | Current spot alpha price, as a decimal string. |
data[].spend_count | string | Yes | Number of Gamma spends. |
data[].tao_spent_on_gamma | string | Yes | All-time TAO spent on Gamma mints, in rao. |
pagination | object | Yes | Pagination metadata appended to collection responses. next_page / prev_page are explicitly required+nullable in the OpenAPI spec: per docs/api_standards.md we emit null rather than omitting the field, so the SDK should model them as Option/nullable types that are always present in the response. total_items is the exact number of matching rows on every route (issue #992). It used to stop at 1,000,000, which reported a million transfers when finney holds 7,513,252 and a million events when the real figure is 981,179,110; the cap was removed on 29 Sep 2026 and nothing may reintroduce one — crate::pagination::exact_count_sql is the only count form, and no_capped_count_reaches_the_api_surface in data-debug-scripts fails the build if a capped one comes back. total_pages is still bounded, to crate::pagination::max_reachable_page(per_page), because the page parameter is capped to a 1,000,000-row window: deep OFFSET paging reads every skipped row (24.7M rows / 36.6 GiB / 42 s measured on one endpoint, issue #413). So total_pages is exactly the last page this API will serve and next_page / prev_page stay coherent at the window edge, while total_items tells the caller how many rows there really are. History beyond the window is reached with each endpoint's range filters, not a larger page. |
pagination.current_page | integer (int32) | Yes | 1-indexed page that produced the rows in data. |
pagination.next_page | integer (int32), nullable | Yes | Next page number, or null if this is the last page. |
pagination.per_page | integer (int32) | Yes | Number of items requested per page. |
pagination.prev_page | integer (int32), nullable | Yes | Previous page number, or null if this is the first page. |
pagination.total_items | integer (int64) | Yes | Number of items matching the query across all pages. This is the exact count — every matching row, however many there are. It is not bounded by total_pages, so a listing can legitimately report far more items than total_pages × per_page. |
pagination.total_pages | integer (int32) | Yes | Number of pages at the current per_page that this API will serve: ceil(total_items / per_page), capped at ceil(1000000 / per_page) because the page parameter only reaches into the first 1,000,000 rows. When the cap bites, total_items is still the true total and this is the last page a request can ask for; reach deeper history with the endpoint's range filters instead of a larger page. |
400 — Invalid query parameter
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
500 — Internal server error
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Plain-english message describing the failure from the caller's perspective. |
status_code | integer (int32) | Yes | HTTP status code (mirrored in the response status line for convenience). |
Every request needs an Authorization header holding your API key — see Getting started with the Taostats API.