Fast answer
A crypto signal bot should explain what it does and what it cannot do.
Before using a signal bot, check whether it only sends alerts or can place trades. Review strategy logic, backtest limits, live sample size, stop handling, exchange permissions, latency, and whether the provider can change settings without notice.
Never connect exchange permissions until you know whether the bot can withdraw, trade, change size, or override stops.
Bot checklist
What to inspect before using a signal bot.
Alert versus execution
A notification bot has different risk from a bot with exchange API trading access.
Logic source
Ask what inputs create alerts, how often rules change, and whether old versions remain documented.
Backtest limits
Backtests need fees, slippage, sample period, failed periods, and live-forward comparison.
Permission controls
Use the smallest possible permissions and know how to revoke access quickly.
Official warnings
AI or bot language can be used to sell false confidence.
NFA summarizes a CFTC customer advisory warning that fraudsters exploit interest in AI to promote automated algorithms, trade signal strategies, and crypto-asset trading schemes with unrealistic claims. Treat "bot" as a feature to verify, not a reason to skip verification.
Review standard
Bot proof needs live records, not only dashboard screenshots.
A useful bot record should include alert timestamp, trade timestamp if automated, settings, skipped signals, failed trades, latency notes, stop behavior, and fee assumptions. If the dashboard cannot export a reviewable history, confidence should stay low.