AI-native runtime for Bitstamp trading strategies

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

No. Bitstamp API access is provided by Bitstamp. You are responsible for your Bitstamp account, API permissions, credentials and compliance with Bitstamp’s terms.

No material change. Robinhood closed the acquisition on June 2, 2025 and Bitstamp continues to run under its own brand, API surface, FIX gateway and licence portfolio. Authentication, endpoints, sub-accounts and rate limits are unchanged. Robinhood Crypto remains a separate venue with a separate API.

No. TradingHost is the cloud runtime where your strategy code runs. We do not provide signals, AI prediction models or pre-built strategies. 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's `bitstamp` exchange id covers spot trading end to end. Margin, swap, future and option flags are off in the unified config, so route derivatives flow through Bitstamp's native FIX or HTTP surface instead. Inside the TradingHost container, instantiate CCXT with the API key and secret pulled from runtime secrets, not from the repo. See the CCXT framework runtime for the full setup story.

Yes. Bitstamp supports sub-accounts and per-key permissioning, and any request can be scoped to a sub-account through the X-Auth-Subaccount-Id header. On TradingHost, mint one key per deployment, restrict its verbs to the minimum the strategy needs, IP-whitelist the TradingHost egress, and isolate the keys per sub-account so one strategy cannot read or cancel another's orders. 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 API key and secret. See platform secrets for the full handling model.

The minimum the strategy needs, no more. Bitstamp supports per-key permissioning, so a market-making strategy gets read and trade verbs only, never withdrawal. Pair each key with IP whitelisting against the TradingHost runtime egress range for your selected region, and scope it to a sub-account via X-Auth-Subaccount-Id where strategy isolation matters.

Yes, through Bitstamp USA Inc., which holds a NYDFS BitLicense plus state money-transmitter licences and FinCEN MSB registration. State availability varies, so check Bitstamp USA's coverage before assuming access. The Bitstamp USA API surface mirrors the global surface for the products it offers.

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.

Bitstamp's v2 auth treats each X-Auth-Nonce as single-use inside a 150-second window and rejects timestamps more than 150 seconds from server time. The error is almost always a horizontally scaled deploy sharing one key across workers, or two co-located strategies racing on the same nonce. Fix by serialising the nonce source (one monotonic generator per key), or by minting one key per worker and whitelisting both egress IPs.

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.