AI-native runtime for CoinEx trading 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
- CoinEx
- Venue type
- Crypto exchange (global, no new US accounts post-NYAG settlement)
- Asset class
- Crypto
- Supported products
- Spot, perpetual and quarterly futures, cross and isolated margin. Default spot fees 0.2% maker/taker with Market Maker rebate program (-0.01% maker, 0.05% taker) at $1M spot / $5M futures monthly volume.
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native CoinEx API v2 REST and WebSocket, CCXT, custom connectors
- AI workflow integration
- MCP control surface for Cursor, Claude Code, GitHub Copilot and CLI agents
- TradingHost role
- Runtime, deployment, logs, health checks, region selection, MCP control
- CoinEx role
- Exchange account, API access, market access, execution venue
- Affiliation
- TradingHost is independent and is not affiliated with CoinEx
Section 02 · What CoinEx offers
What CoinEx offers
CoinEx offers spot trading, perpetual and quarterly futures, and cross/isolated margin via REST API V2 and WebSocket V2. Default spot fees are 0.2% maker/taker with a Market Maker rebate program reaching -0.01% maker and 0.05% taker at $1M spot or $5M futures monthly volume. Post-NYAG settlement, CoinEx does not provision new US accounts and existing US balances may withdraw only. MiCA documentation is required for EU margin and futures offerings. Endpoint specifics change over time. The shape is durable; the precise rate-limit weights, symbol lists and fee tiers live in CoinEx's docs.
Markets and strategy patterns
- Spot market making to chase the MM rebate at $1M monthly volume
- USDT-quoted perpetual futures strategies
- Quarterly futures basis trading
- Cross and isolated margin strategies on spot
- Funding-rate carry strategies on USDT perpetuals
- WebSocket V2 real-time market data and account streams
- API key permission scoping per endpoint class (market data unsigned, account signed)
- Multi-strategy deployments under one CoinEx account
API surface
- Product surfaces
- Spot trading on USDT, BTC and other quote pairs, perpetual futures, quarterly futures, cross and isolated margin. Default fees 0.2% maker/taker on spot. Market Maker rebate program reaches -0.01% maker and 0.05% taker at $1M spot or $5M futures monthly volume; tiers recompute at 01:00 UTC on the first of each month.
- Connection methods
- REST API V2 for order placement and account queries. WebSocket V2 for real-time market data, depth and account events. Market data endpoints are unsigned; account and transaction endpoints require signature.
- Authentication
- API key and secret per strategy. API key permissions are scoped per endpoint class: market endpoints are unsigned, account and transaction endpoints require HMAC signing. Strategies should never need withdrawal permission.
For specifics, refer to CoinEx
Specific endpoints, rate-limit weights, symbol lists, fee tiers and version history live in CoinEx's documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your CoinEx strategy with AI
Pick an integration method, fork a TradingHost framework starter, and author your strategy in an AI IDE. Cursor, Claude Code, GitHub Copilot and CLI-based AI agents all work with the same GitHub-native deployment loop.
Native CoinEx API
Direct control over CoinEx-specific behaviour, the MM tier program, account data and futures order execution.
CCXT
Common interface across CoinEx and other crypto exchanges. CCXT exposes CoinEx through the unified `coinex` class spanning spot and futures.
Hummingbot
Framework-based deployments using the `coinex` connector. Spot only on Hummingbot.
Custom connector
Your own internal trading engine or proprietary CoinEx integration against the API V2 REST and WebSocket surface.
Framework support for CoinEx products
Coverage varies by framework. CCXT spans spot and futures via the unified `coinex` class. Hummingbot's `coinex` connector covers spot only. Freqtrade does not list CoinEx in its officially supported exchange list. Native CoinEx API access reaches everything CoinEx publishes including margin.
✓ confirmed support per official framework docs. "no" indicates not officially documented as supported. "partial" indicates limited coverage, see prose above for detail.
TradingHost does not force a framework. It runs your project.
Author with AI
The framework starters above pair 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
CoinEx provides the exchange and API access. TradingHost provides the production environment where your CoinEx-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 CoinEx.
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 a framework
Point TradingHost at your existing strategy repo, or fork a TradingHost framework runtime (CCXT or Hummingbot) for a working baseline against CoinEx API V2.
- STEP 03
Deploy into a TradingHost container
Pick a region (EU or US-East), supply the environment values your strategy needs (CoinEx API key, secret, scoped permissions), 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 CoinEx
Things that bite you when you actually run a CoinEx strategy in a containerised cloud runtime, not in CoinEx's docs, not in framework READMEs. Every claim below is quoted or paraphrased from CoinEx's own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · US accounts
No new US account provisioning post-NYAG settlement
Following the February 2023 New York Attorney General settlement, CoinEx is prohibited from creating any new accounts for US customers, and existing US customers may only withdraw their crypto from the platform. CoinEx also implements geo-blocking via IP address and GPS. Strategies that authenticate from a US-resident KYC account will fail on order placement regardless of API key permissions. Treat the account jurisdiction as a hard runtime gate, not a permissioning issue.
02 · Market Maker tiers
MM rebate at $1M spot or $5M futures monthly volume; tiers recompute at UTC 01:00 on the 1st
CoinEx's Market Maker rebate program reaches -0.01% maker and 0.05% taker once a single account hits $1M spot or $5M futures monthly volume. Tiers are recomputed at 01:00 UTC on the first of each month. A strategy that crosses the threshold mid-month does not get the rebate until the next tier cycle, and a strategy that falls below the threshold mid-month keeps the rebate until the next reset. Plan capital deployment with the tier-reset cadence in mind, not against the running monthly volume.
03 · Endpoint signing
Market endpoints are unsigned; account and transaction endpoints require HMAC signing
CoinEx API V2 splits endpoints into signed and unsigned classes. Market data endpoints (tickers, depth, klines) are unsigned. Account state, balance, order placement and transaction endpoints require HMAC signing. Strategy code that signs every request wastes CPU; code that forgets to sign account endpoints fails authentication. The split is documented in the API V2 reference; encode the endpoint class in your client wrapper rather than signing globally.
SourceCoinEx API V2 reference04 · Default fees
Default spot fees are 0.2% maker/taker; size your strategy accordingly
CoinEx default spot fees are 0.2% maker and 0.2% taker before any MM tier rebate kicks in. That is materially higher than top-tier global venues (Binance default 0.1% maker/taker before BNB discount). Strategies that port from a lower-fee venue may be unprofitable at CoinEx default tier until the volume reaches the MM threshold. Model your edge with the actual tier fee, not an aspirational rebate target.
05 · EU compliance
MiCA documentation required for EU margin and futures offerings
Under the EU Markets in Crypto-Assets (MiCA) regulation, CoinEx requires additional documentation for EU residents to access margin and futures offerings. A strategy authored against a CoinEx account whose KYC residency is in the EU may see futures and margin endpoints respond with permission errors until the MiCA documentation is on file. This is account-side, not API-side; the runtime cannot work around it. Verify your account's MiCA status in the CoinEx dashboard before deploying margin or futures strategies.
SourceCoinEx API V2 reference06 · Key scoping
Permission scoping per endpoint class; never grant withdrawal
CoinEx API key permissions are scoped per endpoint class. Strategies should never need withdrawal permission, and keeping withdrawal off the key contains the blast radius if the key leaks. The right pattern is per-strategy keys with read and trade scopes only; withdrawal lives on a separate manually-managed key on a fixed-IP host that no strategy ever loads.
SourceCoinEx API V2 reference
Section 06 · Built for
Built for
TradingHost CoinEx runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Systematic crypto traders
- Quant developers
- CCXT and Hummingbot users
- 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 CoinEx.
No. Your strategy code connects to CoinEx and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. CoinEx API access is provided by CoinEx. You are responsible for your CoinEx account, API permissions, credentials and compliance with CoinEx’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 `coinex` class that covers spot and futures trading. 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. Perpetual and quarterly futures, plus cross and isolated margin, are reachable through CoinEx API V2 once your account is eligible. TradingHost is venue-agnostic at the runtime level: any code that can authenticate against the futures or margin endpoints can run inside a container. EU residents may need MiCA documentation on file with CoinEx before futures and margin endpoints respond; that is an account-side check, not a runtime one.
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 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.
No. Following the New York Attorney General settlement, CoinEx does not provision new US accounts and existing US balances may withdraw only (no trading). Strategies authenticating from a US-resident KYC account will fail on order placement regardless of API key permissions. If your account residency is non-US, behaviour is unchanged. Treat the account jurisdiction as a hard runtime gate; the API key cannot override the KYC residency. See the Operational notes section above for the full context.
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.