AI-native runtime for Bitnomial trading strategies

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

No. Bitnomial API access is provided by Bitnomial / Payward. You are responsible for your Bitnomial / Payward account, API permissions, credentials and compliance with Bitnomial’s and Payward’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 against the native Bitnomial / Payward API.

Yes. TradingHost supports any language that can run inside a container. Bitnomial does not have a first-class CCXT, Freqtrade or Hummingbot connector, so a custom client wrapper is typical regardless of language choice.

CCXT does not currently expose Bitnomial as a unified exchange. Strategies that want a framework abstraction must route through the native Bitnomial API (under Payward post-acquisition) directly or build a custom CCXT-style wrapper. TradingHost runs the wrapper code the same way it runs any other strategy. See the CCXT framework runtime for context on how the framework integration shape changes when no native connector exists.

Bitnomial offers spot margin, perpetual futures, options and prediction markets, all cleared through the integrated Bitnomial Clearinghouse. Post-Payward acquisition, the surface consolidates under Payward infrastructure. Strategies that span multiple products (perp + option + prediction, for example) must model each contract's margin separately because margin and liquidation thresholds are defined per contract specification rather than via a single account-wide margin engine.

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.

Bitnomial does not have framework starter kits the way Binance or Coinbase do, so the fastest path is to connect your own GitHub strategy repo that targets the native Bitnomial / Payward API or the NinjaTrader integration. 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 Bitnomial / Payward credentials. 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.

Payward completed the acquisition of Bitnomial on May 1, 2026, and existing Bitnomial traders transition to Payward infrastructure via a single auth migration endpoint. Strategy code that targets pre-acquisition Bitnomial credentials needs to be re-pointed at the Payward-managed auth path. Pin your client wrapper to the latest Payward documentation rather than legacy Bitnomial references, and keep migration and post-migration secrets in separate TradingHost Secrets entries during the transition. 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. Bitnomial is a US-regulated venue; US-East is the natural choice for latency-sensitive Bitnomial strategies. 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.