Topstep Bots: API, Platforms and Account Rules

Topstep permits custom automation in specified environments, with important account and infrastructure conditions. A product called a “Topstep EA” does not establish a functioning connection, permission, a pass rate or a future Payout. This guide separates those questions using Topstep’s current documentation, checked on 16 October 2026.

Which connection and account does the bot use?

The TopstepX/ProjectX API supports custom bots on eligible simulated accounts; its API page excludes Live Funded Accounts. Check the actual account shown in the dashboard rather than treating “funded” as a single technical environment. API access is a separate service with its own conditions and billing.

A MetaTrader EA is a program for its particular terminal. An MT4/MT5 executable cannot simply be installed into TopstepX. A proposed connector needs its own implemented interface, contract mapping, order handling and permission checks. A platform name or an untested bridge diagram is insufficient.

Keep order transmission on the permitted device

Topstep requires personal-device order flow and prohibits VPS, VPN and remote-server trading. Its API policy permits supporting private-server tasks that do not transmit orders. Moving the final button locally does not make a remote order trigger or relay acceptable.

Draw the complete path from signal to order endpoint, including third-party services. Check where placing, modifying and cancelling occur. Keep credentials out of articles, public code and untrusted tools. Topstep’s allowance of an API does not endorse a vendor or make that vendor’s implementation reliable.

Separate loss rules, controls and objectives

For ordinary Trading Combine/XFA accounts, the MLL ratchets at day-end while losses are monitored during the session, including open P&L. Do not substitute an intraday-high rule. The general DLL policy describes a session pause, not an automatic rule breach. Labs offers and account stages can have different mandatory controls or static limits.

The current Combine consistency target is 55%; exceeding it raises the required profit. The XFA Consistency payout path has a separate 40% test. Record the exact product, phase, settings, denominator and consequence. A personal stop setting, MLL event and unmet Payout objective are different events; a software guard cannot guarantee an uncrossable limit.

Ask for records rather than a claimed success percentage

A strategy label such as breakout, mean reversion or scalping does not establish approval or an edge. Compare actual behaviour with the official prohibited-strategy and conduct policies. Simulator exploitation and prohibited account arrangements remain relevant even when a program can place an order.

Require the exact software/version, data, contracts, costs, complete result period and selection process. Keep unsuccessful runs, losses and execution exceptions. A vendor screenshot or a passing account does not establish a general EA pass rate. Historical observations, a Practice run, evaluation eligibility and an actual Payout answer separate questions.

Check operations before any connection decision

In an authorised test environment, compare expected signals, contract quantities and attempted controls with logs. Include stale data, rejects, partial orders, restart and reconnect handling. Confirm that repeated messages cannot silently duplicate exposure and that the operator can suspend the program.

Test calculations for the whole account, including other strategies, manual positions, pending orders, fees and the actual session clock. Record requested versus executed prices and unresolved failures. A faster connection, long backtest or fixed number of demo days is not proof of safe execution, compliance or profitability.

What JPTC evidence does and does not establish

The JPTC EA Hub provides downloads for documented files and platforms. An EA Hub licence or preset name does not establish a working, permitted TopstepX integration. Check the actual file and implementation report; do not infer Topstep compatibility from generic risk-management copy.

The separately hosted JPTC Algo needs no customer installation or VPS. That product description is not permission to route Topstep orders from a hosted service or an offer to take over a challenge. Its monthly broker-statement figures are company-published results, not an independent audit, client success dataset or evidence for another bot. Check current product and licence terms before any purchase decision.

Sources checked 16 October 2026: TopstepX API · Prohibited strategies · Prohibited conduct · Trading Combine · Consistency · DLL · MLL · Labs.

JPTC EA Hub · JPTC Algo

FAQ