Tradier vs Tastytrade API 2026

Tradier and tastytrade are the two options-first broker APIs retail AI traders reach for, and they publish their limits differently: Tradier states per-scope REST caps (120 requests/minute for market data and standard endpoints, 60/minute for trading in production), while tastytrade throttles REST by "reasonable thresholds" with no published quota but documents hard caps on its DXLink streamer (5 concurrent sessions, 25,000 subscriptions per session, 10,000 subscription changes per minute). Both were re-checked against the brokers' developer docs on 2026-10-11¹². Plan Tradier throughput from its numbers; plan tastytrade around streaming and back off on 429s. Compare the field in the Broker API Comparator.

How do Tradier and tastytrade compare?

What are tastytrade's actual limits?

Its rate-limit guide says REST requests are throttled by "reasonable thresholds rather than a published per-endpoint quota", and that 429 responses carry no rate-limit headers². Too many failed logins block the IP for about eight hours². The streamer is different: DXLink allows 5 concurrent sessions per set of credentials, 25,000 subscriptions per session, 100 subscriptions each for the Candle, Order and Series events, and 10,000 subscription changes per minute². The quote snapshot endpoint takes up to 100 symbols per call².

For a client-side ceiling, tastytrade points to the per-endpoint, per-second limits its own MCP server applies, plus a 50 requests/second global cap².

What are Tradier's limits?

Tradier enforces limits per minute and per access token: in production, standard and market-data endpoints get 120 requests per minute and trading gets 60; the sandbox allows 60 across all classes¹. Each response carries X-Ratelimit-Allowed, X-Ratelimit-Used, X-Ratelimit-Available and X-Ratelimit-Expiry headers, so a client can throttle from live counts¹. The 60-per-minute trading cap is the number to design around.

How do the sandboxes differ?

tastytrade's sandbox is a full copy of the API with simulated money at api.cert.tastyworks.com, but it does not serve market data (market-data routes return HTTP 502), fills are synthetic (market orders fill at $1; limit orders under $3 fill, at or above $3 never fill), credentials are a separate OAuth application, and the environment resets every 24 hours⁴. A common pattern is to read quotes from production and send orders to the sandbox. Tradier's sandbox shares the production surface with 15-minute-delayed data and a 60-per-minute limit¹⁸.

Which should an options agent use?

• Published REST limits to plan against: Tradier (120 market data / 60 trading).
• Heavy streaming of quotes and Greeks: tastytrade, within its DXLink caps.
• Throwaway order testing with no data dependency: tastytrade's sandbox, aware of its synthetic fills.
• An official MCP server for an LLM agent: tastytrade ships one with a dry-run-first confirmation model⁷.

Both are options-first; the deciding factors are how you consume data (polling versus streaming) and which brokerage you already use.

Connects to

• Tradier API Rate Limits and Pricing 2026: the Tradier spec page.
• Alpaca vs Tradier API 2026: Tradier against the free-data alternative.
• Broker API Comparator: the broader broker field.
• Why LLMs Fail Options Greeks: what goes wrong when a model reasons over the options-chain data.

References

Footnotes

1. Tradier. "Rate Limiting" (production: standard and market data 120/min, trading 60/min; sandbox 60/min; per minute, per access token; X-Ratelimit headers). Read 2026-10-11. https://docs.tradier.com/docs/rate-limiting ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷

2. tastytrade. "Rate limits & backoff" (REST throttled by reasonable thresholds; 429 without headers; ~8-hour IP block after failed logins; DXLink caps; 100-symbol snapshot; MCP server per-endpoint ceilings plus 50/sec global cap). Read 2026-10-11. https://developer.tastytrade.com/docs/guides/rate-limits-and-backoff ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸

3. tastytrade. "OAuth2 authentication" (refresh token exchanged for a 15-minute access token). Read 2026-10-11. https://developer.tastytrade.com/docs/authentication/oauth2 ↩

4. tastytrade. "Sandbox" (base URLs; synthetic fills; no market data; separate credentials; 24-hour reset). Read 2026-10-11. https://developer.tastytrade.com/docs/sandbox ↩ ↩²

5. Tradier. "Pricing" (Lite $0, Pro $10/month, Pro Plus $35/month; API access included). Read 2026-10-11. https://tradier.com/pricing ↩

6. Tradier. "Tradier MCP" (hosted server over Streamable HTTP; tools for profile, balances, positions, real-time market data, documentation search and order placement). Read 2026-10-18. https://docs.tradier.com/docs/tradier-mcp ↩

7. tastytrade. "Developer Docs" home (Open API for equities, options, futures, futures options and crypto; MCP server with dry-run-first confirmation). Read 2026-10-11. https://developer.tastytrade.com/ ↩ ↩²

8. Tradier. "Market Data" (real-time data for brokerage account holders; delayed data 15 minutes). Read 2026-10-11. https://docs.tradier.com/docs/market-data ↩

Frequently asked questions

Tradier vs tastytrade: which has better-documented rate limits?

Tradier publishes REST caps: 120 requests/minute for market data and standard endpoints and 60/minute for trading in production. tastytrade publishes no REST quota (it returns 429 above reasonable thresholds) but documents DXLink streaming caps: 5 sessions, 25,000 subscriptions per session and 10,000 subscription changes per minute (read 2026-10-11).

Does the tastytrade sandbox serve market data?

No. Its market-data routes return HTTP 502 in the sandbox, fills are synthetic (market orders at $1, limit orders under $3 fill), credentials are separate from production, and the environment resets every 24 hours.

Is the Tradier API free?

API access is included on every Tradier plan: Lite ($0/month), Pro ($10/month) and Pro Plus ($35/month). Commissions differ by plan.