AI-native runtime for Bitso trading strategies

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

No. Bitso API access is provided by Bitso. You are responsible for your Bitso account, API permissions, credentials and compliance with Bitso’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. The CCXT bitso exchange covers spot endpoints, handles HMAC-SHA256 signing, and runs unchanged inside a TradingHost container. Margin and futures methods are not applicable since Bitso offers spot only. 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 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. Use scoped permissions (read, trade) and enable IP whitelisting where appropriate. Reserve the withdrawal scope for keys you operate manually from a fixed-IP host.

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.

Almost always a nonce or signature-construction issue. Bitso requires a strictly increasing nonce per key (Nonce v2 in rollout) and signs over nonce + METHOD + path + body with HMAC-SHA256, hex-encoded. Common causes: clock skew across replicas, two workers sharing one key, or a stripped trailing slash in the path.

SPEI in Mexico (MXN), PIX in Brazil (BRL), and local CBU/Alias in Argentina (ARS). PIX and SPEI both settle in seconds, but rail cut-off windows and bank holidays still apply. Strategies that auto-rebalance fiat inventory should treat rail availability as a runtime input.

Bitso operates under Mexico's Fintech Law via CNBV oversight, is registered with Argentina's CNV as PSAV no. 51, holds a Brazil presence, and uses a Gibraltar GFSC licence for institutional virtual-asset services. Mexico's July 2025 AML reform added reporting obligations for VASPs at roughly USD 1,180 per transaction.

No. Bitso does not offer accounts to US residents and restricts roughly 33 jurisdictions including the United States and Canada. TradingHost runs your strategy regardless of region, but the Bitso account itself must be eligible under Bitso's terms.

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.