AI-native runtime for BitMart 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
- BitMart
- Venue type
- Crypto exchange
- Asset class
- Crypto
- Supported products
- Spot, isolated margin, USDT-margined futures and inverse futures via separate endpoint families
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native BitMart REST and WebSocket, CCXT, Freqtrade, Hummingbot, 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
- BitMart role
- Exchange account, API access, market access, execution venue
- Affiliation
- TradingHost is independent and is not affiliated with BitMart
Section 02 · What BitMart offers
What BitMart offers
BitMart offers spot, isolated margin and USDT-margined and inverse futures via three separate endpoint families with their own rate-limit pools. Authentication uses an API key, secret and a memo string signed with HMAC-SHA256; a missing memo trips a signature error even when the HMAC is correct. KYC tier gates the rate-limit ceiling. Futures trading is restricted in the US, Hong Kong SAR and a number of other regions; restriction is enforced at account creation and at order submission. Endpoint specifics change over time. The shape is durable; the precise rate-limit weights, fee tiers and symbol lists live in BitMart's docs.
Markets and strategy patterns
- Spot strategies on USDT and BTC pairs
- USDT-margined perpetual futures (non-restricted jurisdictions)
- Inverse (coin-margined) perpetual futures
- Isolated margin lending strategies
- KYC-tiered execution with higher rate limits
- Sub-account-isolated multi-strategy deployments
- WebSocket order-book and trade-stream consumers
- Cross-family execution (spot + futures with separate domains)
API surface
- Product surfaces
- Spot v3 at the open API portal, isolated margin endpoints, and futures on a distinct domain. Each family carries its own rate-limit pool and authentication scope. Futures trading is restricted in the US, Hong Kong SAR and a number of other regions; restriction is enforced at account creation and at order submission, not only at sign-in.
- Connection methods
- REST for order placement and account queries. WebSocket for market data and private account events. Public WebSocket streams are open; private WebSocket subscriptions are auth-scoped per key.
- Authentication
- API key, secret and memo signed with HMAC-SHA256 (lowercase hex). Keys are scoped per family (spot, margin, futures) and KYC tier gates the rate-limit ceiling. The memo string is BitMart-specific and is verified server-side; a missing memo returns a signature error even when the HMAC itself is correct.
For specifics, refer to BitMart
Specific endpoints, rate-limit weights, symbol lists, fee tiers and version history live in BitMart's documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your BitMart 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 BitMart API
Direct control over BitMart-specific behaviour, account data and order execution logic across the three endpoint families.
CCXT
Common interface across BitMart and other crypto exchanges. CCXT exposes BitMart spot and swap markets via the unified `bitmart` class.
Freqtrade or Hummingbot
Framework-based deployments using their strategy structure and configuration model. Both ship BitMart connectors with primary coverage on spot.
Custom connector
Your own internal trading engine or proprietary BitMart integration, signing requests with HMAC-SHA256 including the BitMart memo string.
Framework support for BitMart products
Coverage varies by framework. CCXT spans BitMart spot and swap markets; Freqtrade covers spot; Hummingbot covers spot with partial perpetual support; native BitMart API access covers everything BitMart offers, including isolated margin and the futures families. Futures coverage is unavailable to accounts in restricted jurisdictions regardless of framework.
✓ confirmed support per official framework docs. "no" indicates not officially documented as supported. "partial" indicates limited coverage. Workflow links target /workflows/ pages currently in authoring.
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
BitMart provides the exchange and API access. TradingHost provides the production environment where your BitMart-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 BitMart.
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, Freqtrade or Hummingbot) for a working baseline.
- STEP 03
Deploy into a TradingHost container
Pick a region (EU or US-East), supply the environment values your strategy needs (BitMart API key, secret, memo string and any per-family scope flags), 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 BitMart
Things that bite you when you actually run a BitMart strategy in a containerised cloud runtime, not in BitMart's docs, not in framework READMEs. Every claim below is quoted or paraphrased from BitMart's own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · Three families
Spot v3, Margin and Futures live behind separate endpoint families
BitMart's REST surface splits into three families: Spot v3 at the open API portal, isolated Margin endpoints, and Futures on a distinct domain. Each family carries its own rate-limit pool, its own auth scoping and its own error vocabulary. A strategy that touches both spot and futures has to budget against the per-family pools rather than a single combined cap; cross-family retries that ignore the split will throttle one side while the other still has headroom.
02 · Signing memo
The API memo string is part of the signature, not a label
BitMart's HMAC-SHA256 signing scheme includes the API memo string alongside the key and secret. The memo is set when the key is created and is verified server-side on every signed request. A common silent failure is treating the memo as a UI label and dropping it from the signature payload; the request returns a signature error even when the HMAC computation is otherwise correct. Store the memo in the same secrets entry as the key and secret, and have client code refuse to sign if the memo is absent.
03 · Futures geo
Futures are restricted in the US, Hong Kong SAR and other regions
BitMart restricts futures trading in the US, Hong Kong SAR and a list of other regions. Enforcement happens at account creation and at order submission, so a futures order from a restricted-jurisdiction account is rejected regardless of key tier or KYC level. If your strategy is multi-jurisdictional, encode the venue/region selection as a first-class config value rather than a per-key switch, and let the strategy route around BitMart when the operating jurisdiction is on the restricted list.
SourceBitMart support center04 · KYC tiers
KYC tier gates the rate-limit ceiling and withdrawal capacity
API access is account-level KYC-tiered: higher tier unlocks elevated rate limits and withdrawal quotas. A strategy that runs comfortably on a verified account can hit unexpected 429s when copied to a fresh account at the lower tier. Verify the operating account on the same tier as production before sizing strategy throughput, and gate any per-second send rate behind a per-account configuration rather than a hard-coded constant.
SourceBitMart support center05 · Post-incident posture
Rotate keys that pre-date the December 2021 security event
BitMart disclosed a security incident in December 2021 in which approximately $196M was lost from hot wallets. The exchange subsequently revamped key issuance and sub-account verification controls. If you hold a BitMart API key issued before that period and have not rotated it since, treat the key as suspect and re-issue. The signing scheme is unchanged; the operational hygiene point is to rotate any key that pre-dates the post-incident security posture.
Section 06 · Built for
Built for
TradingHost BitMart runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Systematic crypto traders
- Quant developers
- CCXT, Freqtrade 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 BitMart.
No. Your strategy code connects to BitMart and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. BitMart API access is provided by BitMart. You are responsible for your BitMart account, API permissions, credentials and compliance with BitMart’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 exposes BitMart spot and swap markets via the unified `bitmart` class. 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, 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 BitMart API key, secret or memo string. See platform secrets for the full handling model.
No. Strategies should never need withdrawal permissions. Use scoped permissions (read, spot trade, futures trade) and keep withdrawal off the strategy key. Issue separate manually-managed keys for transfers and operational tasks.
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.
BitMart enforces futures restrictions at the jurisdictional level, not only at the key level. The US, Hong Kong SAR and a number of other regions are blocked from BitMart futures regardless of key scope. If your account was created in a restricted jurisdiction, futures orders return a regional rejection and no key change will unlock them. Route your futures flow to a non-restricted venue, or use BitMart only for spot from that account. 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. 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.