About this skill

The problem

The Graph has a large, inconsistent set of subgraphs. Agents that try to locate a data source often need a human to browse Studio, compare names, copy an API key, and inspect entity fields before running a query. This skill packages 15,500+ classified subgraphs into a local registry so agents can search by defi, nfts, dao, ethereum, arbitrum, or a natural-language goal and receive executable query URLs.

How it works

Core tools include:
- search_subgraphs: filter by domain, network, protocol type, entity type, or keyword;
- recommend_subgraph: match a goal like “find DEX trades on Arbitrum” to the best subgraphs;
- get_subgraph_detail: return classification, entities, reliability score, query_url_x402, and legacy URL;
- list_registry_stats: inspect registry coverage.

Results prioritize the x402 path: an agent posts a GraphQL query to query_url_x402, receives HTTP 402 with a payment manifest, completes roughly $0.01 USDC on Base via EIP-3009, and retries. No Studio key is required. A legacy API-key path is also included for existing integrations.

Boundaries

This skill fits “discover the right subgraph before querying” workflows and does not replace a GraphQL client. Querying uses a local SQLite registry; first run fetches a ~5MB registry.db and verifies SHA-256, refusing to start on mismatch. x402 use needs Base USDC in the signing wallet. If local HTTP/SSE is enabled, bind it only to trusted networks. Audit the source before autonomous-agent use.

Screenshots

Use Cases

Select an Arbitrum DEX trade-monitoring subgraph by searching a natural-language goal and inspecting entity fields.
Compare Base lending protocol data sources by domain, network, and reliability score, then retrieve query URLs.
Configure a DAO governance analysis tool by listing registry domains, filtering governance subgraphs, and getting x402 URLs.
Before writing a The Graph query, fetch subgraph entity schemas and query instructions to reduce manual Studio exploration.

Best For

Engineers building on-chain trade-data agents who need to choose DEX subgraphs and get executable query URLs.
Developers building DeFi monitoring tools who want to compare lending and DEX data sources by network and reliability.
AI agent developers integrating The Graph who need keyless subgraph discovery and x402 query instructions.
Backend engineers wiring Web3 data pipelines who need entity fields and query URLs without manual subgraph hunting.