> For the complete documentation index, see [llms.txt](https://docs.stargazer.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stargazer.sh/stargazer-platform/reading-the-data.md).

# Reading the Data

Stargazer shows two views per token: Chat and Data. Chat returns a natural-language summary written by AI. Data shows the structured breakdown: Distribution and Triggers.

#### Distribution

<figure><img src="/files/ZayqcAnkYHcC5GyoyqHx" alt="" width="375"><figcaption></figcaption></figure>

Distribution: who holds and trades the token:

* Organic: human users. From seasoned traders to retail and degens. Individual decisions.
* Bundled: wallets with coordination patterns. Farm clusters, bounded wallets. High share may indicate manufactured traction or legitimate multi-wallet strategies depending on context.
* Automated: bots. Arbitrage, DeFi ops, algorithmic strategies. Healthy markets need them. The signal is in the ratio to organic.
* dApps/CEX: infrastructure. DEX routers, bridges, protocols, exchange deposits.

Two metrics per category: Holders % (wallets) and Supply % (tokens held).

These four groups are aggregates: triggers and chat may reference subgroups (farm clusters, sybil clusters, deposit-like addresses), but the breakdown panel always rolls them up into the four.

<figure><img src="/files/5qKXAuiXdlAMTL08xJrS" alt="" width="375"><figcaption></figcaption></figure>

The top of the breakdown highlights two summary numbers: Organic Holders % and Bundled Supply % (share of supply concentrated in Bundled wallets). Read them together. High Organic Holders with low Bundled Supply is healthy: real users hold the float. High Organic Holders with high Bundled Supply means coordinated wallets control most of the supply behind a surface of organic activity. Manufactured traction or coordinated accumulation.

#### Triggers

<figure><img src="/files/EDEcJlCpBU7bXQiMgkT0" alt="" width="375"><figcaption></figcaption></figure>

Triggers fire on specific on-chain events: cluster activations, volume surges, flow asymmetries, rotation patterns. Each shows signal name, value, and current trends.

Price trends:

* Bearish: low organic demand. Automated activity dominates.
* Transition (Pre-Growth): organic activity returning. Direction forming, not confirmed.
* Bullish: organic participation expanding. Early positioners may begin taking profit.
* Exhaustion: highest signal density. Multiple groups repositioning. Behavioral structure shifting even if chart looks strong.
* Transition (Pre-Bearish): momentum fading. Organic declining, redistribution accelerating.

Each trend comes with a model confidence indicator (low / medium / high). Strong trends are backed by clear behavioral signals; weak trends reflect ambiguous data and should be treated with caution.

The top 10 triggers per day per token are sorted by relevance, so you can see the signals Stargazer AI bases its decisions on.

<figure><img src="/files/d94WHDZ4y93tGPWKrp9y" alt=""><figcaption></figcaption></figure>

Categories and triggers are inferred from on-chain behavior, so a few edge cases are worth knowing:&#x20;

* CEX/Deposits often captures staking contracts and vault-style deposit addresses used by dApps, including for tokens not listed on exchanges.&#x20;
* DeFi Bot can include advanced DeFi users running complex strategies manually.&#x20;
* For stablecoins and wrapped assets, payment and deposit addresses can appear in Bounded wallets or Farm Wallets.
* Trends reflect on-chain behavior and often lead price by hours or days, not match it intraday.&#x20;
* Transition(Pre-Growth) trend during flat or slightly declining price often means bullish flows are cushioning the drop. We recommend looking for 2+ days of confirmation before acting rather than relying on a single day's signal.


---

# 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:

```
GET https://docs.stargazer.sh/stargazer-platform/reading-the-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.