Tiers & Rate Limits
Every API key carries a tier. The tier determines which endpoints you can call, how many REST requests per minute you get, and how many WebSocket connections you can hold open. Each tier includes everything in the tiers below it.
| Tier | Price | REST (req/min) | WS connections | Adds |
|---|---|---|---|---|
| Free | $0 | 5 | 0 | Buyer quality, bundle summary |
| Layer 1 | $79/mo | 100 | 5 | Market data — OHLCV, trades, ticks, holders |
| Layer 2 | $249/mo | 300 | 20 | Wallet intelligence — PnL, positions, labels, profile, provenance |
| Layer 3 | $599/mo | 600 | 50 | Security & coordination — bundles, wash trades, entanglement, follows/entities |
| Enterprise | from $999/mo | 3,000+ | Unlimited | Bulk endpoints, dedicated NATS, custom limits |
Your tier is fixed to your API key. Get a key or upgrade →
REST rate limits
The per-minute limit is enforced per key. Exceed it and the request returns 429 Too Many Requests — back off and retry. The free tier is for evaluation; for production traffic start at Layer 1.
WebSocket limits
WebSocket access starts at Layer 1 (Free gets 0 connections). Each tier caps both the number of concurrent connections and the subscriptions per connection (50 on Layer 1–3, unlimited on Enterprise).
| Tier | Connections | Subscriptions / connection |
|---|---|---|
| Free | 0 | — |
| Layer 1 | 5 | 50 |
| Layer 2 | 20 | 50 |
| Layer 3 | 50 | 50 |
| Enterprise | Unlimited | Unlimited |
Exceeding the subscription cap returns an error message on the socket; it does not disconnect you. See the WebSocket Protocol for the full lifecycle.