---
title: "Api V2 Signals Advanced Market-Pressure Get"
method: GET
path: "/api/v2/signals/advanced/market-pressure"
tags: ["Trade Signals (v2)"]
---

# Api V2 Signals Advanced Market-Pressure Get

`GET /api/v2/signals/advanced/market-pressure`

## Request

- Base URL: `https://api.zerogex.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.zerogex.io/api/v2/signals/advanced/market-pressure`
- Auth: HTTP bearer

Market Pressure Index — forward-looking "coiled spring" detector.

Answers: *is the market loaded to move, and which way will it break?*
Distinct from `squeeze_setup` (reactive, fires AFTER momentum starts) and
from `range_break_imminence` (regime-switch inside chop) — this signal
measures how much DEALER HEDGING DEMAND is loaded into the book right
now and which direction that hedging flow will run when any catalyst
fires.

**Logic highlights** (`src/signals/advanced/market_pressure.py`):
- Magnitude is MULTIPLICATIVE across four pillars (all must be present):
  - **Compression** (C): geometric mean of wall pinch
    `1 − (call_wall − put_wall)/spot` and flip-proximity Cauchy kernel
    `σ²/(σ² + d²)`; net-GEX regime multiplier amplifies short-gamma
    and damps long-gamma.
  - **Hedging vector** (H): session-weighted blend
    `α·vanna + (1−α)·charm·charm_amp` (α ramps 0.7→0.3 open→close);
    +20% alignment bonus when vanna and charm share sign, dealer-DNI
    gate mutes the response when dealers are flat.
  - **Flow asymmetry** (F): 0.6·premium_skew + 0.4·smart_money_skew,
    magnitude-gated on total premium flux.
  - **Vol tension** (T): `√((1 − iv_rank) · vol_squeeze)` where
    `vol_squeeze` maps the 10-bar/60-bar realized sigma ratio to [0, 1];
    modulates loading 0.5×–1.0× via a floor.
- `loading = 100 · C · H_mag · F_mag · (0.5 + 0.5·T)`  (0–100).
- Direction is a weighted vector: `0.45·H + 0.40·F·F_mag + 0.15·dealer`,
  with a ±30% confidence multiplier based on how many of those three
  inputs agree.
- `score = sign(direction) · √|direction| · (loading/100)` ∈ [-1, +1].
- **Triggered when `loading ≥ 50` AND `|direction| ≥ 0.20`** — both
  magnitude AND directional clarity required.

**Params:** `symbol` (default `SPY`). Returns 404 when no data exists.

**Returns:**
```json
{
  "score": 56.0, "clamped_score": 0.56, "direction": "bullish",
  "triggered": true,
  "signal": "bullish_pressure",
  "loading": 78.2,
  "direction_value": 0.91,
  "label": "Critical",
  "playbook": "Coil at the limit. Expect violent resolution to the upside. Take the directional trade with reduced size on stops; cut all counter-pressure exposure.",
  "confidence_mult": 1.3,
  "context_values": {"...compression, hedging, flow, tension, dealer, weights..."},
  "score_history": [{"score": 56.0, "timestamp": "..."}, "...up to 90"]
}
```

- `score` — [-100, +100]; sign = pressure direction, magnitude tracks
  both loading and directional clarity (`sign·√|direction|·loading`).
- `signal` — `"discharged"` | `"bullish_pressure"` |
  `"bearish_pressure"` | `"loaded_neutral"`.
- `loading` — [0, 100]; multiplicative pressure magnitude
  (Compression × Hedging × Flow × tension-modulator).
- `direction_value` — signed [-1, +1] directional vector after the
  agreement-based confidence multiplier; *not* a clamped score.
- `direction` — `"bullish"` | `"bearish"` | `"neutral"` (sign of
  `direction_value`, using a 1e-6 deadband).
- `label` — `"Discharged"` (0–24) | `"Building"` (25–49) |
  `"Loaded"` (50–74) | `"Critical"` (75–100).
- `playbook` — trader-facing guidance string matching the label and
  direction.
- `confidence_mult` — [≈0.7, ≈1.3]; reward/penalty applied to
  direction when the hedging/flow/dealer inputs agree or fight.
- `triggered` — `true` when `loading ≥ 50` AND `|direction_value| ≥ 0.20`.

