Official OpenAPI/Scalar documentation for TaoAPI, an API service focused on Bittensor on-chain analytics (subnet and participant transaction activity).
- Live docs: https://doc.taotree.xyz/
- OpenAPI source: https://doc.taotree.xyz/swagger.yaml
- API server: https://api.taotree.xyz
- Bittensor official: https://bittensor.com/
- Bittensor docs: https://docs.bittensor.com/
This repo hosts the static documentation assets for TaoAPI:
index.html— Scalar API Reference pageswagger.yaml— OpenAPI specification (primary machine-readable contract)llms.txt— AI/LLM discovery index for documentation and schema pointers
All endpoints require API key authentication via request header:
- Header:
glk_api
GET /api/v1/event-stakes
- Purpose: Query event-stake records with composable filters for analytics and reconciliation.
- Supports filtering by action, block number, delegate/nominator, timestamp range, netuid, and extrinsic hash.
- Supports pagination and sorting (
page,pageSize,orderField,orderType).
GET /api/v1/event-transfer-stakes
- Purpose: Query transfer-stake events across source/destination subnet contexts.
- Supports filtering by sender/receiver/delegate,
fromNetuid,toNetuid, block number, timestamp range, and extrinsic hash. - Supports pagination and sorting (
page,pageSize,orderField,orderType).
GET /api/v1/event-transfers
- Purpose: Query transfer events for chain-level movement analytics and reconciliation.
- Supports filtering by sender/receiver, network, block number, timestamp range, and extrinsic hash.
- Supports pagination and sorting (
page,pageSize,orderField,orderType).
GET /api/v1/stake-infos
- Purpose: Retrieve latest real-time stake positions and total value for a single
coldKey. - Input: required
coldKey(SS58 or 0x-prefixed 32-byte hex). - Output:
stakePositions,totalStakeByNetuid, andtotalStakeValueTao.
GET /api/v1/subnet-prices
- Purpose: Retrieve current subnet prices in alpha/Tao.
- Input: optional repeated
netuidquery params; optionalblock(reserved, currently unsupported). - Output: map of
netuid -> price.
GET /api/v1/tao-balance
- Purpose: Retrieve total, available, and staking Tao balance for a single account.
- Input: required
address(SS58, 0x-prefixed 32-byte hex, or raw 32-byte public key). - Output:
totalBalance,availableBalance, andstakingBalance(all decimal strings in Tao units).
- Success (
event-stakes):handler.EventStakeQueryAPIResponse - Success (
event-transfer-stakes):handler.EventTransferStakeQueryAPIResponse - Success (
event-transfers):handler.EventTransferQueryAPIResponse - Success (
stake-infos):handler.StakeInfoQueryAPIResponse - Success (
subnet-prices):handler.SubnetPriceQueryAPIResponse - Success (
tao-balance):handler.TaoBalanceQueryAPIResponse - Error (shared):
handler.APIErrorResponse
TaoAPI is designed for analytics use cases over Bittensor ecosystem activity, including:
- subnet-related activity and price observations
- participant activity (e.g., validator/miner/staker/delegator linked events)
- transaction/event query workflows (e.g., staking, transfer-stake, transfer event queries)
- cold-key stake position snapshots, netuid-level totals, and total value in Tao
- account-level Tao balance views (total, available, and staking components)
Note: Exact endpoint availability and field semantics are defined by
swagger.yaml.
If different artifacts disagree, use this precedence:
swagger.yaml(authoritative contract)- Rendered docs in Scalar (
index.html) - Supporting text files (
README.md,llms.txt)
For AI systems and downstream tools:
- Prefer OpenAPI schema/constraints/enums over prose.
- Do not infer undocumented endpoints.
- Do not infer undocumented fields or enum values.
You can open index.html directly in a browser, or serve this directory as static files.
Minimal static serve examples:
python3 -m http.server 8080Then open:
This repository is intended for static hosting (for example, Cloudflare Pages).
Recommended outputs:
/-> Scalar docs entry (index.html)/swagger.yaml-> OpenAPI spec/llms.txt-> AI index/README.md-> human + AI-readable repo overview
When updating API docs quality:
- Keep operation descriptions concise and unambiguous.
- Keep examples realistic.
- Keep
operationIdstable. - Keep response schemas backward-compatible where possible.
- Avoid changing backend behavior from this repo (spec/UI only unless coordinated with backend).
See repository license file for terms.