Setup and Launch
A step-by-step breakdown of all features — from selecting the wallet for purchases and configuring fees to setting up filters and lists.
How to Access the Auto Buy Feature
1. Open the Telegram bot and click “🌖 Swoop Pro.”
2. Select “⚡ Go to Auto Buy.”
3. Log in to Swoop using your Telegram account.
4. Click the settings gear icon in the top-right corner, then select the “Auto Buy” section.
Auto Buy Indicators and Status Labels
🔴 When the Indicator Is Red
To make working with Auto Buy clearer and safer, we implemented a status indicator system. These indicators allow you to quickly see whether Auto Buy is currently active or disabled.
If the AB indicator is red, it means that the Auto Buy feature is turned off and no purchases will be executed.
The indicator appears in two places:
in the Settings menu next to the Auto Buy tab
in the top header next to the settings icon
🟢 When the Indicator Is Green
If the AB indicator is green, it means that the Auto Buy feature is active and running.
In this state, Auto Buy is ready to automatically execute purchases according to your configured settings.
The indicator is also displayed in two places:
in the Settings menu next to the Auto Buy tab
in the top header next to the settings icon
Labels
When Auto Buy is triggered, a corresponding label appears on the token card.
When you hover over the heart icon, a note from the Whitelist added for that developer will be displayed.
Auto Buy Setup for Tokens With a Community
Community Filter Settings
To enable Auto Buy for tokens with an attached community, turn on “Enable Auto Buy for Community.”
Wallet Settings
In this section, you select the wallet from which Auto Buy will execute token purchases. If you are not familiar with how to create or use a wallet, please refer to the guide here.
Purchase Parameters
In this section, you define the main parameters that Auto Buy will use when purchasing tokens.
Here you can specify:
Buy Amount — the amount of SOL that will be used to purchase the token
Slippage — the acceptable price deviation during transaction execution
Priority Fee — an additional Solana network fee used to speed up the transaction
Bribe — an additional incentive paid to validators to increase the chance of your transaction being included in a block
Anti-MEV — protection against MEV bots targeting your transaction
Developer Filters for Community Tokens
In this section, you can configure additional filters for communities where tokens appear.
You can:
skip communities if the number of subscribers exceeds a specified value
skip tokens if their total supply is below a defined threshold
These parameters help filter out unwanted or suspicious tokens, allowing Auto Buy to operate more accurately and safely.
⚠️ Important: The parameter “Total Tokens Greater Than” has priority over the AM, MM, and AF filters.
If a developer does not meet this requirement, the transaction will not be executed, even if all other parameters meet the conditions.
Developer Metrics
In this section, you can set minimum values for developer metrics calculated from their previous token launches. This helps evaluate the developer’s experience and performance before Auto Buy reacts to a new token.
Parameters:
AM (Average Market Cap) — the average market capitalization of the developer’s previous tokens. This metric shows the typical market cap level reached by their projects. If the value is below the specified threshold, the token will be ignored.
MM (Median Market Cap) — the median market capitalization of the developer’s tokens. The median represents the “typical” market cap and is less affected by rare large pumps. This metric helps assess the real performance level of a developer’s projects without distortion from outliers.
AF (Average Fee) — the average total fees traders paid when trading the developer’s tokens. This metric reflects overall trading interest and activity around the developer’s previous projects.
⚠️ Combine Option
The “Combine” option enforces all three filters simultaneously. In this mode, a developer must meet AM, MM, and AF requirements, otherwise the token will not be purchased.
Working With Developer Lists
In this section, you configure how Auto Buy interacts with developers included in the Whitelist and Blacklist.
Buy if Admin Is in Whitelist If a developer is included in the Whitelist, Auto Buy can purchase their tokens according to your configured settings.
Skip Community Tokens From Blacklisted Admins If a developer is included in the Blacklist, tokens appearing in communities managed by that developer will be automatically ignored.
These settings allow you to manage previously identified developers and control how Auto Buy interacts with their tokens.
⚠️ Don’t forget to click “Save.”
Auto Buy Setup for Tokens With a Tweet
By default, Auto Buy only purchases tokens where the tweet was attached first.
Tweet Filter Settings
To enable Auto Buy for tokens with an attached tweet, turn on “Enable Auto Buy for Tweets.”
Wallet Settings
In this section, you select the wallet from which Auto Buy will execute token purchases. If you are not familiar with how to create or use a wallet, please refer to the guide here.
Purchase Parameters
In this section, you define the main parameters that Auto Buy will use when purchasing tokens.
Here you can specify:
Buy Amount — the amount of SOL that will be used to purchase the token
Slippage — the acceptable price deviation during transaction execution
Priority Fee — an additional Solana network fee used to speed up the transaction
Bribe — an additional incentive paid to validators to increase the chance of your transaction being included in a block
Anti-MEV — protection against MEV bots targeting your transaction
Developer Filters for Tweets
In this section, you can configure additional conditions for how Auto Buy interacts with tokens that appear in tweets.
Tweet Age Less Than (minutes) — allows Auto Buy to react only to recent tweets. The system will only consider tweets published within the specified number of minutes.
Total Tokens Greater Than — limits the number of tokens created by the tweet author. If the author has launched fewer tokens than the value specified in this parameter, their new tokens will be ignored.
These filters help ensure that Auto Buy works only with relevant tweets and reduce interaction with authors who launch an excessive number of tokens.
Developer Metrics
In this section, you can set minimum values for developer metrics calculated from their previous token launches. This helps evaluate the developer’s experience and performance before Auto Buy reacts to a new token.
Parameters:
AM (Average Market Cap) — the average market capitalization of the developer’s previous tokens. This metric shows the typical market cap level reached by their projects. If the value is below the specified threshold, the token will be ignored.
MM (Median Market Cap) — the median market capitalization of the developer’s tokens. The median represents the “typical” market cap and is less affected by rare large pumps. This metric helps assess the real performance level of a developer’s projects without distortion from outliers.
AF (Average Fee) — the average total fees traders paid when trading the developer’s tokens. This metric reflects overall trading interest and activity around the developer’s previous projects.
⚠️ Combine Option
The “Combine” option enforces all three filters simultaneously. In this mode, a developer must meet AM, MM, and AF requirements, otherwise the token will not be purchased.
Working With Developer Lists
In this section, you configure how Auto Buy interacts with developers included in the Whitelist and Blacklist.
Buy if Admin Is in Whitelist If a developer is included in the Whitelist, Auto Buy can purchase their tokens according to your configured settings.
Skip Community Tokens From Blacklisted Admins If a developer is included in the Blacklist, tokens appearing in communities managed by that developer will be automatically ignored.
These settings allow you to manage previously identified developers and control how Auto Buy interacts with their tokens.
Auto Buy Setup With Whitelist / Blacklist
In addition to filters, Auto Buy can also be configured using developer Whitelists and Blacklists.
Whitelist allows you to add developers whose projects you consider reliable or profitable. If a developer is included in the Whitelist, Auto Buy can react to their tokens even if some filters are not met.
Blacklist allows you to exclude developers whose projects you do not want to interact with. If a developer is included in the Blacklist, their tokens will be ignored by Auto Buy, even if they meet all configured filters.
Using these lists helps you manage Auto Buy more flexibly — prioritizing trusted developers while excluding unwanted projects.
You can also disable all filters and operate exclusively using Whitelists.
Last updated