Bring the right market data into one pricing flow.

Institutional liquidity over FIX

CoinPriceFeeds can receive institutional market data through FIX sessions. Available connectors include LMAX, oneZero, and Match-Trade.

These connections are useful when the brokerage wants tradable institutional pricing to be the main input, a high-priority reference, or one leg in a wider consensus. Venue access and credentials remain the client’s responsibility, and connector availability is confirmed during onboarding.

The feed can re-establish its subscriptions after a venue reconnects, while source state remains visible to monitoring.

Exchange and reference-market inputs

Direct exchange data can add breadth, independent context, or a fallback leg—especially for crypto and related instruments. Available connectors include Binance spot and futures, Bitfinex, HitBTC, HTX/Huobi, and OKX. TrueFX and FXCM can provide additional FX reference inputs.

CoinPriceFeeds treats these as individual sources, not as one blended black box. A pricing rule can use several, prefer a selected subset, or leave an input out of a particular symbol entirely.

Source availability depends on venue access, instrument support, and onboarding checks. The website does not imply an exchange partnership.

Your own prices can be an input

A brokerage may already have useful prices in a trading platform, bridge, or proprietary calculation. Those quotes can enter the flow through an authorized client-side bridge or publisher.

That makes it possible to:

• keep an internal book as the preferred input;
• compare a proprietary price with independent references;
• reuse one source across several client-specific feeds; or
• migrate platforms without rebuilding the pricing policy around a new vendor’s names.

The brokerage must have the rights and venue permissions needed to use any source it provides. Private inputs remain scoped to that client’s pricing flow.

Symbol names follow your business

Venues rarely agree on instrument names. Your client-facing symbols do not need to inherit that inconsistency.

CoinPriceFeeds can map one venue instrument to one or more internal names. The pricing sheet then refers to stable names chosen for your operation, even when a venue uses a different convention.

This mapping also helps when the same source price needs to support multiple aliases across platform integrations.

Source state is part of the price

A source may be connected yet no longer valid for a particular instrument. Contracts can be suspended or delisted, an order book can become incomplete, or a venue can explicitly withdraw its quote.

CoinPriceFeeds recognizes source availability signals and prevents an invalid leg from quietly remaining in the calculation. Dependent outputs are recalculated from the valid inputs that remain. If a source simply becomes old, freshness-aware pricing rules stop accepting it.

That behavior connects directly to quote protection and the client dashboard, where the reason is visible.

Choose sources by role, not by logo

The useful question is not “How many venues are on the list?” It is “What job should each input do?”

A practical source design usually defines:

• which inputs are suitable for the primary price;
• which sources provide independent comparison;
• what qualifies as a valid backup;
• how symbols should be normalized; and
• what should happen when one input disappears.

The pricing engine turns those decisions into a per-symbol policy.