Metagraphed

Every subnet, metagraphed.

The Bittensor subnet integration registry. For every subnet it answers: what does it expose (public APIs, docs, schemas), is it healthy, and how do I call it — machine-readable, for AI agents and developers alike.

What it is

The native Bittensor metagraph tells you what's happening at the protocol layer. Metagraphed adds the builder-facing layer it lacks — a registry of public subnet interfaces, endpoint health, and machine-readable schemas, built for integration developers (often reached through their AI agents) who need to discover and call subnet APIs.

Not an official OpenTensor/Bittensor project · not a replacement for the native metagraph · not an alpha/price dashboard · not a wallet, validator, or credential tool.

The web UI lives at metagraph.sh. The API is served from https://api.metagraph.sh (REST under /api/v1, artifacts under /metagraph).

Quickstart

Three ways to use Metagraphed. Pick one.

🤖 AI agent (MCP)

Agent-native, public, read-only, Streamable-HTTP. 14 tools to discover a subnet, check if it's up, and learn how to call it.

claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp

Cursor / other clients: add an MCP server with url https://api.metagraph.sh/mcp, transport streamable-http.

Tools: search_subnets · find_subnets_by_capability · get_subnet · get_subnet_health · list_subnet_apis · get_api_schema · get_fixture · get_agent_catalog · get_best_rpc_endpoint · registry_summary · semantic_search · ask · find_subnet_for_task · how_do_i_call

📦 Typed client

Generated from the OpenAPI contract, published with provenance.

npm i @jsonbored/metagraphed   # JS/TS
pip install metagraphed        # Python

🌐 REST

Stable JSON envelope { ok, data, meta, error }. OpenAPI at /metagraph/openapi.json.

curl https://api.metagraph.sh/api/v1/subnets

For agents

Resource	URL
Copyable agent prompt	`/agent.md`
Machine index	`/llms.txt`
Drop-in skill	`/skills/bittensor/SKILL.md`
Resources index	`/metagraph/agent-resources.json`

This repo

Cloudflare Worker API + Node build scripts. Schema-first: JSON Schema is the canonical contract → OpenAPI → types/clients. Artifacts are deterministic JSON; data refreshes on a schedule to R2/KV.

docs/              product + operating notes (start here)
registry/          subnet overlays, candidates, community submissions
schemas/           canonical JSON Schema components
scripts/           validation, generation, probe, safety
workers/           Cloudflare Worker API routes
public/metagraph/  compact generated artifacts + contracts
generated/         generated TypeScript types + client

Deeper docs: docs/api-stability.md (the /api/v1 contract), docs/submission-gate.md, docs/curation-playbook.md.

Contributing

Issues are labeled good first issue and help wanted — start there.

Schema-first edits require npm run build (regenerates openapi.json + types).
Community submissions are PR-first: touch exactly one registry/candidates/community/*.json file, no generated artifacts.

See CONTRIBUTING.md and docs/submission-gate.md.

Frontend — JSONbored/metagraphed-ui: the web app at metagraph.sh. Vite + React 19 + TanStack Start, deployed as a Cloudflare Worker. Holds no subnet data — it renders what this backend serves.

License

The backend (Cloudflare Worker + build pipeline) is AGPL-3.0. The published client SDKs are permissively licensed so you can embed them freely — packages/client (npm) and python/ (PyPI) are Apache-2.0.

metagraphed — Bittensor subnet operational registry