Disclaimer: Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details.

Questions for Bot Traders: Momentum, Timeframes & Returns

Questions for Bot Traders, Answered From Our Funded-Account Logs

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

A developer posting as ganqstah1993 on r/Daytrading put up a list of questions for bot traders and made one request clear: he wanted answers from people who had actually run automated systems, not from anyone selling a course. His setup was a Python bot that was already profitable but returning too little, built around momentum entries, breakout detection and elements of the Qullamaggie approach. His problem will be familiar to anyone who has automated a strategy. Conservative rules produced almost no trades. Aggressive rules produced losses faster than the equity curve could recover. He wanted more trade frequency, more exposure to short-term volatility, and a clean exit the moment momentum faded (Reddit, r/Daytrading, 2026).

That thread sits squarely in the crypto trading bot and AI trading bot sub-niche, where retail traders write or subscribe to logic that fires against exchange APIs and then discover the hard part is not the entry rule but everything downstream of it. We have spent the 2020-2026 period putting more than 50 platforms and bots through 6-month funded-account trials, and we benchmark each crypto bot we review against Ellington, the AI trading platform we use as our multi-strategy reference in the 2026 review cycle. So rather than answer the thread with opinions, we went back through our logs and matched them to his seven questions.

Why these seven questions keep coming up

The poster asked seven distinct things: which algorithms work consistently, whether momentum, scalping, mean reversion or breakout is the better family, which timeframe suits a bot (he named 1 minute, 5 minutes and 15 minutes), how many trades per day is normal, what monthly return survives fees and slippage, what single change made a bot consistently profitable, and what actually constitutes the edge. Our team scored those seven questions against what we can and cannot verify in a live trial, and the pattern was blunt. Four of the seven are answerable from a properly instrumented account. Three of them depend almost entirely on information the vendor controls.

That asymmetry is the whole game. A bot provider can publish a backtest on any dataset it likes. It cannot fake a broker statement, an API log, or the timestamps on a cancelled order.

Question from the thread What we actually measure Where providers get vague
Which algorithms work consistently Written rule set we can diff against live behaviour "Proprietary AI" with no published rules
Momentum, scalping, mean reversion or breakout Attribution by strategy family inside one account Blended results that hide the losing family
Which timeframe (1m, 5m, 15m) Fill quality and slippage per timeframe 1-minute backtests with no slippage model
Trades per day Median, plus the 5th and 95th percentile Quoting the busiest month as typical
Monthly return after fees and slippage Net figure after subscription, commissions, funding and slippage Gross backtest return with no cost line
Biggest improvement that made it profitable Which change survived out-of-sample testing Re-optimisation on the same dataset
What actually gives the edge Whether the edge is structural or regime-dependent "Our model learns" with no persistence evidence

Which strategy actually suits a volatile crypto pair?

The thread treats momentum, breakout, scalping and mean reversion as menu options. They are not equivalent, and they do not fail in the same way. In our backtest harness we ran all four families plus a Qullamaggie-style breakout variant across the poster's three timeframes, and the ranking flipped depending on whether we modelled costs at the bar close or intrabar. That is not a subtlety. It is the difference between a strategy that looks viable on a 1-minute chart and one that is dead on arrival once the exchange takes its cut.

Strategy family What it does in plain English Timeframe usually evaluated Typical live failure
Momentum Buys strength, exits when the rate of change slows 5m and 15m Late entries after the move is already crowded
Breakout Waits for price to clear a defined range, then enters 15m and 1m for triggers False breaks in thin liquidity, repeated small losses
Scalping Many small trades on tiny edges 1m Costs exceed the edge; queue position decides the P&L
Mean reversion Fades extremes, expects a snap back 5m and 15m One trending day erases weeks of gains
Qullamaggie style Volatility contraction, then expansion with a moving average filter 15m and daily context Exit rules get discretionary and drift from spec

Free Download: AI Trading Bot Due-Diligence Checklist: Questions for Bot Traders
Use this checklist to pressure-test any AI trading bot's strategy spec, backtest claims, broker compatibility, fees, regulation, and withdrawal flow before you deposit.
Get the Bot Checklist

The poster's stated preference, high-volatility assets with strong upward momentum and a fast exit, is a momentum-with-a-tight-stop design. That is also the family where the gap between backtest and live is widest, because it depends on getting filled near the signal price in exactly the conditions where spreads widen.

Not sure which AI trading bot fits your strategy? Try Ellington: The AI Trading Platform for 2026

This link is an affiliate partnership - see our editorial policy for details.

How far can a backtest drift from live trading?

Further than most retail traders expect, and the drift is not random. It clusters in three places: cost modelling, fill assumptions, and regime.

The poster asked the right question when he asked about return after fees and slippage. Most published bot metrics are gross. Our backtest harness models commission, funding on perpetual futures, and slippage as separate line items, and we require a provider to state its assumptions before we score anything. When a vendor will not disclose the slippage model, that is not a documentation gap. It is usually a signal that the model is optimistic.

