Can You Use Trading Bots at Prop Firms? Topstep vs Tradeify

Rules verified: August 22, 2026, 7:05 AM MDT

Next review: September 5, 2026, or sooner if a cited automation, API, device, stage, or prohibited-conduct rule changes

The practical answer: some futures prop firms allow automated trading, but “bots allowed” is never enough detail to launch safely. Topstep allows automated strategies with conditions and sells TopstepX API access, while Tradeify allows a personally owned, exclusive, non-HFT bot that the trader can prove and demonstrate. In both cases, the trader remains responsible for every order, rule breach, malfunction, and strategy behavior.

Before connecting software, get written answers to six questions: who owns the strategy, where it runs, which account stage it will trade, how orders reach the platform, whether anyone else uses the same logic, and how the system stops on a rejected or divergent order. Permission at evaluation does not automatically establish permission in a live account.

Quick policy comparison

This table is a policy map, not a recommendation to automate. A technically supported connection can still violate strategy, hedging, news, size, session, or account-stage rules.

Separate automation from copying and order aids

The word “automation” covers tools with very different risk:

• Order aid: A hotkey, bracket template, auto-breakeven rule, or risk preset helps submit or manage a trade the trader chose.
• Trade copier: Software mirrors a lead order into other accounts. The trader still selected the lead trade.
• Automated strategy: Code decides when to enter, exit, size, or modify orders.
• API integration: Software sends or manages orders through a documented programming interface.
• Third-party signal execution: Software reproduces another person's strategy or trade calls.

The existing prop-firm copy-trading guide explains owner-controlled mirroring. This guide addresses the added policy risk when code makes or submits the trading decision.

Topstep: automation is allowed, but the route and stage matter

Topstep's current Trading Combine and Express Funded Account pages allow automated strategies with conditions. Topstep says it does not set up or troubleshoot them, does not make exceptions for errant trades or malfunctions, and tells traders to test on a Practice Account first.

TopstepX also has a published API route. The current API page says traders can build automated strategies, connect third-party tools, pull market data, create custom risk rules, and execute orders. API access is billed separately at $29 per month; Topstep currently publishes a recurring 50% code that reduces it to $14.50 per month.

That permission has three important boundaries.

Personal-device boundary

Topstep says trading activity must originate from the trader's personal device. Its API guidance prohibits VPS, VPN, and remote-server use and warns that running automation on a VPS can lead to suspension or removal.

A cloud-hosted bot can therefore be technically capable of reaching the API while still violating the published environment rule. Verify the deployment location, not just the credentials.

Live-stage boundary

Topstep's current Live Funded Account guidance permits automated strategies generally but expressly prohibits automated trading through the ProjectX API in the LFA. That is narrower than a universal bot ban: the strategy may be allowed through another approved live setup, but the ProjectX API route does not carry forward.

Rebuild the compliance checklist when an account moves from Trading Combine to XFA or LFA. Do not assume an API key, platform connection, copier, or hosting pattern remains approved after call-up.

Conduct boundary

Topstep prohibits software, AI, ultra-high-speed systems, or mass data entry that creates an unfair advantage, manipulates the program, or exploits simulated fills. Its examples include scalping algorithms designed around unrealistic SIM fills, hundreds of rapid trades that exploit queue treatment, and repeated attempts to benefit from unrealistic slippage or stop execution.

The dividing line is not merely manual versus automated. The system must produce trading that could function in a real futures market without exploiting the simulator or program structure.

Tradeify: exclusive ownership and proof are central

Tradeify's current Guidelines for Traders allows bots and algorithms under a more explicit ownership test. The trader must be able to prove sole ownership of the bot or strategy, ensure no one else has access to or uses it, and keep it exclusive to Tradeify rather than operating the same bot across multiple firms.

Tradeify also says it may scan for similar orders and require a live video of the trader enabling the code on the trader's own PC. That makes evidence preparation part of the practical setup, not something to reconstruct after a payout review.

Tradeify prohibits HFT bots and retains the right to request documentation if risk monitoring flags the account. Its funded-account microscalping rule also matters to automation: more than half of trades and more than half of profit must come from positions held longer than 10 seconds to activate a passed evaluation or request a payout under the current guidance. Falling short delays activation or payout eligibility rather than automatically failing the account, but a bot designed around sub-10-second trades can still make the strategy commercially unusable.

What both policies make the trader own

Neither firm transfers responsibility to the software vendor. The trader remains responsible for:

