AI-native runtime for Gemini 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
- Gemini
- Venue type
- Crypto exchange and NYDFS-chartered trust company
- Asset class
- Crypto (spot), crypto perpetuals in select non-US jurisdictions
- Supported products
- Spot (web and mobile), ActiveTrader (advanced order book interface), Gemini Perpetuals (non-US, via Gemini Artemis Pte. Ltd., up to 100x leverage; pairs like ETHGUSDPERP), Gemini Custody (qualified custodian, separate but composable), sandbox environment
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native Gemini REST, WebSocket and FIX 4.4, CCXT (gemini), custom HMAC-SHA384 clients. Freqtrade and Hummingbot do not officially support Gemini.
- AI workflow integration
- MCP control surface for Cursor, Claude Code, GitHub Copilot and CLI agents
- TradingHost role
- Runtime, deployment, logs, health checks, region selection, secrets, MCP control
- Gemini role
- Exchange account, API access, market access, execution venue, qualified custodian for institutional users
- Affiliation
- TradingHost is independent and is not affiliated with Gemini. Gemini Trust Company, LLC is a New York limited-purpose trust company chartered by the NYDFS (October 2015). Gemini’s parent listed on Nasdaq as GEMI in September 2025.
Section 02 · What Gemini offers
What Gemini offers
Gemini is a NYDFS-chartered trust company offering spot trading through its web and mobile apps, ActiveTrader for an advanced order-book interface, and Gemini Perpetuals for eligible non-US accounts (operated by Gemini Artemis Pte. Ltd.). Connectivity is via REST, WebSocket and FIX 4.4, with HMAC-SHA384 signing. Hummingbot and Freqtrade have limited or no Gemini support, so most strategy code is either native API or CCXT-based. Specific symbols, rate limits and venue eligibility live in Gemini’s docs.
Markets and strategy patterns
- ActiveTrader unified order-book execution
- GUSD / USDC / RLUSD combined order-book arbitrage
- Sandbox-validated deployments before production rollout
- Master-key fan-out across institutional sub-accounts
- Per-session nonce isolation for parallel strategy instances
- Cancel-all-session-orders kill switch on strategy stop
- Custody-integrated treasury rebalancing
- FIX 4.4 co-located execution for institutional desks
API surface
- Product surfaces
- Spot exchange, ActiveTrader, Gemini Derivatives / Perpetuals (where eligible), Sandbox (independent test environment).
- Connection methods
- REST (HTTPS), WebSocket (public + private), FIX 4.4 Order Entry, FIX 4.4 Market Data, FIX Drop Copy. FIX requires a cross-connect from an approved data centre or extranet into Gemini’s US East Coast footprint; not available over public internet.
- Authentication
- HMAC-SHA384 over a base64-encoded JSON payload. Signature in X-GEMINI-SIGNATURE, API key in X-GEMINI-APIKEY, payload in X-GEMINI-PAYLOAD. Key prefixes: master- (group-wide, requires account parameter) and account- (single account). Each provisioned key is a "session" with its own nonce stream.
For specifics, refer to Gemini
Specific endpoints, rate-limit weights, symbol lists, fee tiers and version history live in Gemini’s documentation. Treat these as the source of truth.
- docs.gemini.comGemini API documentation portal
- developer.gemini.com/authentication/api-keyAPI key authentication and master vs account-level keys
- developer.gemini.com/get-started/sandboxSandbox environment at api.sandbox.gemini.com
- developer.gemini.com/rate-limitRate limits (120/min public, 600/min private)
Section 03 · Build with AI
Build your Gemini 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 Gemini API
Direct control over Gemini-specific behaviour (REST, WebSocket, FIX 4.4), account data and order execution logic.
CCXT
Common interface across Gemini and other crypto exchanges via the gemini connector.
Freqtrade or Hummingbot
Hummingbot has no Gemini connector. Freqtrade is community-only via CCXT and not officially supported. Most production code uses native API or CCXT.
Custom connector
Your own internal trading engine or proprietary Gemini integration, often built around HMAC-SHA384 signing and the FIX 4.4 surface.
Framework support for Gemini products
Gemini is a NYDFS-chartered trust company with spot trading through web and ActiveTrader, and a separate perpetuals venue run by Gemini Artemis in select jurisdictions. Hummingbot has no Gemini connector and Freqtrade only reaches Gemini through CCXT as community support, so most production strategy code is either native REST / WebSocket / FIX 4.4 or CCXT-based.
✓ confirmed support per official framework docs. "partial" indicates incomplete or version-dependent coverage. "no" indicates not officially documented as supported.
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
Gemini provides the exchange and API access. TradingHost provides the production environment where your Gemini-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 Gemini.
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 or a native Gemini starter) for a working baseline.
- STEP 03
Deploy into a TradingHost container
Pick a region (EU or US-East), supply the environment values your strategy needs (Gemini API keys, master- or account- prefix, HMAC-SHA384 secret), 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 Gemini
Things that bite you when you actually run a Gemini strategy in a containerised cloud runtime, not in Gemini’s docs, not in framework READMEs. Every claim below is quoted or paraphrased from Gemini’s own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · Auth
Gemini signs with HMAC-SHA384, not SHA256
Every private request needs X-GEMINI-APIKEY, a base64-encoded JSON payload in X-GEMINI-PAYLOAD, and the hex HMAC-SHA384 of that payload (using the API secret as the key) in X-GEMINI-SIGNATURE. Libraries copy-pasted from Coinbase or Kraken examples almost always default to SHA256 and silently fail with InvalidSignature. The signed payload must include the request path and a nonce, plus the account parameter when using a master key.
02 · Key model
master- keys act on a group, account- keys act on a single account
Gemini groups multiple accounts under one institutional structure. A key with the master- prefix can target any account in the group by passing the account nickname in the request payload’s account field; a key with the account- prefix rejects that parameter. Picking the wrong key type is the most common cause of MissingRole / 403 errors. Keep deployment-specific keys at the account level; reserve master keys for treasury automation.
03 · Nonces
Each API key gets its own nonce stream within ±30 seconds of Unix time
Gemini documents nonces as monotonic per session (per API key), so two keys can run on different containers without clock coordination. The nonce must be strictly greater than the previous one for that key and within ±30 seconds of the current Unix epoch; violating either rule returns InvalidNonce. Running one key from two containers is the usual failure mode. Provision a separate key per strategy runtime and treat the key as the unit of horizontal scale.
04 · Sandbox
Validate against api.sandbox.gemini.com before touching production
Sandbox lives at https://exchange.sandbox.gemini.com (UI) and https://api.sandbox.gemini.com plus wss://api.sandbox.gemini.com (API). Accounts are seeded with test USD, BTC, ETH, BCH, LTC, OXT, LINK, BAT and DAI; prices drift from production. Production keys do not work in sandbox and vice versa. Two-factor can be bypassed for automation with the 9999999 code.
05 · Rate limits
Public 120/min, private 600/min, with a 5-request burst queue
Gemini documents 120 requests per minute on public endpoints and 600 on private endpoints, with steady-state of 1 and 5 requests per second respectively. The exchange queues up to five excess requests and then returns HTTP 429 with the RateLimit reason. Order management bursts at the open or during volatility are the classic cause of self-inflicted 429s; batch and stagger cancels.
SourceGemini rate limits06 · Risk
Cancel All Session Orders is your kill switch
Every order is recorded against the API key that created it. The Cancel All Session Orders endpoint targets only that key’s open orders, so a runaway strategy can be killed without taking down sibling strategies running on different keys in the same account. Wire this into your container’s SIGTERM handler so deployments don’t leave stale orders alive. Pair it with Cancel All Active Orders for emergency account-wide stops.
07 · Hardening
Lock keys to your TradingHost egress IPs before enabling withdraw scope
Gemini supports Trusted IP allowlisting on API keys; off-allowlist requests fail with RemoteAddressForbidden. Keys also have separate scopes for trading, fund management and withdrawals; granting withdrawal scope on a strategy key is the wrong default. Treat withdrawals as a separate operations key, IP-pinned to a control host, and let strategy runtimes use trading-only keys.
Section 06 · Built for
Built for
TradingHost Gemini runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Systematic crypto traders
- US-regulated institutional desks
- 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 Gemini. Gemini Trust Company, LLC is a New York limited-purpose trust company chartered by the NYDFS in October 2015; its parent listed on Nasdaq as GEMI in September 2025. The regulated trust status is independent of TradingHost.
No. Your strategy code connects to Gemini and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. Gemini API access is provided by Gemini. You are responsible for your Gemini account, API permissions, credentials and compliance with Gemini’s terms.
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 ships a gemini connector with spot coverage and includes perpetual swap handling in its source. Verify symbol and margin endpoint coverage against your current CCXT release before relying on derivatives features; the native Gemini REST and WebSocket APIs remain the lowest-risk path for derivatives. See the CCXT framework runtime for the 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. Gemini’s per-session nonce model pairs naturally with one API key per strategy. See the TradingHost runtime page for the multi-strategy model.
The fastest path is to fork a TradingHost framework runtime such as CCXT, or connect your own GitHub strategy repo built around the native Gemini REST, WebSocket or FIX 4.4 surface. 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. Gemini supports scoped permissions for trading, fund management and withdrawals, plus Trusted IP allowlisting. Keep strategy keys at trading-only scope and pin them to the TradingHost egress IPs for your selected region; reserve withdrawal scope for a separate operations key on a fixed-IP control host.
Gemini returns MissingRole (HTTP 403) when an API key lacks the scope for the endpoint, and RemoteAddressForbidden when the request comes from an IP not on the key’s Trusted IP allowlist. InvalidSignature and InvalidNonce are the other two auth-class failures to wire into alerting.
Two containers using the same API key race each other’s nonce sequence. Gemini scopes the nonce stream per key (session) and the value must be monotonically increasing and within ±30 seconds of Unix time. Provision a separate API key per runtime instance; use a time-based nonce only with single-writer semantics.
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. Wire Cancel All Session Orders into your SIGTERM handler so deployments don’t leave stale orders alive; your strategy code is still responsible for safe error handling, duplicate-order protection and risk controls. See observability for the logs and health surface.
TradingHost runs in the EU and US-East regions. Gemini’s FIX 4.4 connectivity needs a cross-connect from an approved data centre or extranet into its US East Coast footprint, so US-East is the natural choice for latency-sensitive Gemini strategies. See the regions page for routing and proximity details.
Yes. Gemini Trust Company, LLC is a New York limited-purpose trust company chartered by the NYDFS in October 2015, making it a fiduciary and qualified custodian under New York Banking Law. Gemini Trust’s parent listed on Nasdaq as GEMI in September 2025. The regulated trust status is independent of TradingHost.
No. Gemini Earn was a yield product (not the spot exchange or API) that wound down via the Genesis bankruptcy. Customers received 100% in-kind recovery during May to June 2024 distributions; the SEC voluntarily dismissed its case against Gemini Trust with prejudice on January 23, 2026. It does not affect exchange access, API behaviour, or custody operations.
Where eligible, yes. Gemini Perpetuals is operated by Gemini Artemis Pte. Ltd. in select non-US jurisdictions, with up to 100x leverage and contracts denominated in GUSD (e.g. ETHGUSDPERP) or USDC. US retail access is being built out via the CFTC-approved Gemini Titan designated contract market. Verify your account’s jurisdiction and the symbol’s listing venue before deployment.
No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack, framework or AlgoBuilder.