crypto-trade-context

# Crypto Trade Context The user is making or holding a trade. Your job is the data picture, stated so they can decide: crowding as a percentile of the coin's own recorded days, carry cost in dollars, whale direction vs their side, where forced selling actually fired, and what to watch while holding. The decision is theirs; you never make it. ## Data sources (in order) 1. **MCP connected?** `coinlobster:trade_context` (args: `pair`, optional `position_usd`, optional `compact`) is the one-call blob: price, 24h stats, funding + OI with percentile judgment vs the pair's own recorded days, whale flow vs the coin's own baseline, visible liquidations, carry arithmetic, crowding (keyed). Keyless it answers on EVERY streamed pair; `depth` reports which shape you got (`lite` off the free pair, `free-pair`, or `keyed`) and `locked_layers` names exactly what a developer plan key (from $29/mo) adds: `stats_24h`, `whale_flow USD magnitudes` and `crowding`. **`vs_own_history` is never locked**: the percentile judgment is keyless on every pair, here and on `/api/public/baseline` and `market_screener`. 2. **No MCP:** assemble the same picture keyless: ```bash curl -s "https://coinlobster.com/api/public/baseline?pair=BTC/USD" # percentile judgment + outcome history curl -s "https://coinlobster.com/api/public/whale-context?coin=BTC" # whale flow vs own baseline (coin param required) curl -s "https://coinlobster.com/api/public/liquidation-history?pair=BTC/USD&limit=10...