> 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/filters-and-sorting.md).

# Filters and sorting

![The lane filters panel: scout set, Signal, Token at signal, Now, Noise, sound](/files/A9eax5b7A1ygTC6tkQQO)

Open a lane's `Filters` panel. Every filter is optional; an empty field means "no bound". One rule applies everywhere: **a value that is unknown for a token never passes a filter**. If you set `Holders at signal ≥ 100` and a token has no holder count, that token is dropped, not waved through.

## Scouts set

Which set of scouts this lane listens to. One set today (Scouts v8); more are coming.

## Signal

These five describe the moment of the signal. They are also the filters the [Leaderboard](/leaderboard.md) can model, because every one of them is known at the time you would have acted.

| Filter                | Unit               | Meaning                                                                                |
| --------------------- | ------------------ | -------------------------------------------------------------------------------------- |
| **Scouts ≥**          | count              | At least this many tracked wallets bought.                                             |
| **Crews ≥**           | count              | At least this many independent operators bought.                                       |
| **⚡ Vol at signal ≥** | $                  | Volume traded in the minute of the first scout buy.                                    |
| **Age at signal**     | minutes, from – to | Token age when the first scout bought. `5 – 960` = between 5 minutes and 16 hours old. |
| **MC at signal**      | $, from – to       | Market cap at the first scout buy. A lower bound cuts sub-$10k noise.                  |

## Token at signal

A snapshot of the token as it was when the card fired. These are filters only — they never change when a card enters a lane.

| Filter                    | Unit  | Meaning                                                 |
| ------------------------- | ----- | ------------------------------------------------------- |
| **Holders at signal ≥**   | count | Holders at the signal.                                  |
| **Liquidity at signal ≥** | $     | Pool liquidity at the signal.                           |
| **Top10 at signal ≤**     | %     | Share of supply held by the top-10 holders. `20` = 20%. |
| **Dev at signal ≤**       | %     | Share held by the deployer.                             |

## Now

| Filter     | Unit         | Meaning                                                                                                                                 |
| ---------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| **MC now** | $, from – to | Market cap right now — the one live filter. A token drops out of the lane when its cap leaves the range and comes back when it returns. |

## Noise

Two switches that remove clutter without touching the signal logic:

* **Hide if all scouts left** — drops cards where every scout has sold or moved out (the dimmed cards). On a typical day this is about half the board. Tokens whose positions have not been checked yet stay.
* **Hide returns** — drops tokens that left the board and came back.

## Reset

`Reset` clears every filter of the lane, including the noise switches and the scout set. The lane's name, sort and sound stay. The recommended presets are not restored — set the values you want and `Apply`.

## Sorting

The `Sort` menu orders the lane. Every sort is descending, and ties are broken by the newest entry.

| Sort              | Orders by                                              |
| ----------------- | ------------------------------------------------------ |
| **Newest**        | The moment the card **entered this lane** (see below). |
| **Scouts**        | Number of scouts.                                      |
| **Crews**         | Number of crews.                                       |
| **Multiplier**    | Market cap now ÷ entry.                                |
| **Vol at signal** | Volume in the signal minute.                           |
| **MC now**        | Market cap now.                                        |

### What "Newest" means

A card enters a lane the moment the lane's filters **first hold** for it. For a lane without thresholds that is the moment the token arrived on the board. For a lane with `Scouts ≥ 10`, it is the moment the **10th scout bought** — even if the token had been on the board for hours with nine scouts. That card goes to the top, gets the green rail and the sound, because for this lane it is genuinely new.

Only the two count thresholds (Scouts ≥, Crews ≥) move that moment. The at-signal filters are fixed when the card fires, and `MC now` deliberately does not move it: a price drifting into a range is not an event worth a sound, and the card would flap in and out of the top.

This is different from the token's **age** (the `12m` / `2h` chip), which is time since the token was created on-chain.


---

# 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/filters-and-sorting.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.
