bittensor.ai API
One account for subnets, validators, staking pools, markets and wallets, on the site and through the API. Start free, and pay monthly when you need more.
For browsing: the explorer and its public analytics. Free.
Usage included: requests are not charged on top.
Create a free accountFor people tracking their own wallets.
Usage included: requests are not charged on top.
Choose HolderFor active stakers.
Usage included: requests are not charged on top.
Choose TraderFor professional stakers and quants.
Usage included: requests are not charged on top.
Choose ProLarge customers that need custom limits and terms.
Contact usWhat each plan includes. Building a product for other people? Contact us.
| Feature | ExplorerFree | Holder$5 per month | Trader$19 per month | Pro$49 per month |
|---|---|---|---|---|
| Your wallets | ||||
| Wallets you can analyseWallets you have proved you own, by signing a message. | 2 | 10 | 25 | 50 |
| PerformanceCost basis, profit and loss, and returns. | No | Yes | Yes | Yes |
| The API | ||||
| API keys | 1 | 2 | 10 | 25 |
| Requests per minuteShared by all your keys. Every request counts as one. | 10 | 30 | 120 | 300 |
| Requests per dayStarts again each UTC day. | 500 | 2,000 | 10,000 | 25,000 |
| Prices and subnet basics | Yes | Yes | Yes | Yes |
| Data about your own wallets | Yes | Yes | Yes | Yes |
| Data about any wallet | No | Yes | Yes | Yes |
| Where-to-stake analyticsSubnets, validators, yields and flows, with their history. | No | No | Yes | Yes |
| Raw chain and operator dataBlocks, extrinsics and events, and the data validators work from. | No | No | No | Yes |
| Address labels and entities | No | No | No | No |
| Direct node access (RPC)Reading the chain and sending your own signed transactions. | Standard | Standard | Standard | Full, with EVM |
| How you can use it | ||||
| Use in products you build for others | No | No | No | No |
| Reselling or redistributing the data | No | No | No | No |
Net TAO flowing into each subnet over 7 and 30 days (from the chain's own counter, emissions excluded), realised staker yield, and entry and exit cost at a reference stake.
Holder total return for root stakers, fund NAV per share, validator take, stakers per pool and root daily return.
Holdings, activity, per-wallet returns and claimable amounts for your wallets, or for any public address on the plans that include it.
Blocks, decoded extrinsics, events and call trees, and subnet identity history.
Alpha prices, candles and pool state.
A standard OpenAPI document that gives the unit of every numeric field, ready to hand to an AI assistant, an agent framework or an OpenAPI-to-MCP bridge.
Authorization header or in the X-API-Key header.Need more than a plan offers? Contact [email protected] for higher limits.
The API is served at https://api.bittensor.ai/api/v2 and returns JSON.
Send your key on every request, either as a bearer token in the Authorization header or in the X-API-Key header. Both carry the same key with the same access and limits. A request without a valid key gets 401 UNAUTHORIZED; the OpenAPI spec is the one thing that can be fetched without one.
curl "https://api.bittensor.ai/api/v2/subnets?limit=10" \
-H "Authorization: Bearer YOUR_API_KEY"The public specification at https://api.bittensor.ai/api/v2/openapi.json lists every public endpoint, parameter and response schema. Numeric fields carry their unit (x-unit) and conversion (x-convert). Token amounts are integer strings in rao, null means unknown (never zero), and timestamps are UTC.
Because it is a standard OpenAPI document, you can hand it to an AI assistant, an agent framework or an OpenAPI-to-MCP bridge and let it build the calls.
A plan has request limits per minute and per day, shared by all of the account's keys. Every request counts as one. Successful responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset for the window with the least room left, so a client can pace itself.
429 with the error code RATE_LIMITED. Retry-After and X-RateLimit-Reset say when it reopens.429 with CONCURRENCY_LIMIT and Retry-After: 1. Lower your parallelism.429 with Retry-After: 60.Wait for the time in Retry-After rather than retrying in a loop.
Within /api/v2, a breaking change is never made without notice. A retired field or parameter is deprecated at least 90 days before removal, an endpoint at least 6 months, with Deprecation and Sunset headers on the response. Additions need no notice. Beta routes (x-stability: beta in the spec) can change with one release's notice.
Every error has a stable code; the API errors page lists each one and what to do about it.