Query Details
Returns one entry per probed DEX with a rolled-upstatus, the individual probe results powering that rollup, and any active or upcoming maintenance windows.
- Probes both HTTP and WebSocket upstreams. WS probes connect, wait for the first message, and disconnect.
- Results are cached server-side per check to avoid hammering upstreams. Concurrent cold-cache calls are deduped —
Nparallel requests fire a single upstream probe. - Probes never throw — failures surface as
ok: falseon the corresponding check. - Auxiliary checks are informational and never affect the rollup; only
criticalchecks do.
Endpoint
Query Parameters
Usage Examples
- Both DEXes:
- Lighter only:
- Gains only:
Response
Top-level shape:PerpDexHealth
One entry per probed DEX.
PerpDexCheckResult
One per upstream probe.
PerpDexMaintenanceWindow
Status Rollup
Ranking best → worst:maintenance— any maintenance window withactive === true.operational— every critical check isok && !slow.down— zero critical checksok.degraded— anything else (some critical OK and some not, or one critical isslow).
Checks Reference
Lighter
Gains
Onetrading-variables and one ws-trading per supported chain, plus a single shared ws-pricing.
Per-chain weights:
Caching & Timeouts
In-memory per-check TTLs:
Probe budgets:
- HTTP — timeout: 5000 ms · slow threshold: 2000 ms.
- WS — timeout: 4000 ms · slow threshold: 3000 ms.
Example Response
Truncated for readability.Errors
Probes themselves never throw — upstream failures are reflected as
ok: false on the per-check result, not as HTTP errors.
Related
Perpetuals APIs Overview
Supported exchanges and capability map.
Perp Fees
Fee structure for each integrated DEX.
Get Perp Quote
Preview fees, fills and venue routing before executing.
Perp Execution Flow
Build → execute flow against Lighter and Gains.