> For the complete documentation index, see [llms.txt](https://docs.hashhunter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashhunter.ai/hash-hunter-terminal/x-engagement-tracker.md). # X Engagement Tracker Most "trending" lists on crypto Twitter are gameable. A paid raid, a coordinated thread, a bot farm pushing replies — all of it shows up as engagement, none of it means anything for whether a token actually has demand. The engagement tracker is built around organic signal. It scans X for mentions of Solana tokens, ranks them by engagement velocity, and **filters out the obvious manufactured patterns** — raid bots, low-quality reply networks, brand-new accounts spamming the same ticker. What's left is the signal you actually want: tokens that real wallets and real accounts are talking about, in volumes that don't match the patterns of a bought campaign. #### How to read it Each row in the tracker shows: * The ticker and contract * Engagement count over the recent window * A trend indicator — is the engagement climbing, peaked, or already decaying * Time since the engagement started — useful for catching the early move vs. the late chase #### What's useful about it The biggest win from the tracker isn't seeing the top of the list. The top of the list is everyone — by the time something is #1, it's been pumping for hours. The real edge is three or four rows down: a token climbing fast but not yet visible to everyone else. That's the window most traders never see, and it's the window the tracker is built around. --- # 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.hashhunter.ai/hash-hunter-terminal/x-engagement-tracker.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.