Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Industry ProvidersProvider profile

Tradefeedr: FX execution analytics, forecasting and shared trading data

Tradefeedr standardises institutional FX trading data for cost analysis, algorithm forecasts and broker reviews. This profile covers the four API families, integrations, data permissions and analytical AI workflows.

By FXBrokers.ai ResearchOperating status: ActivePublished Sources checked

Tradefeedr provides a common data and analytics layer for institutional FX trading. It combines trading records from liquidity providers, venues and clients so that execution can be reviewed on comparable measures. Users include investors, corporates, regional banks, brokers, liquidity providers and trading platforms. The service supplies analysis and collaboration tools within the trading workflow.[1]

Analytics services and customer workflows

Sections ↑

The main distinction is between understanding an execution and selecting how to execute the next order. Post-trade tools compare fills, costs and market impact; pre-trade forecasting uses historical observations to estimate an algorithm’s likely behaviour. A trading desk can use those results for broker reviews, liquidity allocation or an execution-policy discussion.[3][8]

Reference table01

Four documented FX analytics families

Four documented FX analytics families
API familyPrimary analysisUseful outputs
AlgoParent instructions, child fills and algorithm execution.Parent-order statistics, profit-and-loss and event history, markouts, market data, execution statistics and risk-transfer cost.Source 4
RFSRequest-for-stream execution.Summary statistics, execution history, execution statistics and markouts.Source 4
RFS BilateralAgreed sharing of aggregated client execution information with selected liquidity providers.Execution quality, market-impact curves and market-share history after sensitive information is removed and data aggregated.Source 4
RFQRequest-for-quote execution, for outrights and swaps.Execution history/statistics, opportunity reports and participation reports.Source 4

The Algo workflow links the client’s parent instruction, including amendments, with the provider’s child fills. LSEG’s overview identifies those as the essential inputs for meaningful analysis; extra events such as order placements and rejections can also be analysed where supplied. The platform also provides execution-speed studies, single-order drill-down, backtesting, forecasting and trend reports.[3]

LSEG describes Algo Forecasting as selecting candidate bank algorithms using currency pair, trade size, time of day, liquidity conditions and the user’s risk policy. The model draws on observed trades and cost estimates. A forecast is a decision-support output; it does not lock in a future fill price or execution duration.[8]

Delivery channels and trading-platform connections

Sections ↑
Reference table02

Documented integrations

Documented integrations
ConnectionWhat is integratedScope and date
LSEG WorkspacePre-trade cost modelling and post-trade execution analytics within the FX workflow.LSEG announced the first integrated deliverable in December 2024; its developer portal also documents Tradefeedr APIs.Source 7
LSEG Workspace and Microsoft TeamsNatural-language requests for Tradefeedr analytics and reports, with discussion in bilateral chats.LSEG’s December 2025 explainability note describes analytics queries converted into structured API calls.Source 9
FlexTRADER EMSTradefeedr API data and customisable analytics in the order blotter.FlexTrade’s December 2021 release confirms a first live production client and an add-on for existing customers.Source 12
MarketFactoryShared trading markouts, impacts and spreads within MarketFactory’s service.ION’s October 2021 announcement describes a fully integrated analytics add-on for new and existing customers.Source 13
Reactive Markets SwitchboardOptional streaming of FX post-trade data to Tradefeedr.Reactive’s December 2021 release describes a live integration for clients who opt in, with data appearing within minutes.Source 14
BMLLHistorical equities and futures order-book datasets combined with Tradefeedr APIs.Announced 25 March 2026 as a year-long pilot; this is development beyond the established FX service.Source 15

Tradefeedr also publishes a browser-based environment with an integrated Python workspace. Traders can use templates and configurable dashboards; developers can extract raw transactional tick data and calculated statistics into internal applications. This provides a route to reuse the analysis beyond a single screen.[2]

LSEG’s April 2026 description places Tradefeedr analytics inside a workflow spanning data, execution context and counterparty collaboration. Its current FX workflow page describes natural-language access and shared performance reports. Those functions concern retrieving and discussing analytics; they do not, by themselves, confer authority on a Tradefeedr assistant to place a trade.[10][11]

Commercial access and pricing

Sections ↑

The current public platform and API pages do not provide a standard per-seat, per-provider, data-volume or API-call tariff. LSEG’s Tradefeedr catalogue offers a trial-enquiry route; it does not specify a universal trial duration or production entitlement. Commercial access should therefore be tied to the direct or integrated service actually being supplied.[6][7]

