AI-native runtime for Coinbase trading strategies

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

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

No. TradingHost is the cloud runtime where your strategy code runs. We do not provide signals, AI prediction models or pre-built bots. With TradingHost you write or generate the strategy yourself (often with Cursor or Claude Code), keep it in GitHub as your code, and use TradingHost to run it in production. 3Commas, Cryptohopper and similar products own the strategy logic; TradingHost runs your strategy.

AWS and DigitalOcean give you raw compute. You handle OS updates, container orchestration, log shipping, secret rotation, region failover and uptime monitoring yourself. TradingHost gives you a managed runtime purpose-built for trading strategies: GitHub-native deployment, MCP-driven control from AI IDEs, log and health surfaces out of the box. If you want to operate the infrastructure yourself, AWS works. If you want the runtime as a managed service, TradingHost is the shorter path.

Yes. TradingHost runs Python strategies; pick the framework runtime that matches your stack or deploy your own repo.

Yes. TradingHost supports any language that can run inside a container.

Yes. CCXT ships unified `coinbase` and `coinbaseexchange` classes that cover spot trading on Coinbase Advanced and the institutional Coinbase Exchange. Coinbase International Exchange perpetuals are not exposed as a first-class CCXT swap market today, so for INTX perps route through the native Coinbase INTX REST or FIX API. Drop your CCXT strategy into a container, point it at GitHub, and TradingHost runs it like any other Python or Node project. See the CCXT framework runtime for the full setup story.

TradingHost is venue-agnostic at the runtime level: any code that can authenticate against a Coinbase surface can run inside a container. CFM-listed US perpetual-style futures (BTC and ETH, including the nano contracts live since July 21, 2025) are reached via Coinbase Advanced once your account is eligible. Coinbase International Exchange perps require INTX onboarding under Coinbase Bermuda and are restricted to eligible non-US institutions. Eligibility is decided by Coinbase, not TradingHost; we run the strategy code that authenticates against whichever venue your account can access.

Yes, if your project is designed that way. You can run multiple strategy processes or services inside one runtime, or separate them into different runtimes for isolation and operational clarity. See the TradingHost runtime page for the multi-strategy model.

The fastest path is to fork a TradingHost framework runtime: CCXT or Hummingbot for a ready-to-deploy project. Or connect your own GitHub strategy repo. Linking a GitHub repo 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 your CDP API key, INTX access-signature credentials or Prime credentials. See platform secrets for the full handling model.

Coinbase deprecated the standalone Coinbase Pro REST and WebSocket API on June 6, 2024 and stopped issuing new Pro keys at that point. From February 5, 2025 Coinbase began expiring the remaining legacy retail API keys. Any strategy still wired to Pro-style HMAC keys returns 401s and cannot be revived. The fix is to generate a new key in the Coinbase Developer Platform (CDP), default to Ed25519 unless your SDK forces ECDSA P-256, and update your strategy to sign Advanced Trade requests as JWTs. See the Operational notes section above for the full deprecation context.

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.

Both. The MCP control surface works equally well from CLI-based agents (Claude Code CLI, custom MCP clients, scripted MCP calls) and from inside an IDE. The GitHub-native deployment loop also works without any AI tooling: a regular git push to your main branch triggers a redeploy.

The runtime detects the crash and exposes the relevant logs and health information. Where supported, the affected strategy can be restarted without disrupting other strategies running in the same container. Your strategy code is still responsible for safe error handling, duplicate-order protection and risk controls. See observability for the logs and health surface.

Coinbase’s most common auth failure is HTTP 401 on the Advanced Trade REST or WebSocket API. The usual causes are an expired JWT (Coinbase JWTs only live for 2 minutes), an ECDSA key being used with a library that defaults to Ed25519 or vice versa, an API key still inside its activation delay, or a legacy Coinbase Pro key that was retired in June 2024. Generate a fresh CDP key, pick Ed25519 unless your SDK forces ECDSA, and regenerate the JWT on every request. See the Operational notes section above for the full guidance.

The Advanced Trade sandbox host is `https://api-sandbox.coinbase.com/api/v3/brokerage/`. It mocks Accounts and Orders endpoints only. Market data, products, fees and portfolio endpoints are not in the sandbox, so end-to-end strategy testing has to combine sandboxed order flow with production read-only market data, or run against a local mock. INTX and Prime have their own institutional onboarding paths rather than a public sandbox. Keep sandbox and production secrets in separate TradingHost Secrets entries; never reuse one across environments.

Crypto options live on Deribit. Coinbase closed its acquisition of Deribit on August 14, 2025 for roughly $2.9B, but Deribit options trading continues to operate on the existing Deribit API and brand; there is no merged Coinbase options endpoint as of May 2026. Strategies that want options exposure integrate the Deribit API directly, alongside Coinbase spot or perp flow, and run inside a TradingHost container the same way any other multi-venue strategy does.

TradingHost runs in the EU and US-East regions. Pick the region closest to the matching engine your strategy depends on. 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.