Logo
New RPC users get 35% off their first monthView the offer
Bittensor logo

Bittensor Finney RPC Endpoint & API

TAO Bittensor: Decentralized Machine Learning

Connect directly to Bittensor Finney through OnFinality's managed Subtensor RPC over HTTPS and WebSocket. Query TAO balances, subnet and validator state, monitor miners, build analytics, and access historical chain data without operating your own Bittensor node.

CurrencyTAO
Sign up for a Free Plan to unlock up to 40 req/sec and API Usage and Performance Insights. Get Started
Open In Polkadot JS

Public endpoint rate limit: 5 req/sec

Quick Start
btcli -n wss://bittensor-finney.api.onfinality.io/public-ws \
  query metagraph --netuid 1 --json
btcli -n wss://bittensor-finney.api.onfinality.io/public-ws \ query metagraph --netuid 1 --json

btcli accepts a custom WebSocket endpoint through --network, allowing Bittensor CLI workflows to query Finney through OnFinality instead of the default RPC.

HTTPs
https://bittensor-finney.api.onfinality.io/public
https://bittensor-finney.api.onfinality.io/public
Websocket
wss://bittensor-finney.api.onfinality.io/public-ws
wss://bittensor-finney.api.onfinality.io/public-ws

Go to Growth Plan

  • High Performance
  • Powerful RPC Analytics
  • Up to 500 rps
  • No daily response limit
  • Priority Support
  • Decentralized Servers
Get Started

Bittensor Finney RPC details

Item
Value
Network
Bittensor Finney Mainnet
Native token
TAO
Chain layer
Subtensor
Protocol
Substrate JSON-RPC
HTTPS
Supported
WebSocket
Supported
Public rate limit
5 RPS
Authenticated
Up to 500 RPS
Archive access
Supported
Dedicated nodes
Full / Archive / Validator
Regions
N. Virginia / Hong Kong
Service status
Independent benchmark

Bittensor data you can query

Subnets

Subnet list Subnet metadata Metagraph Hyperparameters Subnet registration cost

TAO & staking

TAO balances Stake positions Validator stakes Delegation Alpha / subnet token data

Validators & miners

Hotkeys UIDs Metagraph Weights Validator state Miner registration

Query Bittensor Subnets

Bittensor 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 1

Bittensor RPC for Validators and Miners

Validators

Bittensor validators rely on consistent access to Subtensor chain state to monitor subnet activity, evaluate miners, manage staking-related workflows, and publish or inspect weights.

  • Metagraph datamonitor UIDs, hotkeys, validator/miner state and subnet participants
  • Weightsquery current on-chain weight information
  • Subnet statemonitor subnet configuration, hyperparameters and registrations
  • Staking dataquery TAO stake and delegation-related chain state
  • Finalized chain stateuse finalized data for workflows that require stronger consistency
  • WebSocket RPCsubscribe to chain updates without continuously polling HTTP endpoints

Miners

Miners can use Bittensor RPC to monitor their on-chain identity and registration status across the subnets where they participate.

  • Registration statusverify whether a hotkey is registered on a subnet
  • UID and hotkey dataquery miner identity and current subnet position
  • Subnet membershipmonitor participation across specific netuids
  • Metagraph datainspect miner and validator state for a subnet
  • Emissions and rewards-related dataaccess relevant on-chain state used for monitoring earnings and subnet economics
  • Chain monitoringtrack blocks and state changes through HTTP or WebSocket RPC

Shared Bittensor RPC vs Dedicated Bittensor Node

Workload
Shared RPC
Dedicated
TAO wallet
Subnet dashboard
optional
Analytics
Large backfills
Miner monitoring
High-volume
Validator operations
Possible
Recommended
Public explorer
Possible
Recommended
Archive/indexing
Possible
Recommended at scale

Build faster with Bittensor RPC endpoints

Use OnFinality's Bittensor RPC APIs to connect wallets, dApps, dashboards, bots, and backend services without operating your own node from day one.

Public endpoint testing

Start with the Bittensor public RPC endpoint for lightweight checks, prototypes, and quick integration tests.

Authenticated API access

Move production traffic to authenticated endpoints when you need clearer limits, analytics, and operational visibility.

Standard RPC methods

Query Bittensor blocks, transactions, balances, events, and chain state through HTTP and WebSocket workflows.

Operate Bittensor infrastructure with more control

Production teams need more than an endpoint URL. They need observability, predictable capacity, and a path from shared RPC access to isolated infrastructure.

Request visibility

Track usage patterns and response activity so your team can understand traffic growth before it becomes an incident.

Dedicated node path

Use dedicated Bittensor nodes when your workload needs isolated resources, custom operations, or stronger capacity planning.

Archive and historical data

Plan for archive access when analytics, audits, indexers, or advanced app features need older Bittensor state.

Choose the right Bittensor RPC setup

Different Bittensor products need different infrastructure. OnFinality gives teams a practical path from public RPC testing to production-grade API and node operations.

For prototypes

Use public RPC for simple reads, connection checks, and early experiments where strict performance guarantees are not required.

For live apps

Use authenticated API endpoints when users depend on stable request handling, monitoring, and scalable access.

For heavy workloads

Use dedicated nodes for sustained traffic, latency-sensitive services, validator tooling, exchange systems, and indexing pipelines.

Never Worry about Infrastructure Again

OnFinality takes away the heavy lifting of DevOps so you can build smarter and faster.

Get Started