Skip to main content
All accounts start on Free. Upgrade in the billing portal when you outgrow it.

Tiers

The websocket is metered separately, on capacity rather than requests — streaming never draws down the numbers above. Connections are capped per account (shared across all your keys), subscriptions per connection, and bandwidth is a fair-use allowance: Details in WebSocket plan limits.

What each tier unlocks

  • All 115 MCP tools / 124 API endpoints (tier-gated)
  • 1 active key
  • Public-only data (no private wallet correlation)
  • WebSocket: 1 connection, 2 subscriptions, six feeds — tradesByCoin, tradesByUser, candle, twapSliceFillsByUser, bbo and allMids
  • 4× the per-minute rate
  • 50k requests / month bucket
  • 3 active keys (rotate without disruption)
  • Live positioning and risk, right now: cohort bias (who is long or short, by trader tier), the liquidation heatmap, the cross-coin risk overview and per-coin risk snapshot, and recent liquidations with their summary
  • The interactive chart (candles and indicators) and the L4 book summary
  • Sharpe ratios: any tracked wallet’s realized-PnL Sharpe (30 days, a custom 1–90-day window, or three monthly buckets) and the top-50 Sharpe leaderboard
  • Builder analytics: leaderboard, builder profiles, per-wallet builder usage
  • WebSocket: 25 subscriptions per connection, the trades firehose, and multi-wallet feeds following up to 1,000 wallets on one subscription
  • 20× Free’s per-minute rate
  • 500k requests / month bucket
  • 10 active keys
  • Deep builder analytics: traders, fills, cohorts, retention, cross-builder overlap
  • History and depth behind the Starter snapshots: cohort-bias and risk history, open-interest history, the chart’s Coinversa layers (entry profile, average entries, Apex vs Crowd history, biggest trades), and the per-order book tools (whales, stop map, levels)
  • TP/SL trigger orders: every pending stop-loss and take-profit order, by market or by wallet
  • Cohort drill-downs, archetypes and deeper analytics tools (entity resolution, HIP-4 perp-position context, etc.)
  • WebSocket: 5 concurrent connections, 100 subscriptions each, all 24 feeds (l4Book, bbo, l2Book, allMids, liquidations, leverage changes, TWAP orders, TWAP statuses and the multi-wallet variants), 250 GB fair-use bandwidth
  • Negotiated rate / volume / SLA
  • Custom historical exports beyond the standard 90-day window
  • Unlimited active keys
  • Priority support, custom data delivery, optional SLAs
  • Email chat@coinversa.ai to scope.

How billing works

  • Subscriptions are managed by Stripe. Manage payment methods, view invoices, change plan, and cancel in the billing portal.
  • Plan changes take effect immediately on upgrade (prorated) and at period end on downgrade.
  • If your subscription lapses (failed payments keep access for up to 14 days), keys fall back to Free limits — they’re not deleted, they just stop being entitled to the paid tier.
  • Each key is entitlement-checked on its own: a key serves the tier it was provisioned at, capped by your account’s active entitlement. A Free key is never promoted by a paid key on the same account — see how tier resolution works.

FAQ

Yes — Starter and Pro both have yearly cadence (~17% cheaper than 12× monthly). Pick “Yearly” on the checkout page.
That’s Enterprise — limits are negotiated independently. Email chat@coinversa.ai.
REST RPM and daily/monthly usage are shared across keys on the same account. Additional keys do not create separate allocations. Access is still evaluated using the presented key’s effective tier, capped by your account’s entitlement — a Free key does not inherit a paid sibling’s access.The websocket connection cap is also per account, shared across every key you own — five Pro connections are five in total, however many keys hold them. See WebSocket plan limits.
Yes. The MCP server forwards your key to the API, so both paths consume the same quota.