> For the complete documentation index, see [llms.txt](https://docs.solscan.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solscan.io/browsing-the-site/solscan-knowledge-base/general/nft-dashboard/dashboard-overview/collections.md).

# Collections

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

### **Collections**

Collections listed in this tab are the ones that have the highest volumes within the last 24hr period. Here is some of the key info for each collection that you can see on this tab:

* Collection: name of the collection
* Item: number of items within the collection
* Holders: number of unique wallets holding at least 1 item from the collection
* Floor price: Lowest price of the NFT in this collection that is currently listed on market places
* Vol 24h: Trading volume within the last 24hr. The higher the volume (denominated in SOL) the higher the ranking of the collection in this tab.&#x20;
* Trade On: where users can find a secondary offer for an item on this collection.&#x20;


---

# 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.solscan.io/browsing-the-site/solscan-knowledge-base/general/nft-dashboard/dashboard-overview/collections.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.