Read time … min

AI-native runtime for Axi trading strategies

Author Axi FIX 4.4 strategies 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.

By the TradingHost engineering team

Section 01 · At a glance

At a glance

Broker
Axi (formerly AxiTrader)
Broker type
Forex and CFD broker (Australia-origin)
Asset class
Forex, indices CFDs, commodities CFDs, share CFDs, cryptocurrency CFDs (entity-dependent)
Supported products
70+ spot FX currency pairs, major and minor indices CFDs, metals (XAU/USD, XAG/USD), energies, soft commodities and share CFDs. Crypto CFDs are entity-dependent. US clients are not accepted.
Runtime model
Containerised strategy runtime
Deployment source
GitHub
Languages
Any language that runs in a container
Common integrations
Axi FIX 4.4, MT4 + MT5 bridges, Axi Trading Platform (ATP), 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
Axi role
Broker account, market access, execution venue
Regulators
AxiTrader Limited (ASIC AFSL 318232, Australia); Axi Financial Services UK Limited (FCA firm reference 466201, UK); AxiCorp Financial Services Pty Ltd (DFSA, DIFC UAE). Axi is not CFTC-registered and does not accept US retail clients.
Retail leverage caps
Australia (AxiTrader Limited, ASIC, ESMA-aligned since March 2021): 30:1 on major FX, 20:1 on non-major FX and gold, 10:1 on non-gold commodities and non-major indices, 5:1 on stocks, 2:1 on crypto CFDs. UK (Axi Financial Services UK, FCA, ESMA-aligned): same caps. UAE (DFSA): per-jurisdiction caps. Offshore Axi entities (Saint Vincent) may permit higher leverage.
Affiliation
TradingHost is independent and is not affiliated with AxiTrader Limited, Axi Financial Services UK or AxiCorp Financial Services

Section 02 · What Axi offers

What Axi offers

Axi offers spot FX on 70+ pairs, indices and commodities CFDs, metals, share CFDs and (per entity) crypto CFDs through FIX 4.4, MT4, MT5 and the Axi Trading Platform (ATP). The TradingHost-compatible path is FIX 4.4; MT4 / MT5 strategies run inside their terminals rather than on TradingHost containers. US clients are not accepted.

Markets and strategy patterns

  • Axi FIX 4.4 strategies on 70+ FX pairs
  • Indices CFD breakout strategies (NAS 100, US 500, DAX 40)
  • XAU/USD precious-metals strategies
  • Energy CFD strategies (WTI, Brent)
  • Share CFD systematic strategies
  • Axi Trading Platform (ATP) account workflows
  • MT4 / MT5 bridge for EA migration paths

API surface

Product surfaces
70+ spot FX currency pairs, major and minor indices CFDs, metals (XAU/USD, XAG/USD), energies, soft commodities and share CFDs. Crypto CFDs are entity-dependent. US clients are not accepted by any Axi entity.
Connection methods
Axi FIX 4.4 for institutional-style and pro-retail execution. MT4 and MT5 bridges for EA-style strategies running inside the MetaTrader terminal. Axi Trading Platform (ATP) is Axi's proprietary web/mobile interface (manual or platform-internal automation, not a TradingHost runtime path).
Authentication
FIX session credentials (SenderCompID, Password and host) issued by Axi after onboarding. MT4 and MT5 accounts use account number plus password directly in the MetaTrader terminal. Demo and live FIX endpoints are separate.

For specifics, refer to Axi

Axi platform pages and ASIC / FCA registers are the source of truth. Confirm FIX-session specifications with Axi during onboarding.

Section 03 · Build with AI

Build your Axi strategy with AI

Pick an integration method, fork a TradingHost framework starter, and author your strategy in an AI IDE. Axi FIX 4.4 is the canonical TradingHost-compatible path; MT4 / MT5 EAs run inside the desktop terminal, not on TradingHost. NautilusTrader does not ship an Axi adapter.

  • Axi FIX 4.4

    Standard FIX 4.4 session for order routing and market data. The canonical TradingHost-compatible path.

  • Custom FIX engine

    quickfix, QuickFIX/J, OnixS or your own FIX 4.4 implementation against Axi FIX credentials.

  • MetaTrader 4 / 5 bridge

    Axi offers MT4 and MT5 for EA strategies. EAs run inside the desktop terminal, not on TradingHost.

  • Custom connector

    Your own Python, Java, .NET or Go integration against Axi FIX 4.4.

