Binance→Coinbase Lead-Lag
Binance→Coinbase lead-lag.
What it measures
The displacement at which the cross-correlation between Binance and Coinbase returns peaks (argmax cross-corr lag). It is a direct measurement of which venue is discovering price first and by how much — and it is not a constant: the lead can compress, stretch or hand over across sessions and regimes, which makes the moving estimate itself a state variable for cross-venue strategies.
References: Cross-exchange lead-lag.
Point-in-time, leak-free
Like every QUANT_API feature, cross_market.lead_lag_cb is computed point-in-time: each value uses only data that had actually arrived at the timestamp you query — live or historical. No restatements, no backfills that quietly rewrite the past, no look-ahead. The value your backtest sees at a given stamp is the value the live API would have returned at that stamp. How we enforce this is documented on the methodology page.
Windows & transforms
The signal is computed over rolling windows; each window can be served raw or through a transform (z-score, percentile rank, delta…). Which windows and transforms you can query depends on your plan — the signal itself supports:
Plan & access
cross_market.lead_lag_cb unlocks on the Quant plan ($2,500/mo) and every plan above it. Every new account starts with a 14-day free trial of the Signal plan — no card required. The trial covers Signal-plan features, so you can evaluate the API end-to-end before upgrading to Quant.
Example call
Resolve the latest value for BTC (5m window, zscore transform — both available on the Quant plan):
curl -G https://api.quant-api.dev/v1/features/live \
-H "Authorization: Bearer fk_live_<your_key>" \
--data-urlencode "asset=BTC" \
--data-urlencode "features=cross_market.lead_lag_cb@5m:zscore"Same key works on /v1/features/historical for point-in-time backtesting — see the API docs.