# Proposal: Subgraph Finder - AI-Powered Discovery Tool for Graph Explorer

**URL:** <https://forum.thegraph.com/t/proposal-subgraph-finder-ai-powered-discovery-tool-for-graph-explorer/6500>\
**Category:** Questions & Feedback\
**Tags:** subgraph-devs\
**Created:** [March 30, 2025, 10:53pm UTC](https://forum.thegraph.com/t/proposal-subgraph-finder-ai-powered-discovery-tool-for-graph-explorer/6500 "2025-03-30T22:53:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaulieB](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/paulieb/32/2006_2.png) [@PaulieB](https://forum.thegraph.com/u/PaulieB)\
**Post date:** [March 30, 2025, 10:53pm UTC](https://forum.thegraph.com/t/proposal-subgraph-finder-ai-powered-discovery-tool-for-graph-explorer/6500/1 "2025-03-30T22:53:21Z")

</div>

Hey Graph Community,

As The Graph grows with more subgraphs being deployed, it’s becoming harder for users—especially newcomers—to find the right subgraph for their data needs or determine if they need to build one. I’d like to propose a feature to improve discoverability and usability: **Subgraph Finder** , an AI-powered tool integrated into Graph Explorer.

_I don’t have the skillset to implement this myself, but wanted to suggest it in case it sparks interest._

**Here’s the idea:**

The Problem

With thousands of subgraphs across networks, users face friction:

- Finding a subgraph that indexes the contract or data they care about.

- Understanding what data a subgraph provides without diving into its schema.

- Deciding whether to use an existing subgraph or create a new one.

This slows onboarding and adoption, which we can fix with smarter tools.

The Solution: Subgraph Finder

A step-by-step tool in Graph Explorer to pinpoint subgraphs based on user needs:

1. Filter by Network

- Status: Already exists in Graph Explorer (e.g., Ethereum, Arbitrum).

- Action: Users select their network of interest.

1. Filter by Smart Contract

- Status: Feasible with existing tools like Mike from DataNexus’s subgraph (FMTUN6d7sY2bLnAmNEPJTqiU3iuQht6ZXurpBh71wbWR ), which searches manifests by contract address. I’ve built a dashboard using it here: [subgraph-search-by-contract.vercel.app](https://subgraph-search-by-contract.vercel.app/).

- Action: Users input a contract address (e.g., 0xd829c1d3649dbc3fd96d3d22500ef33a46daae46), and it returns matching subgraphs (e.g., Monadex).

1. Retrieve Schemas

- Status: Possible via the Graph Network Subgraph. Here’s a sample query:

graphql

```auto
query {
  subgraphDeployments(first: 5, where: { id_in: ["A3Np3RQbaBA6oKJgiwDJeo5T3zrYfGHPWFYayMwtNDum"] }) {
    id
    ipfsHash
    manifest {
      schema { schema }
      manifest
    }
    versions { subgraph { id owner { id } } }
  }
}

```

- Action: Fetches the schema.graphql contents (e.g., Monadex’s Pair, Token) for filtered subgraphs.

1. AI-Assisted Matching

- Status: New feature using an LLM (e.g., Grok or similar).

- Action:

```graphql

query {
  pairs(first: 10, orderBy: volumeUSD) {
    id
    volumeUSD
    reserveUSD
  }
}

```

**Or provide**

```
  * No Match: “No subgraph exists. Check [docs](https://thegraph.com/docs) to build one.”

```

Benefits

- Ease of Use: Simplifies subgraph discovery for all skill levels.

- Adoption: Lowers barriers, encouraging more dApp development.

- Scalability: Handles growing subgraph counts with AI efficiency.

Why It’s Feasible

- Builds on existing tools: Graph Explorer’s network filter, Mike’s subgraph, and the Graph Network Subgraph.

- My dashboard proves Step 2 works.

- The query in Step 3 already retrieves schemas (tested with Monadex).

- AI integration is the main lift—leverage tools like xAI’s Grok for schema parsing and query generation.

---

<div class="post-metadata">

**Author:** ![NSun](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/nsun/32/632_2.png) [@NSun](https://forum.thegraph.com/u/NSun)\
**Post date:** [April 1, 2025, 3:49am UTC](https://forum.thegraph.com/t/proposal-subgraph-finder-ai-powered-discovery-tool-for-graph-explorer/6500/2 "2025-04-01T03:49:53Z")

</div>

I really like this idea! The easier it is to onboard the better. Solving this problem would be a huge help on that front. Hopefully someone can build on what you’ve presented here!

---

<div class="post-metadata">

**Author:** ![PaulieB](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/paulieb/32/2006_2.png) [@PaulieB](https://forum.thegraph.com/u/PaulieB)\
**Post date:** [April 3, 2025, 1:41am UTC](https://forum.thegraph.com/t/proposal-subgraph-finder-ai-powered-discovery-tool-for-graph-explorer/6500/3 "2025-04-03T01:41:51Z")

</div>

I may have figure it out, but work in progress - [https://claude.ai/chat/7b3b9c69-9b1d-4c7b-9bf8-0046d0651af1](https://claude.ai/chat/7b3b9c69-9b1d-4c7b-9bf8-0046d0651af1)