Skip to main content
Tier gates are enforced server-side. A request without sufficient entitlement returns 403 with code TIER_GATE and machine-actionable fields:
reason is missing_api_key (no key), invalid_api_key (key present but inactive) or insufficient_tier (key below the required tier). Every endpoint requires an API key — keyless requests are rejected with the shape above (current_tier: "none"), even on endpoints whose required tier is free. The keyless exception is the x402 pay-per-call surface below.

​
Comparison

Free has no monthly bucket — its ceiling is the daily cap. Rate-limit behavior, header semantics, and error response shapes are documented in Authentication. These are REST limits. The WebSocket is metered on capacity instead — connections per account (shared across keys), subscriptions per connection, and fair-use bandwidth — and never draws down the request counts above: Enterprise websocket numbers are per-account overrides reported in the connected frame — see WebSocket plan limits.

​
Endpoints by tier

Global and per-trader basics. Only four /live/* endpoints are Free — the long/short trio and official open interest for one coin (last 24 hours); the live cohort-bias and risk snapshots are Starter, and longer history, the whole-dex OI batch and the chart layers are Pro. Most /market/* endpoints are Free, but not all. See the table below for the exact list.
  • Custom RPM, daily, and monthly caps
  • Unlimited active keys
  • Custom data windows beyond 90 days (see Data windows)
  • Dedicated support channel
  • SLA on uptime and response times
  • Optional bulk historical exports and custom data delivery
Negotiated per-engagement. Contact chat@coinversa.ai.

​
x402 pay-per-call

Every GET endpoint has a pay-per-call twin — no API key, no subscription. The twin lives at the same path under the /x402 prefix; the builder analytics endpoints are the first surface we document for it:
Payment is negotiated via the x402 protocol: an unpaid request returns HTTP 402 with a challenge (base64 JSON in the Payment-Required header) listing the accepted networks, assets, and the per-call price; your client signs a payment and retries with the payment header. x402 client libraries handle the handshake automatically — the per-call price is whatever the 402 challenge quotes. Two things to know:
  • The x402 twins are intentionally absent from the OpenAPI spec and the “Try it” panels — this page and Builder endpoints are their documentation surface.
  • The MCP server does not sign x402 payments natively — pay-per-call is a direct-REST feature today.

​
How tier resolution works

Each API key has an effective tier. Endpoint access and daily/monthly caps are checked using that tier, but REST usage is shared across the account’s keys — creating another key does not create another request allocation. A Free key calling alongside an unused Pro key still has Free endpoint access and daily/monthly caps. The websocket resolves differently: a connection gets the highest entitled tier across the account’s keys, and its connection cap is shared by all of them. See WebSocket plan limits. Tier entitlement is granted by an active Stripe subscription, an explicit grandfather override, or a failed payment still inside its grace window (up to 14 days, never past the current billing period). A paid key whose own entitlement ends is still served at its tier if another active key on the same account is entitled at that tier (or at the lower paid tier that sibling holds); otherwise it falls back to Free limits. The key is not deleted — your existing integrations keep working at reduced quota until you reactivate. See Authentication for the request-time mechanics and rate-limit headers.