AI-native runtime for Tradier trading 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
- Tradier Brokerage Inc.
- Broker type
- US-regulated retail broker with an options-developer-first API
- Asset class
- US equities, US options, ETFs
- Asset coverage
- US equities (NYSE, NASDAQ, ARCA, BATS, IEX listings), US listed options (single-leg and multi-leg, OCC-cleared), ETFs. Tradier separately offers crypto through Tradier Brokerage; the Trading API surface documented here is equities and options.
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Tradier REST API, Tradier WebSocket streaming, python-tradier and community SDKs, NautilusTrader, native HTTP clients, custom connectors
- 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
- Tradier role
- Broker account, API access, market data, execution venue, custody, settlement, tax reporting
- Regulators
- Tradier Brokerage Inc.: SEC and FINRA registered broker-dealer (CRD 142315). SIPC member.
- US retail
- Yes. Sandbox environment available for development.
- Affiliation
- TradingHost is independent and is not affiliated with Tradier Brokerage Inc. or Tradier Inc.
Section 02 · What Tradier offers
What Tradier offers
Tradier exposes a REST and WebSocket API with options-developer audience as the positioning. Multi-leg orders, options chain endpoints with Greeks, and a sandbox that mirrors production are the strongest distinguishing features. Specific endpoint paths and request shapes live in Tradier’s documentation.
Markets and strategy patterns
- Multi-leg US options strategies (verticals, condors, butterflies)
- Weekly and 0DTE SPX, QQQ, SPY options automation
- Sandbox-validated strategies promoted with one config swap
- WebSocket-streamed quotes and option chain monitoring
- Programmatic options chain Greeks consumption
- Equity-plus-options paired strategies under one credential
API surface
- Product surfaces
- Trading API for US equities, US options and ETFs. Market Data API for quotes, options chains (with Greeks), historical data and time-and-sales. Streaming API over WebSocket for real-time quotes and account events. Sandbox endpoints mirror production with the same routes.
- Connection methods
- HTTPS REST for orders, account state, options chains and account history. WebSocket streaming for live market data and account events. Both production (api.tradier.com) and sandbox (sandbox.tradier.com) use the same endpoint shapes; only the host and access token change.
- Authentication
- OAuth 2.0 bearer token in the Authorization header. Tokens are issued per app and per environment (sandbox vs production), and can be scoped to read, trade or market-data permissions. A sandbox token cannot place a production order.
For specifics, refer to Tradier
Specific endpoints, rate limits, options approval requirements and market data entitlements live in Tradier’s documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your Tradier 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 Tradier REST and WebSocket
Direct HTTPS REST against api.tradier.com (production) or sandbox.tradier.com. WebSocket streaming for live quotes and account events. OAuth 2.0 bearer-token auth.
Community Python libraries
Community-maintained Python wrappers around the REST and WebSocket surfaces. python-tradier is one of the actively maintained options; pick a library that fits your strategy stack.
Framework adapters
NautilusTrader and other event-driven frameworks expose Tradier through broker adapters. Coverage is option-strategy-friendly because Tradier exposes multi-leg orders natively.
Custom connector
Your own in-house trading engine or proprietary Tradier integration. Tradier’s REST surface is small enough to wrap in a few hundred lines of Python or TypeScript.
Library and framework support for Tradier products
Tradier’s REST and WebSocket surfaces are small enough that custom connectors are practical alongside community libraries. NautilusTrader’s adapter coverage varies by release; verify against the current adapter docs before relying on specific cells.
✓ confirmed support per the library or surface docs. "check adapter" indicates the framework integration’s coverage varies by release; verify against current docs.
TradingHost does not force a library. It runs your project.
Author with AI
Tradier’s small, well-documented surface makes it a strong target for AI-assisted authoring: the REST API is a thin wrapper around order placement, account state and options chain queries, all of which an AI IDE can scaffold from documentation links. 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
Tradier provides the broker account, API access and execution venue. TradingHost provides the production environment where your Tradier-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 Tradier.
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 Tradier strategy repo, or fork a python-tradier starter for a working baseline.
- STEP 03
Deploy into a TradingHost container
Pick a region (US-East is the natural pick for US equity and options strategies), supply your Tradier access token as an environment value, and deploy. TradingHost builds your container from the repo and runs your strategy on managed Kubernetes infrastructure. Sandbox-keyed deployments validate end-to-end before you promote with a production token.
- 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, so Cursor, Claude Code or a CLI agent can read deployment state and manage the runtime alongside you. 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 sandbox-keyed deployment is the natural test environment before promoting to a production token.
Section 05 · Operational notes
Operational notes for Tradier
Things that bite you when you actually run a Tradier strategy in a containerised cloud runtime. Every claim below is quoted or paraphrased from Tradier’s own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · OAuth2 bearer
Access tokens are bearer tokens, per app and per environment
Tradier authenticates via OAuth 2.0 bearer tokens in the Authorization header. Tokens are issued per application and per environment, so a sandbox token cannot place a production order and vice versa. The same source code reads the token from a TradingHost Secrets entry; keep sandbox and production tokens in separate secrets.
02 · Sandbox
sandbox.tradier.com mirrors api.tradier.com endpoint-for-endpoint
The sandbox environment exposes the same endpoint paths and request shapes as production, with sandbox-issued tokens and a sandbox-only account balance. Promoting a sandbox-validated strategy to live is a configuration swap (host plus token), not a rewrite. This is one of Tradier’s strongest developer-experience features.
03 · Multi-leg orders
Multi-leg option orders use the order class field on a single request
Tradier exposes single-leg, multi-leg, OTOCO and other order classes through one orders endpoint with the class field specifying construction. The body carries per-leg specifications. Tradier’s order endpoint shape is more compact than the per-leg-array endpoints some brokers expose; the trade-off is more careful body construction. Refer to the orders documentation for the exact field layout.
04 · Market data
Real-time data is entitlement-gated; delayed quotes are the default
Tradier accounts receive delayed quotes by default. Real-time market data requires explicit entitlement on the account, which is enabled through Tradier rather than through TradingHost. Strategies that depend on top-of-book real-time data should confirm entitlement before deploying.
05 · Options approval
Options approval is per account and gates the order endpoint
Options trading on Tradier requires a separate approval step beyond brokerage onboarding. Approved level controls which strategies the order endpoint accepts; orders that exceed the approved level are rejected at the broker. Plan strategies around your approved level or upgrade approval with Tradier before deploying.
Section 06 · Built for
Built for
TradingHost Tradier runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Options-strategy automators (verticals, condors, calendars)
- Weekly and 0DTE systematic options traders
- Python developers building API-first equity tools
- Solo quants and small trading shops
Connecting GitHub and creating your first strategy is free.
Section 08 · FAQ
FAQ
No. TradingHost is independent and is not affiliated with Tradier Brokerage Inc. or Tradier Inc.
No. TradingHost is a runtime for trading strategy code. Tradier Brokerage Inc. is the broker-dealer, registered with the SEC and FINRA (CRD 142315) and a SIPC member. Your account, custody, market access, settlement and tax reporting all sit with Tradier.
No. Your strategy code connects to Tradier and sends order instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. Tradier API access is provided by Tradier. You are responsible for your Tradier account, application registration, OAuth tokens and compliance with Tradier’s terms.
Yes. Tradier exposes a multi-leg orders endpoint that accepts vertical spreads, iron condors, butterflies, calendars and diagonals. Approval level on your Tradier account controls which strategies the broker accepts; TradingHost does not bypass approval.
Yes, subject to your options approval level and market data entitlements. Tradier exposes the chains for weekly and 0DTE expiries through the same options chain endpoint as monthly contracts. Real-time data may require an entitlement upgrade.
Any language that runs in a container. Tradier’s API is HTTPS REST plus WebSocket streaming, so any HTTP and WebSocket client can talk to it. Community Python libraries (including python-tradier) are popular; Node.js, Go, Rust and others work the same way.
Connect your GitHub repo containing the strategy code, link it to TradingHost, and deploy. Use a sandbox-token deployment as the test environment and promote to a production token once the strategy is stable. Linking GitHub and creating a strategy is free; runtime plans are listed 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 the bearer tokens. See platform secrets for the full handling model.
No. Strategies should never need withdrawal or money-movement permissions. The access token only needs the scopes required for order placement and market data access.
Yes. TradingHost supports MCP-based control for AI IDEs including Cursor, Claude Code, GitHub Copilot and CLI-based AI agents. AI tools can inspect deployments, review logs, restart strategies and manage runtime workflows. MCP is a control and observability surface, not the trade execution path. See the MCP control surface for the full picture.
No. The PDT rule (FINRA Rule 4210) is enforced by Tradier, not by TradingHost. Margin accounts under $25,000 are subject to PDT restrictions on day trading.
No. Your 1099 forms come from Tradier at year-end, not from TradingHost.
No. SIPC covers your Tradier brokerage account up to $500,000 (including $250,000 in cash) under SIPC member protection. 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 closest to US equities and US options matching engines, which is the natural pick for Tradier strategies. See the regions page for routing and proximity details.
No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack, framework or AlgoBuilder.