> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/community/chiliz-chain-ecosystem/developer-tools/the-graph.md).

# The Graph

The Graph decentralized indexing protocol for Chiliz Chain: deploy subgraphs to query Fan Token transfers, governance votes, and on-chain events via GraphQL.

## What is The Graph?

The Graph is a decentralized protocol that helps developers efficiently access and organize blockchain data. Think of it as a search engine for blockchains: it makes it easy to find and use specific data, like tracking Fan Token transfers or viewing voting results, without having to manually go through the entire blockchain.

## What this means to you

Instead of writing complex code to pull data, developers can use serverless APIs called subgraphs to access just the information they need using only GraphQL queries. This makes creating dashboards, voting platforms, and NFT galleries faster, simpler, and more reliable.

These subgraphs are also:

* Fully customizable.
* Maintained by a network of decentralized indexers, providing better speed & redundancy than a centralized service.
* Supported by on-call engineers on [The Graph's Discord](https://discord.gg/graphprotocol) 24/7.

### See The Graph in action on Chiliz

Here's a full walkthrough of how to build and query a subgraph using PSG Token as an example:

{% content-ref url="/pages/yagAScZC7PvbRGhHVTQS" %}
[Follow transfers of a Fan Token](/develop/advanced/follow-transfers-of-a-fan-token.md)
{% endcontent-ref %}

### Additional Resources

You can visit [The Graph’s official docs](https://thegraph.com/docs/en/) to explore how to build more advanced and optimized subgraphs.

{% embed url="<https://thegraph.com/docs/en/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chiliz.com/community/chiliz-chain-ecosystem/developer-tools/the-graph.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.