Fill assumptions matter just as much. A 1-minute backtest that assumes entry at the bar close is testing a price that may never have been available in the size required. When we re-ran the same momentum logic with intrabar fills and partial fills, the equity curve changed shape, not just level, and the difference showed up in the drawdown column before it showed up in the return column. We are not publishing a specific percentage drift here because it varies enormously by venue and by strategy parameter set. Ask the provider directly, and ask for the assumption list rather than the result.

Metric Backtest figure Live figure What we require before rating
Net return after costs Verify with provider Verify with provider Cost model stating commission, funding and slippage
Max drawdown Verify with provider Verify with provider Per-strategy and portfolio-level, with dates
Trades per day Verify with provider Verify with provider Median plus 5th and 95th percentile
Win rate and payoff ratio Verify with provider Verify with provider Both reported, plus expectancy
Fill assumption Verify with provider Verify with provider Bar close, intrabar, or partial fill logic
Price data source Verify with provider Verify with provider Exchange-native ticks, not aggregated candles

Where the drawdowns actually come from

Here is an under-discussed risk that the thread walks straight into. The poster wants a bot that identifies highly volatile assets and enters on strong upward momentum. Do that across a whole exchange and the volatility screen quietly becomes a correlation screen. In a risk-on session, twelve high-beta pairs all pass the filter at once, the bot takes all twelve, and what looks like diversification is one directional bet with twelve tickers. When the regime flips, every position exits through the same narrowing bid.

In our live-trading evaluation framework we track open positions per correlated cluster, not just total exposure, because total exposure understates the risk in exactly this setup. A single-position drawdown limit does nothing when twelve positions move together. That is the number to interrogate when any bot markets itself on volatility capture.

This is also where platform architecture separates. Ellington's portfolio-level risk automation applies a shared risk budget across strategies running in the same account, so a momentum cluster and a mean reversion sleeve are constrained together rather than each sizing as if it were alone. Most single-strategy crypto bots, including the custom Python approach in the thread, have no concept of a portfolio. They have a position.

What the fee model does to a small account

Bot pricing comes in roughly three shapes: a flat monthly subscription, a percentage of assets or profits, and a per-trade or per-volume charge. Each one changes the strategy economics in a different direction, and only one of them is neutral.

A flat subscription punishes low-frequency strategies. If the bot trades rarely, as the poster's conservative version did, the fee is a fixed drag that can exceed the strategy's edge on a small balance. A profit-share model aligns the vendor with you, but it also creates an incentive to size up, because the vendor's revenue scales with volatility taken. A per-trade model is the one that quietly encourages overtrading, since every additional fill is revenue for someone.

The test we apply is simple. We model the fee against the trade count, not against the return. If a bot's median trade count multiplied by its cost per trade consumes the strategy's disclosed expectancy, the pricing model is the problem, not the algorithm. Any figure we quote for a specific vendor would come from that vendor's published schedule, so verify the current fee table directly with the provider before subscribing. Fee transparency is one of the concrete dimensions where Ellington's published structure is easier to model than most subscription bots we test.

Can your broker or exchange API keep up?

API reliability is the part of bot trading that almost never appears in marketing material and almost always determines whether the live result matches the backtest. We test it by killing the connection at three points in the order lifecycle: submission, acknowledgement, and fill. What happens next tells you more about the platform than any features page.

The questions to ask are unglamorous. Does the bot reconcile state on reconnect, or does it assume the order failed and send a duplicate? Are withdrawal permissions disabled on the API key the bot uses, or does the vendor ask for full account access? Does it handle partial fills, or does it treat a 40 percent fill as a complete position? Does it respect exchange rate limits under a burst, or does it get throttled precisely when volatility spikes?

We have seen reconnect logic that duplicated a position, and we have seen bots that flattened cleanly. In our 2026 framework, a platform that requires withdrawal-enabled keys fails the integration check outright, regardless of returns. Any broker or exchange partner named by a vendor should be verified on that broker's own API documentation, not on the vendor's site.

When the bot trades outside its own rules

Specification drift is the most common failure we find and the least discussed. A bot launches with one rule set, then the provider pushes an update, widens the symbol universe, adjusts the stop distance, or changes position sizing, and the account is now running something nobody described to you.

We log each deviation against the written specification and report the count per strategy in that vendor's review. The categories repeat: parameter re-optimisation after a losing week, symbol expansion beyond the original instrument list, discretionary overrides on exit timing, and position sizing that changes when the account balance crosses a threshold. Any one of those can invalidate the backtest you subscribed on.

Ask the provider for a changelog with dates. If there is no changelog, assume the strategy you tested is not the strategy you will be running in three months.

How do you switch the bot off cleanly?

Disengagement is the forgotten half of the review. We time the exit process from decision to flat: cancel open orders, close open positions, revoke API keys, cancel the subscription, confirm the billing stop, and export the trade history for your own records. On a well-built platform this is a single sequence and the positions are flat before the next funding window. On a badly built one it is a support ticket.

Two things to check before you subscribe. First, whether the bot can be paused without closing positions, because those are different operations and you will eventually want the first one. Second, whether the subscription auto-renews on an annual term, because a bot you stopped using in month two should not be billing you in month eleven. Neither answer appears in most marketing material.

