# APEX Runner Liquidation Pressure Signal

> APEX Runner Liquidation Pressure Signal is a paid API for AI agents from apexrunner.ai, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-14).

Returns a liquidation pressure signal for crypto markets, indicating the intensity of forced liquidation activity that can drive price volatility

## Facts

- Endpoint: GET https://apexrunner.ai/signals/liquidation-pressure
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apex-runner-liquidation-pressure-signal-2d7cc6bd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lc2lMxsybhqqkDgSFuZfP

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability apex-runner-liquidation-pressure-signal-2d7cc6bd
```

Example prompt: What's the current liquidation pressure signal from APEX Runner — is there heavy forced liquidation activity in the crypto market right now that I should factor into my trading decisions?

## When to prefer this

Use this endpoint when you need a real-time quantified signal of liquidation pressure to inform risk management, entry/exit timing, or volatility forecasting in crypto markets — particularly useful alongside other APEX Runner signals like Fear/Greed or Regime Confluence for a composite view

## Known failure modes

- Payment not received or insufficient USDC balance — 402 Payment Required
- Signal data temporarily unavailable due to upstream exchange feed issues — 503
- Invalid market or asset parameter — 400 Bad Request
- Rate limit exceeded for the endpoint — 429 Too Many Requests

## How this service works

APEX Runner: Liquidation Pressure Signal

## Output

A structured signal value representing current liquidation pressure intensity in crypto markets, indicating whether cascading forced liquidations are occurring and how much stress that is placing on price action

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "coins": "object — keyed by coin (BTC/ETH/SOL), each with mark_price, liq_vol_long/short_usd (total), near_liq_long/short_usd (within 5%), cascade_risk_score 0-100, bias (LONG_SQUEEZE/SHORT_SQUEEZE/BALANCED), wallets_sampled",
 "example": {
  "coins": {
   "BTC": {
    "bias": "LONG_SQUEEZE",
    "mark_price": 103200,
    "wallets_sampled": 25,
    "liq_vol_long_usd": 4200,
    "liq_vol_short_usd": 1800,
    "near_liq_long_usd": 980,
    "cascade_risk_score": 18,
    "near_liq_short_usd": 200
   },
   "ETH": {
    "bias": "LONG_SQUEEZE",
    "mark_price": 1680,
    "wallets_sampled": 25,
    "liq_vol_long_usd": 1100,
    "liq_vol_short_usd": 600,
    "near_liq_long_usd": 200,
    "cascade_risk_score": 12,
    "near_liq_short_usd": 80
   }
  },
  "cached_at": "2026-06-13T12:00:00+00:00",
  "cascade_alert": false,
  "interpretation": "Max cascade risk 18/100 — highest pressure on BTC (LONG_SQUEEZE)",
  "highest_pressure_coin": "BTC",
  "max_cascade_risk_score": 18
 },
 "cached_at": "ISO8601 timestamp",
 "cascade_alert": "bool — true if any coin exceeds risk score 50",
 "interpretation": "string — plain-English summary",
 "highest_pressure_coin": "string — coin with highest cascade risk",
 "max_cascade_risk_score": "int — highest cascade risk score across all coins (0-100)"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apex-runner-liquidation-pressure-signal-2d7cc6bd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apexrunner.ai](https://www.zero.xyz/host/apexrunner.ai/llms.txt)