Framework support for Axi products

Axi FIX 4.4 spans Axi's full product surface. MetaTrader EAs run inside the terminal. Crypto CFD availability depends on the Axi entity.

FrameworkFXIndicesCommoditiesCFDCrypto CFDs
Axi FIX 4.4SupportedSupportedSupportedSupportedPartially supported
Custom FIX engineSupportedSupportedSupportedSupportedPartially supported
MetaTrader 4 / 5Partially supportedPartially supportedPartially supportedNot documented as supportedNot documented as supported
NautilusTraderNot documented as supportedNot documented as supportedNot documented as supportedNot documented as supportedNot documented as supported

✓ confirmed support per axi.com platform pages. "in terminal" means the strategy runs in the MetaTrader desktop. "entity-dependent" means availability depends on the Axi entity.

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

Axi provides the broker account and FIX 4.4 access. TradingHost provides the production environment where your Axi-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 Axi via FIX 4.4.

TradingHost

  • Keeps the runtime online.
  • Surfaces logs and health checks.
  • Region selection.
  • Controlled deployment surface.

Deployment flow

  1. STEP 01

    Connect GitHub

    Authorise TradingHost to access your GitHub account.

  2. STEP 02

    Link a repo or start from a framework

    Point TradingHost at your existing strategy repo, or fork a TradingHost Axi FIX 4.4 starter.

  3. STEP 03

    Deploy into a TradingHost container

    Pick a region (EU for Axi Financial Services UK FCA traffic and EU clients; US-East when paired with US market data), supply the environment values your strategy needs (Axi FIX SenderCompID, Password, host and port), and deploy. TradingHost builds your container from the repo and runs your strategy on managed Kubernetes infrastructure.

  4. 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.

  5. STEP 05

    Update and redeploy

    Push changes to your GitHub main branch and TradingHost redeploys automatically.

Deploy

Section 05 · Operational notes

Operational notes for Axi

Things that bite you when you actually run an Axi strategy in a containerised cloud runtime. Every claim is paraphrased from Axi's own pages or the relevant regulator's register; the deployment-side guidance is from running these strategies on TradingHost.

  1. 01 · FIX 4.4

    Axi FIX 4.4 is standard FIX with no published institutional-only minimum

    Axi's programmatic surface is standard FIX 4.4 with Quote and Trade sessions. Unlike some institutional FX venues, Axi does not gate FIX behind a publicly-published minimum-deposit threshold; the API surface is accessible to retail clients on a sensibly-funded account after KYC. Confirm the current onboarding requirements with Axi at sign-up, because broker policies on this can change.

    SourceAxi platform pages

  2. 02 · Multi-entity

    Leverage and product availability depend on the Axi entity

    AxiTrader Limited (Australia, ASIC AFSL 318232), Axi Financial Services UK Limited (FCA firm reference 466201), AxiCorp Financial Services Pty Ltd (DFSA, DIFC UAE) and offshore Axi entities (Saint Vincent) operate separately. UK and AU entities apply ESMA-aligned 30:1 majors caps. Offshore entities may permit higher leverage. The API surface is the same across entities, but a strategy that hard-codes leverage assumes the entity.

    SourceASIC AFSL register (AxiTrader 318232)FCA register (Axi Financial Services UK 466201)

  3. 03 · US clients

    No Axi entity accepts US retail clients

    Axi is not CFTC-registered and none of its entities accept US retail clients. The Axi onboarding flow rejects US-resident applicants at the KYC stage. Strategies for US retail traders must use a CFTC-registered broker such as OANDA Corporation or FOREX.com.

    SourceAxi legal information (AU)

  4. 04 · MetaTrader vs FIX

    FIX 4.4 is the TradingHost path; MetaTrader EAs run inside the terminal

    Axi supports MetaTrader 4, MetaTrader 5 and the Axi Trading Platform (ATP), but those are terminal-based or web-based products rather than a programmatic API a container can speak. The TradingHost-compatible runtime is Axi FIX 4.4. For MQL EAs, run MT4 / MT5 separately or port the logic to FIX.

    SourceAxi platform pages

  5. 05 · Rebrand from AxiTrader

    AxiTrader rebranded to Axi in 2021; legal entity name is still AxiTrader Limited

    Axi's customer-facing brand became 'Axi' in 2021, replacing 'AxiTrader' across the website and marketing. The Australian legal entity is still 'AxiTrader Limited' on ASIC's register under AFSL 318232. When citing the regulator-of-record on a TradingHost page, use the legal entity name. The UK legal entity is 'Axi Financial Services UK Limited' under FCA 466201, post-rebrand.

    SourceASIC AFSL register

  6. 06 · Trade reporting

    EMIR, MiFID II and ASIC reporting is Axi's responsibility

    Axi Financial Services UK Limited reports under FCA / MiFID II / EMIR rules. AxiTrader Limited reports under ASIC derivative trade-reporting rules. AxiCorp Financial Services reports under DFSA rules. TradingHost does not perform regulatory trade reporting on your behalf. The strategy code you run on TradingHost is your own algorithmic activity; reporting attaches to the Axi entity holding the account.

    SourceFCA register

