> For the complete documentation index, see [llms.txt](https://docs.hashhunter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashhunter.ai/hash-hunter-terminal/token-analyzer.md).

# Token Analyzer

The analyzer is the most-used tab. It exists because reading a token in the trenches is not one piece of information — it's six or seven, weighted against each other.

#### How to use it

Paste a Solana contract address into the chat. That's it. Within a few seconds you get back a structured analysis with:

* **Meta classification** — what narrative this token sits inside (dog, AI agent, political, parody, infra, etc.) and how old it is
* **Market state** — price, market cap, liquidity, 24h volume, and whether the flow looks organic or artificial
* **Holder structure** — how many holders, how concentrated the top wallets are, what percent of supply is held by real users vs. liquidity pools, burn addresses, and the dev wallet
* **Vesting, burns & locks** — exactly how much supply is locked, how much is vested, how much is burned, and on what schedule
* **Security read** — mint authority, freeze authority, liquidity lock status
* **Social pull** — what's being said about this token on X, who's saying it, and whether the volume of chatter is organic or manufactured
* **Top X accounts mentioning it** — the biggest accounts that have actually posted about the token, their handles, and their follower counts — so you can see whether the narrative has real reach or is being whispered into an empty room
* **The play** — a direct call: **scalp**, **hold**, or **fade**. One word, no hedging, based on the full picture.

#### Example: walking through a real analysis

You paste a fresh CA, say a memecoin three hours old. The analyzer comes back with:

> 12,847 holders. top 10 real wallets hold 18.4%. biggest single wallet at 4.1%. dev wallet at 0.8%.
>
> 4.2% of supply burned. 11.6% sits in 3 liquidity pools. no vesting unlocks pending.
>
> all liquidity is locked. mint and freeze authorities are revoked — supply is fixed and no one can freeze your wallet.
>
> social pull is organic, \~340 unique mentions in last 6h, real wallets driving the chatter. top X accounts posting on this: @ansemf (290k followers) @0xMert\_ (180k followers) @cobratate (450k followers)
>
> meta: parody finance, riding the bank-collapse narrative.
>
> the play: **scalp**. clean structure, organic flow, but supply distribution is tight enough that any one of those top 10 wallets can swing it. take profit on the way up.

Compare that to manually opening five different sites, cross-checking holders against a known-snipers list, eye-balling the LP, opening the chart on a separate tab, and finally searching X for the ticker. That's the time the analyzer is buying you.

Beyond single-CA reads, the analyzer also tracks **upcoming ICOs and active narrative plays** — ask it what's launching this week, what narrative is heating up, or what cluster of tokens is moving as a theme, and it pulls a fresh read.

What you do with that read is up to you. Most of our users say it's the difference between catching a move at +30% and chasing it at +300%.


---

# 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.hashhunter.ai/hash-hunter-terminal/token-analyzer.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.