Read time … min

AI-native runtime for Tastytrade options 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.

By the TradingHost engineering team

Section 01 · At a glance

At a glance

Broker
Tastytrade Inc.
Broker type
US-regulated options-first retail brokerage
Asset class
US options (lead product), US equities, US futures, crypto
Asset coverage
US listed options (OCC-cleared equity and index, single-leg and multi-leg up to four legs), US equities (NYSE, NASDAQ and US listings), US futures, options on futures, crypto (BTC, ETH and select others). Tastytrade’s brand identity is options-first; futures since 2018 and crypto since 2022.
Options approval
Tiered options trading levels. Approval level controls which strategies the broker accepts (covered calls and cash-secured puts at lower levels, uncovered and complex multi-leg at higher levels).
Runtime model
Containerised strategy runtime
Deployment source
GitHub
Languages
Any language that runs in a container
Common integrations
Tastytrade REST API, OAuth 2.0, Session API for direct login, community Python wrappers including tastytrade and tastyworks-api, 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
Tastytrade role
Broker account, API access, market data, execution venue, custody, settlement, tax reporting
Regulators
Tastytrade Inc.: SEC and FINRA registered broker-dealer (CRD 39562). SIPC member.
US retail
Yes. Sandbox / certification environment available for development.
Affiliation
TradingHost is independent and is not affiliated with Tastytrade Inc. or IG Group Holdings plc, Tastytrade’s parent since January 2021.

Section 02 · What Tastytrade offers

What Tastytrade offers

Tastytrade exposes a unified REST API covering options, equities, futures, options on futures, and crypto under one account credential. Multi-leg option orders up to four legs ship in a single request. The brand and audience are options-first; the API is not. Specific endpoint paths, request schemas and rate limits live in Tastytrade’s developer docs.

Markets and strategy patterns

  • Multi-leg options strategies (verticals, condors, butterflies, calendars)
  • 0DTE SPX and weekly XSP, SPY, QQQ options automation
  • Probability-weighted entry filters using broker-supplied Greeks
  • Defined-risk premium selling at scale
  • Cross-asset stock-plus-options pair strategies
  • Options-on-futures spreading (ES, /CL, /GC)
  • Crypto strategies under the same credential (BTC, ETH and select others)

API surface

Product surfaces
Tastytrade exposes a unified REST API covering options, equities, futures, options on futures, and crypto under a single account credential. Order endpoints accept up to four-leg complex option orders in a single request. Account streaming is delivered over a separate streaming endpoint.
Connection methods
HTTPS REST for orders, account state, options chains and history. Session-based authentication issues a session token used in subsequent requests; OAuth 2.0 is the recommended pattern for third-party applications. Real-time market data streams over a separate streamer endpoint.
Authentication
Two patterns: (1) Session API where the strategy POSTs username + password to a session endpoint and receives a session token used in subsequent requests; (2) OAuth 2.0 for applications acting on behalf of users. Sandbox / certification credentials are separate from production credentials.

For specifics, refer to Tastytrade

Specific endpoints, rate limits, options approval requirements and market data entitlements live in Tastytrade’s developer documentation. Treat these as the source of truth.

Section 03 · Build with AI

Build your Tastytrade 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 Tastytrade REST

    Direct HTTPS REST against the Tastytrade API. OAuth 2.0 or session-token authentication; multi-leg orders shipped in a single request body.

  • Community Python libraries

    Community-maintained Python wrappers around the REST surface. The tastytrade Python package and tastyworks-api (legacy) are commonly used; check repository activity before choosing.

  • Framework adapters

    Event-driven frameworks may ship a Tastytrade adapter. Coverage varies by adapter; confirm against the current docs of the framework you choose.

  • Custom connector

    Your own in-house engine or proprietary Tastytrade integration. The REST surface is small enough to wrap in a focused client.

Library and framework support for Tastytrade products

Tastytrade’s REST surface is wrapped by several community Python libraries. The tastytrade package is the most actively maintained; tastyworks-api still works for existing strategies but reflects the pre-rebrand brand identity. Custom connectors are practical because the API surface is small.

Library or frameworkSingle-legMulti-legWeeklies / 0DTEFuturesCrypto
Native RESTSupportedSupportedSupportedSupportedSupported
tastytrade (Python)SupportedSupportedSupportedPartially supportedPartially supported
tastyworks-api (legacy)SupportedSupportedSupportedPartially supportedPartially supported
Custom connectorSupportedSupportedSupportedSupportedSupported

✓ confirmed support per the library or surface docs. "check repo" indicates support is library-version dependent; verify against the current repository before deploying.

TradingHost does not force a library. It runs your project.

Author with AI

Multi-leg options strategies pair well with AI-IDE authoring: the strategy logic (choose strikes, choose expiry, choose delta target, choose risk-defined width) is repetitive boilerplate that an AI IDE can generate, while the strategy intent (filter, exit, sizing) is the part you actually author. 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

Tastytrade provides the broker account, API access and execution venue. TradingHost provides the production environment where your Tastytrade-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 Tastytrade.

TradingHost

  • Keeps the runtime online.
  • Surfaces logs and health checks.
  • Region selection.
  • Controlled deployment surface.

