Multi-chain DeFi trading bots: Dexfy routes, fees, and limits
A current, source-linked summary of where Dexfy can execute, what a listed integration means, which costs remain separate, and when a route can still be unavailable.
Direct answer
Dexfy currently exposes production workflows across Binance Smart Chain, Ethereum, Robinhood Chain, and Solana, using the DEX integrations shown in its live documentation. A listed chain or DEX does not guarantee that every token pair or route is available: execution still depends on the selected adapter, pair, liquidity, chain state, enabled protections, and current product form.
Questions answered
- Which chains and DEX routes does Dexfy support?
- What does multi-chain trading-bot support actually mean?
- Which fees and live-route limits apply?
Current chain surface
The current product metadata lists Binance Smart Chain, Ethereum, Robinhood Chain, and Solana. The EVM chains share an account-and-transaction model, while Solana uses separate transaction, priority-fee, adapter, and router-program paths.
The relevant dashboard form is the final availability check before funding a wallet or enabling a live workflow.
Current DEX surface
Current production metadata includes integrations for PancakeSwap, SushiSwap, Uniswap, Raydium, Orca, Meteora, Pump.fun, Flap, and Four.meme. Exact versions and chain mappings are generated in the documentation from the same shared metadata used by the app and engine.
A listed DEX means Dexfy has a production adapter for the displayed version and configured chains. Route availability still depends on token pair, pool, liquidity, protocol behavior, and whether the enabled protection can be enforced.
Fees and third-party costs
The currently available Free plan applies Dexfy’s documented service fee to successful swaps. Network gas, validator fees, DEX fees, token taxes, slippage, price impact, and other third-party costs are separate and can materially change the outcome.
Pro and Premium remain planned tiers until the dashboard actually offers them. Do not treat a coming-soon plan as purchasable or active.
Common availability limits
- Unsupported chain, DEX version, pool, or token pair.
- Insufficient liquidity or an unavailable quote.
- A protection that cannot be proven or enforced.
- Insufficient native balance for transaction fees.
- Provider, chain, or protocol failure.
- Plan limits for wallets, actions, monitoring, or configurations.
Sources and evidence
Sources support the product facts and protocol mechanics above. They do not convert risk observations into guarantees.
- Dexfy: Supported chains
Generated current chain list and execution model.
- Dexfy: Supported DEXs
Generated current DEX/version list and route limitations.
- Dexfy: Service fee
Current service-fee behavior and separate third-party costs.
- Dexfy: Pricing and limits
Current Free plan and coming-soon plan status.
Continue learning
Check the workflow in Dexfy
Verify current chain, route, quote, liquidity, and protection availability in the live product before funding or enabling automation.