Skip to main content
Infrastructure

Endpoints

A load-balanced reverse proxy for Bittensor RPC, plus the registry of callable Subtensor and subnet endpoints behind it.

LiveLoad-balanced reverse proxyfinney · mainnet

One endpoint for Bittensor RPC

POST JSON-RPC to a single URL and Metagraphed routes it across the healthiest, most in-sync public endpoints — with failover, edge caching, and abuse controls. No key, no account, no single point of failure.

POSThttps://api.metagraph.sh/rpc/v1/finney
Try it
curl -s 'https://api.metagraph.sh/rpc/v1/finney' \
  -X POST -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"chain_getHeader","params":[]}'
  • Health-aware load balancing

    Requests fan out across the public endpoint pool, weighted by live probe health and score.

  • Block-height routing

    Nodes trailing the freshest reported tip are demoted behind synced peers, so reads hit current state.

  • Automatic failover

    A dead or transient upstream is retried against the next-best endpoint — transparent to the caller.

  • Edge caching

    Block-pinned reads (chain_getBlockHash/Block/Header) are cached at the edge for instant repeat hits.

  • Read-only + rate-limited

    Only safe read methods pass the allowlist; 100 requests/min per client keeps the pool healthy.

Proxy usage

Updated

Snapshot freshness unknown — verify before relying on this data.

Requests
4
7d
p50
0 ms
p95 0 ms
Success
0.0%
0 ok
Errors
100.0%
4 failed
Failover
0.0%
0 retried
Cache hits
0.0%
0 served
By networkfinney4
Endpoints
1597tracked
RPC pools
54 proxy
Archive-capable
4
Healthy
91%103/113 probed

Latency & severity heatmap

Latency heatmap · provider × kind
<150ms<400ms<1sslow/down

RPC pools

Snapshot from — may be lagging behind live.
PoolRegionMembersArchiveEligibility
finney-rpc5Pool
finney-wss4yesProxy
finney-archive4yesProxy
test-rpc2Proxy
test-wss2Proxy

Proxy-eligible members serve live traffic through the reverse proxy above; the proxy prefers in-sync, healthy nodes and fails over automatically.

Callable endpoints

188 of 188
URL
000subtensor-rpcopentensorOK694ms
000subtensor-rpcopentensorOK472ms
000subtensor-rpcnodiesUnknown
000subtensor-rpcopentensorOK1449ms
000subtensor-rpconfinalityOK597ms
000subtensor-wss
wss://bittensor-finney.api.onfinality.io/public-ws
onfinalityOK304ms
000subtensor-wss
wss://archive.chain.opentensor.ai:443
opentensorOK736ms
000subtensor-wss
wss://lite.chain.opentensor.ai:443
opentensorOK392ms
000subtensor-wss
wss://entrypoint-finney.opentensor.ai:443
opentensorOK209ms
001data-artifactmacrocosmosUnknown
002data-artifactinference-labsUnknown
003data-artifactone-covenantOK92ms
005data-artifacthoneOK410ms
006data-artifactnuminousOK457ms
007data-artifactallwaysOK63ms
007sseallwaysOK67ms
008data-artifactvantaOK288ms
009data-artifactmacrocosmosUnknown
010data-artifacttaofiUnknown
011data-artifacttrajectoryrlOK354ms
013data-artifactmacrocosmosOK138ms
014data-artifactcacheonOK128ms
015data-artifactoroUnknown
015data-artifactoroUnknown
015data-artifactoroUnknown
Page 1 of 8 · showing 25 of 188

Incidents timeline

Incidents · 24h
  • Host-24hnowlinks
  • endpoint-srf-2d3306d2cfa2223e
    1 ongoing1 total
  • endpoint-srf-3ffcb1a074d13547
    1 ongoing1 total
  • endpoint-srf-d6ad3703dbed701f
    1 ongoing1 total
  • endpoint-srf-dece284ea80ec36c
    1 ongoing1 total
  • endpoint-srf-6bf50fe9203db27c
    1 ongoing1 total
  • endpoint-srf-93a99fb7593a4bf5
    1 ongoing1 total
  • endpoint-srf-43db9970eda54936
    1 ongoing1 total
  • endpoint-srf-ee8180c137f9a543
    1 ongoing1 total
  • endpoint-srf-34a4ac83864d4ae7
    1 ongoing1 total
  • endpoint-srf-6acf119341034de8
    1 ongoing1 total
  • endpoint-srf-db88986ea3dcbe82
    1 ongoing1 total
  • endpoint-srf-d27e72d2681f9787
    1 ongoing1 total
  • endpoint-srf-731498de4723ad3c
    1 ongoing1 total
  • endpoint-srf-fc7e63cd7f0f1ca9
    1 ongoing1 total
  • endpoint-srf-c80a6fac708c791c
    1 ongoing1 total
  • endpoint-srf-b7903c0191b3c777
    1 ongoing1 total
  • endpoint-srf-196044ef4420d344
    1 ongoing1 total