If you trade a funded futures account, you have almost certainly traded on Rithmic without ever signing up for it. Rithmic automated trading questions usually start from confusion about what Rithmic even is: it is not a broker you open an account with, and it is not a platform you place orders in. It is the execution and market-data infrastructure sitting underneath many futures brokers and prop firms. This piece explains what Rithmic actually is, the R ecosystem you touch when you use it, why prop firms route through it, and what it really means to automate on a Rithmic-backed account, including the boundary that does not move no matter how good the plumbing is: your firm’s own rules.
What Rithmic is
Rithmic describes itself, on its own homepage, as “Trading Infrastructure for Futures” (rithmic.com, retrieved 2026-07-13). The core product is the R|Trade Execution Platform, the engine that routes orders to the exchanges and delivers market data back. Rithmic operates the connectivity; brokers, FCMs, and prop firms plug their accounts into it, and you, the trader, reach it through some front-end application.
That layering is the thing to internalize. In the retail futures stack there is the exchange (CME, CBOT, NYMEX, COMEX), a clearing firm or broker, an infrastructure and routing layer, and finally the platform you look at. Rithmic is the infrastructure and routing layer for a large slice of the industry. When a prop firm says your data feed is Rithmic, they mean your orders and quotes travel Rithmic’s execution platform, even though the window in front of you might be NinjaTrader, Quantower, Sierra Chart, or Rithmic’s own R|Trader Pro.
The R ecosystem: R|Trader Pro and R|API+
Rithmic ships its own applications and developer interfaces, all under the R| naming. Two matter most for anyone thinking about automation.
R|Trader Pro is Rithmic’s trading application for humans: it is “R|Trader with charts and a real-time interface to and from Microsoft Office Excel,” able to stream studies into spreadsheets and to “send configured trades back into the R|Trade Execution Platform, automatically or with the click of a button” (rithmic.com, retrieved 2026-07-13). For many traders R|Trader Pro is the direct way to interact with a Rithmic-backed account without any third-party platform in the middle.
R|API+ is the developer door. Rithmic describes it as “a collection of software libraries and interface definitions that developers and screen designers incorporate into their proprietary software to gain access to R|Trade Execution Platform,” providing “a normalized view of market data and reference data and of order and execution reports across all supported exchanges” (rithmic.com programmatic interfaces, retrieved 2026-07-13). A higher tier, R|Diamond API, is the same interface with “access to R|Trade Execution Platform’s ultra-low latency and high frequency trading capabilities.” R|API+ is the route a serious quant or vendor uses to talk to Rithmic directly, but access is arranged through your broker or firm, and whether it is available to you, and at what cost, is their detail to confirm.
Why prop firms run on Rithmic
Prop firms are in the business of evaluating and funding traders, not building execution infrastructure. Rithmic lets a firm offer real-time futures data and order routing by connecting accounts through it, which is why so many firms standardize on it. Two examples you can verify at the source:
- Bulenox documents connecting through Rithmic: its setup has you install and log in to Rithmic R|Trader, then in NinjaTrader select “My Rithmic for NinjaTrader Brokerage” and “Rithmic Paper Trading” as the system (bulenox.com connection help, retrieved 2026-07-13).
- Apex Trader Funding publishes an official “Connection Guide for NinjaTrader Using Rithmic,” where you get Rithmic credentials from the Apex dashboard and add “My Rithmic for NinjaTrader Brokerage” as your connection (support.apextraderfunding.com, retrieved 2026-07-13).
The pattern repeats across the industry, but treat any list of “firms on Rithmic” as a snapshot: firms change providers and add platforms, so confirm the current connection method with your own firm rather than trusting a third-party roundup. The full picture of which firms permit automation at all, separate from what infrastructure they use, is in which futures prop firms allow automated trading.
What automating on a Rithmic-backed account really involves
Say you have a Rithmic-backed account and you want to run an automated or agent-driven strategy on it. Three practical things shape what that looks like, and none of them are decided by Rithmic alone.
Data-feed access. Real-time exchange data on a professional-classified account carries per-exchange market-data fees, and the classification (non-professional versus professional) changes what you pay. The exact figures and your classification are set by the exchanges and administered through your firm or broker, so confirm the current cost with them rather than assuming a number you read online.
API cost and availability. Reaching Rithmic through R|API+ is not automatically included with every account. Some brokers and firms enable programmatic API access, sometimes for an additional fee, and some do not offer it at all on evaluation-style accounts. If your plan depends on the API, confirm with your firm or broker that R|API+ access is available on your specific account.
Platform routing. The most common automation path is not the raw API at all; it is a platform that already speaks Rithmic. NinjaTrader connects to Rithmic through the “My Rithmic for NinjaTrader Brokerage” connection, which both the Bulenox and Apex guides above walk through, so automating in NinjaTrader means your automation reaches the Rithmic-backed account through NinjaTrader’s connection. How code and agents reach a NinjaTrader account in turn is its own subject, mapped in the NinjaTrader 8 Python API piece.
| Property | r|trader pro | r|api+ direct | ninjatrader on rithmic |
|---|---|---|---|
| what it is | rithmic's own app | developer libraries | third-party platform, rithmic connection |
| who it suits | direct manual trading | quants and vendors | chart traders and automation |
| automation route | excel round-trip, limited | full, if your firm enables it | ninjascript, plus external bridges |
| where risk limits would sit | with the trader | with the code you write | in your platform or a bridge in front |
r|trader pro
- what it is
- rithmic's own app
- who it suits
- direct manual trading
- automation route
- excel round-trip, limited
- where risk limits would sit
- with the trader
r|api+ direct
- what it is
- developer libraries
- who it suits
- quants and vendors
- automation route
- full, if your firm enables it
- where risk limits would sit
- with the code you write
ninjatrader on rithmic
- what it is
- third-party platform, rithmic connection
- who it suits
- chart traders and automation
- automation route
- ninjascript, plus external bridges
- where risk limits would sit
- in your platform or a bridge in front
The boundary: the firm’s rules still apply
Here is the part that matters most and gets skipped most. Rithmic being underneath your account changes nothing about whether you are allowed to automate it. Rithmic is infrastructure; it does not grant, certify, or override a prop firm’s rules. If your firm restricts automated or agent-driven order entry, that restriction applies whether the account runs on Rithmic, Tradovate, or anything else.
The firm’s rules are the real gate, and they are their own discipline: how to find and read a firm’s written automation policy, why the evaluation phase trips automated accounts hardest, and which limits you can actually enforce, are covered in prop firm automation rules for AI agents and trading bots. The short version: the automation policy comes from the firm, not the plumbing, and staying inside it is your responsibility.
Where PitBridge fits, lightly
PitBridge does not connect to Rithmic and has no Rithmic integration. It connects to NinjaTrader 8 through a local NinjaScript AddOn, and NinjaTrader is what connects to Rithmic. So if you run a Rithmic-backed account in NinjaTrader, PitBridge can sit in front of the orders your agent or script proposes and refuse any order past the numeric limits you configure, before NinjaTrader routes anything to the Rithmic-backed account.
# your NinjaTrader account happens to be backed by Rithmic; PitBridge does not see or touch that
place_order account=sim instrument="MES 09-26" side=BUY qty=1 -> SUBMITTED, then FILLED filled_qty=1
place_order account=sim instrument="MES 09-26" side=BUY qty=8 -> BLOCKED reason_code=MAX_CONTRACTS_PER_ORDERReal tool name and reason code against the local daemon. Fills are synthetic simulation fills. The limit is yours; it is not a Rithmic setting and not a firm policy.
The important boundary, stated plainly: PitBridge enforces your own configured limits locally and keeps a local audit log. It does not read, know, or bypass any prop firm’s automation policy, and it makes no promise about passing an evaluation or keeping an account. What the engine refuses is on the guardrails page; how compliance responsibility splits between you and the software is in prop firm automation rules.
Honest status and the boundaries
Everything above describing PitBridge runs against paper and simulation accounts today. In the open core mode = "live" is intentionally out of reach: arm-live refuses, live execution ships separately as a paid, closed component, and no agent tool or API route can change that. Live execution has been in production on a funded futures account since 30 July 2026, behind an operator-run arm step. The NinjaScript AddOn is the Windows piece; the daemon and your agent run on macOS, Linux, or Windows.
So: Rithmic is the execution and market-data infrastructure under a large part of the futures and prop-firm world, reached through R|Trader Pro, R|API+, or a platform like NinjaTrader that connects to it. Automating on a Rithmic-backed account is usually a platform-routing exercise, gated not by Rithmic but by your firm’s written automation rules. The NinjaTrader 8 MCP bridge is where PitBridge fits that stack, guarding the orders locally before NinjaTrader routes them, and the quickstart is the uvx pitbridge setup. If a guarded local path on your NinjaTrader account is what you want, tell us your firm and platform on the waitlist. PitBridge is trading infrastructure, not financial advice: it enforces the limits you configure, does not know or bypass any firm’s rules, and does not promise any trading outcome. Futures trading carries a substantial risk of loss.