Methodology & scope

Source on GitHub

An unofficial, public explorer and integration registry for Bittensor — blocks, subnets, validators and accounts alongside the public interfaces each subnet exposes, every one of them machine-readable. unofficialnon-custodialopen source

Application subnets: Loading Application subnets
Adapter-backed: Loading Adapter-backed
Healthy surfaces: Loading Healthy surfaces
Avg freshness: Loading Avg freshness

Updated — · registry + probes ·

What this is. Two halves — an explorer over the chain, and a registry over what subnets publish.

The explorer reads chain-direct data — blocks, subnets, validators and accounts — with endpoint health, schema drift and freshness alongside it. The registry maps every public interface a subnet exposes: APIs, OpenAPI schemas, docs, repos, SSE streams, data artifacts and the providers behind them, each with the source evidence that proves it and the curation gaps still to fill.

Everything is served over REST, GraphQL and MCP, and published as static JSON artifacts, so a human, a script and an agent all read the same numbers.

registry truth lives in version control, reviewed in the open — there is no in-app submission flow

What this is not. Four claims worth making outright rather than leaving to inference.

Not an OpenTensor or Bittensor Foundation product — an independent, unofficial project.
Not a custodial wallet or exchange — your keys and funds never leave your own wallet, and any signing stays local.
No private keys, PATs, or token-gated data are ever requested or displayed.
Endpoint pool eligibility is metadata only — proxy routing is future-scoped.

Curation levels. How a subnet's overlay came to exist, from chain identity to a typed adapter.

Level	What it means
native	Sourced directly from the Bittensor chain.
candidate-discovered	Leads from public sources, not yet verified.
machine-verified	Reachable and shape-checked by automated probes.
maintainer-reviewed	A human reviewer accepted the overlay.
adapter-backed	A typed adapter publishes live metrics.

a subnet's level is the highest rung any of its surfaces has reached

Coverage levels. How far through that ladder a subnet has got.

Level	What it means
native-only	Chain identity present, no curated overlay yet.
manifested	Curated overlay with at least one public surface.
probed	Surfaces or endpoints actively probed for health and freshness.

counted per level on /health and in the coverage artifact

Interfaces. The same registry, four ways in.

Endpoints

REST: https://api.metagraph.sh/api/v1
GraphQL: https://api.metagraph.sh/api/v1/graphql
MCP: https://api.metagraph.sh/mcp
OpenAPI: https://api.metagraph.sh/api/v1/openapi.json
Artifacts: https://api.metagraph.sh/metagraph/

JSON Schema is canonical — OpenAPI and the typed clients are projections of it