AI-native runtime for Robinhood Crypto 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
- Venue
- Robinhood Crypto
- Venue type
- Retail US crypto trading venue, separate entity from Robinhood Financial (equities) and Robinhood Markets Inc. (parent)
- Asset class
- Crypto spot only via the public API. No public API for US equities, options or futures.
- Supported products
- Robinhood Crypto Trading API (launched 30 May 2024) with two versions: v1 covers read endpoints and orders without fee tiers, v2 adds the fee-tier order endpoint for eligible jurisdictions.
- Geography
- United States only. Restricted to customers with an active Robinhood Crypto account.
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native Robinhood Crypto REST and WebSocket APIs. CCXT, Freqtrade and Hummingbot do not list Robinhood among their supported venues, so most production code is native HTTPS with Ed25519 signing or a community Python wrapper.
- AI workflow integration
- MCP control surface for Cursor, Claude Code, GitHub Copilot and CLI agents
- TradingHost role
- Runtime, deployment, logs, health checks, region selection, secrets, MCP control
- Robinhood role
- Crypto account, API credentials, market access, execution venue, custody for crypto balances
- Affiliation
- TradingHost is independent and is not affiliated with Robinhood Markets, Inc., Robinhood Financial LLC, or Robinhood Crypto, LLC.
Section 02 · What Robinhood offers
What Robinhood Crypto offers
The Robinhood Crypto Trading API launched on 30 May 2024 and is the only public programmatic surface Robinhood ships. It covers crypto spot for active Robinhood Crypto customers in the United States. There is no public API for Robinhood’s US equities, options, or futures products. Authentication uses Ed25519 signatures over a fixed message format; connectivity is REST plus WebSocket. CCXT, Freqtrade, and Hummingbot do not list Robinhood among their supported venues, so production strategies are typically written against the native API directly.
Markets and strategy patterns
- Small-account US crypto automation (no equities API needed)
- 24/7 spot rebalancing across BTC, ETH, SOL and majors
- Limit-ladder accumulation around a moving reference price
- Stop-loss and stop-limit risk overlays on a long-only book
- Fee-tier-aware order routing via the v2 fee-tier endpoint
- Cross-exchange arbitrage with a US-listed leg
API surface
- Product surfaces
- Robinhood Crypto Trading API for crypto spot. The exchange exposes account, holdings, products, quotes, and order endpoints; v2 adds a fee-tier-aware order endpoint. There is no public API for US equities, options, or futures.
- Connection methods
- REST (HTTPS) for account, market data and order endpoints, with WebSocket support documented in the same portal. No FIX. Some community tooling reverse-engineers private endpoints; that path violates Robinhood’s terms and is not what the Trading API gives you.
- Authentication
- Ed25519 keypair. Every authenticated request carries three headers: x-api-key, x-signature, and x-timestamp. The signed message is the concatenation of api_key, current_timestamp, request path, HTTP method, and body. The public key is registered through the API Credentials Portal on a desktop web browser; the private key never leaves your runtime.
- Order types
- market, limit, stop_loss, stop_limit. v1 places orders without fee tiers; v2 places orders that count toward eligible 30-day trading volume for the fee schedule.
For specifics, refer to Robinhood
Specific endpoints, rate-limit numbers, supported pairs, fee tiers and version history live in Robinhood’s documentation. Treat these as the source of truth.
- docs.robinhood.com/crypto/tradingRobinhood Crypto Trading API documentation portal
- robinhood.com/support/crypto-apiCustomer-facing overview of v1 and v2 endpoints
- robinhood.com/newsroom/robinhood-crypto-trading-apiAPI launch announcement, 30 May 2024
- robinhood.com/support/coin-availabilityLive coin list for Robinhood Crypto
Section 03 · Build with AI
Build your Robinhood Crypto strategy with AI
Pick an integration method, fork or start a strategy repo, and author it in an AI IDE. Cursor, Claude Code, GitHub Copilot and CLI-based AI agents all work with the same GitHub-native deployment loop.
Native Robinhood Crypto API
Direct REST and WebSocket calls with Ed25519 signing. The lowest-risk path for Robinhood Crypto because there is no framework abstraction to lag the venue’s feature set.
CCXT
CCXT does not list Robinhood among its supported exchanges. If a Robinhood connector lands in CCXT in future, this page is the place to track it.
Freqtrade or Hummingbot
Neither framework ships a Robinhood connector. Freqtrade depends on CCXT so it inherits the gap; Hummingbot’s exchange index has no Robinhood entry.
Custom or community client
Community Python clients exist (for example robin-stocks) and some target the official Crypto Trading API; verify each library uses the documented endpoints with Ed25519 and not reverse-engineered private endpoints before relying on it in production.
Framework support for Robinhood Crypto
Robinhood Crypto is not listed by CCXT, Freqtrade or Hummingbot, so the multi-exchange framework story that exists for Binance or Coinbase does not apply here. Strategies are written directly against the Robinhood Crypto Trading API, signed with Ed25519, and run on TradingHost without a framework intermediary.
✓ confirmed support per official framework docs. "no" indicates not officially documented as supported at publication. Workflow links target /workflows/ pages currently in authoring.
TradingHost does not force a framework. It runs your project.
Author with AI
Direct API code pairs naturally with AI IDEs. 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
Robinhood Crypto provides the exchange and API access. TradingHost provides the production environment where your Robinhood-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 Robinhood Crypto.
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 scratch
Point TradingHost at your existing Robinhood Crypto strategy repo, or start a new repo built around the native REST and WebSocket surface with Ed25519 signing.
- STEP 03
Deploy into a TradingHost container
Pick a region (EU or US-East), supply the environment values your strategy needs (Robinhood Crypto API key, base64-encoded Ed25519 private key), and deploy. TradingHost builds your container from the repo and runs your strategy on managed Kubernetes infrastructure. No local Docker install required.
- 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.
- STEP 05
Update and redeploy
Push changes to your GitHub main branch and TradingHost redeploys automatically.
Section 05 · Operational notes
Operational notes for Robinhood Crypto
Things that bite you when you actually run a Robinhood Crypto strategy in a containerised cloud runtime, not in Robinhood’s docs, not in framework READMEs. Every claim below is quoted or paraphrased from Robinhood’s own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · Scope
Robinhood’s only public API is crypto spot, US-only
Robinhood Crypto Trading API launched on 30 May 2024 and is the only public programmatic surface Robinhood publishes. It is restricted to active Robinhood Crypto customers in the United States. There is no public API for US equities, options, or futures. If your strategy needs equities or options, choose a venue with a documented API such as Alpaca, Interactive Brokers, Tradier or Tastytrade; do not depend on community libraries that reverse-engineer Robinhood’s private endpoints.
02 · Auth
Sign requests with Ed25519, not HMAC
Every authenticated request needs three headers: x-api-key, x-signature, and x-timestamp. The signed message is the concatenation of api_key, current_timestamp, request path, HTTP method, and request body (omit the body part if empty). Generate the signature with your Ed25519 private key. Libraries copy-pasted from a Binance or Coinbase HMAC example will fail with signature errors; pick a library that explicitly targets Ed25519 over a base64-encoded keypair.
03 · Versions
v1 places non-fee-tier orders, v2 places fee-tier orders
Robinhood publishes two versions of the Trading API. v1 covers all read endpoints plus an order endpoint without fee tiers. v2 adds the fee-tier-aware order endpoint, which is required for eligible jurisdictions to have their API trades count toward the published 30-day volume fee schedule. Pick the version per endpoint deliberately; mixing v1 orders with a v2 fee-tier expectation is the usual source of unexpected fee outcomes.
04 · Orders
Four order types: market, limit, stop_loss, stop_limit
The Trading API supports market, limit, stop_loss and stop_limit orders. There is no native bracket, OCO or trailing-stop primitive at the API layer; implement those at strategy level in your container. WebSocket streams are documented in the same portal as REST and are the right path for live quote updates rather than polling the REST quote endpoint on a tight loop.
05 · Frameworks
CCXT, Freqtrade and Hummingbot do not list Robinhood
At publication, the CCXT exchange list, Freqtrade documentation (which relies on CCXT) and the Hummingbot exchanges index all omit Robinhood Crypto. Strategy code that wants a multi-exchange framework will need to wrap the Robinhood API behind a compatible interface itself, or stay native. Re-check these three sources before relying on framework-based shortcuts.
06 · Credentials
Provision API keys from a desktop browser, store the private key in the runtime
API credentials are created through the Robinhood Crypto Settings portal on a desktop web browser, not in the mobile app. The portal registers your public Ed25519 key; the matching private key never leaves your control. Treat the private key as you would a wallet seed: keep it in GitHub-controlled secrets, inject at runtime, never commit to a repo, and rotate keys when staff leave or when a runtime is reprovisioned.
Section 06 · Built for
Built for
TradingHost Robinhood Crypto runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Solo US retail crypto traders
- Existing Robinhood Crypto customers automating their account
- Small-account 24/7 spot strategies
- Teams moving from VPS hosting to containerised deployment
Connecting GitHub and creating your first strategy is free.
Section 08 · FAQ
FAQ
No. TradingHost is independent and is not affiliated with Robinhood Markets, Inc., Robinhood Financial LLC, or Robinhood Crypto, LLC. Robinhood Crypto, LLC operates the crypto exchange and Trading API; the relationship is independent of TradingHost.
No. Your strategy code connects to Robinhood Crypto and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. API access is provided by Robinhood Crypto. You are responsible for your Robinhood Crypto account, API credentials, eligibility, and compliance with Robinhood’s terms.
No. Robinhood’s only public programmatic API is the Robinhood Crypto Trading API, which covers crypto spot. There is no documented public API for US equities, options, or futures. Community libraries that target Robinhood’s mobile-app endpoints rely on reverse-engineering and violate Robinhood’s terms of service. For automated equities or options, pick a venue with an officially supported API (Alpaca, Interactive Brokers, Tradier, Tastytrade).
No. At publication, CCXT does not list Robinhood among its supported exchanges. Freqtrade depends on CCXT so it inherits that gap. Hummingbot’s exchange index has no Robinhood connector. Strategies on Robinhood Crypto are written directly against the native API with Ed25519 signing.
Four order types: market, limit, stop_loss, and stop_limit. Bracket, OCO and trailing-stop logic must be implemented at the strategy level in your container.
Yes. TradingHost runs Python strategies; deploy your own repo against the native Robinhood Crypto Trading API with Ed25519 signing.
Yes. TradingHost supports any language that can run inside a container. Any language with an Ed25519 library will work against the Robinhood Crypto Trading API.
Create API credentials in the Robinhood Crypto Settings portal from a desktop web browser, generate an Ed25519 keypair, register the public key, then connect a GitHub repo containing your strategy to TradingHost. Linking a GitHub repo and creating a strategy is free; runtime plans are listed on the pricing page.
In your GitHub-controlled secrets workflow. The Ed25519 private key and the API key are injected into the runtime through GitHub repository secrets, environment secrets, or your own approved secret-management process. TradingHost does not need custody of either. See platform secrets for the full handling model.
Concatenate api_key + current_timestamp + request_path + http_method + body (omit body if empty). Sign the resulting string with your Ed25519 private key. Send three headers: x-api-key, x-signature, and x-timestamp. Robinhood verifies the signature against the public key registered for the API key.
Both versions cover the read endpoints (accounts, holdings, orders, products, quotes). v1 places orders without fee tiers. v2 places orders that count toward your eligible 30-day trading volume and use the published fee schedule. Pick v2 in eligible jurisdictions so API trades follow the same fee logic as Robinhood’s in-app trades.
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.
TradingHost runs in the EU and US-East regions. Robinhood Crypto is a US venue, so US-East is the natural choice for the lowest network round-trip to the API. See the regions page for routing details.
No. Robinhood limits Crypto Trading API access to active Robinhood Crypto customers in the United States. If you live outside the US, this venue is not a fit; pick a globally available crypto exchange instead.
Robinhood announced the Crypto Trading API on 30 May 2024 for active US Robinhood Crypto customers. v2 of the API added the fee-tier order endpoint after launch.
Treat them carefully. Libraries that target the official Crypto Trading API with Ed25519 are fine in principle; libraries that target Robinhood’s mobile-app private endpoints are reverse-engineered and violate Robinhood’s terms, with the risk of account termination. Before using any third-party Robinhood library in a TradingHost runtime, confirm it calls the documented Crypto Trading API endpoints, not the private mobile-app endpoints.
No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack, framework or AlgoBuilder.