crypto-market-snapshot

Crypto Market Snapshot

The "why is X moving" skill: assemble one coherent picture from price, derivatives, whale flow and news, then answer in that order of evidence.

Data sources (in order)

1. MCP connected? coinlobster:market_snapshot (args: pair) then coinlobster:crypto_news (args: coin) for the narrative layer. Keyless, the snapshot serves BTC/USD only; other pairs return {"available": false, "note": ...}. Always check available first. With an active developer plan (from $29/mo), any covered pair works. A CoinLobster Pro website subscription ($9/mo) does not lift this.
2. No MCP client: the hosted MCP answers plain JSON-RPC curl:

   curl -s -X POST https://coinlobster.com/mcp \
     -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
     -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"market_snapshot","arguments":{"pair":"BTC/USD"}}}'
   

   Market-wide context (totals, regime, BTC, whale net flow):

   curl -s "https://coinlobster.com/api/public/overview?limit=10"
   

   Per-coin whale trades: curl -s "https://coinlobster.com/api/public/crypto-whales?coin=SOL&limit=30"
3. Keyless, non-BTC coin: skip the snapshot (it will answer available: false) and build the picture from what IS keyless for every coin: /api/public/overview (magnitude, regime, totals), /api/public/crypto-whales?coin=X (trades; keyless these are 15-min delayed on every coin except BTC/USD, and except any $1M+ trade, which is always live), the liquidations MCP tool, and crypto_news. Say which layer came from delayed data.

The "why is X moving" workflow

Answer from data layers, strongest evidence first:

1. Magnitude first: price change vs its 24h range. Keyless, judge magnitude from chg24hPct alone; do not estimate a coin's typical daily range from memory. On MCP, coinlobster:market_overview with coin returns that one symbol's row directly (no paging). Over REST, /api/public/overview is volume-sorted with tokenized stocks dominating the top rows, so do not page for one coin: it takes a q search param that matches the base symbol or the name, e.g. ?q=SOL. Rows arrive under page.rows with page.total; limit caps at 200 and pages with offset.
2. Forced flow? Check liquidations: a cascade explains fast moves better than any narrative. Only some venues publish liquidation trades; when quoting totals say "liquidations we can see".
3. Whale flow: were there large trades before or during the move, and which direction? (whale-flow skill / whale_trades). Whales leading the move and whales chasing it are different stories.
4. Positioning: funding rate and open interest. Rising OI + rising price = new longs; falling OI = closing, not conviction.
5. Narrative last: crypto_news sentiment and headlines. Only cite news when the timing actually matches the move. Quote sentiment as attributed history and strip forecast wording ("expected", "likely") from summaries; never carry it in your own voice.