Prop Firm Automation and Copy-Trading Rules Database

As of August 30, 2026, official pages show materially different approaches. Topstep documents custom bots through TopstepX API access but separately states that ProjectX API automation is prohibited in its Live Funded Account. My Funded Futures says copy trading is available across account types while its fair-play page restricts high-frequency behavior, simulated-fill exploitation, certain news trading, collaborative trading, and hedging. Earn2Trade says trade copiers are not allowed in any program, including LiveSim and live accounts.

Apex and Tradeify also publish official prohibited-activity, trader-guideline, and group-trading pages. Those pages must be read directly for the precise account being configured. This database deliberately avoids converting a page title, a platform login, or another trader's experience into a blanket verdict.

A useful record separates automated strategy execution, same-owner copying, copying another person, opposite-direction trading, hedging, news windows, maximum size, drawdown method, hosting location, API route, device sharing, order frequency, and prohibited simulated-market exploitation. Each field needs a stage, source URL, quoted or carefully summarized rule, verification date, reviewer, and unresolved-question flag.

Keep a technical status beside, but never inside, the policy status. For example, ProjectX or Rithmic may be connected and healthy while the policy gate remains denied or pending. That separation prevents an engineer from treating a green socket as authorization.

Different pages can discuss different products. A platform API article may explain what software can do, while a funded-account article limits where that API may be used. A copy-trading page may permit same-owner replication, while a fair-play page prohibits collaboration, hedging, abusive fills, or another trader's signals. These statements are not interchangeable.

Send support a concrete scenario: account program and stage, legal owner, leader and follower relationship, platform, API or copier, local or remote deployment, markets, expected order rate, news behavior, and risk controls. Preserve the response with the source snapshot. A generic yes from a forum, affiliate, or software vendor is not controlling policy evidence.

A policy-aware launcher should verify rule freshness, account stage, enabled strategy, deployment location, leader ownership, follower count, contract mapping, news state, current drawdown buffer, maximum size, and daily loss budget. A mismatch should fail closed. The system should log both the intended order and the policy version that permitted or rejected it.

Runtime controls need duplicate suppression, stale-signal rejection, bounded retries, rate limits, per-account sizing, reconciliation, emergency flattening, and a kill switch. These controls reduce operational error; they do not make a prohibited strategy permissible. Re-run approval after an account moves stages because the rule set, credentials, and capital model may all change.

Program labels are not standardized. An evaluation or challenge normally tests eligibility under simulated conditions. A funded, express, performance, or LiveSim account may still be simulated while adding conduct, consistency, or withdrawal rules. A live account routes real capital and can add broker, exchange, infrastructure, and risk-team requirements. Confirm what the firm means by each label before enabling an algorithm.

For prop-firm automation and copy trading, build a stage-specific rule record rather than one firm-wide yes-or-no flag. The notes below are a verification map, not permission, legal advice, or a substitute for the controlling agreement.

The official materials reviewed for this guide were TopstepX API Access, Topstep Live Funded Account Parameters, Apex Prohibited Activities, MFFU Fair Play and Copy Trading, Tradeify Guidelines and Group Trading, Earn2Trade Trade Copier Policy. Help-center text, account products, platform access, and enforcement language can change without preserving the assumptions in an old automation profile. Record the URL, page title, access date, account stage, and the exact operational conclusion you reached.

If two official pages appear inconsistent, do not select the more convenient interpretation. Pause order transmission and ask the firm to resolve the conflict in writing for your exact account type, platform, strategy behavior, hosting location, and multi-account arrangement.

A HexTrade connection does not create, expand, or certify permission from a prop firm. The trader remains responsible for the firm's current terms, the account-stage rules, exchange obligations, credentials, strategy behavior, and every order sent. Firm names in this guide identify independent policy publishers and do not imply endorsement or affiliation.

Nothing in this article promises that an account will pass an evaluation, receive funding, qualify for a payout, retain eligibility, or produce a trading return. Automation can repeat mistakes as efficiently as valid instructions, and software availability is not evidence that a strategy is suitable for a firm's risk model.