liquidvision (Python)
Client for LiquidVision.app: exchange-exact crypto derivatives data for bots and AI agents. Standard library only, Python 3.9+. Pay-per-call needs one optional extra.
pip install liquidvision # live data, history with a key
pip install "liquidvision[x402]" # + pay per call in USDC without an account (eth-account)
Start here
from liquidvision import LiquidVision
lv = LiquidVision() # no key: the conclusions (brief, regime, cascades, maps, carry...), 60/min per IP
# lv = LiquidVision(api_key="lv_...") # free key: 120/min on the conclusions; Pro/Bot keys: raw rows, history, alerts
lv.brief("BTCUSDT") # one coin, one JSON: liquidations by window, funding extremes, OI by venue, risk zones
lv.regime(240) # who is driving the move: new_longs / short_covering / new_shorts / long_flush per coin
lv.cascades(hours=24) # liquidation cascades as events, with what price did in the hour after
lv.funding_dispersion() # where the same coin pays very different funding (each leg on its own cycle)
lv.funding_arbitrage() # what the carry pair actually earned over 7 and 30 days
lv.microstructure() # spread, executable depth, cross-venue gap on Binance, Bybit, OKX, Aster
lv.tokenized_stocks() # stocks / indices / commodities / FX as perps on DEXs, one row per underlying
Measured, not modeled:
lv.hl_liqmap("BTCUSDT") # real Hyperliquid positions binned by exchange-reported liquidation price
lv.lighter_liqmap("BTCUSDT") # the same for Lighter
lv.hl_whales(coin="BTC", max_dist_pct=5) # positions within 5% of liquidation
Modeled, and scored: lv.liqmap("BTCUSDT") is the CEX liquidation map (a model);
lv.accuracy()["liqmap_validation"] is how it did against realized liquidations.
Every dict answer carries age_s (seconds since the data was read from the exchange); rows
of oi(), funding(), long_short() carry age_s each and stale=True when a venue feed is
behind. Check it before acting on a number.
History
# free: last 24 h; Pro key: any 31-day window; Bot key: everything
rows = lv.export("liquidations", symbol="BTCUSDT", start="2026-09-01", end="2026-09-08")
lv.packages() # monthly Parquet files: rows, bytes, sha256
lv.package("liquidations", "2026-08", "liq_2026-08.parquet") # Pro: this and last month; Bot: all
Pay per call without an account (x402)
An agent with a wallet can buy one file for one signed USDC payment on Arbitrum One. The key
never leaves your process: the server receives a signed transferWithAuthorization for exactly
the asked amount, to the server's address, valid for a short window; a public facilitator
submits it on-chain.
from liquidvision import LiquidVision, X402Payer
lv = LiquidVision(payer=X402Payer(private_key="0x...", max_usd_per_call=2))
lv.package("liquidations", "2026-08", "liq_2026-08.parquet") # $1.00
rows = lv.export("funding_hourly", start="2026-09-01", end="2026-09-30", pay=True) # $0.10, Pro terms
print(lv.last_payment) # {"success": true, "transaction": "0x...", "network": "arbitrum", "payer": "0x..."}
Without a payer the same calls raise PaymentRequired with .requirements (price, network,
address) so you can decide. Terms: lv.x402_info().
Webhook alerts (Pro and Bot keys)
sub = lv.create_alert("cascade", "https://your.host/hook", symbol="BTCUSDT", min_usd=2_000_000)
secret = sub["secret"] # shown once
# in your handler
from liquidvision import verify_signature
ok = verify_signature(secret, raw_body, request.headers["X-LiquidVision-Signature"])
Alert types: cascade (a liquidation cascade just ended), hl_near_liq (a Hyperliquid whale
near its liquidation price), cluster_sweep (price reached a large modeled cluster).
What to know about the data
- Open interest is counted on one side on every venue; an aggregator showing Bybit, Gate or HTX at twice the figure is showing both sides.
- Liquidation events from Binance and Bitget are throttled by the exchanges to one order per contract per second, so totals are a floor.
- Funding is annualized with each contract's own settlement cycle (1h / 4h / 8h).
- Errors raise
LiquidVisionErrorwith.statusand.detail;PaymentRequiredfor 402.
For agents: MCP at https://liquidvision.app/mcp/lite (13 tools) and /mcp (42).
Endpoint list: https://liquidvision.app/llms.txt · plans: https://liquidvision.app/pricing
Metadata
Release files for liquidvision 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| liquidvision-0.2.0.tar.gz | 9.1 kB | With provenance | Details for liquidvision-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| liquidvision-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for liquidvision-0.2.0-py3-none-any.whl |
Total release size: 18.6 kB
Release files / liquidvision-0.2.0.tar.gz
| Download URL | liquidvision-0.2.0.tar.gz |
|---|---|
| Size | 9.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e7f47a076dc3d576daeaad852b6372f2d2974299e032688c59ccbd90d210fce
|
|
BLAKE2b-256 checksum How to use checksums |
e090e294f66e32fd1eb877e8e781f8113b0d066be01b8267b979a490506674b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / liquidvision-0.2.0-py3-none-any.whl
| Download URL | liquidvision-0.2.0-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0124667f2e565ca399a749aaeefd4d47cfc647b4ea94d0b76dfbf3484f594ef3
|
|
BLAKE2b-256 checksum How to use checksums |
0b66c0ff0938e6a88e878a50f998738b6fe544b820115546a8bf346e7d7b067e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logSecurity for liquidvision 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for liquidvision-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.