Subnet list
Subnet metadata
Metagraph
Hyperparameters
Subnet registration costTAO balances
Stake positions
Validator stakes
Delegation
Alpha / subnet token dataHotkeys
UIDs
Metagraph
Weights
Validator state
Miner registrationBittensor applications often need chain data associated with a specific netuid: subnet metadata, metagraph state, validator/miner registrations, weights, stake and hyperparameters.
btcli subnets list
btcli query metagraph --netuid 1Bittensor validators rely on consistent access to Subtensor chain state to monitor subnet activity, evaluate miners, manage staking-related workflows, and publish or inspect weights.
Miners can use Bittensor RPC to monitor their on-chain identity and registration status across the subnets where they participate.
Use OnFinality's Bittensor RPC APIs to connect wallets, dApps, dashboards, bots, and backend services without operating your own node from day one.
Start with the Bittensor public RPC endpoint for lightweight checks, prototypes, and quick integration tests.
Move production traffic to authenticated endpoints when you need clearer limits, analytics, and operational visibility.
Query Bittensor blocks, transactions, balances, events, and chain state through HTTP and WebSocket workflows.
Production teams need more than an endpoint URL. They need observability, predictable capacity, and a path from shared RPC access to isolated infrastructure.
Track usage patterns and response activity so your team can understand traffic growth before it becomes an incident.
Use dedicated Bittensor nodes when your workload needs isolated resources, custom operations, or stronger capacity planning.
Plan for archive access when analytics, audits, indexers, or advanced app features need older Bittensor state.
Different Bittensor products need different infrastructure. OnFinality gives teams a practical path from public RPC testing to production-grade API and node operations.
Use public RPC for simple reads, connection checks, and early experiments where strict performance guarantees are not required.
Use authenticated API endpoints when users depend on stable request handling, monitoring, and scalable access.
Use dedicated nodes for sustained traffic, latency-sensitive services, validator tooling, exchange systems, and indexing pipelines.
OnFinality takes away the heavy lifting of DevOps so you can build smarter and faster.
Get Started