Enterprise: eContext
Trade context at point of RFQ.
When an RFQ lands on the trader's blotter, eContext delivers the market picture in real time. Embeds into OMS/EMS for venues, brokers, and banks running their own trading UI.
What it is
Your UI.
Ediphy analytics.
eContext is the enterprise framing of Ediphy's pre-trade analytics layer, exposed as an embeddable capability for platform operators. When an RFQ lands — or at the moment of a trading decision — an eContext panel appears alongside your existing UI without replacing it. The trader sees Ediphy's fair-value pricing, liquidity scores, axe-matching, and trade-context signals in a sidecar that pops up at exactly the right moment. Your UI stays in place; your workflow stays yours.
Built for platform embedding.
Four dimensions matter when a platform embeds another vendor's intelligence, eContext is engineered against each.
Real-time SLAs
Response times are SLA-backed and sized to ensure the context is available on the blotter at the moment the trader needs it, the operative latency requirement at point of RFQ.
REAL-TIME · SLA-BACKED
Mid, liquidity, axes, flow
Streaming independent mid (liveMid), bond-level liquidity scores, live axes from dealer streams, and historical flow context. Every signal that moves a trader's decision, in one payload.
LIVEMID · SCORES · AXES
API + widget
Integrate two ways: an API your UI calls at RFQ time, or a drop-in widget that renders the context panel in your frame. Pick the one that matches your build cadence.
API · WIDGET
White-label UI option
The widget can render entirely in your brand; Ediphy attribution is optional. Your platform, your trader, your relationship.
WHITE-LABEL
Sample API response
One call. Decision-ready payload.
When an RFQ lands, the embedding platform issues one call. The response carries the streaming independent mid, the bond-level liquidity score, the live axes from dealer streams in scope, and a flow-context summary, sized to render directly in the trader's blotter without further enrichment.
The payload on the right is illustrative. Field set is stable across the API and the widget, the widget is the same payload, rendered.
Who it's for
For platforms, venues,
and brokers.
eContext is built for the platform operators, venues, brokers, and banks that already support the trader relationship and own the trading UI, and want to deepen it with institutional analytics without building those analytics themselves. The typical deployment is measured in weeks, not quarters: the API is stable, the widget is production-hardened, and the data layer is the same one we operate for Ediphy's own trading products. You add a capability your competitors cannot match without buying a full execution stack.
Sell-side variant
At point of RFQ, client context on arrival.
For sell-side platforms and venues, eContext appears the moment an RFQ lands. The bundle carries the market picture alongside client context: who is asking, similar clients' recent activity, the instrument's own trade history, and a fair-value reference. The trader has the evidence needed to quote with confidence.
Platform operators embed this as an API call or a drop-in widget. The context panel renders in the trader's existing UI, your interface, your relationship, Ediphy intelligence.
Buy-side variant
At point of trade, market and own history, no client data.
For buy-side platforms, eContext appears at the moment of a trading decision, or on demand during instrument selection. The bundle delivers what matters for the buy side: market timing signals, similar instruments trading now, recent prints across venues, the institution's own historical trades in the instrument, and pre- and post-trade risk metrics.
Buy-side desks embedding eContext give their traders a decision-ready view of market conditions and own-position history, before the order is committed. The same API and widget surface; different context payload.
Embedding questions
What CTOs ask before integrating.
Embedding a third-party signal layer into a trading UI carries operational tail risk. Latency outliers, outages, and version drift each surface at inconvenient moments. The answers below are how Ediphy addresses each.
How is latency budgeted? +
Response times are SLA-backed. The widget short-circuits to a degraded display if the API misses budget, so the blotter never blocks on the embed.
What happens during an Ediphy incident? +
The widget falls back to a blank-but-functional state, your blotter continues to render, the trader continues to operate. Incident notifications go to your ops channel; the RFQ workflow does not break.
How is API versioning handled? +
Versions are pinned per-customer; we run old and new in parallel for at least one quarter after a breaking change. You move on your cadence.
Where does our trader data go? +
Inbound RFQ payloads are processed for the response and discarded. Aggregate flow signals you contribute back are opt-in and configurable per book. With the BYOC deployment, no data leaves your perimeter.
Can the widget be fully white-labelled? +
Yes. Ediphy attribution is optional. Default deployments render entirely in your brand, typography, palette, and chrome configurable. Custom design is also available through Ediphy Consult.