Section 06 · Built for

Built for

TradingHost Axi runtimes are best suited to:

  • Developers building strategies in AI IDEs (Cursor, Claude Code)
  • FIX 4.4 quant FX developers without institutional minimums
  • Share CFD and indices systematic traders
  • AU and UK retail strategy developers
  • Teams moving from MetaTrader and 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 AxiTrader Limited, Axi Financial Services UK or AxiCorp Financial Services.

No. TradingHost is not a broker and is not a registered investment firm. TradingHost is a cloud runtime that runs your strategy code. The broker relationship, the account, the leverage, the execution and the regulatory protections all live with the Axi entity that holds your account.

No. Your FIX client connects to Axi and sends instructions according to your own logic. TradingHost provides the runtime where that code runs.

No. Axi FIX 4.4 access is provided by Axi after onboarding. You are responsible for your Axi account, FIX credentials and compliance with Axi's terms.

No. No Axi entity accepts US retail clients. US-resident traders need a CFTC-registered broker. See the OANDA or FOREX.com pages for US-accessible alternatives.

Yes. Axi FIX 4.4 is standard FIX, so any Python FIX engine (quickfix-python, simplefix, etc.) works against Axi FIX credentials.

Yes. TradingHost supports any language that can run inside a container. Axi FIX is standard FIX 4.4, so any FIX engine in any language works.

Yes, traditionally. If your strategy is an MT4 / MT5 Expert Advisor, that EA runs inside the MetaTrader terminal and traditionally needs a Windows VPS to stay online. For TradingHost, port the logic to Axi FIX 4.4; that becomes the TradingHost-compatible shape.

Open an Axi account, request FIX 4.4 credentials at onboarding. Fork a TradingHost Axi FIX 4.4 starter, 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.

Yes. Leverage is set by the Axi entity. AxiTrader Limited (ASIC) and Axi Financial Services UK (FCA) apply ESMA-aligned caps (30:1 majors). AxiCorp Financial Services (DFSA) follows DFSA rules. Offshore Axi entities (Saint Vincent) may permit higher leverage. The API surface is the same across entities.

In your GitHub-controlled secrets workflow. TradingHost reads the SenderCompID, Password and host details at runtime through GitHub repository secrets.

Yes. TradingHost supports MCP-based control for AI IDEs including Cursor, Claude Code, GitHub Copilot and CLI-based AI agents. MCP is a control and observability surface, not the trade execution path.

No. EMIR and MiFID II trade reporting is the broker's responsibility. Axi Financial Services UK reports under FCA / MiFID II / EMIR rules. AxiTrader Limited reports under ASIC derivative trade-reporting rules. TradingHost runs your code; the Axi entity handles regulatory reporting.

No. TradingHost is focused on production runtime and deployment. Backtesting belongs in your research stack or AlgoBuilder.