> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/trader-tools/token-analytics.md).

# 🧪 Token analytics

The **Analytics** tab on every token page is the 10-second due-diligence read-out:

* 👥 **Holder count** and **top-10 holder concentration** — how much of the supply sits with a few wallets.
* 🎨 **Creator holdings %** — how big the dev's bag is.
* ⚖️ **Buy/sell pressure** — counts and balance of recent flow.
* 📦 **Bundle flag** — detects clusters of buys at creation (multiple buys in the same block), the classic signature of a coordinated snipe.
* 🎓 **Graduation progress** — how far along the curve the token is.

{% hint style="warning" %}
🚩 High top-10 concentration + big creator bag + a bundle flag is the classic exit-liquidity setup. The data won't stop you — but it will make sure you knew.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fyuz.fun/trader-tools/token-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.