• maximum contracts and micro-to-mini conversion;
• loss limits, drawdown, consistency, and payout eligibility;
• session close and holiday close requirements;
• news, hedging, and prohibited-conduct rules;
• duplicate, rejected, partial, or stale orders;
• connection loss and restart behavior; and
• every trade the bot sends after an account stage or risk limit changes.

An automation vendor's marketing page cannot override the firm. Save the firm rule, account agreement, platform/API permission, and vendor configuration that applied when the system ran.

A pre-launch automation checklist

1. Name the exact tool. Record whether it is a strategy runner, API client, order-management aid, copier, or signal service.
2. Prove ownership and access. Save source-control history, license terms, configuration ownership, and the list of people or services that can run the logic.
3. Map every account stage. Confirm permission separately for evaluation, simulated funded, Pro/bridge, and live accounts.
4. Verify the execution route. Record platform, API, credentials, device, network, and whether a VPS or remote server is involved.
5. Test on the smallest safe environment. Exercise rejected orders, partial fills, lost connections, restarts, duplicate callbacks, and emergency flattening.
6. Hard-code firm limits outside the signal logic. Use independent caps for quantity, daily loss, drawdown distance, permitted products, and session close.
7. Prevent cross-account hedging. A bot and copier together can leave accounts offset after one follower rejects or lags.
8. Log every decision and order. Preserve timestamps, signal state, requested quantity, platform response, fills, cancels, and errors.
9. Build a manual kill switch. The trader must be able to stop new orders, cancel working orders, and flatten all positions.
10. Re-verify after every transition. A payout, scaling change, platform migration, or live call-up can change what the system may do.

Three common assumptions that fail

“The API supports it, so the firm permits it everywhere”

Topstep's published API supports automation in eligible TopstepX accounts, but ProjectX API automation is prohibited in the LFA. Technical access and stage permission are separate checks.

“I bought the bot, so I exclusively own the strategy”

A retail license can grant use without granting exclusive ownership. Tradeify's policy asks for sole ownership and no sharing with other traders or firms. Ask Tradeify for written confirmation before treating a mass-market bot license as compliant.

“A malfunction should reverse the violation”

Topstep explicitly says it makes no exceptions for errant automated trades or malfunctions. Design around failure before the first funded order rather than relying on after-the-fact support.

Bottom line

Use automation only when the firm permits the exact strategy, account stage, connection route, device environment, and ownership model. Topstep provides a documented API path but prohibits VPS hosting and ProjectX API automation in Live. Tradeify permits exclusive personal bots that can be proved and demonstrated, while banning shared, cross-firm, and HFT use.

Start with written permission and a failure-tested kill switch. Then recheck the rules whenever the account, platform, or strategy changes. “Bots allowed” is the beginning of the compliance review, not the conclusion.

For broader context, compare the Topstep review, Tradeify review, TopstepX versus Tradovate platform guide, and prop-firm copy-trading rules.

Official sources and verification

• Topstep Trading Combine parameters — checked August 22, 2026; automated-strategy permission, trader responsibility, Practice Account testing, and account limits.
• Topstep Express Funded Account parameters — checked August 22, 2026; XFA automation permission and stage context.
• TopstepX API Access — checked August 22, 2026; supported API uses, separate price, personal-device rule, VPS/VPN/remote-server prohibition, and order responsibility.
• Topstep Live Funded Account parameters — checked August 22, 2026; automated strategies allowed generally, but ProjectX API automation prohibited in LFA.
• Topstep prohibited trading strategies and prohibited conduct — checked August 22, 2026; unfair technology, simulator exploitation, rapid-trade, coordinated-trading, and enforcement boundaries.
• Topstep pricing and payment questions — checked August 22, 2026; current account pricing and data context.
• Tradeify Guidelines for Traders — checked August 22, 2026; ownership proof, live-video verification, exclusive-use, cross-firm, HFT, microscalping, and documentation conditions.
• Tradeify Essential Trading Rules Overview — checked August 22, 2026; account-stage rules and algorithmic-trading summary.
• Tradeify pricing reference — updated August 21 and checked August 22, 2026; current plan, platform, data, and cost context.
• TradingView status and Tradovate status — checked August 22, 2026; TradingView's scheduled maintenance completed and current systems operational; Tradovate listed services operational.
• CME system alerts and CFTC press releases — checked August 22, 2026; no direct exchange emergency or futures-prop regulatory event displaced this guide.