Reference table03

Commercial evidence by route

Commercial evidence by route
RoutePublished commercial position
Direct browser and API servicePublic product information describes the capabilities but does not publish a complete rate card or subscription term.Source 1
FlexTRADER EMSThe partner release describes an add-on for existing FlexTrade clients; analytics availability is not evidence of inclusion in every EMS licence.Source 12
MarketFactoryION describes Tradefeedr analytics as an add-on to the MarketFactory service for new and existing clients.Source 13
Historic buy-side pricing statementThe December 2021 Reactive partnership release quotes zero fees for buy-side clients. That dated statement does not establish current pricing for every module, partner channel or new asset-class pilot.Source 14

Data implementation and operating controls

Sections ↑

The platform normalises the underlying trading records before applying common analytics. Collaboration then adds a separate permission layer: a client can choose to share anonymised, aggregated measures with its liquidity provider or pool data with peers. Shared dashboards and notebooks support the subsequent discussion. Data access and permission to share it are distinct decisions.[2]

Reference table04

Documented data and delivery mechanics

Documented data and delivery mechanics
ComponentPublished behaviour
Partner data feedThe Reactive integration streams post-trade records after client opt-in. This is a documented ingestion route, not a claim that every venue is connected automatically.Source 14
Cloud service and uploadTradefeedr’s backup policy describes public-cloud SaaS, HTTPS access and an SFTP upload area with unique user credentials.Source 16
Query structureLSEG’s Python notebook uses endpoint calls with JSON parameters for grouping, selected variables and filters; results are JSON objects that can be converted to pandas tables.Source 5
Bilateral reportingThe RFS Bilateral reference describes removal of sensitive information and aggregation before sharing with the liquidity providers specified by the client.Source 4
Recovery processThe backup policy describes automated jobs, weekday status checks and reruns of failures the next working day. Data-recovery or reversion requests go to the IT service desk.Source 16

The LSEG notebook demonstrates calls through the LSEG Data Platform and an LSEG Data Library session. It is useful implementation material for that distribution route, not proof that the same authentication or entitlement model applies to every direct Tradefeedr deployment. The public quick start links to the notebook and Tradefeedr’s own analytics documentation.[5][6]

Support and contact routes

Sections ↑

Published assistance channels

Tradefeedr enquiries and complaintsEmail
[email protected]Source 16

Scope Published route for questions about the website or services; also used for privacy enquiries.

LSEG Tradefeedr documentationWebsite
https://developers.lseg.com/en/api-catalog/tradefeedr/tradefeedr/documentationSource 4

Scope Public overview of API families and analytics functions.

LSEG Python quick startWebsite
https://developers.lseg.com/en/api-catalog/tradefeedr/tradefeedr/quick-startSource 6

Scope Links to the worked notebook and Tradefeedr analytics documentation.

Tradefeedr’s policy provides an IT service-desk route for recovery requests, but no public response-time target, recovery-time objective or recovery-point objective was identified. Its general contact route is not evidence of a 24-hour trading desk. Contracted operational support and retention terms remain separate from the website policies.[16]

Analytics role, data sharing and AI scope

Sections ↑

This profile covers trading analytics supplied by a technology company. The documented outputs are data, performance measures, forecasts and reports. Brokerage execution and custody remain functions of the separately contracted trading institutions and platforms; a Tradefeedr integration is not a retail brokerage permission or custody arrangement.[1][7]

Reference table05

Controls and scope distinctions

Controls and scope distinctions
AreaDocumented position
Sharing permissionsThe platform describes bilateral sharing of anonymised aggregate performance measures and permissioned peer pooling. It is not unrestricted access to all clients’ raw trades.Source 2
Information securityTradefeedr describes encrypted data and credentials and SOC 2 compliance. These are provider statements; an underlying assurance report, period and exceptions were not inspected.Source 2
Natural-language analyticsLSEG’s explainability note describes prompts converted into Tradefeedr API requests for specific analytics/reports, returned as cards, graphs or tables. It also describes compliance logs for review.Source 9

The Tradefeedr AI function in LSEG’s note is analytical: it translates a user’s intended analysis into a structured request and supports discussion of results. This should be separated from LSEG’s other AI or dealing functions, which have their own descriptions and controls in the same document.[9]

Operator and company background

Sections ↑

Tradefeedr Limited is an active Northern Ireland private company, number NI645020, incorporated on 4 April 2017. Companies House lists its registered office at Murray House, 4 Murray Street, Belfast BT1 6DN. This corporate identity is separate from the trading firms and technology partners connected to its network.[18]

