AI-native runtime for CoinTR Pro 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
- CoinTR Pro
- Venue type
- Crypto exchange (Türkiye-licensed, successor to Bitget Türkiye)
- Asset class
- Crypto
- Supported products
- Spot, USDT-margined and inverse perpetual futures, isolated and cross margin, native TRY pairs, 1,300+ pairs
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native CoinTR Pro REST and WebSocket (OpenAPI spec), CCXT (tier-1 certified), 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
- CoinTR Pro role
- Exchange account, API access, market access, execution venue
- Affiliation
- TradingHost is independent and is not affiliated with CoinTR Pro or Bitget, the operator of Bitget Türkiye prior to the August 2024 transfer
Section 02 · What CoinTR Pro offers
What CoinTR Pro offers
CoinTR Pro is the Türkiye-licensed successor to Bitget Türkiye after the August 2024 account transfer. The product set covers spot, USDT-margined and inverse perpetual futures across 1,300+ pairs, with native TRY-quoted markets and TRY stablecoin swaps. Authentication uses HMAC-SHA256 signing with the key in X-COINTR-APIKEY and the signature in X-COINTR-SIGN (no separate passphrase header). The OpenAPI specification is published on the CoinTR-EX GitHub Pages site and CCXT tier-1 certifies CoinTR's spot, futures, margin and account-management functions. Endpoint specifics change over time. The shape is durable; the precise rate-limit weights, symbol lists and KYC tier thresholds live in CoinTR's docs.
Markets and strategy patterns
- TRY-quoted spot strategies (BTC/TRY, ETH/TRY)
- TRY native stablecoin swap pairs
- IBAN-linked fiat deposit and withdrawal flows
- USDT-margined perpetual futures
- Inverse (coin-margined) perpetual futures
- Isolated and cross margin futures positions
- TRY arbitrage versus USD/USDT global venues
- Sub-account-isolated multi-strategy deployments
API surface
- Product surfaces
- Spot, USDT-margined and inverse perpetual futures, isolated and cross margin, with native TRY pairs and TRY stablecoin swaps. The pair list is large (1,300+ pairs) and was inherited substantially intact from Bitget Türkiye after the August 2024 transfer. TRY IBAN-linked deposit/withdrawal runs through Turkish bank rails.
- Connection methods
- REST for order placement and account queries, WebSocket for real-time market data, depth and private account events. The OpenAPI specification is published on the CoinTR-EX GitHub Pages site and tracks the surface that Bitget Türkiye exposed pre-migration.
- Authentication
- API key and secret signed with HMAC-SHA256, with the signature carried in X-COINTR-SIGN and the key in X-COINTR-APIKEY. No separate passphrase header (CoinTR diverges from Bitget here). Sub-accounts hold their own scoped keys. KYC tier progressively restricts TRY withdrawal and deposit amounts; large fiat operations require enhanced verification.
For specifics, refer to CoinTR Pro
Specific endpoints, rate-limit weights, symbol lists, fee schedule and KYC tier thresholds live in CoinTR's documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your CoinTR Pro 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 CoinTR Pro API
Direct control over CoinTR Pro-specific behaviour, including TRY-quoted pairs, IBAN-linked deposit flows and the three-header signing scheme inherited from Bitget.
CCXT (tier-1 certified)
CCXT certifies CoinTR Pro tier-1 across spot, futures, margin and account-management functions. The unified `cointr` class is the recommended retail path.
Freqtrade or Hummingbot
Framework-based deployments via the CCXT-backed exchange surface. Both frameworks can carry CoinTR strategies through their CCXT compatibility layer where supported.
Custom connector
Your own internal trading engine or proprietary CoinTR integration, signing requests with HMAC-SHA256 and passing the key in X-COINTR-APIKEY and the signature in X-COINTR-SIGN.
Framework support for CoinTR Pro products
Coverage varies by framework. CCXT tier-1 certifies CoinTR Pro across spot, futures, margin and account-management functions; Freqtrade and Hummingbot ride the CCXT compatibility layer for spot with partial futures support; native CoinTR Pro API access covers everything CoinTR offers, including the TRY-specific IBAN flows.
✓ confirmed support per official framework docs and CCXT certification. "no" indicates not officially documented as supported. "partial" indicates limited coverage.
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
CoinTR Pro provides the exchange and API access. TradingHost provides the production environment where your CoinTR Pro-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 CoinTR Pro.
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 (CoinTR Pro API key and secret), 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 CoinTR Pro
Things that bite you when you actually run a CoinTR Pro strategy in a containerised cloud runtime, not in CoinTR's docs, not in framework READMEs. Every claim below is quoted or paraphrased from CoinTR's own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · Bitget migration
Bitget Türkiye accounts auto-migrated to CoinTR in August 2024
Bitget Türkiye accounts and balances were transferred to CoinTR Pro in August 2024 with no manual user intervention required. The OpenAPI surface CoinTR exposes is substantially the same as the Bitget surface that powered Bitget Türkiye pre-migration, so integrations originally built against Bitget Türkiye should largely keep working with re-issued CoinTR credentials. The key gotcha is that legacy Bitget API tokens issued before the transfer do not authenticate against CoinTR endpoints; re-issue keys under the CoinTR account before pointing a production strategy at the live API.
02 · TRY pairs
Native TRY pairs and TRY stablecoin swaps need TRY-aware tick sizes
CoinTR Pro carries native TRY-quoted pairs (BTC/TRY, ETH/TRY and more) plus TRY stablecoin swap pairs. The tick size, lot size and minimum notional on TRY pairs are TRY-denominated, which means a strategy templated from a USDT-quoted venue will reject orders on price or quantity precision unless the per-instrument metadata is fetched at startup. Pull the pair-info endpoint and respect the precision fields per pair; do not assume the precision is the same as the matching USDT pair on the same asset.
03 · IBAN flows
TRY deposit and withdrawal route through Turkish bank IBAN rails
TRY fiat deposit and withdrawal on CoinTR Pro runs through IBAN-linked Turkish bank rails. The withdrawal endpoint requires the destination IBAN, and KYC tier progressively restricts the per-day, per-month and per-year amounts. A strategy that programmatically settles TRY profits has to handle the tier-based limit explicitly; large flows above the current tier cap require enhanced verification and cannot be unblocked from the API alone. Keep TRY-flow logic gated on a per-tier configuration value rather than a single hard-coded cap.
04 · Header auth
X-COINTR-APIKEY and X-COINTR-SIGN, with timestamp inside the signed string
CoinTR Pro's private endpoints take two HTTP headers: X-COINTR-APIKEY for the key and X-COINTR-SIGN for the signature. The signature is computed via HMAC-SHA256 using the API secret over a request string that incorporates the current timestamp. There is no separate passphrase header (this is one place CoinTR diverges from its Bitget heritage). Confirm the timestamp source your client uses is millisecond-precision UTC and stays aligned with the venue; clock drift turns into a signature error the same way it would on any HMAC-signed REST surface.
05 · Post-merger stability
Endpoints inherited from Bitget can shift as CoinTR diverges
Post-migration, CoinTR's API surface tracks the Bitget OpenAPI specification closely, but the two are operationally separate. As CoinTR diverges (new TRY-specific endpoints, KYC tier features, Turkish regulatory additions), endpoints inherited from Bitget may shift in ways that Bitget itself does not signal. Pin your integration to the CoinTR-EX OpenAPI spec rather than the Bitget docs, and watch the CoinTR announcements channel for breaking changes that the Bitget side will not surface.
Section 06 · Built for
Built for
TradingHost CoinTR Pro runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Turkish lira execution and TRY arbitrage traders
- 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 CoinTR Pro or Bitget, the operator of Bitget Türkiye prior to the August 2024 transfer.
No. Your strategy code connects to CoinTR Pro and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. CoinTR Pro API access is provided by CoinTR. You are responsible for your CoinTR account, API permissions, credentials and compliance with CoinTR’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, and CoinTR Pro is tier-1 certified in CCXT. The unified `cointr` class covers spot, futures, margin and account-management functions. 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 CoinTR Pro API key or secret. 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 entirely. For TRY-to-IBAN flows, use a separate manually-managed key off the strategy runtime; tier-based limits apply.
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.
Bitget Türkiye accounts were transferred to CoinTR Pro in August 2024. Balances migrated automatically, but legacy Bitget API tokens issued before the transfer do not authenticate against CoinTR endpoints. Re-issue keys under the CoinTR account, and update the secrets entry in your TradingHost runtime to use the new key and secret. See the Operational notes section above for the full guidance.
TradingHost runs in the EU and US-East regions. The EU region is the natural pick for CoinTR Pro given the Türkiye-Europe geography. 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.