> For the complete documentation index, see [llms.txt](https://docs.scalp-empire.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scalp-empire.com/fff-sniper/how-to-use-fff-sniper.md).

# How to use FFF Sniper

<img src="/files/a1221O5MHS93v3hn5H6W" alt="" class="gitbook-drawing">

<mark style="color:purple;">**1. Token details**</mark> - You can find here the usual information about tokens:\
\- Floor price;\
\- Listed tokens number;\
\- Holders - number of unique token holders.\
\- Volume, sales, listed and delisted information

<mark style="color:green;">**2. Live Floor Chart**</mark> - This chart regroups key information, similar with the one's in NFT Analytics & Sniping:\
\- current floor price;\
\- number of listed tokens;\
\- occuring sales.\
In addition, we've included the Sales candles which show the number of sales on the timeline.\
Combining all of them lets you understand what the current trend for the token and helps you identify opportunities for buying and selling.

<mark style="color:blue;">**3. Sales History**</mark>\
This will show every successful transaction for this token and details about price per token, quantity, transaction time, buyer and seller.\
Similar to NFTs available data, you can access older transactions by clicking History where you can find also the extended chart that contains all the data listed above.<img src="/files/yl8szyYvXXQv3BXkFfQn" alt="" data-size="original">

<mark style="color:orange;">**4. Buy & Auto-buy**</mark>\
Most important functionality to document here for FFF, for sure.\
How it works? Similar with NFTsSniping Auto buy but with few specifics.

{% hint style="warning" %}
First, the difference is that for tokens we don't have attributes or ranks and also that we can have multiple tokens available in the same sale (quantity >1).
{% endhint %}

Let's talk about two special use cases that you must keep in mind.

**1st use case:** you don't want to use the sniper, just use the simply buy button.\
For this you must always remember to fill the number of the tokens you want to buy in "Items to buy". If not, you'll buy just one.\
![](/files/sZhtx4pfp7RnHzgpbbN8)

The tool will highlight the listings that are compatible with your settings and deactivate the others. This thing you must keep in mind for the next use case too.

**2nd use case:** if you want to sweep the floor and the items you want to buy is larger than any maximum quantity listed, the sniper will buy from all the available ones, in the limit price you have setted (price per token).\ <img src="/files/CszolvKgxqdRQNyyka85" alt="" data-size="original">

Next steps are the usual ones, approve transaction in your wallet and verify if the transaction was succesfull and you have received your tokens.\
\
If you need help or you have recommendations for improving our documentation, please access our [**discord server**](https://discord.gg/scalpempire).


---

# 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.scalp-empire.com/fff-sniper/how-to-use-fff-sniper.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.
