Methodology & scope
Metagraphed extends the native Bittensor metagraph with public-interface and health metadata. Unofficial — not a block explorer.
What this is
A builder-facing public registry and explorer for Bittensor subnets: APIs, OpenAPI schemas, docs, repos, dashboards, data artifacts, SSE streams, endpoint health, schema drift, freshness, source evidence, providers, and curation gaps. Adapted for the heterogeneous, app-layer shape of Bittensor subnets.
What this is not
- Not a block explorer, wallet app, validator dashboard, or operator console.
- Not an OpenTensor/Bittensor product. Unofficial registry only.
- 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
- 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).
Coverage levels
- 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.
Contributing
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.
API & artifacts
JSON Schema is canonical. OpenAPI and TypeScript clients are projections. Every public list and detail view is reachable via the API or as a static artifact.