Skip to main content
Coinversa Pulse is a REST API and MCP server for crypto intelligence on Hyperliquid. It indexes every tracked wallet, classifies behavior into cohorts, and exposes trader analytics, liquidation heatmaps, HIP-4 outcome contract data, and a cross-market asset registry that resolves venue symbols (xyz:GOLD, hyna:PAXG) to canonical assets. The same endpoints power our own dashboard, every MCP client (Claude, Cursor, Perplexity), and external bots.

​
Choose your path

There are three ways into the same data, all with the same API key — pick the one that matches what you’re building.

Building an AI agent?

Use the MCP server. One connector gives Claude, Cursor, or Perplexity first-class tool access — the agent picks and calls tools for you, no HTTP code.https://mcp.coinversa.ai/mcp

Building an app, script, or SDK?

Use the REST API directly. Every endpoint, JSON, in your language. This is the complete and authoritative surface — the MCP wraps a curated subset of it.https://api.coinversa.ai/api/public/v1

Need fills as they happen?

Use the WebSocket. Every fill on Hyperliquid streamed at block cadence — the firehose, one coin, or one wallet — with the trader’s wallet and PnL on each fill. Same key; limits are on connections, not messages.wss://ws.coinversa.ai
The MCP is a thin wrapper over the REST API — it translates tool calls into the same HTTP endpoints documented here. Anything the MCP can do, the REST API can do; the REST API also exposes endpoints not yet wrapped as tools, and supports x402 pay-per-call which the MCP does not yet sign natively. When in doubt, the REST API is the full surface.

​
Get started

Quickstart

Get an API key and make your first request in under 5 minutes.

MCP setup

Connect Pulse to Claude, Cursor, or Perplexity.

API reference

110+ endpoints, auto-generated from the live OpenAPI spec.

Authentication

API keys, rate-limit headers, tier behavior.

WebSocket API

Stream every fill: auth on the upgrade, twenty-four feeds, sequence numbers, plan limits.

​
What’s in the data

Position lifecycles

Every position reconstructed open→close with MAE/MFE — analyze execution quality, drawdowns, and trader archetypes, not just PnL.

Trader cohorts

Every tracked wallet classified by PnL and size tier — from Apex to Blown Out, Heavyweights to Strawweights.

Builder analytics

Ledger-exact revenue for every builder code, plus attributed fills since Jan 2025 — retention triangles, cohort mix, and cross-builder overlap.

Cross-market assets

Canonical taxonomy unifying native HL perps with builder dex listings — PAXG, xyz:GOLD, and hyna:PAXG all resolve to GOLD.

HIP-4 outcomes

Prediction-market style outcome contracts: discovery, settlements, perp-position context, trader overlap.

Live risk

Liquidation heatmaps, recent liquidations, cohort bias, long/short ratios, OI history.

​
How it’s used

  • AI agents — install the MCP server into Claude / Cursor / Perplexity and the agent gets first-class tool access to the Pulse data surface.
  • Trading bots & SDKs — hit the REST API directly with X-API-Key. Same key, same tier, same data — and the full endpoint surface, including anything not yet exposed as an MCP tool.
  • Dashboards — the Coinversa Pulse dashboard and partner integrations consume the same REST endpoints.
  • Indexers & live feeds — subscribe over the WebSocket and receive every fill as it lands, instead of polling.
The MCP server is open source: github.com/Coinversaa/mcp-server. It’s a thin transport layer — the API key you use governs the tier and rate limits at the API layer.