mmflow API · Status

API status

Live health check across the public API surface. Pinged from your browser (so what you see is what your clients see — CORS, latency, and all).

Checking…

0 ok · 0 slow · 0 fail

Auto-refresh (30s)

Perps

Perps OI

/api/v1/perps/oi

Perps funding

/api/v1/perps/funding

Perps liquidations

/api/v1/perps/liquidations

Perps positioning

/api/v1/perps/positioning

Perps whales

/api/v1/perps/whales

Perps OI history

/api/v1/perps/oi/history

Perps funding history

/api/v1/perps/funding/history

Options chain

/api/v1/options/chain

Options GEX

/api/v1/options/gex

Options skew

/api/v1/options/skew

ETF flows

/api/v1/onchain/etf-flows

Treasuries

/api/v1/onchain/treasuries

Onchain valuation

/api/v1/onchain/valuation

Markets spot

/api/v1/markets/spot

Stream: whales

/api/v1/streams/whales

Stream: trades

/api/v1/streams/trades

Stream: funding

/api/v1/streams/funding

How this works

Checks fire from your browser, so what you see is what your clients see — CORS, latency, and caching all included.
Streaming endpoints are pinged with fetch(..., { headers: { Accept: 'text/event-stream' } }); we wait for the first byte or 3.5s timeout, then close.
ok = 2xx response under 1500ms.
slow = 2xx response over 1500ms.
fail = non-2xx status or network error.
No metrics are stored or sent anywhere — this is a pure client-side dashboard.

For runtime troubleshooting: REST reference · OpenAPI spec