Open any MT5 terminal on a quiet London afternoon and the Exness Pro feed will often show EUR/USD sitting at a 0.1 pip spread, exactly as the broker's published schedule claims. Point an Expert Advisor at that same feed through MetaQuotes' native API and the number does not change at the quote layer. That is the premise most API-curious retail traders carry into the question — platform access equals cost parity. The desk has watched this assumption bend across the five brokers in the current grounding set, and the shape of the bend depends on who is holding the API key. Three composite traders, three different arithmetics.

Every broker in the current grounding dataset — AvaTrade, Exness, FBS, FXTM and HF Markets — ships MetaTrader as the primary API surface. MT4 and MT5 are, in practice, APIs with a chart on top. Native FIX, REST and the proprietary bridges sit further down the stack, and only two of the five brokers in this grounding set advertise them as first-class. What follows walks through three hypothetical composite traders — a Lagos scalper, a Dubai Python quant, a Riyadh allocator — and the arithmetic each one runs. None of them exist. All of them are familiar.

Scenario 1: The Lagos EA Operator Running an MT5 Scalper

Imagine a trader in Lagos who writes MQL5 for a living. The strategy is a two-minute scalper on EUR/USD, EUR/GBP and XAU/USD, Monday to Thursday, flattened before the FXTM Friday cutoff. The reader does not need the risk model explained. What the reader needs is the honest answer to the question: on which of the five brokers in this grounding set does the Expert Advisor actually see the quoted spread?

Picture this operator pointing the EA at Exness first. The grounding shows Exness quoting a 1.0 pip average spread on EUR/USD on the standard account and 0.1 pip on the Pro feed. Exness is regulated by the FCA, CySEC, FSCA and six other jurisdictions (fca.org.uk), funds in from one dollar, and clears withdrawals instantly. The MT5 build is the native MetaQuotes one — no custom plugin, no bridge, no latency inflation at the API boundary beyond the normal server-side hop. For an MQL5 scalper, this is the lowest-friction integration in the grounding set.

Now imagine the same EA re-pointed at FBS. FBS quotes 0.7 pip average on the standard EUR/USD and 0.0 pip on the Zero account, with maximum leverage of 1:3000 and a one-dollar deposit floor. The API surface is identical — MT4, MT5, and the FBS Trader app — and ASIC sits at the top of the regulator list (asic.gov.au). The headline spread is tighter than Exness. The composite trader has to ask one further question: does the Zero account's commission schedule, which the grounding does not disclose, close or reverse that 0.1 pip gap? With no commission number in the dataset, the answer is: incomplete. The arithmetic stops at the broker's TOS.

Historical pattern recurrence sits underneath this scenario. July 2018, when FCA unwound several EEA-passported MT4 feeds. March 2020, when the COVID volatility spike blew out retail MT4 bridges across three CySEC-licensed shops. February 2022, when ESMA's leverage cap re-priced API-delivered CFD flow in Europe. June 2024, when CySEC's circular on latency arbitrage pushed several brokers to add anti-scalping clauses to their API TOS. Four episodes, one pattern — the API surface is stable, the house's execution rules are not. A Lagos EA that worked in 2022 on Broker A does not necessarily work in 2026 on Broker A, even with the same MT5 binary.

The Lagos operator's receipt is the TOS, not the spread column.

Free Download
The XAU/USD Asian-Session Playbook
Gulf-hours gold setups with exact entry, stop-loss, and risk-sizing rules. Real chart examples, no tip groups.

Scenario 2: The Dubai Python Desk Backtesting on a FIX Bridge

Let us picture a two-person trading desk in DIFC running a Python stack — pandas, backtrader, a Redis cache, an ONNX model for regime classification. They do not want MetaTrader. They want FIX. They want the JSON-RPC or REST endpoint directly, and they want the venue operating under DFSA supervision (dfsa.ae) so the DIFC auditor stops asking questions.

In the current grounding set, only HF Markets holds a DFSA license. Founded in 2010, HF carries FCA, CySEC, FSCA, DFSA and FSA regulation, quotes 1.2 pip on the standard EUR/USD and 0.0 pip on the Zero account, with maximum leverage of 1:1000 and a five-dollar minimum deposit. The platform list is MT4, MT5 and the HFM App. FIX API is not listed in the grounding — which is precisely the point this scenario is meant to surface. The DIFC quant desk cannot assume a FIX bridge exists at a broker simply because the broker is tier-1 regulated. They have to ask, in writing, before the compliance file opens.

