TL;DR: The Explorer is The Graph’s most public-facing data product, and it currently underdelivers on what The Graph’s own infrastructure makes possible. Rebuilding it on Amp would (1) give Edge & Node a permanent, public, production-grade reference customer for Amp enterprise sales, (2) make subgraphs discoverable to AI agents in a way the current Explorer cannot, and (3) finally surface the economic data: x402 vs. credit-card query mix, usage patterns, indexer performance, that the community has been asking for. The before/after would speak for itself.
The team that built The Graph, built Amp to perfect it! The Explorer could be where that story comes full circle.
The strategic case for E&N
Amp’s pitch to enterprises is that it’s the fastest, most verifiable, AI-ready blockchain data layer, 5.9× BigQuery, SOC 2-aligned, unified SQL/REST/GraphQL, integrated with Power BI, Snowflake, Datadog, and Grafana. Every enterprise pitch deck makes this claim. None of them currently point to a live, public, high-traffic production system that prospects can click through and explore for themselves.
The Explorer is that system, waiting to be unlocked. It already has:
- Real query traffic from thousands of subgraphs
- Multi-chain data (every network The Graph supports)
- A natural audience of technical decision-makers (the exact people E&N sells Amp to)
- Public visibility: it’s the front door of the protocol
Rebuilding the Explorer on Amp turns the front door of The Graph into a live demo of Amp. Every prospect in a sales conversation can be sent a URL. Every analyst writing about The Graph sees Amp’s capabilities firsthand. The dogfooding story writes itself: “The same database we sell to financial institutions powers The Graph’s own Explorer, processing real query traffic across every supported chain.”
This is the cheapest, highest-credibility marketing surface E&N has access to and it’s currently leaving it on the table.
The strategic case for The Graph
For a protocol whose entire value proposition is making blockchain data usable, the Explorer underrepresents what The Graph actually does. A community member or new builder lands there and sees a list of subgraphs with thin metadata. What they don’t see:
- What this subgraph is for. No sector classification (DeFi/NFT/DAO/gaming/RWA/social), no use-case tagging, no relationship mapping to the protocols it indexes.
- Who uses it and how. Query volume over time, user/dapp counts, geographic or chain distribution of demand, peak query patterns.
- How it’s paid for. With x402 live and credit-card query payments active, the community has zero visibility into the payment-rail mix. What % of query revenue is x402? What % is agentic vs. human? Which subgraphs are agent-heavy?
- How well it’s served. Indexer-level performance per subgraph: latency distributions, error rates, cost-per-query trends, which indexers are actually serving this thing well.
- How it relates to other subgraphs. Forks, derivations, schema similarity, version lineage.
This is the data Amp is built to surface. SQL over verifiable indexed state, with sub-second response on aggregations. The Explorer should be the showcase.
The agent-readiness angle
The agentic economy framing E&N has leaned into with ampersend, ERC-8004, and x402 has a discoverability problem the Explorer is uniquely positioned to solve. Right now, an agent trying to find the right subgraph for a task has no programmatic way to filter by sector, usage pattern, reliability, or schema shape. It has to crawl, guess, or rely on out-of-band registries.
An Amp-powered Explorer could expose:
- A structured, queryable catalog (sector, asset class, chain, schema fingerprint, reliability score)
- Usage-derived signals (which subgraphs serve which dapps, query volume, agentic-payment ratio as a proxy for agent readiness)
- A clean SQL/GraphQL interface that agents can query directly to plan routing decisions
This complements work happening at the routing layer (A2A, x402-monetized routers) rather than competing with it. Discovery and routing are different problems; the Explorer is the natural home for discovery.
I attempted this version in the interim to help agents GitHub - PaulieB14/subgraph-registry: Agent-friendly semantic classification of all 15K+ subgraphs on The Graph Network. Domain classification, protocol type detection, schema fingerprinting, and reliability scoring. · GitHub
What “before and after” looks like
Before: Subgraph list with name, signal, indexer count. Click in, see schema and a query playground. End of story.
After: Subgraph entry with sector tags, usage timeline, top-querying dapps, indexer leaderboard with latency and cost, x402 vs. CC payment split, related/forked subgraphs, schema fingerprint, agent-suitability indicators. Filterable, sortable, queryable via SQL endpoint for power users and agents.
A side-by-side screenshot in the launch announcement does more for Amp’s commercial pitch than a quarter of conference talks.
Acknowledging the lift
This is not a weekend project. Reasonable rough scope:
- Schema design for a denormalized analytics view of the protocol (subgraph metadata, query telemetry, payment events, indexer performance)
- Ingestion paths for query telemetry and payment data into Amp
- New Explorer frontend (or staged migration of the existing one) hitting Amp’s APIs
- Sector classification — partially manual (curator-driven), partially automated (schema/ABI heuristics, LLM-assisted)
- Privacy considerations around query telemetry (aggregate-only public views, opt-in granularity)
The ask
Few questions for E&N:
- Is there existing internal appetite for this? It would be unsurprising if some version of this is already on a roadmap somewhere. If so, this post is a community signal-boost.
- If not, what would it take to scope it?
- Would this be a possibility?
The Explorer is the most undervalued surface in the ecosystem right now. Amp is the most strategically important product E&N has launched. Putting them together is the rare proposal where the technical, marketing, and community-transparency wins all point the same direction.