> For the complete documentation index, see [llms.txt](https://docs.mevx.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mevx.io/docs/feature-ecosystem/afk-trade.md). # AFK Trade AFK Trade is an advanced, fully **automated trading execution module.** It allows users to set up pre-programmed trading strategies that monitor, filter, and execute trades Instead of sitting in front of charts 24/7, you can define systematic rules using a modular, node-based structure. Once deployed, the MevX execution engine runs tirelessly in the background to capture on-chain opportunities and manage your risk while you are safely AFK {% hint style="info" %} Try now: {% endhint %}

### 1. System Architecture & Node Configurations The AFK Trade system operates as a sequential pipeline, consists of different nodes. To set up your strategy, you can use the following nodes: #### 1.1. Trigger Node (If) The Trigger Node serves as the **automated ignition** switch for your AFK trading strategy. It is responsible for continuously monitoring real-time on-chain and off-chain data feeds, instantly dispatching an activation signal to kickstart the trading flow the exact moment your predefined conditions are met. **System Properties & Rules** * **Mandatory Component**: Every single flow must include a Trigger Node. It always functions as the absolute starting point of the pipeline. * **Multi-Trigger Logic ("OR" Condition)**: A single trading flow can be activated by one or multiple Triggers simultaneously using "OR" logic. If *any* of the selected triggers fire, the flow executes. * *Example 1:* A "Bonded Flow" is activated only when the Token Migrated event is triggered. * *Example 2:* An "Alpha Pulse Flow" can be activated when either the KOL Fomo event OR the X Call event is triggered. **Supported Trigger Events & Configurations**

Event Type	Description	Additional Configuration
Token deployed	Fires the exact second any new token is created on an integrated launchpad (e.g., Pump.fun).	None
Token migrated	Fires immediately when any token successfully completes its bonding curve and migrates to a primary AMM (e.g., Raydium).	None
MC milestone	Triggers when a token hits one or more specific Market Cap thresholds for the first time.	Reached: Input - Multi-Select (Define target MC milestones).
ATH	Fires the moment a token breaks its All-Time High (ATH) price or highest recorded Market Cap.	None
Price Shift	Triggers when a token experiences a sudden, drastic price fluctuation within a 5-minute interval.	Change: Input - Percentage (%) • Positive value: Price surge is $\ge$ user expectation. • Negative value: Price drop is $\le$ user expectation.
Volume Spike	Triggers when a token's trading volume grows sharply within a 5-minute window.	Increase: Input - Percentage (%) - Positive Only (Volume spike is $\ge$ user expectation).
Dex Ad	Fires when a token purchases a Paid Advertising package on DexScreener that matches your tracking criteria.	Package: Multi-select ($299, $699, $999, $1999, $3999, $6999).
Dex boost	Triggers when a project buys a score-boosting package on DexScreener to increase visibility.	Pack: Multi-select (10, 30, 50, 100, 500 score packs).
CTO	Triggers instantly when a token is officially marked as a Community Takeover (CTO) on DexScreener.	None
Pump Live	Fires the moment a token creator starts a live streaming session on Pump.fun.	None
Smart Money Buy	Triggers when any wallet from the curated Smart Money List buys a token.	Min amount: Input - Number (Fires only if transaction volume is $\ge$ Min amount).
KOL Fomo	Triggers when any tracked Influencer/KOL wallet executes a buy order on a token.	Min amount: Input - Number (Fires only if transaction volume is $\ge$ Min amount).
X Call	Scans X (Twitter) profiles in real-time. Triggers when a Contract Address (CA) or Liquidity Pool (LP) link is detected.	X Handle: Input - Text (Monitors custom Tweets, Retweets, Replies, or Bio Updates from specified handles).
TG Call	Scans selected Telegram alpha channels. Triggers instantly when a new message containing a CA/LP is detected.	TG Channel ID: Multi-select (Choose from available Telegram tracking channels).

#### 1.2. Filter Node (When) The Filter Node acts as a strict screening barrier that decides whether the automated trading flow should proceed to execution or terminate immediately. When a transaction pipeline enters this node, the system validates every single programmed parameter simultaneously: * All Conditions Met: The flow safely transitions to the next node in the sequence. * At Least One Condition Fails: The flow is forced to stop immediately, resetting the bot. **System Properties & Rules** * Optional Component: This node is non-mandatory. You can choose whether or not to include a Filter Node in your automated workflow. * Strict "AND" Logic: There is no limit to the number of safety criteria you can stack. However, when multiple filters are active, the system processes them using strict "AND" logic—every single checkbox and numerical range must return a true value to pass. **Supported Filter Fields & Criteria**

Field	Matching Logic & Description
Symbol	Contains: Token symbol contains specific keywords (Case-insensitive). Exact: Token symbol matches the keyword exactly (Case-insensitive).
Name	Contains: Token name contains specific keywords (Case-insensitive). Exact: Token name matches the keyword exactly (Case-insensitive).
Exchanges	Evaluates integrated Launchpads & DEXs on the current chain: • For Launchpads: Passes if the token was deployed on at least one selected launchpad (including migrated assets). • For DEXs: Passes if the liquidity was manually added or successfully migrated to at least one selected DEX.
Market Cap	Filters tokens based on their live Market Capitalization boundaries.
24h Volume	Filters based on the token's 24-hour trading volume.
Liquidity	Evaluates the total liquidity available in the pool.
Dev Buy	Tracks the initial buying volume or order sizing executed by the token deployer/developer.
Txs	Evaluates the total number of transaction counts within the market.
Holders	Filters based on the minimum or maximum total unique holding addresses.
Snipers	Tracks the absolute number of automated sniper bots that entered at block zero.
24h Bot Traders	Filters by the number of algorithmic bot addresses active over the last 24 hours.
Dev Holding	Restricts execution based on the percentage of supply still held by the developer's wallet.
Top 10 Holding	Measures token distribution safety by filtering the combined supply percentage owned by the Top 10 holders.
Sniper Holding	Filters out tokens where sniper wallets control an unsafe cumulative percentage of the supply.
Insider Holding	Screens assets based on the supply percentage allocated to identified insider/cabal wallets.
Bundler Holding	Evaluates the total supply cluster controlled by supply-bundling architectures.
Dev Bundler Holding	Tracks the explicit subset of bundled tokens tied directly to the developer profile.
Phishing Holding	Monitors and filters based on supply allocation trapped in known phishing or malicious draining nodes.
Has Dex Ad	Passes only if the token currently has an active, valid advertisement package running on DexScreener.
Has Dex boost	Passes only if the project currently has an active, valid score-boosting package running on DexScreener.
Has Community Takeover (CTO)	Passes only if the token has been officially verified and updated as a Community Takeover (CTO) project on DexScreener.

#### 1.3. Action Node (Then) The Action Node is the execution engine of your AFK trading strategy. Once a token successfully fires your predefined Triggers and safely clears your active Filters, this node takes over to execute live on-chain transactions instantly without requiring manual approval. **System Properties & Rules:** * Mandatory Component: Every single automated flow must include an Action Node to successfully deploy. * Multiple Actions ("AND" Logic): There is no limit to the number of executions you can stack within a single node. When multiple actions are configured, the system processes them sequentially using strict "AND" logic—meaning all specified actions will be carried out one after the other. **Supported Execution Actions & Configurations** **Buy Action** Instantly executes a market buy order for the specific token that triggered and passed through the active trading flow. Available Configurations: * Wallets: *Multi-select* (Choose one or multiple integrated wallets to deploy capital). * Amount: *Input - Number* (Specify the fixed amount of native currency, e.g., SOL, to spend per wallet). * Slippage: *Input - Number %* (Set the maximum price slippage percentage you are willing to tolerate). * Fees: *Input - Number* (Configure your custom Jito Tip and Priority Fees to ensure rapid block inclusion). * TP/SL (Optional): Attach standard Take Profit and Stop Loss price execution targets to this position. * Trailing SL (Optional): Attach a dynamic Trailing Stop Loss strategy with a fixed Trailing Delta to follow price rallies. **Sell Action** Instantly executes a market sell order for the token managed within the active trading flow. * Strict Operational Rule: A Sell Action must always be positioned chronologically *after* a valid Buy Action node within the pipeline. * Available Configurations: * Wallets: *Multi-select* (Choose which holding wallets will execute the liquidation). * Amount: *Input - Number %* (User inputs the sell size as a percentage, e.g., 50% or 100%. The system dynamically calculates the exact token amount based on the actual tokens successfully acquired in the immediate preceding Buy Action). * Slippage: *Input - Number %* (Set your maximum acceptable slippage tolerance for the exit). * Fees: *Input - Number* (Configure priority fees and Jito tips to outpace market congestion during liquidation). #### 1.4. Watcher Node The Watcher Node acts as a dynamic, conditional waiting room that enables advanced multi-branching logic within your trading pipeline. Unlike a Filter Node (which instantly decides whether to terminate or continue the flow), a Watcher Node temporarily pauses the execution stream. It continuously monitors live data feeds in the background until all preset conditions are fully satisfied before safely releasing the flow to the next node. **System Properties & Rules:** * Optional Component: This node is non-mandatory. You can choose whether or not to incorporate a Watcher Node into your workflow architecture. * Multi-Branching Execution ("OR" Logic Between Sets): You can configure multiple condition sets within a single Watcher. Each set splits the pipeline into independent, parallel sub-branches. Whichever condition set fully satisfies its criteria first will execute its respective branch immediately and cease monitoring for that specific path. Any remaining unsatisfied sets will continue to be tracked by the bot. * Intra-Set Validation ("AND" Logic Within a Set): If a specific condition set contains multiple individual rules, the system processes them using strict "AND" logic—meaning every single metric inside that specific set must be simultaneously true to trigger the branch. * Placement Rule: A Watcher Node can be inserted at any point in the workflow pipeline as long as it is positioned *after* the initial Trigger Node and terminates into a valid Action Nod **Supported Watcher Metrics & Conditions**


Market Cap (Above)	Input Number ($> 0$): Condition is satisfied the exact moment the token's live Market Cap breaks above your custom threshold.
Market Cap (Below)	Input Number ($> 0$): Condition is satisfied the exact moment the token's live Market Cap drops below your custom threshold.
Price Change	Input % ($> -100\%$): Condition is satisfied as soon as the token's cumulative percentage price shift expands past your custom target.
24h Vol	Input Number ($> 0$): Condition is satisfied when the token's trailing 24-hour trading volume exceeds your defined milestone.

``` ``` --- # 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: ``` GET https://docs.mevx.io/docs/feature-ecosystem/afk-trade.md?ask= ``` 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.