AI-native runtime for Independent Reserve 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
- Independent Reserve
- Venue type
- Crypto exchange (AU/NZ/SG/UK fiat onramp)
- Asset class
- Crypto
- Supported products
- Spot trading across AUD, USD, NZD, SGD and 40+ crypto assets; multi-network deposits and withdrawals since January 2025
- Runtime model
- Containerised strategy runtime
- Deployment source
- GitHub
- Languages
- Any language that runs in a container
- Common integrations
- Native Independent Reserve JSON HTTP API, 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
- Independent Reserve role
- Exchange account, API access, market access, execution venue
- Affiliation
- TradingHost is independent and is not affiliated with Independent Reserve or IG Group, its parent since January 2026.
Section 02 · What Independent Reserve offers
What Independent Reserve offers
Independent Reserve is an AUSTRAC-regulated Australian crypto exchange with strong fiat onramp coverage across AUD, USD, NZD and SGD. The product set is intentionally spot-only; there are no perpetuals, options or margin facilities. The API is a JSON HTTP surface signed with HMAC-SHA256 and an explicit expiry per request. Withdrawal endpoints require explicitly-flagged API-key permissions, scoped independently from trading. Multi-network deposit and withdrawal (introduced January 2025) lets you move assets like USDT and USDC across multiple chains. The IG Group acquisition closed in January 2026; credential migration may follow but the existing JSON API remains the integration target. Endpoint specifics change over time. The shape is durable; the precise rate-limit weights and asset list live in Independent Reserve's docs.
Markets and strategy patterns
- Spot strategies on AUD, USD, NZD and SGD pairs
- BTC and ETH execution against AUD
- Fiat-onramp-aware execution flows
- Multi-network deposit and withdrawal strategies
- Per-asset minimum-withdrawal threshold handling
- Cached market-data consumers (1-second refresh)
- Order-history backfills (30-minute cache window)
- AUSTRAC-regulated AUD execution
API surface
- Product surfaces
- Spot trading across AUD, USD, NZD, SGD and 40+ crypto assets. The product set is intentionally spot-only; there are no perpetuals, options or margin facilities. Multi-network deposit and withdrawal (introduced January 2025) allows assets like USDT and USDC to be moved across multiple chains.
- Connection methods
- Public GET endpoints for market data, private POST endpoints for orders and account state. JSON HTTP API; no WebSocket trading. Market data is cached on the server with a 1-second refresh; order history is cached for 30 minutes.
- Authentication
- HMAC-SHA256 with an API key, secret, nonce and explicit signature expiry on every private POST. Withdrawal endpoints require explicitly-flagged API-key permissions, scoped independently from trading permissions. Scope isolation matters here: a trading-only key cannot reach withdrawal endpoints regardless of session.
For specifics, refer to Independent Reserve
Specific endpoints, rate-limit weights, asset and pair lists, fee schedule and version history live in Independent Reserve's documentation. Treat these as the source of truth.
Section 03 · Build with AI
Build your Independent Reserve 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 Independent Reserve API
Direct control over Independent Reserve-specific behaviour, including the AUD/USD/NZD/SGD pair set and the explicit signature expiry per request.
CCXT
Common interface across Independent Reserve and other crypto exchanges. CCXT exposes Independent Reserve spot markets via the unified `independentreserve` class.
Freqtrade or Hummingbot
Independent Reserve is not a first-class connector in either framework. CCXT generic compatibility can carry spot strategies through Freqtrade where supported; Hummingbot has no listed connector.
Custom connector
Your own internal trading engine or proprietary Independent Reserve integration, signing private POSTs with HMAC-SHA256 and an explicit expiry.
Framework support for Independent Reserve products
Coverage is spot-only. CCXT supports Independent Reserve spot via the unified `independentreserve` class; Freqtrade can ride CCXT generic compatibility where its support permits; Hummingbot does not list a dedicated Independent Reserve connector. Native API access gives the cleanest path for AUD/USD/NZD/SGD-specific behaviour and for handling the multi-network deposit/withdrawal endpoints introduced in January 2025.
✓ confirmed support per official framework docs. "no" indicates not officially documented as supported. "partial" indicates limited coverage. 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
Independent Reserve provides the exchange and API access. TradingHost provides the production environment where your Independent Reserve-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 Independent Reserve.
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.
- STEP 03
Deploy into a TradingHost container
Pick a region (EU or US-East), supply the environment values your strategy needs (Independent Reserve API key, secret and the permission scope flags your code uses), 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 Independent Reserve
Things that bite you when you actually run an Independent Reserve strategy in a containerised cloud runtime, not in Independent Reserve's docs, not in framework READMEs. Every claim below is quoted or paraphrased from Independent Reserve's own documentation; the deployment-side guidance is from running these strategies on TradingHost.
01 · Withdrawal scope
Withdrawal endpoints require explicitly-flagged API key permissions
Independent Reserve scopes withdrawal endpoints behind an explicit permission flag set when the API key is issued. A trading-only key returns a permission error on any withdrawal endpoint regardless of the request body. This is operationally good: strategy keys should never carry withdrawal scope, and the venue enforces that scope split at the API surface rather than only at the UI. Use a separate manually-managed key on a fixed host for withdrawals; never put a withdrawal-scoped key on a strategy runtime.
02 · Multi-network
Multi-network deposit/withdrawal landed in January 2025; endpoint shape changed
Independent Reserve introduced multi-network deposit and withdrawal in January 2025 for assets like USDT and USDC. Older integrations that hard-coded a single-network assumption (one ERC20 address per asset, for instance) need to handle the network identifier on both deposit-address generation and withdrawal submission. If your code predates 2025, verify against the current API reference before shipping; legacy strategies still work for already-supported networks but cannot enumerate the new ones without the updated endpoint shape.
03 · Caching
Market data caches for 1 second, order history for 30 minutes
Independent Reserve caches market data on the server with a 1-second refresh window, and caches order history for 30 minutes. A high-frequency polling loop will see the same response payload from one second to the next; budget the strategy against the cache rather than a per-request quote. For order-history backfills, do not expect immediate reflection of a freshly-placed order; surface the order from the order-status endpoint instead, which is not subject to the 30-minute history cache.
04 · IG Group parent
IG Group acquisition closed January 2026; credential migration to watch
IG Group completed the acquisition of Independent Reserve in January 2026. The existing JSON HTTP API remains the integration target as of May 2026; no merged IG/Independent Reserve API has been published. Strategies should encode the venue as a first-class config value rather than assuming a stable URL forever: if IG-driven credential migration changes the auth shape, the runtime config can be flipped without rewriting the strategy. Watch the official announcements channel for any post-acquisition integration changes.
05 · Fiat surface
AUD, USD, NZD and SGD are first-class; pair availability is asymmetric
Independent Reserve's fiat surface spans AUD, USD, NZD and SGD, but per-asset availability is not symmetric across all four. BTC and ETH trade against every fiat; smaller-cap altcoins may only trade against AUD. A strategy template ported from a USD-centric venue can hit a `pair not found` rejection when applied to NZD or SGD. Enumerate available pairs at strategy startup, do not assume the per-fiat product set.
Section 06 · Built for
Built for
TradingHost Independent Reserve runtimes are best suited to:
- Developers building strategies in AI IDEs (Cursor, Claude Code)
- Systematic crypto traders
- Quant developers
- AUD/NZD/SGD fiat-onramp execution
- 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 Independent Reserve or IG Group, its parent since January 2026.
No. Your strategy code connects to Independent Reserve and sends instructions according to your own logic, account permissions and integration method. TradingHost provides the runtime where that code runs.
No. Independent Reserve API access is provided by Independent Reserve. You are responsible for your Independent Reserve account, API permissions, credentials and compliance with Independent Reserve’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 Independent Reserve spot markets via the unified `independentreserve` class. 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.
No. Independent Reserve is a spot-only exchange. There are no perpetuals, options or margin facilities on the venue. For derivatives, route your strategy to another venue that offers them and keep Independent Reserve for spot AUD/USD/NZD/SGD flow.
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 Independent Reserve API key and secret. See platform secrets for the full handling model.
No. Strategies should never need withdrawal permissions. Independent Reserve scopes withdrawal endpoints behind an explicit permission flag set when the key is issued; a trading-only key returns a permission error on any withdrawal endpoint. Keep withdrawal on a separate manually-managed key never used by a runtime.
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.
IG Group completed the acquisition of Independent Reserve in January 2026. The existing JSON HTTP API remains the integration target as of May 2026; no merged IG/Independent Reserve API has been published. Strategies should encode the venue as a first-class config value rather than assuming a stable URL forever, so a future migration can be handled with a config change. Watch the official Independent Reserve announcements channel for any post-acquisition integration changes. 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.