Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Murex adds native ICE streaming data, with access controls still part of implementation

The new MX.3 connector extends an existing data relationship into real-time feeds. Client software versions and market-data permissions determine how it can be deployed.

Murex has added a native connection from MX.3 to the ICE Consolidated Feed, allowing clients to receive streaming market data within their trading and risk platform. The 8 October announcement gives institutions another feed option alongside Murex’s existing real-time connections.[1]

Specifications01

What the ICE connection requires

What the ICE connection requires
ComponentPublished implementation position
MX.3 versionAvailable from version 3.1.68
ConnectorIDS-CF-MD, for ICE Consolidated Feed market data
Access controlsMurex Entitlement SPI connected to the client’s entitlement system, or a supported native system such as DACs

The relationship began in 2022. Earlier integrations brought interest-rate and inflation curves, volatility data, CDS credit curves and bond curves into MX.3. The new step is direct streaming connectivity, with the entitlement layer still governing which data users can receive.[1]

ICE’s consolidated service places multiple sources into a common format and covers exchange-traded instruments as well as OTC markets. Its content includes order-book and trade data, contributed prices and evaluated fixed-income prices. A single delivery channel can therefore carry economically different kinds of information: a transaction, a dealer indication and an evaluated price should retain their distinct meanings inside a trading or risk system.[2]

The distinction is particularly relevant in FX. ICE describes its OTC currency feed as indicative pricing contributed by market makers, trading platforms, execution venues, banks and brokers. The dataset includes spot, forwards and non-deliverable forwards. Receiving those prices supplies market information; it does not establish an executable bilateral dealing relationship with each contributor.[3]

ICE’s documentation also describes consistent instrument identifiers, market-status fields and timestamps while retaining original exchange representations. That standardisation can help applications consume different markets coherently, but the client still has to select the appropriate fields and permissions for its use. Some additional identifiers require separate licensing.[3]

Follow the evidence

Sources & further reading

  1. MX.3 connects to the ICE Consolidated Feed Murex · 8 Oct 2026 · Accessed 20 Oct 2026
  2. ICE Consolidated Feed: coverage and delivery Intercontinental Exchange · Accessed 20 Oct 2026
  3. ICE OTC Data Services: Foreign Exchange Intercontinental Exchange · Accessed 20 Oct 2026

Report an error or submit an update