API reference / Runtimes and storage
One runtime spec
https://api.bittensor.ai/api/v2/runtimes/{spec_version}- Status
- Stable
- Auth
- API key or OAuth access token
- Scope
data:read- Rate limit
plan
One runtime spec: the same row as in GET /api/v2/runtimes (names and versions, the first and last block it executed, whether it is current, its metadata versions and runtime APIs). Follows the head. Errors are application/problem+json: INVALID_SPEC_VERSION, RUNTIME_NOT_FOUND (404, no such spec), UNKNOWN_PARAMETER, SOURCE_TIMEOUT (503), SOURCE_NOT_READY (503).
Path parameters
- spec_versionpath, required· integer · 0 to 2147483647
The runtime's spec_version (e.g.
470).
Query parameters
- includequery· string
Reserved for opt-in sections. This route defines none yet; the parameter is declared so that adding one later is additive for generated clients. Any value is a 400
INVALID_INCLUDE.
Response
data is an object 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.
The spec: the same row as in GET /api/v2/runtimes.
- spec_versioninteger · unit id
The runtime's spec_version.
- spec_namestring · can be null
spec_name (
node-subtensor). Null for early specs not decoded yet.- impl_namestring · can be null
impl_name. Null for early specs not decoded yet.
- impl_versioninteger · unit id · can be null
impl_version. Null for early specs not decoded yet.
- transaction_versioninteger · unit id · can be null
transaction_version. Null for early specs not decoded yet.
- first_heightinteger · unit block
The first block this spec executed, the same rule as a block's
spec_version: an upgrade enacted in block N still runs the old spec there, so the new spec'sfirst_heightis N + 1, and/blocks/{first_height}shows this spec.- first_timestring (date-time) · can be null
Timestamp of
first_height, RFC 3339 UTC. Null when that block is not indexed yet.- Format: date and time, ISO 8601 in UTC
- last_heightinteger · unit block · can be null
The last block this spec executed: the next spec's
first_height- 1. Null for the current spec.- is_currentboolean
True for the spec the newest indexed block runs (exactly one).
- metadata_versionsarray of integer
The metadata versions served for this runtime by
GET /api/v2/runtimes/{spec_version}/metadata?version=([14, 15, 16]for current runtimes,[14]for runtimes from before metadata V15). That route's default is the highest.- apisarray of objects
The runtime APIs this runtime implements (RuntimeVersion.apis), in the runtime's own order.
3 fields in apis (each item)
- idstring
The API's id: blake2b-64 of its trait name, 0x + 16 lower-case hex (as RuntimeVersion lists it).
- Pattern:
^0x[0-9a-f]{16}$ - namestring · can be null
The trait name (e.g.
Core,Metadata,SwapRuntimeApi). Null for an id nobody has named (none today: every id of every runtime is named).- versioninteger · unit id
The version of the API this runtime implements.
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_INCLUDE
- INVALID_SPEC_VERSION
- PAYMENT_REQUIRED
- PLAN_REQUIRED
- RATE_LIMITED
- RUNTIME_NOT_FOUND
- SERVICE_UNAVAILABLE
- SOURCE_BUSY
- SOURCE_NOT_READY
- SOURCE_TIMEOUT
- UNAUTHORIZED
- UNKNOWN_PARAMETER
- VALIDATION_ERROR
From the API's published specification, version 1.165.0.