AI-native runtime for CoinW trading strategies

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

No. CoinW API access is provided by CoinW. You are responsible for your CoinW account, API permissions, credentials and compliance with CoinW’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 a unified `coinw` class that covers spot trading; futures coverage is partial. 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.

Yes. CoinW perpetual futures are reachable through the `/v1/perpum/` endpoint family on a separate base URL (`wss://ws.futurescw.com/perpum` for WebSocket). The strategy code inside your container must route by market type because the spot endpoints sit on `api.coinw.com` while the futures endpoints sit on the perpum subdomain. TradingHost is venue-agnostic at the runtime level; what matters is that your code encodes the URL split correctly.

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 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 and secret. See platform secrets for the full handling model.

No. Strategies should never need withdrawal permissions. Scope your API key down to trading and account-state reads only, and keep withdrawal off the key entirely.

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.

The CoinW platform UI displays copy-trade positions, strategy-square positions, and user-originated orders together in a unified view. The OpenAPI returns errors when called against copy-trade or strategy-square positions, even though they appear alongside user-originated orders. A strategy that iterates the order list without client-side filtering hits the errors on every copy or strategy-square position, polluting the success rate and triggering retry storms. Filter for user-originated orders client-side before calling order-management endpoints. See the Operational notes section above for the full guidance.

TradingHost runs in the EU and US-East regions. Pick the region closest to the matching engine your strategy depends on. Note: CoinW geo-blocks US, CA, JP, UK accounts at the KYC residency level; choosing a non-blocked TradingHost region does not work around a blocked account residency. 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.