Automate swapping your tokens 24/7 using sell settings that you control.
Tell DEXbot when and how to swap tokens through the secure client application.
Maintain token health with our user queue system that supports hundreds of users on each token.
Never miss out on taking profits during a late night bull run again by automating swaps.
It’s not always a great idea to wait until ‘the price goes a bit higher’ before taking your initial risk or additional profits out on a new crypto project. The price can take a downward turn, and leave you kicking yourself and questioning what if you sold small amounts sooner. DEXbot solves the issue of when and how to sell, and does it 24/7. You can configure settings like minimum time between sells, max sell amount in a swap and minimum sell price per token. DEXbot then runs autonomously and securely makes those swaps for you, which takes away the need to anxiously look at charts all day. Most importantly, the DEXbot Client application takes measures to ensure your private key and seed phrase are kept safely in your control. The Client source code is completely transparent and open source.
If you want to only sell token reflections, we got you covered. If you are on a token team and need to sell tokens from a marketing/dev wallet, DEXbot does it while keeping the token price healthy. Whales no longer have to idly sit by while watching their HODL’d tokens go down in value. With DEXbot, token holders can sit back and relax while DEXbot does the legwork.
DEXbot’s pricing is based on overall swap volume, so you can use DEXbot as much or infrequently as you would like without feeling locked in.
6,315
Currently Supported Token Pairs
$748,435,314
Daily Volume On Supported Blockchains
100%
Support For Cold Wallet Addresses
We know that manually making trades isn’t ideal, but neither is putting your private key or seed phrase into an unknown program. We break down that barrier by publicly releasing the codebase of our client application so you can see exactly how it works and what data it actually sends/receives. DEXbot never stores, retrieves, sends, logs, or shares the private key in any capacity, at any point. The private key is completely local to your machine, is only used when signing transactions, and is destroyed after the program is exited.
Every official release of the Client application has an official checksum to ensure that the code you run is verified so you can go to sleep knowing your tokens are SAFU.
Tune in for roadmap updates, improvements, or other DEXbot news by connecting with us on our socials. Get support and chat with others who also use DEXbot by joining our Community Discord server. Follow our Twitter to get critical updates, improvements, or release information.
Disclaimer: It is critical that you ensure the use of an authentic version of DEXbot before entering any login credentials or private keys. Always validate the checksum of the application and compare it to the version checksum listed on our GitHub before running.
