> For the complete documentation index, see [llms.txt](https://solsqueezer.gitbook.io/solsqueezer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solsqueezer.gitbook.io/solsqueezer/features/token-analysis.md).

# Token Analysis

This command will provide you with information about the format in which you need to send links for token analysis and the number of wallets you can analyze at once.

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

### /top command&#x20;

This will give you top traders, sniper, and holder of the token you given you can quickly analyze each as well with single click on analyze all button &#x20;

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

### /all command

If you add the command "all/" to the beginning of the token link, you will receive information about 1,000 wallets with a positive PnL. However, if you have a Pro tier subscription, you will receive a text document with all wallets with a positive PnL, which you can immediately analyze using /super\_batch.\
make sure that the token is atleast 2h old and you can send up to 5 CAs at a time there is an limit of 50 checks for base usesr an 100 for pro per day , this resets daily at UTC+00 time&#x20;

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

With both `/top` and `/all` commands you can analyse up to 5 token contracts in one call

### t/ command

This scans each and every transaction happened on the token sent by user , and gives both an comprehensive excel report as well as txt file of all the wallets interacted with that tokens no matter either profit or loss unlike all/ which only looks for profitable wallets&#x20;

<figure><img src="/files/HwzZW66GJktC9gcRuAJS" alt="" width="563"><figcaption></figcaption></figure>


---

# 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://solsqueezer.gitbook.io/solsqueezer/features/token-analysis.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.