JSONbored/metagraphed

JSONbored

TypeScript11updated 3d ago

Bittensor didn't ship with a map. We drew one — chain-direct block explorer, developer registry, and an agent toolkit built right in.

ClaudeCodexCursorMCP

agent-skillsbittensorbittensor-clibittensor-docsbittensor-metagraphbittensor-subnetbittensor-subnetsblock-explorerendpoint-monitoringmcpmcp-servermetagraph

View on GitHub

README

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.

</div>

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 `stream