AI trading bot safety checklist
Education only. Updated Nov 10, 2026. This is not a “best AI trading bots” list, not a strategy, and not advice to turn a bot on. It expands our crypto bots, safely path into a page you can use before you give any automated tool an exchange key.
You are responsible for every trade your agent places. TraderStacks explains how the software works; this is not investment advice, and nothing here suggests what to buy, sell or when. Agents can make mistakes, and you can lose money. Freqtrade’s official homepage says the software is for educational purposes, that you should not risk money you are afraid to lose, and that the authors assume no responsibility for trading results.
What this page covers
People search “AI trading bot” for very different products: a hosted service that keeps your API keys, open-source software you run yourself, or an AI agent connected to a broker MCP. The safety problems overlap: custody, key permissions, and whether you tested in paper trading first.
Facts below are from official Freqtrade and Hummingbot documentation opened today, plus links to our existing hosted-bot and broker-MCP guides. Menu names and defaults can change; re-read the live docs before you go live.
1. Know who holds the assets and the keys
- A trading bot that talks to an exchange through your API key does not usually take custody of the coins. The exchange does. The risk is what that key is allowed to do, and who can use it.
- Hosted platforms store your keys on their servers. Open-source bots such as Freqtrade and Hummingbot run on a machine you control. Hummingbot’s connect guide says it stores API keys and private keys on the local machine in encrypted form, using the client password as the key.
- If you only want research, screening or a journal, you may not need a trading key at all. See the TradingView AI Copilot guide and the connect-an-agent path for tools that can stay read-only or approval-based.
2. Paper or dry-run before live keys
- Freqtrade’s homepage: always start in Dry-run and do not engage money before you understand how the bot works and what profit or loss you should expect. The Docker quickstart repeats: always backtest your strategy and use dry-run for some time before risking real money. Sample strategies are for reference, not a recommendation to run them live.
- Freqtrade’s configuration guide: in Dry-run the bot does not engage your money and only runs a live simulation without creating trades on the exchange. Set
dry_runtotrue(the documented default istrue) and use a separate dry-run database URL. You can remove real API credentials or use empty/fake values. Only read-only exchange operations are performed. Orders are simulated and not posted. A simulated wallet starts atdry_run_wallet(documented default 1000 in the stake currency). - Freqtrade’s FAQ: it does not support exchange sandbox accounts; use dry-run instead. Official docs say sandbox markets often have different books and liquidity, so they are a poor stand-in for realistic tests.
- Hummingbot’s paper-trade guide: you can simulate strategies without risking actual assets. Exchange APIs are not required for paper trade on Pure Market Making, Cross Exchange Market Making and Avellaneda Market Making. The client quickstart says a paper-trade connector can simulate against live market data without API keys. A documented limitation: V2 strategy controllers are not currently supported on paper-trade connectors and need a live exchange connection — so check which mode your chosen strategy uses before you assume it is paper-safe.
3. Least privilege, IP allowlists, and secrets
- Least privilege: Hummingbot’s official connect page is explicit — only enable Read and Trade access. Hummingbot does not support deposit and withdrawal, and it is not necessary to enable withdraw, transfer, or anything equivalent to retrieving assets from your wallet.
- Freqtrade says API keys and secrets are required only in production mode, and to keep them secret and not disclose them publicly.
- Freqtrade’s FAQ: a live permission error often means a bad or expired key, or that the bot’s IP is not enabled in the exchange API console. If your exchange offers an IP allowlist, use it so a leaked key is harder to use elsewhere.
- Never paste keys, secrets or keystore passwords into a chat, a ticket, or a public repo. That matches the same “do not paste secrets” rule in our Claude Code broker MCP guide.
- One key per bot, and revoke keys you are not using.
4. Keep the control plane private
Freqtrade’s REST API docs warn that, by default, the API listens on localhost only, and they strongly recommend not exposing this API to the internet, and choosing a strong unique password, because others could control your bot. They also recommend not exposing freqUI directly to the internet (it does not support HTTPS out of the box) and using an SSH tunnel or VPN on a VPS.
If you add Telegram, webhooks or a cloud agent that can start and stop the bot, treat those as the same class of risk: whoever controls them can trade with your key’s permissions.
5. Know how to stop, and that revoke is not a cancel
- Learn the project’s documented stop/start commands before you go live, and confirm you can reach the machine if the bot misbehaves.
- Revoke the exchange API key from the exchange’s own API settings if something looks wrong. Revoking a key does not always cancel orders already resting on the exchange — check the exchange’s open orders yourself. (Interactive Brokers makes the same point for MCP revoke on our IBKR guide.)
- Work through the interactive AI agent safety checklist and the general before-you-connect checklist as well.
Hosted bots and broker agents
If you are comparing hosted crypto automation platforms, start with 3Commas vs Cryptohopper (including published incidents listed there) rather than a “best bot” list. For official broker MCP connections, use Compare official broker MCP setups and the safety settings on each broker’s page.
For a closer look at the two open-source projects cited above, see Freqtrade vs Hummingbot.
- Sources (official pages, opened Nov 10, 2026; each returned HTTP 200)
- Freqtrade homepage, Configuration / Dry-run, FAQ, Docker quickstart, REST API security warning.
- Hummingbot homepage, Paper Trade, Connect Exchange API Keys, Client quickstart.
- Checked on
- Nov 10, 2026
- Not covered
- A ranking of bots, every hosted vendor’s key settings, or a live test with funded keys. Exchange API consoles differ; follow the exchange’s own permission labels.
Frequently asked questions
What is an “AI trading bot” in this guide?
Here it means software that can place orders automatically from rules or from a model, usually through exchange API keys you create. That includes open-source bots you run yourself (such as Freqtrade and Hummingbot) and hosted platforms that hold those keys. This page is a safety checklist, not a roundup of bots to buy, and not a strategy.
Should I start on paper or dry-run?
Official docs for both Freqtrade and Hummingbot say to simulate first. Freqtrade’s homepage tells you to always start in Dry-run and not engage money before you understand how the bot works. Its configuration guide says Dry-run does not engage your money and does not create trades on the exchange; only read-only exchange operations run, and API keys are not required. Hummingbot’s paper-trade guide says you can simulate strategies without risking actual assets, and that exchange APIs are not required for several listed paper-trade strategy types.
What permissions should an exchange API key have?
Hummingbot’s official connect guide says Hummingbot does not support deposit and withdrawal, and recommends only read + trade enabled keys — not withdraw, transfer, or anything equivalent to retrieving assets. Freqtrade’s FAQ says a live “Invalid API-key, IP, or permissions” error often means the key is invalid or expired, or the bot’s IP is not enabled on the exchange, and that live spot trading usually needs a Spot Trading permission (or the exchange’s equivalent). Grant no more than the live mode actually requires, and keep keys secret.
Do these bots hold my crypto?
The official Freqtrade and Hummingbot docs describe software you run that talks to an exchange or venue through keys you configure. Your funds stay in the exchange or wallet account those keys can access. That is different from a broker or exchange that has custody of the assets. Limit what the key can do, and revoke it if you stop using the bot.
Does TraderStacks tell me which bot to run or what to trade?
No. We explain how the software is documented to connect and how to limit damage if something goes wrong. We give no tickers, signals or strategies, and nothing here is financial advice.
Next: Freqtrade vs Hummingbot · Crypto bots, safely · 3Commas vs Cryptohopper · Official broker MCP comparison · Before you connect a tool
Education only, never trade advice.
