AI-native runtime for Zonda 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
- Zonda (formerly BitBay until the 2021 rebrand)
- Venue type
- Crypto exchange (Polish + Estonian regulated)
- Asset class
- Crypto with EUR and PLN fiat quote
- Supported products
- Spot trading on PLN-quote pairs (BTC/PLN, ETH/PLN, USDC/PLN and others), EUR-quote pairs, and major crypto-to-crypto pairs. SEPA EUR rail (free deposit/withdrawal) and Polish Elixir rail (PLN bank transfer) for fiat.
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native Zonda public and trading APIs (REST and WebSocket), CCXT, 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
- Zonda role
- Exchange account, API access, market access, execution venue
- Affiliation
- TradingHost is independent and is not affiliated with Zonda
Section 02 · What Zonda offers
What Zonda offers
Zonda (formerly BitBay until the 2021 rebrand) offers spot trading on PLN-quote and EUR-quote pairs with strong Polish and Estonian regulatory standing. Fiat rails are SEPA for EUR (free deposit/withdrawal, EUR 15,000 per 30 days withdrawal cap with EUR 5,000 single-transaction max) and Polish Elixir for PLN (business-day processing into Polish bank accounts). Strategies authenticate with HMAC-signed API keys against the public and trading APIs. Endpoint specifics change over time. The shape is durable; precise rate-limit weights, symbol lists and fiat-rail limits live in Zonda’s docs.
Markets and strategy patterns
- PLN-quote spot strategies (BTC/PLN, ETH/PLN, USDC/PLN)
- EUR-quote spot strategies on SEPA-funded balances
- Elixir-funded intraday strategies (Polish bank rail)
- Crypto-to-crypto pairs against PLN/EUR base
- WebSocket real-time orderbook and trade subscriptions
- BitBay-legacy API endpoints (deprecated but documented)
- KYC-tiered deposit / withdrawal planning per pair
- Local PLN basis vs EUR carry strategies
API surface
- Product surfaces
- Spot trading on PLN-quote pairs (BTC/PLN, ETH/PLN, USDC/PLN), EUR-quote pairs, and major crypto-to-crypto pairs. Fiat rails: SEPA for EUR (free deposit/withdrawal, minimum EUR 10, withdrawal cap EUR 15,000 per 30 days with EUR 5,000 single-tx max) and Polish Elixir for PLN (business-day processing, targeting Polish bank accounts).
- Connection methods
- REST for order placement and account queries. WebSocket streams for real-time market data and depth. Zonda exposes a public API for market data and a trading API for signed requests; pre-rebrand BitBay API documentation is still discoverable and operationally compatible in many places.
- Authentication
- API key and secret per strategy with HMAC-signed requests. Permissions can be scoped per API key. KYC tier sets fiat deposit / withdrawal limits at the account level; the API key inherits the account's tier rather than carrying its own.
For specifics, refer to Zonda
Specific endpoints, rate-limit weights, symbol lists, fee tiers and version history live in Zonda’s documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your Zonda 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 Zonda API
Direct control over Zonda-specific behaviour, the SEPA/Elixir fiat rails and the PLN/EUR pair surface.
CCXT
Common interface across Zonda and other crypto exchanges. CCXT exposes Zonda spot via the unified `zonda` class (legacy `bitbay` alias is still operational in many CCXT releases).
Freqtrade or Hummingbot
Neither framework lists Zonda as a first-class supported exchange today. Best path is custom or CCXT-backed implementations.
Custom connector
Your own internal trading engine or proprietary Zonda integration against the REST and WebSocket APIs.
Framework support for Zonda products
Coverage varies by framework. Zonda is spot-only at the venue level, so the matrix is narrow by design. CCXT exposes Zonda spot through its unified `zonda` class (the legacy `bitbay` alias from before the 2021 rebrand still ships in many CCXT releases). Neither Freqtrade nor Hummingbot lists Zonda as a first-class supported exchange today; native API access reaches everything Zonda publishes.
✓ confirmed support per official framework docs. "no" indicates not officially documented as supported. Workflow links target /workflows/ pages currently in authoring.
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
Zonda provides the exchange and API access. TradingHost provides the production environment where your Zonda-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 Zonda.
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) for a working baseline against the Zonda public and trading APIs.
- STEP 03
Deploy into a TradingHost container
Pick a region (EU or US-East), supply the environment values your strategy needs (Zonda API key and secret, IBAN-linked account settings), 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 Zonda
Things that bite you when you actually run a Zonda strategy in a containerised cloud runtime, not in Zonda’s docs, not in framework READMEs. Every claim below is paraphrased from Zonda’s own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · Rebrand legacy
Zonda is the BitBay rebrand (October 2021); legacy `bitbay` references still in the wild
Zonda rebranded from BitBay in October 2021. CCXT continues to ship a `bitbay` alias alongside the `zonda` class, and many legacy framework READMEs and third-party tutorials still reference BitBay. Strategy code that imports `bitbay` from CCXT generally still works because of the alias, but new integrations should target `zonda` directly. The underlying endpoints, signatures and rate limits are unchanged across the rebrand, only the brand and domain references have moved to zondacrypto.com.
02 · SEPA EUR rail
Free SEPA deposit/withdrawal; EUR 15,000 per 30 days withdrawal cap
Zonda accepts SEPA EUR deposits and withdrawals at zero fee with an EUR 10 minimum deposit. Withdrawals are capped at EUR 15,000 per rolling 30-day window with a maximum EUR 5,000 per single transaction. A strategy that targets larger EUR off-ramps must either spread withdrawals across the window or escalate the KYC tier. SEPA settlement is business-day; submissions after 13:00 UTC or on weekends process the next business day. Plan strategy capital deployment with the rail cadence in mind.
03 · Elixir PLN rail
PLN deposits / withdrawals route through Polish Elixir bank transfer
PLN flows on Zonda use Poland's Elixir interbank system. Deposits and withdrawals process on business days, typically clearing around 13:00 UTC. PLN withdrawals must target a Polish bank account; non-Polish IBANs are rejected at the rail level rather than the API level. Submissions after the Elixir cutoff or on weekends queue until the next business day. Strategies that depend on intraday PLN availability need to account for the rail schedule rather than treating PLN balance as continuously liquid.
04 · KYC tier
Minimum EUR 10 / PLN 10 verification deposit; escalated AML review for larger amounts
KYC tier on Zonda requires a minimum EUR 10 or PLN 10 verification deposit at signup. Larger deposits and withdrawal amounts trigger escalated AML review, which can delay settlement until manual checks complete. Strategies that ramp from small-balance testing to full-size production must budget for the AML review window on first large transfer; subsequent transfers within the verified tier process at normal rail speed.
05 · MiCA compliance
Estonian FIU MiCA flag on TeamPL token (2024); review per-asset compliance status
Zonda holds Polish and Estonian regulatory standing. Under EU MiCA, Estonian FIU flagged TeamPL token in 2024 with an ongoing compliance audit. Strategies that touch tokens with MiCA flags may see trading restrictions or notice-period delistings that the API will not warn about ahead of time. Periodically reconcile your strategy's tradable-asset list against the Zonda listings page rather than assuming the symbol list is stable.
SourceZonda main portal06 · IBAN-linked accounts
Per-account IBAN binding enables direct SEPA / Elixir settlement
Zonda binds your Zonda fiat account to one or more named IBANs on the account level. The API key cannot rebind IBANs at runtime; that is an account-side operation. Strategies do not need to manage IBAN association beyond knowing that fiat withdrawals always target an account-bound IBAN. A leaked API key therefore cannot redirect fiat to a new bank account, only to the IBANs already on file, which contains the blast radius of a credential compromise.
Section 06 · Built for
Built for
TradingHost Zonda runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Systematic crypto traders
- Quant developers
- CCXT 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 Zonda.
No. Your strategy code connects to Zonda and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. Zonda API access is provided by Zonda. You are responsible for your Zonda account, API permissions, credentials and compliance with Zonda’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 ships a unified `zonda` class (with a legacy `bitbay` alias from before the 2021 rebrand still operational in many releases). 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. Zonda PLN-quote pairs (BTC/PLN, ETH/PLN, USDC/PLN and others) are reached through the same REST and WebSocket APIs as the EUR-quote pairs. The strategy code inside your container authenticates with your Zonda API key, and TradingHost is venue-agnostic at the runtime level. Note that PLN fiat withdrawals route through Polish Elixir, target Polish bank accounts only, and process on business days.
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. Scope your API key down to trading and account-state reads only, and keep withdrawal off the key entirely. Because Zonda binds fiat withdrawals to account-level IBANs, a leaked trading key cannot redirect EUR or PLN to a new bank account, but it can still move crypto, so keep the scope tight.
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.
Zonda rebranded from BitBay in October 2021. Endpoint URLs migrated to zondacrypto domains, and CCXT renamed the exchange class to `zonda` while retaining a `bitbay` alias in many releases. If your code imports `bitbay` and stopped working, check whether your CCXT version still ships the alias and pin to `zonda` for new integrations. The underlying signatures, rate limits and product surface are unchanged across the rebrand. 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. 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.