The company identifies Balraj Bassi as co-founder and chief executive, Dr Alexei Jiltsov as co-founder, Seth Johnson as chairman and Tim Cartledge as chief data officer. Its published team history combines FX trading, quantitative finance and electronic-market experience, and it lists Michael Spencer’s IPGL among its investor relationships.[17]

Operator
Tradefeedr Limited
Service scope
Institutional FX trade-data normalisation, transaction-cost analytics, algorithm forecasting and permissioned client/LP collaboration. APIs and browser tools are available directly and through documented partners; equities/futures expansion is a separate announced pilot.
Customer types
Asset managers and institutional investors; Corporates; Regional banks and brokers; Liquidity providers; Trading platforms; Market-data vendors
Delivery
SaaS; API
Pricing publication
Not disclosed
Platforms
Tradefeedr browser analytics; Tradefeedr APIs; Algo Forecasting
Integrations
LSEG Workspace; LSEG Data Platform; Microsoft Teams: LSEG analytics workflow; FlexTRADER EMS; MarketFactory; Reactive Markets Switchboard; BMLL: equities/futures pilot
Pricing scope
Current full tariff not published. Historical buy-side zero-fee statement is dated December 2021 and is not treated as a universal current entitlement.
Implementation
Normalised trade-data feeds, browser templates/Python workspace and documented APIs. Partner ingestion may require explicit opt-in; bilateral aggregate sharing is separately permissioned. LSEG supplies worked API examples for its distribution channel.
Support
Published [email protected] enquiry/complaint route, IT service desk for recovery requests and partner developer documentation. Public support hours, response targets and RTO/RPO were not established.
Permissions and regulatory scope
Tradefeedr is profiled as an analytics/data technology supplier. Company registration and security statements do not confer brokerage or custody permissions. Execution and custody remain with the separately contracted institutions.

Provider metadata checked 21 Oct 2026Source 1Source 2Source 3Source 4Source 16Source 18Source 14Source 7Source 5Source 8Source 9Source 12Source 13Source 15

Additional Information

Sections ↑
Reference table06

Interpreting execution measurements

Interpreting execution measurements
SettingWhy it matters
Risk-transfer benchmarkThe Python guide distinguishes Tradefeedr’s fitted model, a bank-reported benchmark, a user-uploaded static benchmark and a volatility-adjusted user benchmark. These are different reference prices.Source 5
Missing bank benchmarkBankReported is available only for providers that supply it; the documented result is None for others.Source 5
Performance versus shortfallThe notebook supports both notations. Positive values mean favourable results in performance notation and unfavourable results in shortfall notation.Source 5
RFQ participationThe RFQ analysis separates execution results from participation and opportunity reporting, allowing a review to include quotes and opportunities beyond completed trades.Source 3

BMLL and Tradefeedr’s March 2026 project invites participants to shape metrics, validate data quality and provide feedback on benchmarks and reporting for equities and futures. The announcement describes a pilot built on harmonised historical datasets and existing Tradefeedr distribution. It should not be read as a completed launch of every BMLL asset class within the standard FX product.[15]

Follow the evidence

Sources & further reading

  1. Tradefeedr API overview and FX workflow families LSEG Developer Community · Accessed 21 Oct 2026
  2. Tradefeedr API reference: Algo, RFS, RFS Bilateral and RFQ LSEG Developer Community · Accessed 21 Oct 2026
  3. Getting Started with Tradefeedr API: Python notebook LSEG Developer Community · Accessed 21 Oct 2026
  4. Tradefeedr Python quick start LSEG Developer Community · Accessed 21 Oct 2026
  5. LSEG Workspace AI Explainability Note, version 100.03 LSEG · 16 Dec 2025 · Accessed 21 Oct 2026
  6. LSEG FX and Tradefeedr: AI-enabled analytics workflow LSEG · 29 Apr 2026 · Accessed 21 Oct 2026
  7. Tradefeedr analytics integrated with FlexTRADER EMS FlexTrade · 2 Dec 2021 · Accessed 21 Oct 2026
  8. MarketFactory and Tradefeedr integration ION · 7 Oct 2021 · Accessed 21 Oct 2026
  9. Tradefeedr company and leadership Tradefeedr · Accessed 21 Oct 2026
  10. Companies House: Tradefeedr Limited, NI645020 Companies House · Accessed 21 Oct 2026

This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.

Report an error or submit an update