> 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/collection-analytics-and-sniping-page/3.-volume-and-24h-volume.md).
# 3. Volume and 24h Volume
This is the first indicator that will help you notice if there’s active trading done on this collection. Avoid low volatility collections while Scalping.
Fees - You need to pay attention to fees, as this is what will be taken out from a sell you are making. For example, selling at 4 SOL with 10% fees will result in a 3.6 SOL profit. Buying above 3.6 and selling at 4 is a **loss**.
Profit/loss - **PnL** information. For each NFT there is a list of sales. We compare each sale to the previous (or the mint price if it's the first sale) and calculate a profit or loss. For example, you bought it yesterday at 5 SOL and sold it today at 8 SOL. You generated **3 SOL profit** (minus the royalties and ME fee that we also take into account, we're not including them in the example to keep the math simple). Someone else then sells it tomorrow for 7 SOL, generating a **1 SOL loss** on the sale. We sum all those profits and that's the new stat that would be 2 SOL in this example.\
Sales speed is calculated based on the activity of the last 15 minutes.
---
# 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/collection-analytics-and-sniping-page/3.-volume-and-24h-volume.md?ask=&goal=
```
`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.