How do I mock the The Graph (GraphQL over subgraphs) API locally?

Install stunt, add a one-service block to stunt.yaml (adapter: embedded:thegraph-style), and run stunt up. You get a local, stateful stand-in for The Graph (GraphQL over subgraphs) 1.0 — 1 routes over rest — with no remote account, no network, and no bills.

Is the The Graph (GraphQL over subgraphs) mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of The Graph (GraphQL over subgraphs) (routes, status codes, pagination, webhooks), never real records.

← all adapters

thegraph-style

simulates The Graph (GraphQL over subgraphs) 1.0

restadapter v0.2.01 routes

verification

VMVM tier — no SDK suite yet· surface 1 · not implemented 3 · differs 2

use it

# add to stunt.yaml
services:
  thegraph:
    adapter: embedded:thegraph-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the The Graph (GraphQL over subgraphs) API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of The Graph (GraphQL over subgraphs). It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real The Graph (GraphQL over subgraphs) 1.0 surface — the data is fake, the behavior is real.

backing stores

poolstokensdomains

api surface (1)

generated from the adapter manifest — exactly what boots, nothing more

1 routes · graphql

GET/subgraphs/id/{subgraphId}/graphql

VM-verified behaviors (6)

✓pools collection arguments sort by volume and join token0/token1
✓where filters map the graph-node suffix operators
✓validation failures and the first cap surface as GraphQL errors
✓domains join owner/resolvedAddress; lookups miss as null
✓_meta reports the deployment head; Token.pools joins in reverse
✓the REST SDL surface is public and rejects unknown bearer keys

Not implemented (3)

No subgraph deployment/management surface; the two seeded ids are fixed
No indexing-status queries beyond _meta (no /status endpoint)
No GraphQL subscriptions over websockets; HTTP queries only

Differs from the real API (2)

One merged schema serves Uniswap and ENS entities; real Graph serves one per deployment
_meta.block.number advances per query; the real head is block-height driven

full scorecard →

want more of the The Graph (GraphQL over subgraphs) surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.