> For the complete documentation index, see [llms.txt](https://docs.scoutradar.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scoutradar.xyz/scouts-and-scout-sets.md). # Scouts and scout sets ## Scouts A **scout** is a wallet we track because of how it behaves across the whole chain: how early and how consistently it finds the tokens that move, over thousands of tokens, not over one lucky trade. Scouts are **not** picked by profit. Profit rankings are dominated by luck, insiders and wallets nobody can follow; a scout set is built to be followable. When a scout buys a token, that is a **signal**. The board shows the token from the first scout buy onward and counts every further scout that joins. ## Crews Several wallets are often run by one person. Scout Radar groups such wallets into a **crew** and counts the crew once. So a card that says `6 scouts · 2 crews` means six tracked wallets bought, but only two independent operators are behind them. **Crews is the honest measure of agreement**: more crews means more independent traders chose the same token. ## Scout sets Scouts come in **sets**. A set is a named group of wallets recomputed on a schedule from fresh chain data, so it follows the market instead of an old snapshot. Today the board runs one set, **Scouts v8**. More sets are coming — sets built for different styles (earlier entries, larger caps, longer holds) — and each lane will let you choose which set it listens to. The set a lane uses is the first field in its filters (**Scouts set**). The leaderboard has the same selector, so you can score any set the same way. ## Positions After the signal, Scout Radar keeps watching the scouts' wallets on-chain and shows whether they are still in the trade: * **In position** = the scout still holds at least 10% of what they bought. * **Out** = they sold or moved the tokens out. The scouts chip switches from `6 · 2` to `4/2 · 2` (four in, two out) once positions have been checked. When every scout has left, the card is dimmed, and one hour later Scout Radar stops polling that token's price. The card itself stays on the board until the 24-hour window closes, so you can still see what happened — or hide such cards with a filter (see [Filters and sorting](/filters-and-sorting.md)). --- # 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.scoutradar.xyz/scouts-and-scout-sets.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.