Skip to content

Venue Coverage

Chronix separates market-data support from execution support.

Market-data support means Chronix can ingest and normalize live venue data for terminal views, formulas, strategies, risk and historical storage. Execution support means Chronix can route live orders through the trading backend, track order state and consume private account/order updates.

The tables below separate implemented market-data connector coverage from live execution support. For client deployments, venue coverage should be stated by configured and validated venue/account, not only by connector implementation. The final supported list should be confirmed by configured accounts, API permissions, symbology, adapter configuration, smoke tests, monitoring and approval for the exact workflow.

The typical minimal onboarding scope for a straightforward new venue is symbology + market data + execution, with a rough 2-3 day estimate when the venue API has no major specificity.

Currently wired through the Chronix market-data layer:

VenueMarket-data support
AsterSpot, Swap
BinanceSpot, Margin, Swap
Binance USSpot
BitgetSpot, Swap
BithumbSpot
BloFinSpot, Swap
BybitSpot, Swap
CoinbaseSpot, Swap
CoinExSpot, Swap
Crypto.comSpot, Swap
Gate.ioSpot, Swap
GeminiSpot, Swap
HTXSpot, Swap
HyperliquidSpot, Swap
KrakenSpot, Swap
KuCoinSpot, Swap
OKXSpot, Swap
PoloniexSpot, Swap
PolymarketPrediction-market / swap-style venue

Client-facing claims should still distinguish connector implementation from deployed and validated venue support. A venue is production-ready for a specific client only after symbology, adapter config, account/API access, smoke tests and monitoring are validated for that workflow.

Currently wired through the Chronix trading/execution layer:

VenueExecution support
AsterSpot, Swap
BinanceSpot, Swap
BitgetSpot, Swap
BithumbSpot
BybitSpot, Swap
Gate.ioSpot, Swap
KrakenSpot, Swap
OKXSpot, Swap
PolymarketPrediction-market / swap-style venue

Execution support should always be presented together with the configured account, permission scope, smoke-test status and monitoring plan. Routing support and deployed production validation are not the same thing.