WebSockets

Thirteen real-time channel families for agent observation loops. Subscribe after a REST or MCP snapshot, then reconcile periodically because this transport favors low latency over replay guarantees.

Connecting

wss://api.conyr.ai/ws

import WebSocket from "ws";
 
const ws = new WebSocket("wss://api.conyr.ai/ws", {
  headers: { Authorization: "Bearer YOUR_API_KEY" },
});
 
ws.onopen = () => {
  ws.send(JSON.stringify({
    op: "subscribe",
    channels: ["token:EPjFWd...:trades"]
  }));
};
 
ws.onmessage = (event) => {
  const msg = JSON.parse(event.data);
  if (msg.channel) {
    console.log(`[${msg.channel}]`, msg.data);
  }
};

import asyncio
import json
import websockets
 
async def stream():
    async with websockets.connect(
        "wss://api.conyr.ai/ws",
        additional_headers={"Authorization": "Bearer YOUR_API_KEY"},
    ) as ws:
        await ws.send(json.dumps({
            "op": "subscribe",
            "channels": [
                "token:EPjFWd...:trades",
                "token:EPjFWd...:ohlcv:full:1m",
            ]
        }))
 
        async for message in ws:
            data = json.loads(message)
            if "channel" in data:
                print(f"[{data['channel']}] {data['data']}")
 
asyncio.run(stream())

Client → Server Messages

Subscribe

{"op": "subscribe", "channels": ["token:EPjFWd...:trades", "wallet:7xKXtg...:pnl"]}

Subscribe to multiple channels in a single message.

Unsubscribe

{"op": "unsubscribe", "channels": ["token:EPjFWd...:trades"]}

Ping

{"op": "ping"}

Server → Client Messages

Subscription Confirmed

{"op": "subscribed", "channels": ["token:EPjFWd...:trades"]}

Unsubscription Confirmed

{"op": "unsubscribed", "channels": ["token:EPjFWd...:trades"]}

Data Event

{"channel": "token:EPjFWd...:trades", "data": { ... }}

The data payload depends on the channel type.

Pong

{"op": "pong"}

Error

{"op": "error", "message": "Subscription limit reached (max 50)"}

Subscription and message errors are informational — they don’t disconnect you. Subscribing to a channel above your key’s tier returns a non-fatal op:error naming the required tier (e.g. Channel '...' requires Layer N tier; your key is ...); the connection stays open and your other subscriptions in the same batch still succeed.

Connection-level rejections do terminate the connection: a Free-tier upgrade is refused with HTTP 403, and exceeding the per-key connection cap closes the socket with WebSocket close code 1008.

Available Channels

Layer 1 — Market Data

OHLCV parameters:

• view: full or filtered
• tf (timeframe): 1s, 1m, 5m, 15m, 1h
• Example: token:EPjFWd...:ohlcv:filtered:5m

Layer 2 — Wallet Intelligence

The labels channel is activity-driven. Updating a public identity association alone does not guarantee an event for a dormant wallet; use GET /v1/wallet/{addr}/identity when identity freshness is required.

In label-stream payloads, kol_username and kol_platform are strings. An empty string means the preferred public identity is absent and must clear any value cached by the client; do not treat an empty field as a no-op. REST label and leaderboard projections represent the same absence with JSON null.

Layer 3 — Security Intelligence

Limits by Tier

Backpressure Behavior