Auto-generated. This article is rebuilt from app/signals/config/signal_definitions.json by scripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.

0DTE call volume

What it is

0DTE call volume — registry key zero_dte_call_vol.

Zero-DTE call option volume; raw count, persisted on intraday_signals.

Source

Source module: vol_structure
Data source: live_only

Fetched directly from app/sources/vol_structure.py; see source code for the upstream API call and any provider-specific handling.

How it’s computed

Sum of total call volume across every 0DTE SPY strike on the Schwab option chain, expiring today (ET). See app/sources/vol_structure.py:140-142.

Where it surfaces

• API field: zero_dte.call_vol on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)
• Surface: intraday_signals row (per-cycle snapshot)
• Surface: change markers in the rendered report

Health-score / alignment role

Data carrier — no implication, no health-score contribution.

Persisted for downstream consumers (sparklines, base-rate matcher, calibration substrate) but does not classify into BULLISH / NEUTRAL / BEARISH and does not contribute to the 0-100 health score.

Release cadence

• Publishes: intraday

See also

• /kb/api/get-signals-latest — API endpoint that serves this field.