Methodology & scope

An unofficial, public explorer and integration registry for Bittensor. The explorer reads chain-direct data — blocks, subnets, validators, and accounts — with endpoint health, schema drift, and freshness. The registry maps every public interface a subnet exposes — APIs, OpenAPI schemas, docs, repos, SSE streams, data artifacts, and providers — with source evidence and the curation gaps still to fill. Everything is machine-readable, served over REST, GraphQL, and MCP for developers and AI agents alike.

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

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 (e.g. SN7, SN74).

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.

Corrections, new candidate leads, and maintainer review happen through the public repository. There is no in-app submission flow — registry truth lives in version control, reviewed in the open.

JSON Schema is canonical; OpenAPI and the typed clients are projections of it. Every public list and detail view is reachable over REST, GraphQL, and MCP — or as a static JSON artifact — so a human, a script, or an agent all read the same data.