Trade Intensity (per second)
Trade intensity (trades/sec).
What it measures
Trade arrival intensity: the count of trades per second over a rolling 30-second base window. Activity clustering is one of the most robust regularities in market microstructure — formalized in Engle & Russell's (1998) autoregressive conditional duration model — and trade intensity is its simplest observable. The same order-flow imbalance means different things on a tape printing a few trades a second and one printing hundreds.
References: Engle-Russell 1998 ACD.
Point-in-time, leak-free
Like every QUANT_API feature, velocity.trades_per_sec 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
velocity.trades_per_sec 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=velocity.trades_per_sec@5m:zscore"Same key works on /v1/features/historical for point-in-time backtesting — see the API docs.