Time to Expiry (seconds)
Seconds to next expiry / resolution.
What it measures
Seconds remaining until the relevant expiry or market resolution: expiry_ts − now. For binaries and options this is the variable everything else is conditioned on — the same order-flow burst means something entirely different with four hours left and with forty seconds left. Serving the clock as a feature lets a model learn that conditioning explicitly instead of inheriting it implicitly.
References: Time-to-expiry.
Point-in-time, leak-free
Like every QUANT_API feature, context.tte_seconds 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
context.tte_seconds 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, level 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=context.tte_seconds@5m:level"Same key works on /v1/features/historical for point-in-time backtesting — see the API docs.