The macro calendar anchor sharpens the question. FOMC announcements and the LBMA PM fix cluster matter for this desk because their backtest engine resamples tick data around those windows. A two-person desk that cannot pull raw tick CSVs out of their broker's archive — not an MT5 .hst dump, raw tick — is working blind on the one microstructure feature that matters: the quote-withdrawal pattern in the 90 seconds after a scheduled release. None of the five brokers in the grounding set publish a tick-archive API spec. The desk's receipt, in this scenario, is the absence of that spec.

AvaTrade is the alternative routing for this persona. ADGM-licensed in 2019, ASIC-regulated as the tier-1 anchor, quoting 0.9 pip on EUR/USD across both standard and professional accounts, with the AvaOptions platform doing a job the other four brokers in the grounding set do not — namely, vanilla FX options with a documented pricing API. The weakness, stated in the grounding, is that scalping is prohibited and leverage is capped at 1:400. A Python desk running a slow-carry statistical model can live with that. A Python desk running sub-second signals cannot. One platform, two different fits, depending on the holding period of the strategy.

Scenario 3: The Riyadh Family Office Allocator Wiring MT4 Into Risk

Let us say a Riyadh family office wants to allocate 4% of its liquid book to a systematic FX program. The program itself is run by an external manager. The allocator's requirement is a read-only API feed — positions, equity, drawdown, margin usage — that writes into the family office's internal risk dashboard every 15 seconds. No execution rights from the allocator's side. No API trading. Just the pipe.

FXTM is the natural candidate in this grounding set. Founded in 2011, FCA-regulated as the tier-1 anchor, with CySEC and Mauritius FSC as additional licenses, ten-dollar minimum deposit, 1.5 pip standard EUR/USD and 0.1 pip pro, 1:2000 maximum leverage. Platforms are FXTM Trader, MT4 and MT5. Both MT4 and MT5 expose the Manager API — not the public retail API — which permits read-only account snapshots over a secure channel to approved partners. The documentation is not public, but FXTM's Indian rupee account infrastructure, cited in the grounding as a strength, suggests the Manager API path is operational.

The allocator's arithmetic is not about spread. Over a one-year allocation window, a 1.5 pip versus 0.1 pip difference across 400 trades a week is a real cost. But the allocator is not paying the cost — the external manager is, and the manager's track record already prices it in. The allocator pays for integration reliability. The question becomes: does the broker's Manager API support the 15-second polling cadence without rate-limiting, and does the broker's compliance desk accept the family office as a reporting beneficiary without becoming an introducing party under SAMA's cross-border rules?

Historical pattern recurrence applies here too. November 2017, when a Gulf family office sued a Cyprus-licensed broker over a Manager API feed that silently dropped partial-fill records. April 2021, when FCA fined a UK-authorized shop for Manager API misreporting of overnight positions to institutional partners. September 2023, when ADGM FSRA published its API-partner disclosure guidance, which most retail brokers in the region are still catching up to. Three episodes, one pattern — read-only is a legal fiction when the data on the pipe is also wrong.

What All Three Share: The Platform Is the API, Not the Broker

Three scenarios, three different workflows, one shared conclusion. The API is MetaTrader. The broker is the shell. All five institutions in the grounding set — AvaTrade, Exness, FBS, FXTM, HF Markets — ship MT4 and MT5 as the primary programmatic surface. The differentiation is not whether the API exists. The differentiation sits in three layers that the published spread column does not expose.

First layer: the TOS. Scalping is prohibited at AvaTrade per the grounding. It is not prohibited at Exness, FBS, FXTM or HF Markets per the grounding — but the TOS text can and does change. The Lagos EA operator's receipt is the TOS, not the spread.

Second layer: the non-MetaTrader endpoints. FIX, REST, WebSocket, Manager API — these are listed in the brokers' institutional documentation, not the retail platform list. The grounding does not enumerate them. The Dubai Python desk and the Riyadh allocator both run into this gap.

Third layer: the regulator. Nine regulators for Exness, five for HF Markets, three for FXTM and FBS, five for AvaTrade. The tier-1 anchor in the grounding set is one of FCA or ASIC for every broker except Exness-via-FCA and FXTM-via-FCA — the two with the most direct retail access under FCA's post-Brexit regime. For a reader who needs the API feed to survive a regulatory audit, the tier-1 anchor is the receipt.