**Trader interpretation:**
- `label == "Discharged"` → no actionable loading; trade existing setups.
- `label == "Building"` → tighten stops on counter-pressure trades;
  prepare directional templates.
- `label == "Loaded"` → stop fading; scale into continuation entries
  on first confirmation (VWAP reclaim, wall break, flow spike).
- `label == "Critical"` → take the directional trade with reduced
  size on stops; cut counter-pressure exposure.
- A `score = 0` does NOT mean "neutral market" — it means a pillar
  collapsed (no walls, no greeks, no flow) or directional forces are
  perfectly cancelling. Treat as "this lens is dark."

**Page design.** Half-circle gauge (0–100 `loading`) colored by
`direction`, with the label badge below. Four-bar stack of the
sub-component magnitudes (compression / hedging / flow / tension).
A small `confidence_mult` chip (e.g. "1.3× — all 3 agree" or
"0.8× — flow fighting"). Playbook text under the gauge. Flip the
card's accent between "fade-safe" (neutral) and "ride-the-break"
(loaded) at the 50-loading threshold.

## Query parameters

- `symbol` string

## Response `200`

Successful Response

- EnvelopeAny
  - `data` unknown, required
  - `freshness` Freshness, required: The v2 freshness envelope. Present on every ``/api/v2/*`` response.
    - `evaluated_at` string, date-time, required: When the API evaluated this response (server wall clock, UTC). Endpoint-health signal: advances on every request even when the underlying data is unchanged.
    - `generated_at` string, date-time, required: When the served data was computed. Equals the snapshot stamp for cycle-backed endpoints, or evaluated_at for endpoints computed on demand for this request.
    - `source_timestamp` string, date-time, nullable: Timestamp of the upstream market observation the payload derives from. This is what freshness_status is measured against. Null when the endpoint has no upstream feed or returned no rows.
    - `latest_event_at` string, date-time, nullable: Newest event timestamp present in the payload (last bar, last trade, last scored row). Best-effort on very large responses, which are sampled rather than fully walked.
    - `age_seconds` number, nullable: evaluated_at - source_timestamp, in seconds. Null when source_timestamp is null.
    - `market_session_status` string, required: pre-market | regular | after-hours | closed (US/Eastern).
    - `expected_update_cadence` string, nullable: ISO-8601 duration for how often this endpoint's data is expected to change right now, e.g. PT60S. Null means no updates are expected (weekend, holiday, or a feed that only runs during the session).
    - `expected_update_cadence_seconds` number, nullable: expected_update_cadence as a number of seconds.
    - `cadence_profile` string, required: Identifier of the cadence class this endpoint belongs to, e.g. analytics_cycle. Stable across releases; the seconds behind it may be retuned.
    - `stale_after` string, date-time, nullable: Instant after which this payload should be treated as stale. Null whenever expected_update_cadence is null.
    - `freshness_status` 'fresh' | 'aging' | 'stale' | 'session_closed' | 'static' | 'unknown', required: The rolled-up freshness verdict for one response. ``fresh`` ``source_timestamp`` is within one expected update cadence. ``aging`` Past one cadence but not yet past ``stale_after`` — the grace band that absorbs normal cycle jitter. Not an error; a client that polls faster than the cadence sees this routinely. ``stale`` Past ``stale_after`` while updates *were* expected. This is the actionable state: the feed behind this endpoint is late. ``session_closed`` A feed-backed endpoint whose feed is not due to produce anything right now (weekend, holiday, or a feed that only runs during the session). The payload is the last good value — deliberately NOT reported as ``stale``, because an overnight consumer polling a closed market is not observing a fault and should not page on it. ``static`` The endpoint is not feed-backed at all: completed history, or a result computed from the caller's own inputs. Age here carries no health meaning and never becomes a fault. ``unknown`` No source timestamp could be resolved from the payload (e.g. a pure calculator, an admin endpoint, or an empty result set). A consumer should fall back to ``evaluated_at`` for endpoint health and make no claim about data age.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zerogex/apis/zerogex-api.md) · [All operations](https://skmtc.dev/zerogex/apis/zerogex-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zerogex/apis/zerogex-api/revisions/03b8b80a6cd5?raw)