Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

LiquidVision — Crypto Derivatives Data

von lv-analyticsVersion 1.3.0i★ –iLäuft in der Cloud
Name in der Registryapp.liquidvision/derivatives

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Exchange-exact crypto derivatives data for AI agents: OI, funding, liquidations, 13 venues, 42 tools

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft in der Cloud
  • Transport: Streamable HTTP
  • Kategorie: Krypto & Blockchain
  • Das musst du eintragen: X-API-Key

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Führe das in deinem Terminal aus

claude mcp add --transport http derivatives https://liquidvision.app/mcp --header 'X-API-Key: your-value'

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "derivatives": {
      "url": "https://liquidvision.app/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "derivatives": {
      "type": "http",
      "url": "https://liquidvision.app/mcp",
      "headers": {
        "X-API-Key": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

  • X-API-Key geheim HTTP header
    Optional. A free key raises the rate limit; Pro/Bot keys unlock history exports and alerts.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 8. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • list_markets

    [measured] What exists: every venue we track and, for each, the contracts with live open interest right now (BASEUSDT symbols), plus the top-100 coin pool. Call this first when unsure which symbol or exchange string another tool accepts.

  • get_accuracy

    [measured] The public accuracy audit: our open interest and funding vs Binance, Bybit, OKX and Hyperliquid's own endpoints, sampled every 10 min (diff %, snapshot age, 24h mean/max), plus how the modeled liquidation map scored against realized liquidations. Read this before trust

  • get_funding_rates

    Latest perpetual funding rates and mark prices for every tracked exchange/symbol pair. Positive rate = longs pay shorts.

  • get_microstructure

    Cross-venue order book microstructure for BTC, ETH and SOL. Per venue: spread in bps, immediately-executable depth in USD and the bid share of it, measured over a band narrow enough that every venue's stream captured it, each venue around its own mid. Also the basis - how far apa

  • get_positioning_regime

    Per-coin positioning regime from price direction crossed with open interest. price up + OI up = new longs; price up + OI down = short covering (a rally with no new buyers); price down + OI up = new shorts; price down + OI down = long flush. Returns a market summary (coins and net

  • get_liquidation_cascades

    [measured, PAST] Liquidation CASCADES as discrete events: bursts of liquidations detected against each coin's own 7-day normal minute. Use it for "when did forced selling snowball and what did price do"; not for totals (get_liquidations_summary), raw orders (get_liquidations) or

  • list_history_packages

    [measured] Monthly Parquet history packages for backtests: liquidations (11 venues), funding hourly and settlements, open interest hourly, Hyperliquid and Lighter positions with liquidation prices — one file per dataset per month since 2026-07 with rows, bytes and sha256. Each en

  • get_funding_arbitrage

    [measured] Funding carry screener on REALIZED numbers: for each coin, the venue pair a desk would put on (short where funding is richest, long where it is cheapest) and what that pair actually earned from funding over the last 7 and 30 days from our hourly archive, annualized; po

  • get_funding_dispersion

    Coins ranked by how far funding disagrees ACROSS exchanges. For each coin: the spread in APR points between the venue charging the most and the one paying the most, plus which venue to hold the long on and which to hold the short on. Every leg is annualized with its own settlemen

  • get_funding_settlements

    Settled funding rates, one row per settlement, from Binance and Bybit history — up to 730 days for any pool coin (e.g. BTCUSDT). The backtest series; get_funding_history is the live 10-second archive since July 2026.

  • get_open_interest

    Latest open interest (contracts and USD) per exchange/symbol.

  • get_open_interest_history

    [measured] Open interest over time for one contract, one row per venue per time bucket: ts (ms), exchange, oi (coins, one side), oi_usd. Use it to see how positioning built up or unwound; for the current snapshot with shares and 1h/4h/24h changes use get_oi_board, for every contr

  • get_funding_history

    [measured] Funding rate over time for one contract, one row per venue per time bucket: ts (ms), exchange, funding_rate (per settlement interval, a fraction), mark_price and funding_hours (that contract's interval: 1, 4 or 8). Annualize as rate * 8760 / funding_hours. This is the

  • get_long_short_ratio

    Latest global long/short account ratio per exchange/symbol.

  • get_liquidations

    [measured, PAST] Individual liquidation ORDERS that already happened (side, price, qty), newest first, at most `limit` rows (max 2000). This is the raw feed: use it when you need the orders themselves. For totals use get_liquidations_summary; for cascades as events use get_liquid

  • get_liquidations_summary

    [measured, PAST] TOTALS of liquidations that already happened: rekt (USD liquidated in the last 1h/4h/12h/24h, split long/short), by_symbol and by_exchange over the last `minutes`, and series (30-minute buckets). The one to call for "how much was liquidated"; it does not return i

  • get_oi_board

    Per-venue open-interest ranking for a perp symbol (e.g. BTCUSDT): OI in coins and USD, market share %, 1h/4h/24h OI change % and USD flow, and OI / 24h-volume ratio per exchange, plus market totals.

  • get_cash_flows

    Derivatives cash flow per exchange: net USD into/out of open interest over 1h/4h/24h windows, per core symbol. Positive = money flowing in.

  • get_arbitrum_perps

    Arbitrum perps board: GMX v2 open interest per coin and its share of every tracked venue, GMX funding next to the CEX median (8h basis), on-chain liquidations over 24h. Ask this for 'how is Arbitrum positioned vs CEXs'.

  • get_top_traders

    Top lead traders (OKX copy trading, public data): total PnL, win rate, AUM, copiers, live open positions (pair, side, leverage, entry, uPnL) and recently closed trades with realized PnL.

  • get_token_unlocks

    Upcoming token unlock events for pool coins, nearest first: next unlock timestamp and token amount per public vesting schedule.

  • get_stocks

    Crypto-related equities (COIN, MSTR, miners) and spot BTC/ETH ETF quotes: price, day change %, range, volume. ~15-min delayed.

  • get_liquidation_map

    [modeled, RISK AHEAD, CEX, now] ESTIMATED open leveraged positions on Binance/Bybit/OKX per price bin at their liquidation price, from candles and open-interest deltas (the CEXs do not publish positions). Current snapshot only; for its evolution over time use get_liquidation_heat

  • get_hl_liquidation_map

    [measured, RISK AHEAD, Hyperliquid] REAL open positions on Hyperliquid binned by the liquidation price the exchange itself reports: the 10,000 largest accounts plus every account that traded since the reader started (~10,000 accounts, ~40-45% of venue open interest, stated in cov

  • get_liquidation_heatmap

    [modeled, RISK AHEAD, CEX, over time] The same estimated CEX map as get_liquidation_map but as a time series: grid[t][b] is the estimated USD of leveraged positions with their liquidation price in price bin b at time cols[t] (ms), bins[b] the bin's centre price (240 bins fitted t

  • get_orderbook_heatmap

    [measured] Resting limit orders over time on ONE exchange: cells of (time bucket, price bucket, quantity in coins) from archived order-book snapshots, with price_min, price_max, price_step and time_step (seconds) describing the grid. Shows where bid and ask walls stood and when t

  • get_market_brief

    Deterministic market brief for a perp symbol: 24h liquidations (totals, by exchange), current funding + 24h extremes per venue, OI by venue with 1h/4h/24h changes, net position flows, modeled liquidation risk zones above/below price, and top-trader positioning. Free, no LLM invol

  • ask

    ONE CALL instead of five: ask in plain words ('where is leverage stacked on BTC', 'why did ETH drop', 'is SOL funding crowded', 'biggest whales near liquidation') and get `answer`: short statements with the numbers in them, `facts`: the same numbers as JSON, `sources`: which endp

  • get_precedents

    [measured] When did the market look like this before, and what did price do next? Scans our hourly archive for hours whose positioning resembled now (OI change 24h within 3 pp, funding APR within 15 points and same sign, long share within 5 pp, liquidation volume within x2.5), on

  • explain_market

    AI risk-intelligence answer: ask e.g. 'Why did BTC drop 4%?' and get a concise grounded explanation (liquidation cascades, funding extremes, where the positions sit, next risk zone) computed from live derivatives data across 13 venues (CEXs, Hyperliquid and GMX).

  • get_footprint

    [measured] Footprint chart data: for each candle, taker BUY and taker SELL volume in USD and the trade count at each of 30 price levels, from the archived trade streams of Binance, Bybit, OKX, Bitget and Gate. Use it to see at which prices aggressive buyers or sellers were absorb

  • get_cvd

    Cumulative volume delta split by trade size (retail <$10K, mid <$100K, large <$1M, whale >$1M). Whale-vs-retail divergence is the usual smart-money reading; buckets are per published row and only Binance aggregates taker orders, so compare buckets within one exchange (exchange=bi

  • get_spoofing

    Order-book wall lifecycle heuristic: large levels classified as active_wall / absorbed / pulled_wall / suspected_spoof based on whether trades executed into them before they vanished.

  • get_api_key

    Get a free LiquidVision API key for this agent's owner, by email, without a browser. Works for a NEW email only (an existing account's key is never returned; its owner sees it at liquidvision.app/data). Use the key as X-API-Key on REST or on this MCP endpoint: 120 req/min instead

  • get_history

    [measured] Historical rows as CSV, for backtests. dataset: liquidations | funding_settlements (since 2024-09) | funding_hourly | open_interest_hourly | hl_positions (Hyperliquid whale positions with liquidation prices). start/end are ISO dates (UTC). Without a key or on the free

  • create_alert

    Subscribe an HTTPS URL to push alerts instead of polling (Pro: 3, Bot: 20 subscriptions). type='condition': YOUR OWN trigger on one symbol — fires when `metric` `op` `threshold` becomes true (edge-triggered: once per crossing, again only after it was false). metric = funding_apr_

  • list_alerts

    The webhook alert subscriptions that belong to the caller's API key (read-only): id, type, url, filters (symbol, min_usd, x_normal, max_dist_pct) and delivery health: last_status (HTTP code or error of the last delivery), fails (consecutive failures; a subscription pauses itself

  • delete_alert

    Permanently delete one webhook alert subscription. DESTRUCTIVE and not reversible: deliveries to its URL stop at once and its signing secret is discarded (create_alert issues a new one). Only a subscription owned by the caller's API key can be deleted; an id belonging to another

  • get_hl_whales

    [measured] Leveraged positions of the 10,000 largest Hyperliquid accounts with the exchange-reported liquidation price, closest to liquidation first (sort='value' = largest first). Filters: coin (BTC), side (long|short), min_usd, max_dist_pct. Each row carries the account address

  • get_detective_events

    [measured] Detective: what the watched large holders did. Private wallets with a large share of a token's supply (Ethereum, Solana) and Hyperliquid accounts with a large share of a contract's open interest are watched live. Event types: to_exchange (a watched wallet sent tokens t

  • get_lighter_liquidation_map

    [measured, RISK AHEAD, Lighter] REAL open positions on Lighter (zk perp DEX; crypto plus equity indices, stocks, forex, commodities) binned by Lighter's own liquidation price. Not a model. Use this for Lighter; get_hl_liquidation_map for Hyperliquid; get_liquidation_map (modeled)

  • get_lighter_whales

    [measured] Leveraged positions on Lighter with the exchange-reported liquidation price, closest to liquidation first (sort='value' = largest first). Filters: coin (BTC), side (long|short), min_usd, max_dist_pct. address is the Lighter account index, l1_address the wallet. Snapsho

  • get_hl_account

    [measured] One Hyperliquid account by address: live positions (size, entry, mark, liquidation price, distance to liquidation, leverage, unrealized PnL), account value, and its archived position snapshots. History depth: 24 h free, 31 days Pro, everything since 2026-09-27 on Bot (

  • get_tokenized_stocks

    [measured] Tokenized stocks, indices, ETFs, commodities, FX, rates and pre-IPO names traded as PERPS on DEXs (Lighter and Hyperliquid builder markets): one row per underlying (NVDA, TSLA, S&P 500, Gold, EUR/USD, Anthropic...) with every venue's mark, open interest, 24 h volume, f

  • get_hl_builder_markets

    [measured] Perp markets deployed on Hyperliquid by third parties (HIP-3 builder dexs): equity indices, single stocks, commodities and pre-IPO names such as xyz:SP500 or xyz:GOLD. For each dex: its markets (coin named dex:COIN), open interest in USD (one side), 24h volume, mark pr

  • get_hip3_markets

    [measured] The HIP-3 board: Hyperliquid's builder-deployed perp markets (equity indices, stocks, commodities, pre-IPO names; coins named dex:COIN such as xyz:SP500) with what the live list alone cannot tell you. Per dex: OI, share, 24h/7d OI change, 24h volume, liquidations. Per

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 9. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde über die Domain liquidvision.app bestätigt (die Registry prüft, wem die Domain gehört)

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 398 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 46 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Krypto & Blockchaini

  • Mehr Sterne als 0 % der anderen 1622 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 68 % der anderen 1622 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 1622 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist LiquidVision — Crypto Derivatives Data sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: X-API-Key

Läuft er auf meinem Computer oder in der Cloud?

Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.3.0) kam vor 23 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Nftdata MCP, onchaincheck, Bvcc Agent Wallet

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Nftdata MCP

OpenSea NFT data, paid per request in USDC on Base via x402 (default) or MPP.

von Nomad07Am Anfang↓ 735/Wo.Aktualisiert heute

Läuft auf deinem Computer

onchaincheck

100+ pay-per-call tools: token risk, wallet sanctions screening, onchain data, web, company, AI

von lx1112Am AnfangAktualisiert heute

Läuft in der Cloud

Bvcc Agent Wallet

Non-custodial BVCC Agent Wallet on-chain for AI agents: balances, transfers, approvals, swaps.

von blockventurechaincapital-cryptoAm Anfang↓ 622/Wo.Aktualisiert heute

Läuft auf deinem Computer✓ blockventurechaincapital.com

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

LiquidVision.app — MCP server for crypto derivatives data

Crypto derivatives data for AI agents and trading bots: a remote MCP server, no install, no API key needed.

Endpoint: https://liquidvision.app/mcp (Streamable HTTP, 42 tools, read-only; the raw-row tools need a Pro/Bot key sent as X-API-Key, the conclusion tools do not) Lite endpoint: https://liquidvision.app/mcp/lite — the 13 tools that return conclusions (brief, explain, regime, cascades, dispersion, carry, microstructure, three liquidation maps, tokenized stocks, accuracy). Start here if your agent answers questions; use the full server for raw rows, history and alerts. Discovery: /.well-known/agent-card.json, /.well-known/mcp.json, /.well-known/x402.json; worked examples at /llms-full.txt.

Registry: server.json in this repo is the manifest for the Official MCP Registry (io.github.lv-analytics/liquidvision); also listed on Glama and in awesome-remote-mcp-servers.

What it gives an agent

Open interest and funding rates across 13 venues (Binance, MEXC, Bybit, Bitget, Hyperliquid, HTX, Gate, OKX, KuCoin, BingX, Aster, Kraken, GMX on Arbitrum), as each exchange reports them. An audit compares our figures with the exchanges' own endpoints every 10 minutes and publishes the result: https://liquidvision.app/accuracy (tool: get_accuracy).

Start with list_markets, then the computed views. They return a conclusion, not a pile of ticks:

ToolAnswers
get_liquidation_cascadesLiquidations grouped into events: start, duration, multiples of normal, what price did
get_positioning_regimePrice direction x change in positions per coin: new longs, short covering, new shorts, long flush
get_funding_dispersionCoins ranked by how far funding disagrees across venues, each leg annualized with its real settlement cycle
get_funding_arbitrageRealized funding carry per coin: what the short-richest / long-cheapest pair earned over 7 and 30 days, share of positive hours, mark gap now
get_tokenized_stocksTokenized stocks, indices, commodities, FX and pre-IPO names as perps on Lighter, Hyperliquid builder markets, Ostium and gTrade: OI, volume, funding, cross-venue price gap
get_microstructureCross-venue spread, top-of-book depth, basis
get_market_briefOne deterministic risk brief for a symbol: feed it to your own model
explain_market"Why did BTC drop 4%?": a grounded answer built from the live data

Measured, not modeled (Hyperliquid and Lighter, where positions are public):

ToolReturns
get_hl_whalesLeveraged positions of the 10,000 largest accounts with exchange-reported liquidation prices, closest to liquidation first
get_hl_accountOne address: live positions, liquidation prices, archived snapshots
get_hl_liquidation_mapThose positions binned by liquidation price
get_hl_builder_marketsBuilder-deployed (HIP-3) perp markets on Hyperliquid: equity indices, stocks, commodities, with open interest, volume, funding
get_lighter_liquidation_mapMeasured liquidation map for Lighter: positions binned by the exchange-reported liquidation price, with the share of venue open interest covered
get_lighter_whalesLighter positions with exchange-reported liquidation prices, closest to liquidation first (address = account index, l1_address = wallet)

Raw data: get_funding_rates, get_funding_history, get_funding_settlements, get_open_interest, get_open_interest_history, get_oi_board, get_cash_flows, get_long_short_ratio, get_liquidations, get_liquidations_summary, get_liquidation_map, get_liquidation_heatmap, get_orderbook_heatmap, get_footprint, get_cvd, get_spoofing, get_arbitrum_perps, get_top_traders, get_token_unlocks, get_stocks.

For bots: get_api_key (a free key by email, without a browser), get_history (archive rows as CSV for backtests), list_history_packages (monthly Parquet files per dataset with rows, bytes and sha256; Pro: this and last month, Bot: all), create_alert, list_alerts, delete_alert (webhooks: a liquidation cascade ended, a Hyperliquid whale is near liquidation, price reached a large modeled cluster).

Connect

Claude Code

claude mcp add --transport http liquidvision https://liquidvision.app/mcp

Claude Desktop / claude.ai: Settings → Connectors → Add custom connector, URL https://liquidvision.app/mcp.

Cursor / Windsurf / any client with an `mcp.json`

{

"mcpServers": { "liquidvision": { "url": "https://liquidvision.app/mcp" } } }

Raw JSON-RPC

curl -X POST https://liquidvision.app/mcp \

-H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Claude Code skill

Copy skills/liquidvision into ~/.claude/skills/ (or a project's .claude/skills/). It tells the agent which tool answers which question, how to read measured vs modeled data, and how to pay per file with x402 when history is needed.

Without MCP

The same data is a REST API and a WebSocket feed (https://liquidvision.app/llms.txt lists every endpoint). Two small clients live in clients/: Python (standard library only; pip install "liquidvision[x402]" for pay-per-call) and JavaScript (built-in fetch; bring any EIP-712 signer for pay-per-call). Both start at brief().

from liquidvision import LiquidVision

lv = LiquidVision() lv.brief("BTCUSDT") # one coin, one JSON lv.hl_whales(coin="BTC", max_dist_pct=5)["positions"] lv.export("liquidations", symbol="BTCUSDT", start="2026-09-01", end="2026-09-08") lv = LiquidVision(payer=X402Payer("0x...")) # pay per file in USDC without an account lv.package("liquidations", "2026-08", "liq_2026-08.parquet")

Integrations

Drop-in pieces for agent frameworks and trading bots, all on the free endpoints and fail-open: LangChain / LangGraph toolkit (pip install langchain-liquidvision, listed in the LangChain integrations docs), CrewAI tools (pip install crewai-liquidvision), ElizaOS plugin, Freqtrade guard, Hummingbot cascade guard. Overview: integrations/.

Examples

  • examples/passivbot_funding_filter.py: keeps Passivbot out of coins where holding the position is expensive (funding annualized with the contract's real interval) or where a liquidation cascade is running. Writes the ignored_coins file Passivbot reads continuously. Standard library only, no key: python examples/passivbot_funding_filter.py --exchange bybit --once
  • examples/binance_liq_probe.py: which Binance host actually delivers the liquidation stream.
  • collectors/gmx_v2.py: a standalone GMX v2 (Arbitrum) collector.

Limits and honesty

  • Free and anonymous: the conclusion tools and the lite server, 60 requests/min per IP (120 with a free key); raw-row tools need a Pro/Bot key or x402; send it as X-API-Key or Authorization: Bearer lv_.... Paid plans (history exports, webhook alerts, higher limits): https://liquidvision.app/pricing
  • explain_market costs real money to run: 5 answers/day anonymous, 25 with a free key.
  • Every dict answer carries age_s (seconds since the data was read from the exchange); rows of get_open_interest, get_funding_rates and get_long_short_ratio carry age_s each and stale: true when a venue feed is behind.
  • Open interest is counted on one side on every venue. Bybit documents its openInterest as "the sum of both sides" and we serve its singleOpenInterest; Gate and HTX report both sides and are halved. An aggregator showing those venues at twice our figure is showing both sides. Commands to check this yourself: docs/coinglass-vs-exchanges.md.
  • Liquidation events come from Binance, Bitget, OKX, Bybit, HTX, Gate, Kraken, GMX (on-chain, complete) and Hyperliquid whale accounts. Binance and Bitget throttle their feeds to one order per contract per second, so totals are a floor for the whole market.
  • The CEX liquidation map and heatmap are models built from candles and open-interest changes. They show where leveraged positions sit, not where price will go. Scored against realized liquidations (367 snapshots, 21 days): among the price levels actually traded in the next 24 h, the map's top quarter held 32% of the liquidated USD, against 25% by chance. The live score is on https://liquidvision.app/accuracy.
  • Symbols are BASEUSDT (BTCUSDT, ETHUSDT, ...). Computed views accept a fixed set of window sizes; other values snap to the nearest.

More for agents: https://liquidvision.app/llms.txt · REST/OpenAPI: https://liquidvision.app/api/v1/docs · status and uptime: https://liquidvision.app/status

PopNx fragen