Skip to main content
​
API

​
Builder analytics arrives on MCP (connector v0.11.0)

The eight builder-analytics endpoints are now first-class MCP tools on both the hosted connector (https://mcp.coinversa.ai/mcp) and the npx package (@coinversaa/mcp-server@0.11.0), taking the tool surface from 91 → 99: builder_leaderboard, builder_profile, builder_traders, builder_fills, builder_cohorts, builder_retention, builder_overlap, and the inverse trader_builders. Ask your agent “which frontends do MetaMask’s traders also use?” and it can answer from cross-builder attribution no other data source has. Full catalog in MCP tools; endpoint semantics in Builder codes & attribution.

​
Builder analytics: ledger-exact revenue for every builder code

Eight new REST endpoints cover the Hyperliquid builder-code economy — the fees that front-ends, wallet apps, bots, and builder dexes earn on the order flow they route. Revenue is computed from Hyperliquid’s own on-chain cumulative builder-fee ledger (validated to ±0.1% against the chain); fill-level detail comes from order→fill attribution. See the new Builder codes & attribution concept page and the endpoint guide.Starter:
  • GET /builders/leaderboard — every builder ranked by exact ledger revenue, with attributed volume/users/fills and prior-period deltas.
  • GET /builders/{builder}/profile — one builder in depth: revenue, daily series, top coins, user base, fee rate, first/last seen.
  • GET /trader/{address}/builders — which builders a wallet trades through, ordered by fees paid.
Pro:
  • GET /builders/{builder}/traders — the builder’s users with PnL, fees paid, equity, and cohort tiers.
  • GET /builders/{builder}/fills — the raw attributed fill stream (perp / spot / HIP-4), filterable by coin and wallet.
  • GET /builders/{builder}/cohorts — who actually uses the builder: user composition by PnL and size tier.
  • GET /builders/{builder}/retention — a 12-month monthly retention triangle of first-order cohorts.
  • GET /builders/{builder}/overlap — the top 10 other builders a builder’s users also trade through (cross-builder switching — only possible with all-builder attribution).
Every response carries a verified stamp (the ledger block and chain time it was checked against) and a dataNotes disclosure. Attributed history is complete since 2025-01-25 (most trackers’ builder data starts around August 2025). Honest caveat: trigger-order (stop/TP) fills currently attribute at ledger level only — per-builder attribution coverage is ~77–95% while the backfill completes (live capture since 2026-08-20, backfilled to 2026-03-24) — so attributed fills/volume/users slightly undercount versus the exact ledger revenue; every response says so in dataNotes.All 8 endpoints also ship x402 pay-per-call twins — the first x402 surface in the docs (every GET endpoint has carried a keyless /x402 twin since May 2026; builder analytics is where we make it official): no API key, price quoted in the 402 challenge.In review: order-level lifecycle/journey/heatmap endpoints, weekly and revenue-weighted retention, and a live attribution-coverage ratio in the verified stamp. Builder MCP tools are also on the way.
​
API

​
Cohort tiers renamed

The trader cohort tiers have new display names and new canonical input slugs. The new slugs are rolling out with this release everywhere a tier is an input — path parameters, query parameters, and MCP tool arguments. Until the rollout reaches your endpoint (and until your MCP connector refreshes its cached tool schemas, which may still list only the legacy slugs), keep sending legacy slugs if a new slug is rejected. Nothing breaks either way: legacy slugs remain accepted on input indefinitely, and responses are unchanged — they continue to return the legacy slugs (e.g. pnlTier still returns money_printer).See Trader cohorts for the full tier reference.
​
API

​
Liquidation intelligence: notional, sides, and cohorts

The liquidation summary (GET /live/risk/liquidations/summary) now returns the full two-layer picture:
  • totalNotional — liquidated position value (the industry-standard headline number), alongside the existing totalClosedPnl realized losses.
  • longNotional / shortNotional and event counts — which side got force-closed.
  • byCohort — liquidated notional, losses, events, and wallets broken down by behavioral tier. See who actually gets liquidated.
  • wallets — distinct liquidated wallets in the window.
The same aggregates power the explorer’s new public liquidations page. Fields are additive — existing consumers are unaffected.
​
API

​
The Daily Pulse — frozen daily editions via the API

Two new FREE-tier endpoints expose The Daily Pulse, the auto-generated Hyperliquid morning edition:
  • GET /pulse/daily/{date} — the edition for a given YYYY-MM-DD date. Editions are frozen: once stamped (00:05 UTC), the document never changes, so any past date returns exactly what it returned on day one.
  • GET /pulse/daily/latest — the newest edition.
Each edition carries the surprise-ranked stories (whale moves, cohort divergences, OI rotations, liquidation spikes, settlement upsets) with full receipts, matched news headlines, the standing blocks (biggest moves, coin movers, settlements), and the chain-state census stamp the numbers were verified against.Also in recent releases: lifecycle fills now carry per-fill PnL/fee attribution fields (attributedPnl, attributedFee, attributedSize, rawClosedPnl, fillPnlBasis), and cohort bias responses include netBiasByCount / netBiasByNotional.
​
Security

​
Zero-knowledge connector: your API key never leaves our backend

The hosted MCP connector’s credential handling has been rebuilt end to end:
  • Connecting no longer transmits your API key. Picking a key on the authorization page hands over a single-use connect code (2-minute lifetime, dead after first redemption). The MCP server exchanges it server-to-server for an opaque key reference — the raw key never touches the browser or the connector host.
  • Pick any existing key. The authorization page now lists your active keys — connect one in a click, no need to have the value saved and no forced duplicate keys.
  • Encryption at rest for everything else. Sessions from the paste-a-key flow are now AES-256-GCM-encrypted under a key held outside the database, and all OAuth bearer tokens are stored as SHA-256 digests. A stolen copy of the connector’s database yields nothing.
  • Tiers, rate limits, metering, and instant revocation behave exactly as before — revoking a key still disconnects every agent authorized with it.
​
Connector

​
One-click connect: OAuth sign-up on the hosted MCP

Connecting Coinversa to Claude, Perplexity, Cursor, or any MCP client no longer requires copying an API key. Paste https://mcp.coinversa.ai/mcp into your client and it opens the new authorization page:
  • Existing users sign in with their Coinversa account and connect a key in one click — or paste a saved cvsa_ key directly.
  • New users create an account right on the page. Every new account gets 14 days of Pro — all 99 tools, no credit card — and the key is provisioned automatically.
  • Keys stay visible once at creation and revocable any time from the developer portal; revoking a key disconnects every agent authorized with it.
See the updated MCP setup guide — client configs no longer need auth headers.
​
v0.9.0

​
Entity resolution, tier-aware sessions & exchange aggregates

Pulse 0.9.0 adds owner-level intelligence: Hyperliquid traders run named sub-accounts that trade independently, so per-wallet views undercount every multi-account trader. Pulse now resolves any wallet to its owner entity and aggregates across the whole family — a view no other Hyperliquid data product offers. Under the hood, the position dataset is now reconciled hourly against Hyperliquid’s own chain state (the census pipeline), and responses carry the chain block they were last verified against.

​
New features

  • Entity resolution — GET /entity/{address} resolves any wallet (master, sub-account, or unknown) to its owner entity: master address, every named sub-account, each member’s open book, the combined positions across all of them, and a verified-vs-chain stamp. GET /entities/leaderboard ranks the top owners (not wallets) by combined open notional. Both Pro tier. MCP: pulse_entity_profile, pulse_entity_leaderboard.
  • Exchange aggregates — GET /exchange/volume (24h volume by dex — builder dexes are ~43% of Hyperliquid volume and most trackers’ headline numbers omit them), GET /exchange/oi (open interest by dex with long/short split), GET /exchange/active-traders (24h distinct traders). MCP: pulse_exchange_volume, pulse_exchange_oi, pulse_active_traders.
  • Plan introspection — GET /plan returns the caller’s tier, effective limits, and every tier’s limits with an upgrade link. MCP: pulse_my_plan.
  • Chain-verification stamp — GET /census/stamp exposes the chain-state block the dataset was last reconciled against; entity responses include it inline.

​
Updates

  • Tier-gated and rate-limited responses are now machine-actionable: 403s carry current_tier, required_tier, and an upgrade_url (code TIER_GATE), so agents can explain exactly what a request needs instead of a bare “forbidden”.
  • The MCP tool surface grew from 83 → 91 tools; the REST API from 87 → 96 endpoints.
  • Data-accuracy note: this release follows a full reconciliation of the position dataset against Hyperliquid chain state — open positions, open interest, and volumes now match independent trackers to well under 1%, with the residual continuously verified.
​
v0.8.0

​
Position lifecycles & execution quality

Pulse 0.8.0 is built on a fully re-derived position-lifecycle dataset — every position reconstructed open→close from on-chain fills, now carrying MAE/MFE (the worst adverse and best favorable price each position ever saw). For the first time you can analyze execution quality, not just realized PnL.

​
New features

  • Position lifecycles — per-wallet open→close history, aggregate lifecycle stats, single-lifecycle drill-downs (with composing fills), and a one-call wallet briefing. See Position lifecycles.
  • Execution quality (MAE/MFE) — per-position drawdown / run-up curves, “max-pain” survivors (winners that endured deep drawdowns), perfect exits (high MFE capture), and the most catastrophic individual liquidations.
  • Trader archetypes — survivors & anti-survivors, persistent winners, capital-efficient titans (PnL per fee), one-month wonders, newcomer whales, coin kings, top liquidators, and lethal coins — all derived from 90-day lifecycle behavior.
  • Market structure — per-coin winner/loser profit pools, profitability by UTC hour, alpha concentration (percentile profit share), HFT-vs-swing-vs-holder splits, and head-to-head wallet comparison.
  • Refreshed cohorts — pulse_cohort_recent_* tools label wallets by their last-30-day tier (not all-time), surfacing who is printing right now.
  • Global recent feed — pulse_lifecycles_recent streams the most recently closed positions across the entire exchange.

​
Updates

  • The Pulse MCP tool surface grew from 55 → 91 tools — see the full catalog in MCP tools. The REST API now exposes 96 endpoints.
  • The legacy closed-position tools (pulse_trader_closed_positions, pulse_trader_closed_position_stats, pulse_recent_closed_positions) are kept for backward compatibility but are superseded by the lifecycle tools, which read the corrected lifecycle dataset (more history, MAE/MFE, spot coverage).

​
Notes

  • MAE/MFE is perp-only (spot positions have no adverse/favorable excursion by design). The freshest closes may briefly show null MAE/MFE while the hourly risk backfill catches up.
​
v0.7.0

​
HIP-4 outcome intelligence

Coinversa Pulse now indexes the full HIP-4 outcome-contract wire format from Hyperliquid, with discovery, settlement, volume, recent trades, trader overlap, and perp-position context for every outcome.

​
New features

  • 12 HIP-4 MCP tools for outcome-contract discovery, settlements, volume, recent trades, and trader overlap. See the full surface in MCP tools.
  • Outcome + perp context tool lets agents pull a trader’s open perp position alongside their HIP-4 outcome exposure in a single call — useful for hedging and conviction-overlap analysis.
  • Hosted Remote MCP is now documented at https://mcp.coinversa.ai/mcp, so you can connect agents without installing the npm package. See MCP setup.

​
Updates

  • The Pulse MCP tool surface grew from 43 → 55 tools.
  • README, agent SKILL metadata, and server instructions updated for the new HIP-4 surface.

​
Breaking changes

  • Keyless / no-API-key mode has been removed. All MCP tools now require a Coinversa API key. Grab a free-tier key from the dashboard — see Authentication and Pricing for details.