Automated MT5 trading that runs like a real desk.
Your broker already trusts your MT5 client. We do not replace it. iQntX ships a hardened EA that talks to a 32-agent AI brain running on the same machine — and lets your broker do what it has always done: fill orders.
Why MT5 was the right choice
Building a custom broker integration is the most expensive way to lose money in trading-tech land. Every broker has its own quirks, its own rate limits, its own permission tree, its own ten-page API guide. Every webhook hop introduces a few hundred milliseconds of slippage. Every custom integration breaks the moment the broker updates a header.
MetaTrader 5 is the broker-side standard. Every regulated retail broker either runs MT5 natively or supports it via cTrader/MT4 bridges. Your broker already trusts the MT5 client running on your machine. They have already done compliance on it. They already fill orders from it without question.
iQntX ships a hardened MT5 EA that hooks into that existing trust relationship. We don't replace what works; we put a 32-agent brain behind it.
The EA state machine
STATE_IDLE
↓
STATE_CAPTURE_CHARTS ← H1/H4/M15/M1 + volume
↓
STATE_WAITING_FOR_BRAIN ← FastAPI ingress on 127.0.0.1:8765
↓
STATE_EXECUTING_DIRECTIVE ← OPEN / CLOSE / MODIFY / BE
↓
STATE_IDLE ← back to top
If the brain stops responding (FastAPI down, watchdog halt, broker disconnect), the EA transitions to STATE_PAUSED and emits an emergency event. It does not invent trades. It does not retry.
What the EA is, and what it isn't
| Role | EA does | EA does NOT |
|---|---|---|
| Chart capture | Snapshot H1/H4/M15/M1 with volume | Decide what they mean |
| Network | Localhost POST to ingress | Talk to any external service |
| Execution | Fire orders, modify SL/TP, close positions | Generate strategy or sizing |
| State | Track open positions, account, margin | Decide stance or risk policy |
| Heartbeat | Emit every N seconds to the watchdog | Decide what to do when heart is lost |
The EA is dumb on purpose. The 32-agent brain is smart. The boundary is enforced by network namespace: EA ↔ brain talks only on 127.0.0.1.
The five pipelines
The FastAPI ingress dispatches every EA POST to one of five pipelines:
- Phase 1 — Regime classification. Sonnet looks at H1/H4/M15 charts, outputs
STRONG_TRENDING_BULLISH/RANGE_BOUND/CHOPPY/ etc. - Phase 2 — Trade decision. Opus looks at M15/M1 + volume, outputs
{action, SL, TP, confidence}. - Manage Trades. Periodic snapshot of open positions → Opus issues
CLOSE/MODIFY_SLTP/BEdirectives. - Behavior. Opus configures EA caps (max positions, max lot per symbol, etc.) for the active stance.
- News. Sonnet ingests Tier-1 economic events and flags windows where the Risk Gate auto-vetoes trades.
Each pipeline ends in a journal entry. The agent journal is the audit trail.
The hardened-EA audit
The current EA (v13.0, ea_fixed/Qi5_fixed.mq5) is the post-audit version after a March 2026 review found and fixed:
- Reentry bug in
STATE_EXECUTING_DIRECTIVEthat could double-fire on lost-confirmation. - Slippage handler that swallowed broker rejections silently.
- Heartbeat that didn't reset on resume from
STATE_PAUSED. - Symbol-lookup table that hardcoded broker prefixes.
All four are fixed in v13.0. The audit reports live in audit/ for transparency.
Setup, in three steps
- Install MT5 + log into your broker.
- Drop
Qi5_fixed.mq5intoMQL5/Experts/. Compile in MetaEditor. - Run
iqntx setupon the same machine. The Python brain installs as a NSSM service.
That's it. The EA attaches to a chart. The Python brain starts listening on 127.0.0.1:8765. The first iqntx admin status command shows you a green board.
What you can do from the CLI
| Command | Effect |
|---|---|
iqntx admin status | Stance, departments, open positions, watchdog state |
iqntx admin stance set DEFENSIVE | Manual stance override (CEO can flip back) |
iqntx admin halt l4 | Operator-initiated full halt |
iqntx admin resume | Acknowledge halt, resume from STATE_PAUSED |
iqntx admin journal today | Print today's journal in plain text |
iqntx admin report daily | Run report writer |
19 verbs total. Full audit trail of every admin invocation in admin_log.
Compatibility
- Brokers: Any MT5-compatible broker (FXCM, IC Markets, Pepperstone, Exness, OANDA, Tickmill, RoboForex, FBS, Admiral Markets, …).
- Instruments: FX majors, gold, silver, oil, equity indices, BTC/ETH and major crypto pairs your broker offers.
- Hardware: Windows 10/11 or Windows Server 2019+. 4 vCPU, 8 GB RAM is the recommended floor.
- Prop firms: Compatible in principle. You remain responsible for prop-firm-specific compliance.
Join the waitlist
Setup takes a single afternoon. Cohorts open in waves. Early-access pricing locks at signup.
You may also want
Frequently asked questions
Don't see your question? Email hello@iqntx.com — we'll add it.
Why MT5 specifically?
Because the broker already trusts it. Building a custom broker integration adds a permission boundary you do not want — and adds slippage from every webhook hop. MT5 is the most widely supported retail trading platform in the world; the iQntX EA is just another EA from the broker's point of view.
What does the EA actually do?
Three things: (1) captures H1/H4/M15/M1 charts and volume, (2) posts them to the local FastAPI ingress on 127.0.0.1:8765, (3) executes directives that come back — open/close/modify/break-even. It does not contain the trading logic; the 32-agent brain does.
Loopback ingress on 127.0.0.1 — why localhost?
Because we don't want any trading-related traffic crossing a network boundary. The EA posts to localhost. The Python process listens on localhost. No tokens travel over the wire, no public endpoint exists. A local-only API is the smallest blast radius.
Will my broker know I'm running iQntX?
They will see an EA running on your terminal — same as any other EA. They cannot inspect the EA's logic. They do not see traffic to localhost. You are running a third-party EA, which every MT5 broker explicitly permits.
What happens if the EA crashes?
The watchdog detects loss of heartbeat and issues an L4 HALT (close all positions, lock the EA). Restart is operator-triggered via the iqntx admin CLI; the system refuses to auto-recover from an unexplained halt because auto-recovery is exactly how unsupervised bots blow up.
Can I run iQntX on a VPS?
Yes — Windows VPS is the recommended setup. The system is a single Python process under NSSM plus the MT5 terminal; both run side-by-side. Most operators use a 4 vCPU / 8 GB Windows VPS in their broker's preferred region.
Does it work with prop firm accounts?
Yes, with caveats. Some prop firms restrict EA-driven trading or specific instruments. iQntX is compatible with prop accounts in principle, but you remain responsible for compliance with your prop firm's rules. The Risk Gate can be configured to enforce custom prop-firm constraints (max daily loss, max drawdown, etc.).
Get on the waitlist.
Be first in line when private access opens. We onboard in waves so the system never gets in front of itself.