Tier and pricing matrix - Coinversa Pulse

Tier gates are enforced server-side. A request without sufficient entitlement returns 403 with code TIER_GATE and machine-actionable fields:

{
  "title": "Forbidden",
  "status": 403,
  "detail": "Api key needed for this request",
  "code": "TIER_GATE",
  "current_tier": "none",
  "required_tier": "starter",
  "upgrade_url": "https://coinversa.ai/developers#pricing"
}

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

Tier	Rate (req/min)	Daily cap	Monthly cap	Max keys	Price/mo
Free	30	1,000	0	1	$0
Starter	120	2,000	50,000	3	$29
Pro	600	20,000	500,000	10	$199
Enterprise	10,000+	unlimited	unlimited	unlimited	from $1,999

A monthly cap of 0 means unlimited within the daily cap. Rate-limit behavior, header semantics, and error response shapes are documented in Authentication.

Endpoints by tier

Free (with API key)

Global and per-trader basics. All /live/* endpoints are available at this tier with no further gating; most /market/* endpoints are too — see the table below for the exact list.

Group	Endpoints
Global	`/pulse/stats`, `/pulse/market-overview`, `/pulse/leaderboard`
Daily Pulse	`/pulse/daily/{date}`, `/pulse/daily/latest`
Discovery	`/pulse/hidden-gems`, `/pulse/most-traded`, `/pulse/biggest-wins`, `/pulse/biggest-losses`
Cohort summary	`/pulse/cohorts/summary`
Trader profile	`/pulse/trader/{address}`, `/pulse/trader/{address}/trades`, `/daily`, `/performance`, `/tokens`, `/demo`, `/closed-positions`, `/closed-positions/stats`
Coin views	`/pulse/token-leaderboard/{coin}`, `/pulse/trades/recent`
Lifecycle (single)	`/pulse/lifecycle/{id}`, `/pulse/closed-positions/recent`
Live state	All `/live/*`
Market	`/market/positions/{address}`, `/market/price/{symbol}`, `/market/orderbook/{symbol}`, `/market/historical-oi`
Exchange aggregates	`/exchange/volume`, `/exchange/oi`, `/exchange/active-traders`, `/exchange/positions`
HIP-4	`/hip4/outcomes`, `/hip4/outcomes/{outcome_id}`, `/hip4/outcomes/{outcome_id}/recent-trades`, `/hip4/questions`, `/hip4/settlements/recent`, `/hip4/daily-volume`, `/hip4/most-active`
Utility	`/plan`, `/census/stamp`

Starter — includes Free, plus

Group	Endpoints
Lifecycle aggregates	`/pulse/trader/{address}/lifecycles`, `/pulse/trader/{address}/lifecycle-summary`
Comparison	`/pulse/compare`
Coin alpha	`/pulse/coin-alpha-map`, `/pulse/coin-kings`
Behavior	`/pulse/hour-profitability`, `/pulse/style-distribution`
Risk	`/pulse/top-liquidators`
Builder analytics	`/builders/leaderboard`, `/builders/{builder}/profile`, `/trader/{address}/builders` — see Builder endpoints
Exchange aggregates	`/exchange/pnl-leaders`
HIP-4	`/hip4/outcomes/{outcome_id}/summary`, `/hip4/top-traders`, `/hip4/trader/{address}/outcomes`

Pro — includes Starter, plus

Group	Endpoints
Discovery (deep)	`/pulse/persistent-winners`, `/pulse/one-month-wonders`, `/pulse/survivors`, `/pulse/anti-survivors`, `/pulse/capital-titans`, `/pulse/newcomer-whales`
Risk & market	`/pulse/lethal-coins`, `/pulse/backstop-events`, `/pulse/market-concentration`, `/market/candles/recent/{symbol}`
Cohort drilldowns (lifetime)	`/pulse/cohorts/{tierType}/{tier}/positions`, `/trades`, `/history`
Cohort drilldowns (rolling 30d)	`/pulse/cohorts-recent/{tierType}/{tier}/positions`, `/trades`, `/lifecycle-stats`, `/top-positions`, `/alpha-concentration`
Cohort timeseries	`/pulse/cohorts/daily-stats`, `/pulse/cohort-bias/history`
Builder analytics (deep)	`/builders/{builder}/traders`, `/builders/{builder}/fills`, `/builders/{builder}/cohorts`, `/builders/{builder}/retention`, `/builders/{builder}/overlap` — see Builder endpoints
Entity resolution	`/entity/{address}`, `/entities/leaderboard`
HIP-4 (deep)	`/hip4/cross-product/overlap`, `/hip4/outcomes/{outcome_id}/perp-position-context`

Enterprise — everything, plus

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:

https://api.coinversa.ai/x402/api/public/v1/builders/leaderboard?period=week

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 carries its own tier independently. If you have multiple keys on the same account at different tiers, each key is rate-limited and entitlement-checked on its own — a Free key calling with a Pro key sitting unused in the same account still only gets Free limits. Tier entitlement is granted by an active Stripe subscription or an explicit grandfather override. If a paid key’s subscription lapses, that specific key falls back to Free limits but 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.

​Comparison

​Endpoints by tier

​x402 pay-per-call

​How tier resolution works

Comparison

Endpoints by tier

x402 pay-per-call

How tier resolution works