vike

Recipe 28 of 33

Alert me when smart money and whales disagree on a coin

Poll /indices every 5 minutes and compare latest.smart_bias with latest.whale_bias; alert when their signs differ by more than your threshold, and skip a null, which means the cohort holds nothing on the coin.

GET /v1/hl-cohorts/symbols/{symbol}/indices answers it in one call per coin: its latest block carries the net positioning of the whale wallets (whale_bias, the four whale rungs of the account-size ladder) and of the smart wallets (smart_bias, the three smart rungs of the realized-PnL ladder) at the newest 5-minute snapshot. Each is (long - short) / (long + short), from -1 to +1; poll it, and alert when one is net long and the other net short by more than a margin you choose. The full parameter list is on Coin indices.

Quick answer

HYPE here; hours=1 keeps the hourly series short.

cURL
# HYPE's whale and smart bias at the newest snapshot
curl -H "X-API-Key: $VIKE_API_KEY" \
  "https://data.vike.io/v1/hl-cohorts/symbols/HYPE/indices?hours=1"

Example response

Captured from the live API on 2026-10-24 at 17:14 UTC, the whole response. On HYPE the two disagreed: smart wallets were net long (+0.23) while whales were slightly net short (-0.04). On BTC at the same snapshot both leaned short (smart -0.10, whale -0.20), so there was nothing to alert on. A simple rule: alert when the signs differ and smart_bias - whale_bias is beyond plus or minus 0.25, and only when latest.ts has moved since your last poll.

Example response
{
  "symbol": "HYPE",
  "label_basis": "point_in_time",
  "latest": {
    "ts": "2026-10-24T17:07:00+00:00",
    "smi": 0.34022,
    "wsi": -0.333278,
    "whale_bias": -0.040163,
    "smart_bias": 0.231219,
    "label_basis": "current"
  },
  "series": [
    {
      "ts": "2026-10-24T16:00:00+00:00",
      "smi": 0.338996,
      "wsi": -0.331947
    }
  ],
  "has_more": false
}

Variations

The coins to watch. One call per coin. Take the coins with the most open interest and poll each at most once per snapshot, about every 5 minutes.

cURL — universe
# the 20 symbols with the most open interest
curl -s -H "X-API-Key: $VIKE_API_KEY" \
  "https://data.vike.io/v1/hyperliquid/positions/symbols" \
  | jq '.[:20] | map(.symbol)'

Just the two numbers. The fields the alert reads.

cURL — the two biases
# BTC's smart and whale bias, with the snapshot time
curl -s -H "X-API-Key: $VIKE_API_KEY" \
  "https://data.vike.io/v1/hl-cohorts/symbols/BTC/indices?hours=1" \
  | jq '.latest | {ts, smart_bias, whale_bias}'

Before you rely on it

The API has no history of these two fields

whale_bias and smart_bias exist only in latest; series carries smi and wsi alone, so log each poll if you want to backtest the alert. The alert runs on your side: nothing is pushed. A null bias means that cohort holds no position on the coin, so skip it rather than read it as 0. smart_bias uses today's realized-PnL grading, which is the right one for a reading of now.

Ask your agent

Connected to the Vike MCP server (https://vike.io/mcp) in Claude, ChatGPT or Cursor, ask it in plain words. The hl_market tool answers (view indices), at 1 credit a call.

Ask your agent
On which of BTC, ETH, HYPE and SOL do Hyperliquid smart money and whales lean opposite ways right now?

Are Whale-vs-Shrimp extremes a contrarian signal?

Recipe 27

Are Hyperliquid whales taking or making? Market versus limit share of large fills

Recipe 29

Example response
{  "symbol": "HYPE",  "label_basis": "point_in_time",  "latest": {    "ts": "2026-10-24T17:07:00+00:00",    "smi": 0.34022,    "wsi": -0.333278,    "whale_bias": -0.040163,    "smart_bias": 0.231219,    "label_basis": "current"  },  "series": [    {      "ts": "2026-10-24T16:00:00+00:00",      "smi": 0.338996,      "wsi": -0.331947    }  ],  "has_more": false}