StalkChain Data
Reference

Data coverage and limits

Honest limits of the data, so you can design around them.

  • "KOL" and "tracked trader" mean traders the platform tracks and has captured balances for, not a curated influencer list.
  • Percent of holders is computable; percent of supply is not (no total-supply field).
  • Trade history is never complete. Positions return every open position but only the newest 25 closed per page; page with cursor, or use deep for a wider fan-out. closedTotalUpstream tells the real total.
  • Windows are 24h, 7d, 30d and all-time only; arbitrary date ranges are not available.
  • Following / followers are capped at 200 per trader by the source; sourceCapped flags it.
  • Heavy accounts (hundreds of open positions) can time out upstream. We retry within 25 s, keep loading in the background, and serve the last good copy flagged [STALE …s] when we have one. Call again in 30–60 s for a fresh answer. These attempts cost nothing.
  • Alert money fields: on a buy, usdValue is the position value after the fill (not the buy size); on a sell it is signed realized PnL. Use tradeUsd or stalkchain_fomo_trade_detail for fill size.
  • Live stream samples are bounded (up to 120 s per call); there is no customer-facing WebSocket yet.
  • StonkFun is free but shared-rate-limited; results are cached 30–60 s.
  • Candles (OHLCV) require an upstream plan we do not currently include.
Last modified on