Data / API - early access

Whale wallet data/API access

Request access for planned data workflows built from the same definitions as the Telegram channel. Current public pages expose only sanitized examples and summary/latest rows.

Planned data surfaces

Four planned surfaces, one consistent definition.

These are request-access surfaces, not live self-serve product tiers. Public examples avoid sport and crypto markets so the track record is not dominated by their noise.

Signal API

Planned access to signal rows with public trader reference, market, side, detected size, entry price, and rule.

  • Request-access API, not self-serve live streaming
  • Signal emission timestamp in UTC
  • Cohort tags attached at emission
  • For teams that need reproducible research inputs

Historical signal review

Planned reviewed signal history with resolved outcome labels and cohort tags.

  • One row per original signal
  • Resolution status: won, lost, or unresolved
  • Reproducible definitions and timestamps

Lifecycle event fields

Planned post-signal fields per public trader reference and market, separate from accuracy.

  • Event types: add, partial/full exit, take-profit, stop-loss, hedge, reversal
  • Always linked to the original signal id
  • Never collapsed into the accuracy number

Resolved outcome labels

Per-signal market resolution truth for backtesting and dashboards.

  • Original signal direction recorded at emission
  • Market outcome attached after resolution
  • Unresolved markets stay flagged until close

Real market-flow example

Selected market-flow example

A sanitized runtime view chooses a recent non-sport, non-crypto market with enough two-sided activity to render clearly. BUY-side and SELL-side are trade-side volume across all listed outcome tokens; they do not mean BUY YES or SELL NO.

Loading market-flow snapshot...

Schema preview

Stable, documented JSON

Field names match the methodology terminology. Types are stable across tiers. Final field set will be locked when early access opens.

Signal object

{
  "signal_id": "sg_2026_05_05_14_07_00_a1b2",
  "emitted_at_utc": "2026-05-05T14:07:00Z",
  "market": {
    "condition_id": "0xExample...",
    "slug": "example-event-q3-2026",
    "title": "Will Example Event happen by Q3 2026?"
  },
  "trader_ref": "trader_F24",
  "trader_initials": "F24",
  "side": "BUY_YES",
  "detected_size_usd": 18400,
  "entry_price": 0.41,
  "rule": "whale_accumulation",
  "insight": "Why the observed activity matters.",
  "cohort_tags": ["all", "gt_5k", "gt_10k"],
  "resolution": {
    "status": "won",
    "resolved_at_utc": "2026-05-09T22:00:00Z",
    "market_outcome": "YES"
  }
}

Lifecycle event object

{
  "event_id": "ev_2026_05_05_18_42_00_a1b2",
  "signal_id": "sg_2026_05_05_14_07_00_a1b2",
  "observed_at_utc": "2026-05-05T18:42:00Z",
  "event_type": "added_conviction",
  "side": "BUY_YES",
  "delta_size_usd": 9100,
  "price_at_event": 0.46,
  "inference_basis": "price_vs_entry"
}

Use cases

  • Research desks - reproducible backtests against the historical dataset, with resolved outcome labels and fixed cohorts.
  • Trading teams - reviewed signal and lifecycle fields used as a research input.
  • Analytics teams - dashboards on whale wallet behavior, exits, hedges, and reversals, separate from signal accuracy.

Access

Access is allocated by request. Pricing depends on dataset scope and refresh cadence after the product surface is ready. Same data definitions as the public methodology and Telegram record.

Request access

Data products are research inputs. They are not investment advice. We do not provide execution, custody, or recommendations.