AI-native runtime for TradeStation strategies
Author in Cursor, Claude Code or any AI IDE. Deploy from GitHub into a managed cloud runtime with first-class MCP control, logs and region selection.
Section 01 · At a glance
At a glance
- Broker
- TradeStation Securities, Inc.
- Broker type
- US-regulated multi-product broker, active-trader-first
- Asset class
- US equities, US options, US futures, options on futures, FX, crypto
- Asset coverage
- US equities (NYSE, NASDAQ, ARCA, BATS, IEX listings), US listed options (OCC-cleared equity and index, single-leg and multi-leg), US futures and options on futures (CME, ICE US, COMEX, NYMEX, CFE), FX (limited spot pairs), crypto. TradeStation also offers EasyLanguage strategy automation on its desktop platform, which is separate from the REST API surface documented here.
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- TradeStation REST API, WebSocket streaming, OAuth 2.0, native HTTP clients, NautilusTrader, Backtrader, custom connectors, EasyLanguage (desktop-only)
- AI workflow integration
- MCP control surface for Cursor, Claude Code, GitHub Copilot and CLI agents
- TradingHost role
- Runtime, deployment, logs, health checks, region selection, MCP control
- TradeStation role
- Broker account, API access, market data, execution venue, custody, settlement, tax reporting, margin management
- Regulators
- TradeStation Securities, Inc.: SEC and FINRA registered broker-dealer (CRD 12727), CFTC/NFA registered Futures Commission Merchant (NFA 0207302). SIPC member.
- US retail
- Yes. Simulated trading environment available for development.
- Affiliation
- TradingHost is independent and is not affiliated with TradeStation Securities, Inc. or Monex Group, Inc., TradeStation's parent since 2011.
Section 02 · What TradeStation offers
What TradeStation offers
TradeStation exposes a REST and WebSocket API covering US equities, options, futures, options on futures, FX (limited) and crypto. OAuth 2.0 with refresh tokens handles authentication. Simulated trading uses a separate credential against the same endpoint shapes. Specific endpoint paths, request schemas and rate limits live in TradeStation's developer documentation.
Markets and strategy patterns
- Active-trader equity strategies on REST + WebSocket
- CME and ICE futures and options-on-futures automation
- US options multi-leg strategies under one credential
- Crypto strategies through the same Trading API
- Simulated-trading account for parallel risk-off testing
- OAuth 2.0 refresh-token workflows from cloud containers
API surface
- Product surfaces
- Trading API for US equities, US options, US futures, options on futures, FX (limited) and crypto. Market Data API for quotes, options chains, historical bars and time-and-sales. Streaming API over WebSocket for real-time quotes and account events. Simulated trading uses a separate account and mirrors production endpoint shapes.
- Connection methods
- HTTPS REST for orders, account state, options chains, futures contracts and history. WebSocket streaming for live market data and account events. Both production (api.tradestation.com) and simulation use the same endpoint shapes with different credentials.
- Authentication
- OAuth 2.0 with refresh tokens. Application client ID and secret are issued through TradeStation's developer portal; users authenticate the application against their TradeStation account, and the application stores refresh tokens to obtain new access tokens.
For specifics, refer to TradeStation
Specific endpoints, rate limits, options approval requirements and market data entitlements live in TradeStation's documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your TradeStation strategy with AI
Pick an integration method, fork a starter, and author your strategy in an AI IDE. Cursor, Claude Code, GitHub Copilot and CLI-based AI agents all work with the same GitHub-native deployment loop.
Native TradeStation REST and WebSocket
Direct HTTPS REST against api.tradestation.com. WebSocket streaming for live quotes and account events. OAuth 2.0 with refresh tokens.
Python and Node clients
Custom Python or Node.js clients wrap TradeStation REST endpoints. The auth flow (OAuth 2.0 refresh tokens) is the part most worth getting right; the order endpoints are small and straightforward.
Framework adapters
NautilusTrader and Backtrader expose TradeStation through community adapters. Coverage varies by release; confirm against the adapter's current docs.
Custom or EasyLanguage bridge
EasyLanguage is TradeStation's desktop strategy language; it runs in the TradeStation desktop, not in cloud containers. If you have EasyLanguage code, bridge to the REST API for cloud-hosted execution.
Library and framework support for TradeStation products
TradeStation’s REST and WebSocket surface is small enough that custom connectors are practical. NautilusTrader and Backtrader adapters provide higher-level event-driven entry points; verify capability against the adapter’s current docs.
✓ confirmed support per the library or surface docs. "check adapter" indicates support varies by adapter release; verify against the integration's current docs.
TradingHost does not force a library. It runs your project.
Author with AI
The TradeStation REST surface is well-documented and the auth flow is standard OAuth 2.0, which makes it a good AI-IDE target. The TradingHost MCP control surface closes the loop: AI tools can inspect deployments, review logs and manage the runtime alongside you, never the trade execution path.
Section 04 · Run on TradingHost
Run your code on TradingHost
TradeStation provides the broker account, API access and execution venue. TradingHost provides the production environment where your TradeStation-connected strategy runs.
Instead of running strategy code on a laptop, desktop machine, generic VPS or manually configured server, you deploy from GitHub into a TradingHost-managed container runtime.
You
- Your repo contains your code.
- Your deployment defines how it runs.
- Your strategy connects to TradeStation.
TradingHost
- Keeps the runtime online.
- Surfaces logs and health checks.
- Region selection.
- Controlled deployment surface.
Deployment flow
- STEP 01
Connect GitHub
Authorise TradingHost to access your GitHub account.
- STEP 02
Link a repo or start from a starter
Point TradingHost at your existing TradeStation strategy repo, or fork a TradeStation REST + OAuth2 starter for a working baseline.
- STEP 03
Deploy into a TradingHost container
Pick a region (US-East is the natural pick for US equities, options and CME futures; EU covers European session strategies if you route through Eurex), supply your TradeStation OAuth client ID, secret and refresh token as environment values, and deploy. TradingHost runs your strategy on managed Kubernetes infrastructure.
- STEP 04
Monitor logs and health
Watch live logs, health and runtime state from the TradingHost dashboard. The same surface is reachable through MCP from any AI IDE. Trade execution stays on the strategy code path, not on MCP.
- STEP 05
Update and redeploy
Push changes to your GitHub main branch and TradingHost redeploys automatically. A simulated-account-keyed deployment is the natural test environment before promoting to live.
Section 05 · Operational notes
Operational notes for TradeStation
Things that bite you when you actually run a TradeStation strategy in a containerised cloud runtime. Every claim below is quoted or paraphrased from TradeStation’s own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · OAuth 2.0
Refresh-token flow is the cloud-friendly auth pattern
TradeStation authenticates via OAuth 2.0 with refresh tokens. The application client ID and secret are issued through TradeStation's developer portal; users authenticate the application against their TradeStation account once, then the application persists a refresh token and uses it to obtain short-lived access tokens. Store the refresh token in TradingHost Secrets; the access token can be regenerated in-container at startup.
02 · Simulated trading
Simulated accounts are real accounts with simulated balances
TradeStation's simulated trading runs against the same endpoint shapes as live trading; the difference is the account number and balance. Credentials are issued separately. Promote a strategy from simulated to live by swapping the account number and refresh token in your TradingHost environment values.
03 · Futures account
Futures trading requires a separate account designation
TradeStation separates equities and futures accounts at the account-designation level because of CFTC/NFA requirements for Futures Commission Merchants. A user with an equities account who wants to trade futures completes a separate application. The Trading API exposes orders by account ID, so the strategy targets the correct account designation.
04 · Options approval
Options approval is per account and tiered
Options trading on TradeStation requires a tiered approval. Approval level controls which strategies the order endpoint accepts; orders that exceed the approved level are rejected by the broker. Plan strategies around your approved level or upgrade with TradeStation before deploying.
SourceTradeStation options05 · EasyLanguage vs REST
EasyLanguage runs in the TradeStation desktop, not in cloud containers
EasyLanguage is TradeStation's desktop strategy automation language and runs inside the TradeStation desktop application. It is not a programmatic API surface a cloud container can call directly. Strategies authored in EasyLanguage that need to run cloud-hosted are typically re-implemented against the REST API, or bridged via a TradeStation desktop running on a separate host.
Section 06 · Built for
Built for
TradingHost TradeStation runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Active-trader systematic equity desks
- Futures and options-on-futures strategy operators
- EasyLanguage developers bridging to REST + cloud
- Quants moving from desktop strategy code to cloud-hosted runtimes
Connecting GitHub and creating your first strategy is free.
Section 08 · FAQ
FAQ
No. TradingHost is independent and is not affiliated with TradeStation Securities, Inc. or Monex Group, Inc.
No. TradingHost is a runtime for trading strategy code. TradeStation Securities, Inc. is the broker-dealer, registered with the SEC and FINRA (CRD 12727), CFTC and NFA (NFA ID 0207302), and a SIPC member. Your account, custody, market access, settlement and tax reporting all sit with TradeStation.
No. Your strategy code connects to TradeStation and sends order instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. TradeStation API access is provided by TradeStation. You are responsible for your TradeStation account, OAuth application registration, refresh tokens and compliance with TradeStation's terms.
Yes, subject to TradeStation futures account approval. Futures trading requires a separate account designation beyond brokerage onboarding because of CFTC and NFA requirements.
Not directly. EasyLanguage runs inside the TradeStation desktop application; it is not a programmatic API surface a cloud container can call. To cloud-host an EasyLanguage strategy, re-implement the logic against TradeStation's REST API or run the desktop on a separate host that the TradingHost container coordinates with.
Yes, subject to TradeStation options approval. Multi-leg orders are submitted through the same order endpoint with the appropriate option type and legging fields. Approval level controls which strategies the broker accepts.
Any language that runs in a container. TradeStation's API is HTTPS REST plus WebSocket streaming, so any HTTP and WebSocket client can talk to it.
Register an application in TradeStation's developer portal to get a client ID and secret. Run the OAuth authorisation flow once to obtain a refresh token. Connect your GitHub repo containing the strategy code, link it to TradingHost, and deploy with the refresh token in your TradingHost Secrets. Linking GitHub and creating a strategy is free; runtime plans are on the pricing page.
In your GitHub-controlled secrets workflow. TradingHost reads them at runtime through GitHub repository secrets, environment secrets or your own approved secret-management process. TradingHost does not need custody of your client ID, client secret or refresh token. See platform secrets for the full handling model.
No. Strategies should never need withdrawal or money-movement permissions.
Yes. TradingHost supports MCP-based control for AI IDEs including Cursor, Claude Code, GitHub Copilot and CLI-based AI agents. MCP is a control and observability surface, not the trade execution path. See the MCP control surface.
No. The PDT rule (FINRA Rule 4210) is enforced by TradeStation, not by TradingHost. Margin accounts under $25,000 are subject to PDT restrictions on day trading.
No. Your 1099 forms come from TradeStation at year-end, not from TradingHost.
No. SIPC covers your TradeStation brokerage account up to $500,000 (including $250,000 in cash). TradingHost's runtime is not SIPC-insured because TradingHost is not a broker.
TradingHost runs in the EU and US-East regions. US-East is the natural pick for US equities, options and CME futures matching engines. See the regions page.
No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack, framework or AlgoBuilder.