> For the complete documentation index, see [llms.txt](https://docs.tallyprotocol.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tallyprotocol.xyz/product-modules/radar-and-flow.md). # Radar and Flow ## Radar Radar grades every token A to F with a reason for every deduction. See [Integrity grades](/concepts/integrity-grades.md). The Radar page shows the grade, the "vs US price" premium, the share multiplier and any flags (unit trap, ghost, paused), and links to how a grade is made. ## Flow Flow answers "who is actually trading this token?". For each token, a collector gathers recent trades and classifies them: bot wallets and router hops are removed to leave **cleaned flow**. A per-issuer panel then shows, for the last hour, 24 hours and 7 days: net shares, buys and sells, the last real trade and the concentration of the top ten holders excluding custody. Large trades are listed. * **Trade source:** Binance's trade history first, then chain logs as a fallback. The panel says which it used. * **Windows are honest.** A window shows only when the history covers it. Otherwise it says "History still building". * **Radar's cleaned grade** can differ from the quote page's raw grade on purpose. ## What is hard about it The history is the hard part. The collector reads trades 100 at a time from a rate-limited API for hundreds of tokens, and expects each poll's newest page to overlap the previous poll. On busy tokens, or after a gap, it does not, so the window cannot be called complete. Making all three windows available all the time is a [milestone](/reference/roadmap.md), not solved. ## How it is served Radar and Flow pages read two small snapshots per token (a summary and a ghost check) written by the `flow` worker every minute. They never decode the full trade tape on the request path. The first version did, about 300 to 450 MB of JSON per Radar load on a single thread, which froze the whole server for about 28 seconds. See [Challenges](/building-tally/challenges.md#a-radar-page-that-froze-the-whole-server). --- # 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.tallyprotocol.xyz/product-modules/radar-and-flow.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.