Deployment flow

  1. STEP 01

    Connect GitHub

    Authorise TradingHost to access your GitHub account.

  2. STEP 02

    Link a repo or start from a starter

    Point TradingHost at your existing Tastytrade strategy repo, or fork a tastytrade Python starter for a working baseline.

  3. STEP 03

    Deploy into a TradingHost container

    Pick a region (US-East is the natural pick for Tastytrade strategies because Tastytrade is US-only and its options matching engines sit on the US East Coast), supply your Tastytrade credentials as environment values, and deploy. TradingHost builds your container from the repo and runs your strategy on managed Kubernetes infrastructure.

  4. 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.

  5. STEP 05

    Update and redeploy

    Push changes to your GitHub main branch and TradingHost redeploys automatically. A certification-environment-keyed deployment is the natural test environment before promoting to production credentials.

Deploy

Section 05 · Operational notes

Operational notes for Tastytrade

Things that bite you when you actually run a Tastytrade strategy in a containerised cloud runtime. Every claim below is quoted or paraphrased from Tastytrade’s own documentation or a primary regulator source; the deployment-side guidance is from running these strategies on TradingHost.

  1. 01 · Session API

    Two auth patterns: Session API (username + password) and OAuth 2.0

    Tastytrade authenticates via either a Session API (POST username + password to a session endpoint, receive a session token used in subsequent requests) or OAuth 2.0 for applications acting on behalf of users. For your own strategy in a private repo, the Session API is the shorter path; for any application that other users will authenticate against, OAuth 2.0 is the right pattern. Session tokens expire and must be refreshed.

    SourceTastytrade developer documentation

  2. 02 · Certification env

    Certification environment for sandbox testing

    Tastytrade exposes a certification environment that mirrors production endpoint shapes with separate credentials and separate test balances. Keep production and certification credentials in distinct TradingHost Secrets entries; promoting a strategy is a host plus credential swap.

    SourceTastytrade developer documentation

  3. 03 · Multi-leg orders

    Multi-leg option orders accept up to four legs per request

    Tastytrade’s order endpoint accepts complex option orders with up to four legs in a single request. Vertical spreads, iron condors, butterflies, calendars and diagonals all fit inside the four-leg envelope. Strategies that require five or more legs need to decompose into multiple orders, with the implied legging risk that creates.

    SourceTastytrade developer documentation

  4. 04 · Options approval

    Options approval is per account and gates the order endpoint

    Options trading on Tastytrade requires a tiered approval. Approval level controls which strategies the broker accepts; orders that exceed your level are rejected at the broker, not at TradingHost. Plan strategies around your approved level or upgrade with Tastytrade before deploying.

    SourceTastytrade help, options trading

  5. 05 · Pattern Day Trader

    PDT applies on margin accounts under $25,000 per FINRA Rule 4210

    FINRA Rule 4210 applies to Tastytrade margin accounts under $25,000: four or more day trades within five business days trips PDT, restricting further day trading. Tastytrade enforces this at the broker, not at the runtime. Cash accounts are not subject to PDT but are subject to settlement-cycle constraints.

    SourceFINRA Rule 4210

Section 06 · Built for

Built for

TradingHost Tastytrade runtimes are best suited to:

  • Developers building strategies in AI IDEs (Cursor, Claude Code)
  • Mechanic-style probability-driven options traders
  • Defined-risk multi-leg premium sellers
  • 0DTE and weekly automation specialists
  • Stock-plus-options paired-strategy authors

Connecting GitHub and creating your first strategy is free.

Section 08 · FAQ

FAQ

No. TradingHost is independent and is not affiliated with Tastytrade Inc. or IG Group Holdings plc, Tastytrade’s parent since January 2021.

No. TradingHost is a runtime for trading strategy code. Tastytrade Inc. is the broker-dealer, registered with the SEC and FINRA (CRD 39562) and a SIPC member. Your account, custody, market access, settlement and tax reporting all sit with Tastytrade.

No. Your strategy code connects to Tastytrade and sends order instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.

No. Tastytrade API access is provided by Tastytrade. You are responsible for your Tastytrade account, credentials, OAuth registrations and compliance with Tastytrade’s terms.

Yes. Tastytrade’s order endpoint accepts up to four-leg complex option orders in a single request. Vertical spreads, iron condors, butterflies, calendars and diagonals all fit. Approval level on your Tastytrade account controls which strategies the broker accepts; TradingHost does not bypass approval.

Yes, subject to your options approval level. SPX is cash-settled and European-style, so assignment risk is different from physically-settled American-style options like SPY. Tastytrade exposes 0DTE chains through the same options chain endpoint as longer-dated contracts.

Yes. Tastytrade offers US equities, US futures (since 2018), options on futures, and crypto (BTC, ETH and select others, since 2022) under the same account credential. The Trading API surface is unified across these assets; only the order endpoint and instrument symbology differ.

Any language that runs in a container. Tastytrade’s API is HTTPS REST, so any HTTP client can talk to it. Community Python wrappers including tastytrade and tastyworks-api are popular.

Connect your GitHub repo containing the strategy code, link it to TradingHost, and deploy. Use a certification-environment deployment as the test environment, and promote to production credentials 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 credentials. See platform secrets for the full handling model.

No. Strategies should never need withdrawal or money-movement permissions. The credentials only need access for order placement and market data.

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. Assignment is delivered by the OCC through Tastytrade; your strategy can react to assignment events but cannot prevent them. Exercise-by-exception is an OCC default that Tastytrade configures per account. TradingHost does not override either.

No. The PDT rule (FINRA Rule 4210) is enforced by Tastytrade, not by TradingHost. Margin accounts under $25,000 are subject to PDT restrictions on day trading.

TradingHost runs in the EU and US-East regions. Tastytrade is US-only, so US-East is the natural pick for proximity to US options matching engines. 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.