Bots
Create, configure and operate trading bots.
Creating a bot
| Setting | Notes |
|---|---|
| Name, wallet, symbols, initial capital | Required. |
| Mode | autonomous (default), dca, grid, momentum or mean_reversion. |
| AI provider / model | Defaults to the platform provider; pick one of your own LLMs instead if you prefer. |
| Refresh interval | Seconds between cycles. Default 300, minimum 30. |
| Leverage & margin type | Spot is spot; futures bots can set leverage. Locked after the bot's first trade. |
| Quote currency | Default USDT. |
| Decide all symbols | Let the engine consider every eligible symbol for the quote currency. |
| Risk and mode configuration | Position size, stops and mode-specific parameters. |
| Supervisor | Enabled and auto-apply by default, with an optional custom prompt (max 500 characters). |
Lifecycle
- Bots are created paused; press Start to activate.
- While a bot is active you can change its name, instructions and risk, but indicators, symbols, mode configuration and refresh interval require a paused bot.
- Kill all stops every active bot at once; open positions are not closed automatically.
Plan limits
The number of bots is set by your plan (see Plans & billing). Creating a bot over the limit returns 409 Bot limit reached.
Positions, blocked symbols and exports
- Close now closes an open position at the latest price and records the trade.
- Blocked symbols are never traded by any of your bots.
- Export downloads all your trades as CSV (up to 10,000 rows).
How a cycle works
- Fetch klines from Binance market data and compute indicators.
- Detect the market regime (trending, ranging, high volatility, neutral).
- Run the veto pipeline: extreme volatility, low historical edge, timeframe misalignment, order-book depth.
- If a ThunderScript is active, evaluate
entry when/exit when. - Optionally ask the AI model for a final confidence check (
ai_context). - Execute, then record the decision, reasoning and snapshots in the audit trail.