Use AI to explore Bittensor
01Hand off context
Copy once, ingest once — everything an agent needs to start using metagraphed on its own.
Hand this to an agent and it can use metagraphed.
Paste-ready system prompt that turns any agent (Claude, Cursor, …) into a metagraphed-powered Bittensor integration agent.
02Connect your client
MCP is the fastest path — no install in the consuming project. The SDK, skill, and chat links below are alternates for hosts that can't speak MCP.
One CLI command, no config file to hand-edit.
claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp
pip install metagraphedPython · metagraphednpm i @jsonbored/metagraphedTypeScript · @jsonbored/metagraphedgh skill install JSONbored/metagraphed bittensorBittensor skillPaste-ready system prompt that turns any agent (Claude, Cursor, …) into a metagraphed-powered Bittensor integration agent.
03Query the registry live
Grounded answers and vector search over all 128 subnets — the same data the MCP's 204 tools and 2,292 callable services are built on. Run a real query below.
This calls the live HTTP API directly, over the network from your browser — it proves the registry is reachable and answering, not that a specific MCP client's handshake works. The response time shown is round-trip from here, not from an MCP session.
04Try your first prompt
Paste one straight into the client you just connected — each one is a real task, not a demo.
“Evaluate subnet 7 before I stake into it — health, economics, and stake concentration.”
A read on whether a subnet is healthy and how concentrated its stake is, before you commit.
“How is validator hotkey 5FHneW... doing? Current standing, 30-day trend, and who's staking to it.”
A validator's current standing and trend, plus its nominator breakdown.
“I need a subnet that does image generation over an HTTP API — find one and show me how to call it.”
A specific callable service matched to your task, with the actual request to make.
05Deeper integrations
Context files, the OpenAPI contract, GraphQL, bulk data, and everything else the registry exposes directly.
llms-full.txt
The full corpus concatenated into one file, for agents that ingest in bulk.
/llms-full.txtOpenAPI 3.1 contract
Every route, typed. Point any OpenAPI codegen at it for a typed client.
/metagraph/openapi.jsonAgent capability catalog
Every callable service in the registry, in one paginated list.
/api/v1/agent-catalogSemantic search
Vector search over subnets and surfaces — the REST form of Search above.
/api/v1/search/semantic?q=GraphQL (shaped registry queries)
Shaped queries over the registry instead of stitching multiple REST calls.
/api/v1/graphqlLive request/response fixtures
Real request/response pairs captured live, for writing tests against.
/api/v1/fixturesCross-network lineage
Cross-network lineage — which mainnet subnet a testnet one mirrors.
/api/v1/lineageBulk CSV datasets
The whole registry as flat CSV, for a notebook or a spreadsheet.
/datasets/index.json06Task-oriented playbooks
Executed, tested tool-call sequences for the tasks people actually bring — also registered as MCP prompts for harnesses that surface them natively.
Health, economics, and stake concentration before staking into it.
Current standing, 30-day trend, and who's staking to it.
A plain-language task to a callable subnet's base URL.
Reconstruct what one SS58 address has actually done on-chain.