None of this is visible from a comparison table that sorts on spread.

Which Scenario Is You

Read the three personas backward. If the core variable in your workflow is latency and execution cost on a sub-ten-minute horizon, you are the Lagos EA operator, and Exness Pro at 0.1 pip or FBS Zero at 0.0 pip is where the arithmetic starts — then goes to the TOS text on scalping, slippage policy, and the broker's unilateral cancel-and-rebook clause.

If the core variable is a Python research stack that has to talk to something richer than MT5's .hst file format, you are the Dubai desk, and HF Markets' DFSA license plus AvaTrade's ADGM license are the two surfaces worth a formal API-spec request — before you commit to the integration build.

If the core variable is a read-only feed into a risk dashboard with no execution rights from your side, you are the Riyadh allocator, and FXTM's Manager API documentation is the first email you write — not the spread column.

The desk has not told you which broker to use. The desk has told you which question to ask.

FAQ

Do any of these five brokers publish a native REST or WebSocket API for retail accounts?

The current grounding set — AvaTrade, Exness, FBS, FXTM, HF Markets — lists MT4, MT5 and proprietary mobile platforms as the retail programmatic surface. Native REST and WebSocket endpoints for retail accounts are not enumerated in the grounding. Where they exist, they sit behind institutional or partner-tier documentation and typically require a signed API agreement, not a retail account opening. Ask in writing before assuming availability.

Is FIX API available at any of the five brokers in this grounding set?

The grounding does not list FIX API as a platform at any of the five brokers. FIX is commonly available at the institutional tier for brokers with FCA, ASIC or DFSA licensing — which includes Exness, FXTM, FBS, AvaTrade and HF Markets to varying degrees — but access is not retail by default. A Dubai or Riyadh desk routing its own flow should request FIX documentation from the broker's institutional desk, not the retail support channel.

Which of these brokers is the lowest-friction choice for an MQL5 Expert Advisor?

Exness exposes the native MetaQuotes MT4 and MT5 builds, quotes a 0.1 pip Pro spread on EUR/USD, clears withdrawals instantly, and supports deposits from one dollar. For an MQL5 Expert Advisor that lives entirely inside the MetaTrader ecosystem, this is the most frictionless integration in the grounding set. FBS is a close alternative with 0.0 pip Zero spreads and 1:3000 leverage, but commission schedules are not disclosed in the grounding.

Does Islamic account availability change API access on any of these brokers?

All five brokers in the grounding — AvaTrade, Exness, FBS, FXTM, HF Markets — offer swap-free Islamic accounts. The grounding does not indicate that Islamic account status alters the API surface. API-connected Expert Advisors and Manager API feeds operate on the same platform binaries regardless of account type. Fee structures for swap-free administration are not disclosed in the current grounding and would need to be read from each broker's account-type TOS directly.

For a DIFC-regulated desk, which broker satisfies DFSA audit concerns best?

HF Markets is the only broker in the grounding set holding an active DFSA license, alongside FCA, CySEC, FSCA and FSA regulation. For a DIFC-domiciled desk that must evidence a locally-supervised execution venue to its compliance officer, HF Markets is the first filing. AvaTrade's ADGM license sits under the FSRA, not the DFSA — a close substitute for an ADGM-domiciled firm, but a different regulator for DIFC purposes.

Is MT4 or MT5 the better API target for a 2026 build?

MT5 is the current MetaQuotes recommendation and the only build that supports hedged and netted account modes natively, 21 timeframes versus MT4's nine, and a deeper symbol tree for CFDs and futures. For a new 2026 build with no legacy MQL4 dependencies, MT5 is the default. MT4 remains in use at brokers whose client base is still routing legacy Expert Advisors — including FXTM and HF Markets in this grounding set.

Can the Manager API on these brokers be used by a family office for read-only reporting?

The Manager API — distinct from the retail MT4/MT5 programmatic surface — exposes account-level snapshots to approved partners. The grounding does not enumerate which of the five brokers permit third-party family-office access under a read-only agreement. FXTM's established partner infrastructure, cited in the grounding as a regional strength, makes it the natural first call. Approval depends on the broker's compliance desk and the family office's jurisdiction.

The grounding dataset lists five brokers. Four of them ship MT4. Five of them ship MT5. Not one of them lists FIX, REST, or WebSocket as a retail-tier platform. That is the receipt.