AI-native runtime for OKX trading strategies

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

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

No. TradingHost is the cloud runtime where your strategy code runs. We do not provide signals, AI prediction models or pre-built strategies. 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.

CCXT exposes OKX (okx, formerly okex) for spot and perpetual swap trading and for account, market and historical data. Futures are also supported. Options market data is accessible via OKX's symbology, but options order execution through CCXT's unified methods is limited; route options orders through the native OKX v5 client. The OKX exchange object requires apiKey, secret, and password (the passphrase) plus standard sub-account headers. See the CCXT framework runtime for the full setup story.

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, Freqtrade 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 API key, secret or passphrase. See platform secrets for the full handling model.

No. Strategies should never need withdrawal permissions. Use scoped permissions (read, trade) and bind the key to your runtime's egress IP using OKX's IP allowlist (up to 20 IPs per key).

OKX uses a 3-part credential: API key, secret and passphrase. The passphrase is a user-set string entered at API key creation, sent on every authenticated request via OK-ACCESS-PASSPHRASE, and mixed into the HMAC-SHA256 signature alongside the secret. OKX cannot recover the passphrase if lost; you regenerate the key. Treat it as another secret.

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.

50111 means OKX couldn't find the API key (wrong key, wrong environment, or demo key used against live). 50113 means the signature didn't validate. Usual causes: wrong or missing passphrase, wrong secret, clock drift in OK-ACCESS-TIMESTAMP (must be ISO 8601 UTC with ms precision), wrong pre-hash string order (timestamp + method + requestPath + body), or missing x-simulated-trading: 1 when using a demo key. Run NTP sync in the container and log the pre-hash string in non-production builds.

Yes. Create a demo API key from the OKX demo trading panel and add x-simulated-trading: 1 to every REST and WebSocket header. The host stays the same. Demo keys cannot trade live, live keys cannot trade demo, and the header is required on every call; flip both together when promoting.

Account mode is set at the Unified Account level and affects margin math. Multi-currency treats USD-converted assets as shared margin. Portfolio margin applies a risk-based model netting exposure across spot, margin, perps, futures and options. Isolated margin positions are no longer supported inside multi-currency or portfolio modes.

Global OKX (okx.com) restricts US persons under a 2017 policy. In February 2025, Aux Cayes FinTech (OKX-affiliated) pleaded guilty to operating an unlicensed money transmitting business in the US and paid $505M. A separate US entity (okx.com/en-us) relaunched in 2025 in 41 US states. OKX US and global OKX are different venues; confirm which entity your account belongs to before deploying.

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.