AI-native runtime for Bitfinex trading strategies

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

No. Bitfinex API access is provided by Bitfinex. You are responsible for your Bitfinex account, API permissions, credentials and compliance with Bitfinex’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 Bitfinex under two ids: bitfinex targets the v1 API and bitfinex2 targets v2. Use bitfinex2 for new strategies; v2 is the supported path. Note that some Bitfinex pair listings use USD where the underlying is actually USDT, which CCXT normalises during conversion. See the CCXT framework runtime for the full setup story.

Margin is funded by a peer-to-peer book, not by the exchange. Lenders post funding offers in fUSD, fBTC, etc.; borrowers consume them when opening margin positions. The lending side is itself a strategy surface, which is unusual among major venues.

Perpetuals trade at derivatives.bitfinex.com under F0 symbols (for example tBTCF0:USTF0). They require USDt0 in a dedicated derivatives wallet, operated by iFinex Financial Technologies Limited. Transfer funds via the Transfer Between Wallets endpoint. Leverage is configurable per order, default 10, up to 100.

No. Bitfinex does not serve US-domiciled customers. If you are in the US, use Coinbase or Kraken instead. TradingHost runs your runtime regardless of region, but the venue itself must accept your account.

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. Each running strategy should hold its own API key (ideally under a sub-account) so the strict per-key nonce monotonicity does not collide. See the TradingHost runtime page for the multi-strategy model.

The fastest path is to fork a TradingHost framework runtime: CCXT or Freqtrade 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 (account info, orders, margin, funding) and only enable the surfaces your strategy actually touches.

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.

Bitfinex requires a strictly increasing nonce per API key, capped at 9007199254740991. Two processes sharing one key will collide and one will be rejected. Fix it by giving each running strategy its own API key, ideally on its own sub-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.