Data Services
The catalogue of data services on Graph Horizon — every service follows the same TAP v2 / GraphTally payment pattern. The signal that matters most is whether anyone is actually serving paid queries.
Services tracked
9
across 4 maturity tiers
Live on Arbitrum One
3
Subgraph · Seahorn · Dispatch
With active providersOnly the Subgraph Service has a substantial active indexer set serving paid queries. Every other service has zero active providers.
1
Subgraph Service only
Tier 1Production
Live on Arbitrum One and in active paid use.Subgraph Service
GIP-0068graphprotocol
The first and only widely-used data service — subgraph indexing and GraphQL query-serving.
Tier 2Mainnet-deployed, unexercised
Contract live on Arbitrum One, but no completed paid-query loop yet.Dispatch
GRC-005cargopete
Decentralized JSON-RPC / dRPC data service — stake, register a chain, get paid per request.
Seahorn
GRC-008lodestar-team
A Solana structured-data service — the "missing third lane" alongside Subgraphs and Substreams.
Tier 3Testnet / in development
Working code on a testnet or local devenv; mainnet not yet targeted.Substreams Data Service
graphprotocol
Payment infrastructure for Substreams — the "second data service being built on the network".
Mainline (Firehose)
GRC-006PaulieB14 · GRC by cargopete
A decentralized Firehose data service — raw, fork-aware, cursor-resumable block streams over gRPC.
Compass
GRC-007lodestar-team
A decentralized Subgraph-MCP gateway — every subgraph becomes a pay-per-call MCP tool for AI agents.
camp-data-service
lodestar-team
Monetizes a self-hosted camp instance — pay per request in GRT for decoded Arbitrum One data.
Tier 4Local reference / demo
Pedagogical scaffolds — exercise the payment lifecycle on a local chain.Vince Data Service
lodestar-team · cargopete
A whimsical-but-functional service "for locating individuals named Vince, worldwide".
Hello Data Service
lodestar-team · cargopete
A minimal (~120-line) working Horizon data service reference — the simplest of the set.
Curated research · reviewed 2026-05-31 · provider counts and addresses are point-in-time snapshots — verify on-chain before relying on them.