Question 1

How do I get started with WebSockets?

Accepted Answer

Create a free account, generate an API key from your dashboard, and connect to the websocket endpoint. The documentation covers the handshake, room subscriptions, and payload shapes. The TypeScript SDK ships a typed client with auto-reconnect and subscription replay so you can subscribe to a room in a few lines.

Question 2

Can I connect end users directly from the browser?

Accepted Answer

Yes. Users connect with JWTs from any auth provider like Clerk, Auth0, or your own IdP. Ship a public key to the browser and keep your secret key server-side, so each logged-in user gets their own socket without exposing credentials.

Question 3

What do the streams cover?

Accepted Answer

The self-serve socket is Polymarket: trades, order books, candlesticks, and positions. Need other chains or protocols? That is an engagement. We stand up the rooms with your team.

Question 4

What streams are available?

Accepted Answer

Typed data rooms cover trade streams, order book snapshots and deltas, price and candlestick ticks, positions and PnL updates, live market and event feeds, aggregated metrics, and wallet balances. A dedicated alerts socket adds pre-computed triggers for whale trades, volume spikes, price moves, and metric thresholds on Polymarket.

Question 5

How fresh is the data?

Accepted Answer

Data is pushed the moment it lands onchain or crosses a threshold, with benchmark-leading latency in production. There are no polling loops, cache windows, or reconnect bookkeeping. Your socket stays open and messages arrive as events happen.

Question 6

How do subscriptions and filters work?

Accepted Answer

Each room accepts typed filters so you subscribe to exactly the slice you need, by chain, market, token, wallet, or type. One socket per user holds many subscriptions at once, each with its own filters and per-user rate limits.

Question 7

What happens when a connection drops?

Accepted Answer

The TypeScript client reconnects automatically and replays your active subscriptions, refreshes JWTs, and emits lifecycle events so state stays consistent. You never have to rebuild subscription state by hand after a reconnect.

Question 8

How is WebSocket usage billed?

Accepted Answer

Credits are billed per message delivered, not per connection, with rates that vary by room. Quiet rooms cost nothing beyond a 1-credit hold when you open the socket, and filters let you pay only for the data you actually consume. See the pricing page for plan details.

Question 9

How many concurrent sockets can I open?

Accepted Answer

Plan caps scale from 1 to unlimited concurrent sockets, so one socket per logged-in user just works. Each connection gets its own subscriptions, filters, and per-user rate limits.

Question 10

Where can I find the full WebSocket reference?

Accepted Answer

The complete room reference, subscription parameters, and payload schemas live in the API reference. It documents every room, filter, and alert trigger across all supported chains.

Live onchain data,
streamed across every chain

One socket, every chain

Unified rooms

Typed, resilient client

Millisecond latency

Every onchain stream, one socket away

Trade streams

Discovery & pulse streams

Holder & account updates

Positions & PnL streams

One socket, everything you build on top

Trading Apps

Wallets & Portfolio

AI Agents

Everything the platform gives you

Frequently Asked Questions

Getting Started

Streams & Performance

Auth & Billing

We ship the data backend with your team

Live onchain data, streamed across every chain