Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.coinversa.ai/llms.txt

Use this file to discover all available pages before exploring further.

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.

​
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

59 endpoints, auto-generated from the live OpenAPI spec.

Authentication

API keys, rate-limit headers, tier behavior.

​
What’s in the data

Trader cohorts

Every tracked wallet classified by PnL and size tier — from money_printer to giga_rekt, leviathan to shrimp.

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 55 tools covering the entire data surface.
  • Trading bots — hit the REST API directly with X-API-Key. Same key, same tier, same data.
  • Dashboards — the Coinversa Pulse dashboard and partner integrations consume the same endpoints.
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.