> For the complete documentation index, see [llms.txt](https://docs.dexscreener.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexscreener.com/trending.md). # Trending How tokens trend on DEX Screener DEX Screener assigns every token on the platform a **Trending Score** - a snapshot of the token's buzz and market activity. This score is used to rank tokens on the trending screener and trending bar, showcasing the hottest pairs at any given time. While we keep the special blend of our algorithm close to our chest, here are some of the key metrics we take into account: ### Market Activity * **Volume** * **Liquidity** * **Transactions** * **Unique makers** * **Holders** ### Community Engagement * **Visitors** on the token's DEX Screener page, both on website and app * **Reactions:** how the community feels about the token 🚀 🔥 💩 🚩 ### Trust & Credibility * Tokens with **verified info** get a boost, especially those with [**Enhanced Token Info**](https://marketplace.dexscreener.com/product/token-info) * **Security audit:** we value tokens that are open-source and pass security checks with flying colors For projects keen on climbing the trending list, a **robust trading activity** and **community engagement on DEX Screener** are your tickets to the top! --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dexscreener.com/trending.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.