Tick vs Trade Imbalance Gap
Tick vs trade imbalance gap.
What it measures
The gap between count-based and size-based reads of directional pressure: tick_imb − trade_imb. The two agree when pressure is uniform across trade sizes; a gap means the tape leans one way in number of prints and another in volume — many small orders walking price while size leans against it, or the reverse. The decomposition follows the spirit of Easley & O'Hara (1992): trade count and trade size carry different information.
References: Easley-O’Hara 1992.
Point-in-time, leak-free
Like every QUANT_API feature, flow.tick_trade_imbalance 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
flow.tick_trade_imbalance unlocks on the Signal plan ($99/mo) and every plan above it. Every new account starts with a 14-day free trial of the Signal plan — no card required.
Example call
Resolve the latest value for BTC (5m window, delta transform — both available on the Signal 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=flow.tick_trade_imbalance@5m:delta"Same key works on /v1/features/historical for point-in-time backtesting — see the API docs.