# 24-Hour Developer Scanner

### Scanner Description

**Scanner** allows you to find token developers added to the database within the last 24 hours at the time of the request, with search available by **Twitter community**, **individual tweets**, or **developer address**. It also supports additional filters such as **Mcap**, **Fee**, and **match percentage**, allowing you to get the most relevant and high-quality selection for further analysis.

#### To open the **24-hour developer collection** section, click the icon in the top-right corner

<div data-with-frame="true"><figure><img src="/files/Z4QuGpCRErgnq3k6nh5q" alt=""><figcaption></figcaption></figure></div>

### Main Filters

<div data-with-frame="true"><figure><img src="/files/i4x4UgU0C43X6oQiPtGa" alt=""><figcaption></figcaption></figure></div>

1. **Mcap From / To**

**Mcap** — the token’s market capitalization.\
If you set the Mcap range from **$5,000 to $30,000**, the system will display developers whose tokens fall within that market cap range over the last 24 hours.

2. **Fee From**

**Fee** — the total amount of Solana network fees paid by users while trading a token.\
This filter allows you to find token developers by **Fee**, starting from a specified minimum value. For example, if you set **Fee from 2**, the system will display token developers whose tokens have generated a fee of **2 or more**.

3. **Search by Community, Tweets, or Developer Address**

This parameter defines the token’s association type and allows you to search by **Twitter community**, **individual tweets**, or **developer address**.

4. **Match Percentage**

* If the user does not specify a match percentage (or sets it to **100%**)

The filter works as a strict rule: a developer will only be shown if **100% of their tokens created within the day** match both conditions (**Mcap** and **Fee**).

* If the user sets the match percentage to **70%**

The rule works as follows a developer will be shown if the share of tokens that fully match both conditions (**Mcap** and **Fee**) is **70% or more** of all tokens they created within the last 24 hours.

**User conditions:**

* Mcap: $3,000–$10,000
* Fee: from 4 SOL
* Match percentage: 70%

**The developer created 5 tokens:**

| Token | Mcap  | Fee     | Matches                                                |
| ----- | ----- | ------- | ------------------------------------------------------ |
| 1     | 4000$ | 5 SOL   | Yes, Mcap is within the selected range, and Fee is ≥ 4 |
| 2     | 2000$ | 6 SOL   | No, Mcap is below $3,000                               |
| 3     | 5000$ | 4 SOL   | Yes, Mcap is within the selected range, and Fee is ≥ 4 |
| 4     | 9500$ | 3.5 SOL | No, Fee is 3.5, which is below 4                       |
| 5     | 8000$ | 10 SOL  | Yes, Mcap is within the selected range, and Fee is ≥ 4 |

**Conclusion**

* Matching tokens: **1, 3, 5**
* Match percentage: **60%**
* Since **60% < 70%**, the developer **will not be shown in the table**.

**Note:**\
A token will only be displayed if it meets both the **Mcap** and **Fee** conditions at the same time. If a token matches the **Mcap** condition but does not meet the **Fee** condition, it will not be shown — and vice versa.

### **Working with the Table**

In the developers table, you can sort results by the selected parameters. In this example, the table is sorted by **Mcap**, so developers with the highest market capitalization appear at the top of the list. This makes it easier to quickly identify the strongest and highest-priority options for further analysis.

<div data-with-frame="true"><figure><img src="/files/AHYWQZNgmIjzGPt3p7sa" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: 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:

```
GET https://docs.swoop.fun/swoop-pro/24-hour-developer-scanner.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.