The Graph provides blockchain data solutions for on-chain apps, AI agents & institutions. Follow for ecosystem updates, builder guides & what ships.

Based in United States
An AI agent needs three things to act on-chain: identity, awareness, and payment. The Graph powers two. Subgraphs and MCP turn unsearchable blocks into context an agent can read. x402 lets it pay per query, no API key. The stack beneath the agentic web:
Article

The Infrastructure Stack Behind Autonomous AI Agents in Web3

Millions of autonomous AI agents are coming to web3. They will book hotels, manage yield, and execute trades for the people who own them, all running in the background. It is tempting to picture an

16
23
152
12,884
In 2025, 15.2% of indexing rewards on The Graph went to Indexers serving little to no queries. The Rewards Eligibility Oracle changes that and it just went live. Same issuance, better allocation. Learn more below:
Article

A New Service Standard for Subgraph Indexing Rewards

Indexing rewards on The Graph Network used to be distributed by curation signal and allocated stake. Neither of those measures whether an Indexer served a single query. So a share of issuance every

3
22
119
18,114
Everything that shipped on The Graph in July, in one place. A managed sink service. Twelve new Substreams Skills. A new chain. A registry rebuilt around what the data is rather than who published it. Ten projects from ETHGlobal Lisbon.
Article

What Shipped in The Graph Ecosystem: July 2026

July was a Substreams month. A new sink service moved the hardest operational parts of a data pipeline off developers' machines, the registry was rebuilt around what the data is rather than who wrote

23
30
199
44,500
"Verifiable" spans spot-checkable transparency, 1-of-N trust models, consensus, and cryptographic proof — very different paradigms. This post maps them and shows how The Graph (Subgraphs, Substreams, Amp) makes extraction and queries verifiable onchain.
Article

What "Verifiable" Actually Means for Blockchain Data

In April 2026, attackers manipulated the RPC infrastructure feeding a verification layer tied to KelpDAO. The blockchain's cryptography held up fine. The data pipeline did not. The result was a loss

9
14
84
39,187