Channel Catalog
Every channel you can subscribe to over the WebSocket Protocol, what it carries, and the tier it needs. {mint} is a token mint; {address} is a wallet address.
Market data
| Channel | Carries | Tier |
|---|---|---|
token:{mint}:trades | Every swap on the token — full trade tape | L1 |
token:{mint}:ticks | Per-trade chart ticks (price + volume) | L1 |
token:{mint}:ohlcv:{view}:{tf} | Live OHLCV candles | L1 |
The ohlcv channel takes two parameters in the name: view = full or filtered, and tf = 1s · 1m · 5m · 15m · 1h. Example: token:EPjFWd...:ohlcv:filtered:5m.
Wallet intelligence
| Channel | Carries | Tier |
|---|---|---|
wallet:{address}:pnl | Realized PnL on every sell | L2 |
wallet:{address}:positions | Position deltas (open / partial / close) | L2 |
wallet:{address}:labels | Label updates, on state change | L2 |
Security & coordination
| Channel | Carries | Tier |
|---|---|---|
token:{mint}:security | Token security events (bundle, wash, rug, coordination) | L3 |
wallet:{address}:security | Wallet security events | L3 |
wallet:{address}:follow | Follow-edge activations and updates | L3 |
wallet:{address}:entity | Entity membership changes | L3 |
token:{mint}:campaign | Campaign activations on the token | L3 |
The three coordination channels (follow, entity, campaign) carry the same primitives as the REST Coordination endpoints. They’re opt-in on the backend — if one is silent, fall back to REST and check /v1/coordination/health.
Planned
Planned On the roadmap, documented with their primitives today:
| Channel | Carries |
|---|---|
token:{mint}:holders | Holder balance updates |
token:{mint}:holders:summary | Holder concentration summaries |
token:{mint}:score | Token Health Score on every recompute |
Subscribe with {"op": "subscribe", "channels": [...]}; data arrives as {"channel": "...", "data": { ... }}. See the WebSocket Protocol for the full message lifecycle and per-tier limits.