# Crypto Liquidation Map: Real Liquidation Levels (Hyperliquid) (`scrapemint/crypto-liquidation-map`) Actor

Liquidation heatmap from real positions, not estimates: where the biggest Hyperliquid whales get liquidated on BTC, ETH, SOL and 200+ perps. Price bands with dollar size and cumulative totals, plus the positions closest to liquidation. CoinGlass alternative.

- **URL**: https://apify.com/scrapemint/crypto-liquidation-map.md
- **Developed by:** [Ken M](https://apify.com/scrapemint) (community)
- **Categories:** Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 liquidation levels

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Crypto Liquidation Map: Real Liquidation Levels (Hyperliquid)

A **crypto liquidation heatmap built from real positions**, not estimates.

Liquidation maps for centralised exchanges are guesses, because nobody outside Binance or Bybit can see positions. **Hyperliquid is on-chain**, so the exact liquidation price of every position is public. This actor reads the open positions of the **2,000 largest Hyperliquid accounts** and returns two things:

- **Liquidation levels:** price bands around the mark (1% wide by default) with the dollar size that gets liquidated in each, for longs below the price and shorts above. A running total answers questions like "how much gets liquidated if BTC drops 5%".
- **Positions closest to liquidation:** coin, side, size, entry, liquidation price, distance, leverage, unrealized PnL and the wallet address.

Covers **BTC, ETH, SOL** by default, and any of Hyperliquid's 200+ perps (HYPE, XRP, DOGE...). No account, no key, no proxy. A **CoinGlass liquidation heatmap alternative**.

### What you get

Levels: `coin`, `side`, `markPrice`, `priceFrom`, `priceTo`, `distancePct`, `liquidationNotionalUsd`, `positions`, `largestPositionUsd`, `cumulativeNotionalUsd`, `sideOpenInterestMappedUsd`, `accountsScanned`

Positions: `coin`, `side`, `sizeCoins`, `notionalUsd`, `entryPrice`, `markPrice`, `liquidationPrice`, `distanceToLiquidationPct`, `leverage`, `marginType`, `unrealizedPnlUsd`, `returnOnEquityPct`, `marginUsedUsd`, `fundingSinceOpenUsd`, `address`, `accountValueUsd`, `accountUrl`

### Example input

BTC, ETH and SOL map plus the 200 positions nearest liquidation (the default):

```json
{
  "coins": ["BTC", "ETH", "SOL"],
  "topAccounts": 2000,
  "bucketPct": "1",
  "rangePct": "25"
}
```

Whale positions within 5% of liquidation, any coin, $1M and up:

```json
{
  "coins": [],
  "output": "positions",
  "minPositionUsd": 1000000,
  "maxDistancePct": 5,
  "maxPositions": 100
}
```

### Example output

```json
{
  "type": "position",
  "coin": "BTC",
  "side": "long",
  "sizeCoins": 1355.6,
  "notionalUsd": 111247384.58,
  "entryPrice": 81913.8,
  "markPrice": 82077,
  "liquidationPrice": 80038.4,
  "distanceToLiquidationPct": -2.48,
  "leverage": 40,
  "marginType": "isolated",
  "unrealizedPnlUsd": 204864.07,
  "address": "0x30afce2f6842bf183c7e3fe7162e279ff0b6393e",
  "accountUrl": "https://app.hyperliquid.xyz/explorer/address/0x30afce2f6842bf183c7e3fe7162e279ff0b6393e"
}
```

```json
{
  "type": "level",
  "coin": "BTC",
  "side": "long",
  "markPrice": 82078,
  "priceFrom": 65662.4,
  "priceTo": 66483.2,
  "distancePct": -19.5,
  "liquidationNotionalUsd": 82297886.14,
  "positions": 1,
  "cumulativeNotionalUsd": 82863415.05
}
```

### Uses

- **Liquidation hunting:** see where big stops cluster before price gets there
- **Whale watching:** the largest leveraged positions, their size and how close they are to liquidation
- **Alerts:** schedule it every 15 minutes and alert when a $10M+ position comes within 3% of liquidation
- **Pair it with** [Hyperliquid Data](https://apify.com/scrapemint/hyperliquid-data) for funding and per-wallet history, and [Crypto Liquidations Tracker](https://apify.com/scrapemint/crypto-liquidations-tracker) for liquidations that already happened

### Pricing

- **$0.002** per liquidation level
- **$0.001** per position
- No start fee. A run that finds nothing is free.

A default run (BTC, ETH, SOL) returns roughly 100-150 levels and 200 positions, about $0.50.

### Notes

- Hyperliquid only. It is the largest on-chain perp exchange, and the only major venue where real liquidation prices are public.
- The map covers the scanned accounts, which hold most of the open interest but not all of it. `sideOpenInterestMappedUsd` and the run summary show how much was mapped.
- Positions with no liquidation price have enough collateral that they can't be liquidated. They count in the summary but not on the map.
- Positions already past the mark (being liquidated right now) are left off the map.

# Actor input Schema

## `coins` (type: `array`):

Hyperliquid perp names, e.g. BTC, ETH, SOL, HYPE, XRP, DOGE. Empty = every coin.

## `topAccounts` (type: `integer`):

The N largest Hyperliquid accounts by account value. 2,000 takes about 90 seconds; more accounts fill in smaller positions.

## `minPositionUsd` (type: `integer`):

Ignore positions smaller than this.

## `bucketPct` (type: `string`):

Width of each price band as a percent of the mark price, 0.1-10.

## `rangePct` (type: `string`):

Only map liquidations within this percent of the mark price, up and down.

## `output` (type: `string`):

Levels = the liquidation map (price bands). Positions = individual positions closest to liquidation.

## `maxPositions` (type: `integer`):

How many positions to list, closest to liquidation first.

## `maxDistancePct` (type: `integer`):

Positions output only: list only positions within this percent of their liquidation price. Empty = no limit.

## Actor input object example

```json
{
  "coins": [
    "BTC",
    "ETH",
    "SOL"
  ],
  "topAccounts": 2000,
  "minPositionUsd": 10000,
  "bucketPct": "1",
  "rangePct": "25",
  "output": "both",
  "maxPositions": 200
}
```

# Actor output Schema

## `rows` (type: `string`):

Levels: coin, side, price band, liquidation notional, cumulative. Positions: coin, side, size, entry, liquidation price, distance, leverage, wallet.

## `summary` (type: `string`):

Accounts read, positions found and notional per coin.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "coins": [
        "BTC",
        "ETH",
        "SOL"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapemint/crypto-liquidation-map").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "coins": [
        "BTC",
        "ETH",
        "SOL",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("scrapemint/crypto-liquidation-map").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "coins": [
    "BTC",
    "ETH",
    "SOL"
  ]
}' |
apify call scrapemint/crypto-liquidation-map --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapemint/crypto-liquidation-map"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vz5EjPKssWp1HEbWA/builds/GJs1abffX2X8s805q/openapi.json