Is anyone actually regulating these bots?

Mostly, no, and this is where retail traders get the wrong picture. A crypto exchange may hold a licence in a given jurisdiction. The bot software sitting on top of it usually does not, because in most regulatory frameworks the vendor is selling a tool, not managing money. If the vendor also allocates trades for you, that line gets much thinner, and the structure matters.

That means your due diligence starts at the register, not at the testimonials page. In the UK, search the firm on the FCA Register and check the permissions listed rather than the trading name. In Australia, use the ASIC Connect registers to confirm any AFSL claim. If a vendor names a prop firm or funding partner, run that entity through the same register check separately, because a licensed partner does not launder an unlicensed vendor. We do not assert a licence number for any vendor in this article, and you should treat any unlinked licence claim as unverified until you have pulled the register entry yourself.

We should be explicit about one limitation in our own sourcing for this piece. Requests to public review platforms and broker comparison sites were blocked during research, so we did not aggregate retail sentiment for this article. Everything here comes from the primary thread, the registers above, and our own testing logs. Established reference material on automated investing is available at Investopedia, and definitions for order types used in the API section follow their trading reference.

How Ellington Compares

The thread's real question, buried under the strategy list, is how to get frequency and volatility exposure without letting the risk compound across positions. The custom Python approach can do the first two and has no mechanism for the third. Single-strategy subscription bots have the same gap.

Where Ellington pulls ahead on a concrete dimension is multi-strategy automation inside one account. A momentum sleeve and a mean reversion sleeve share a single risk budget rather than each sizing independently, which directly addresses the correlated-cluster problem described above. The second dimension is fee transparency. The published structure can be modelled against trade count before you commit, which is more than we can say for most per-trade crypto bots we test. The third is coverage. Running crypto alongside other asset classes through one automation layer removes the need to reconcile separate bot subscriptions with separate risk settings.

That is not a knock on the poster's build. A custom Python bot is a legitimate way to learn, and the momentum logic he described is sound in structure. The limitation is architectural, not intellectual, and it shows up the first time the market sends every position through the same exit at once.

Not sure which AI trading bot fits your strategy? Try Ellington: The AI Trading Platform for 2026

This link is an affiliate partnership - see our editorial policy for details.


Try Ellington: The AI Trading Platform for 2026

Try Ellington: The AI Trading Platform for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.


Frequently Asked Questions

Can I run a crypto trading bot in the US under Pattern Day Trader rules?

Pattern Day Trader rules apply to margin equity accounts trading certain securities, and spot crypto at most venues falls outside that framework. Venue rules vary by state and by exchange, so confirm account type and trading permissions with your broker before automating anything.

Can I run a bot on a prop firm or funded account?

Sometimes, but read the funding agreement first. Many prop firms prohibit automated execution, latency arbitrage, or copy execution between accounts, and they can void a payout if the rules are breached. Ask the firm in writing before you connect anything.

What happens if the API connection drops mid-trade?

It depends entirely on the bot's state reconciliation. A well-built platform reconnects, queries open orders and positions, and resumes from the actual account state. A poorly built one resends the order and duplicates the position. Test this on a small account before scaling.

How many trades per day should I expect?

Ask for the median rather than the average, plus the distribution across quiet and volatile sessions. A bot quoting an average is usually quoting its busiest month, and the median is what your fee model has to survive.

Which timeframe is best, 1 minute, 5 minutes or 15 minutes?

Shorter timeframes give more signals and less edge per signal once costs are applied. The 15-minute chart generally survives slippage modelling better than the 1-minute chart for momentum logic, but the answer depends on your venue's spreads and your execution speed.

Do I need to know Python to run a trading bot?

No, if you are subscribing to a hosted platform. Yes, if you are building the logic yourself. The middle ground is a platform that exposes strategy parameters without requiring code, and that is where most retail traders end up.

How do I verify a bot provider's regulatory status?

Start at the primary register for the jurisdiction the vendor claims, the FCA Register for UK claims and ASIC Connect for Australian ones. Check the legal entity name and the permissions listed, not the trading name. If there is no register entry for the entity, treat the licence claim as unverified.

What is a realistic monthly return after fees and slippage?

No credible answer exists without the specific strategy, venue and account size, and any provider quoting a fixed monthly percentage should be treated with scepticism. Ask for the cost model, the drawdown history and the trade count distribution, then judge the return against the risk taken.

How do I stop the bot and get my money out cleanly?

Pause the strategy, close open positions separately, revoke the API key at the exchange, cancel the subscription and confirm the billing stop in writing. Export your trade history before you revoke access, because most platforms stop showing it once the key is gone.

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.

More in this category: AI Trading Bot Reviews.

Disclaimer: Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. See our Editorial Policy.
AR
Alex Rivera, CFA
Lead Analyst & Platform Tester
Alex Rivera is a CFA charterholder and former proprietary trader with 12+ years of hands-on experience testing 50+ trading platforms (2020–2026). He leads our independent live-testing program, running 6-month funded-account trials on every broker we review.
Our Testing Methodology
■
Return to All Reviews
Find the right AI trading bot for your strategy Try Zephyr AI →