AI Agents For MT5 Trading

Why the MT5 Responsibility Map Matters

Daria, a 31-year-old fintech engineer at a prop desk, found a trade signal in a backtest that looked reliable. The signal came from a custom indicator, but the indicator also checked spread, calculated position size, and sent orders. When Daria attached it to two charts, both instances could submit the same trade. A second problem appeared during a terminal restart: the indicator had no clear way to reconstruct its trade state. The model was not the main failure. The boundary between the indicator and the Expert Advisor (EA) was.

The MT5 Responsibility Map fixes that boundary. An indicator answers, “What does the market data say?” An EA answers, “What should the account do?” An Artificial Intelligence (AI) agent can evaluate context, select a permitted action, or coordinate several models, but it should not quietly bypass the EA’s execution controls. Keeping these responsibilities explicit prevents duplicate orders, inconsistent state, and expensive model calls in the wrong event handler.

After applying the map, you can place each operation in the correct part of the MetaTrader 5 (MT5) event loop, define the data passed between components, and trace a model decision from a new price bar to an accepted or rejected trade request. You will also know which work belongs inside MQL5 and which work should run in an external service. The practical takeaway is simple: make the indicator descriptive, make the EA authoritative, and make the agent advisory unless you deliberately grant it a narrow, tested action interface.

How the MT5 Responsibility Map Works

MT5 drives an EA through event handlers. `OnInit()` runs when the EA loads, `OnTick()` runs when a market tick arrives, `OnTimer()` runs on a timer schedule, and `OnTradeTransaction()` reports changes related to trade requests and account state. A custom indicator normally uses `OnInit()` for setup and `OnCalculate()` for recalculating indicator buffers. These handlers do not provide equal-purpose execution slots. `OnCalculate()` should transform market history into values; `OnTick()` or `OnTimer()` should coordinate decisions and execution.

The MT5 Responsibility Map assigns each responsibility to one owner:

Use the following numbered sequence when mapping a new feature:

1. Classify the output. If the output describes price structure, volatility, or a model score, place it in the indicator or feature layer. If it changes account state, place it in the EA. This rule prevents a chart component from becoming an untracked trading engine.

2. Create a typed signal record. Pass fields such as symbol, timeframe, bar time, direction, confidence, and model version instead of passing a loose Boolean. The EA needs enough context to reject stale or duplicated signals.

3. Run agent reasoning behind a bounded interface. Give the agent a structured market snapshot and a fixed set of allowed actions, such as `HOLD`, `BUY`, `SELL`, or `CLOSE`. The EA remains responsible for checking whether the selected action fits account and strategy rules.

4. Validate before execution. Check spread, trading session, position limits, volume step, stop distance, margin, and current position state immediately before sending the request. Earlier checks can become invalid after a new tick.

5. Record the result. Store the decision identifier, request result, retcode, fill details, and reason for rejection. Without this record, you cannot distinguish a weak model decision from a broker or execution problem.

A useful signal record might contain `bar_time=2026.08.02 10:15`, `symbol=EURUSD`, `direction=BUY`, `confidence=0.78`, `feature_version=12`, and `decision_id=EURUSD-M15-20260802-1015`. The indicator can publish this record through buffers, global variables, files, or an in-process EA module. For production execution, an EA-owned feature calculation often reduces synchronization risk because the EA can read the same snapshot that it validates.

AI agents fit between signal creation and trade authorization. A classification model might estimate the probability of an upward move....