Compatibility & integrations
Connect the sources and platforms your brokerage uses.
CoinPriceFeeds can receive prices from trading platforms, hubs, bridges, exchanges, FIX sessions, and custom APIs, then deliver one controlled feed to several destinations.
- MT4, MT5, institutional, exchange, bridge, and custom inputs.
- Trading-platform, hub, bridge, Unifeeder, and FIX destinations.
- Source and destination paths confirmed in writing before a demo.
Use existing access
Bring the venue accounts, platform prices, and provider relationships your brokerage already has.
Keep one policy
Use the same client-specific pricing logic across several downstream systems.
Scope custom paths
Confirm protocol, network direction, authentication, symbols, and support before implementation.
On this page
What the compatibility matrix means
The tables below describe public integration categories, not an automatic entitlement to third-party data and not a claim of partnership with every named provider. A brokerage must hold the accounts, permissions, licences, and redistribution rights required for its sources.
“Supported” means CoinPriceFeeds has a practical connection path for that category. Exact fields, symbols, credentials, network direction, vendor configuration, and testing requirements are confirmed in writing. When a connection is client-specific, it is scoped before a demo or implementation begins.
Supported quote sources
Swipe or scroll horizontally to see all columns
| Source | Typical connection path | How it can be used |
|---|---|---|
| Cryptocurrency exchanges | Venue WebSocket or other real-time API | Primary, reference, aggregation, or fallback input for suitable instruments |
| Binance | Exchange market-data connection | Spot or derivatives inputs, subject to instrument scope and access |
| OKX | Exchange market-data connection | Spot or derivatives inputs with venue-state handling |
| HTX | Exchange market-data connection | Real-time best-bid-and-offer input |
| KuCoin | Exchange market-data connection | Crypto market input where required by the client scope |
| BitMart | Exchange market-data connection | Crypto reference or pricing input where enabled for the scope |
| Bitfinex | Exchange order-book connection | Real-time crypto pricing or independent comparison input |
| MetaTrader 4 | Authorized client bridge or price publisher | Prices already available in the brokerage’s MT4 environment |
| MetaTrader 5 | Authorized client bridge or price publisher | Prices already available in the brokerage’s MT5 environment |
| eSignal | Scoped data connection | Reference or primary input according to the client’s entitlement |
| CQG | Scoped data connection | Exchange or derivatives input according to the client’s entitlement |
| oneZero Hub | Hub or FIX-based market-data connection | Institutional or aggregated source prices |
| Takeprofit Bridge | Bridge connection | Prices already available through the client’s bridge environment |
| PrimeXM XCore | Hub or FIX-based connection | Institutional or aggregated source prices |
| Match-Trader | Platform or bridge connection | Prices available through the client’s Match-Trader environment |
| Other FIX APIs | FIX session with an agreed dialect and symbol map | Institutional, venue, reference, or client-provided market data |
| Custom WebSocket APIs | Documented client or provider API | Proprietary or specialist real-time inputs |
| Custom TCP APIs | Documented client or provider stream | Proprietary platform, bridge, or internal prices |
The exchange list is not exhaustive. Other sources can be reviewed when they provide a stable, authorized real-time interface and a clear instrument model.
Supported quote destinations
Swipe or scroll horizontally to see all columns
| Destination | Typical delivery path | Important scope questions |
|---|---|---|
| MetaTrader 4 | Client bridge, publisher, or compatible integration | Symbol mapping, update path, primary/backup behavior |
| MetaTrader 5 | Client bridge, publisher, or compatible integration | Symbol mapping, update path, primary/backup behavior |
| TradeLocker | Compatible bridge or custom platform integration | Accepted interface, symbols, environment, and test process |
| VertexFX | Platform-compatible integration | Destination format, symbol map, and failover ownership |
| oneZero Hub | Hub-compatible or FIX delivery | Session model, subscriptions, symbols, and network direction |
| Takeprofit Bridge | Bridge-compatible delivery | Feed format, symbols, environments, and acceptance checks |
| PrimeXM XCore | Hub-compatible or FIX delivery | Session details, symbol coverage, and connection ownership |
| Match-Trader | Platform or bridge integration | Supported interface, symbols, and test environment |
| Unifeeder-compatible consumers | Simple authenticated streaming TCP | Login, optional subscriptions, parsing, keepalive, and reconnect behavior |
| FIX API-compatible consumers | FIX 4.4 market-data delivery | Acceptor or initiator mode, session settings, subscriptions, and field mapping |
CoinPriceFeeds normally connects through the brokerage’s existing bridge, hub, FIX consumer, or integration layer. The matrix does not imply that a separately packaged native plug-in is supplied for every platform.
A source and a destination can be the same platform
Some platforms can appear on both sides of the flow. For example, prices may enter from one MT4 or MT5 environment, pass through client-specific pricing and protection, then be delivered to another platform or consumer.
The important boundary is the role of each connection:
- source: supplies an input price;
- pricing layer: decides how valid inputs become the client’s output;
- destination: receives the resulting bid and ask; and
- verification path: shows whether the intended feed arrived and whether primary and backup agree.
Keeping those roles explicit prevents a platform name from hiding where pricing responsibility actually sits.
What is confirmed before implementation
A written compatibility check should establish:
- the source and destination products and versions;
- who owns each account, entitlement, bridge, and API;
- protocol and connection direction;
- symbol names, precision, and expected instrument count;
- authentication and network allow-list process;
- primary and backup endpoints;
- representative quote and failure cases;
- monitoring and acceptance evidence; and
- the required integration and ongoing support level.
The written-first onboarding path explains how these answers move from a demo scope to production acceptance. Pricing factors are described on the pricing page .
Public detail stops at the integration boundary
Public pages explain the supported connection categories and client-visible behavior. Production credentials, private hostnames, private symbol mappings, client identities, exact FIX dictionaries, security material, and deployment topology are provided only to the authorized client team when needed.
A feed shaped around your setup
Request a demo for your connection path.
Start with the short form. We’ll ask by email for your sources, target destinations, preferred protocols, and one representative symbol.