Skip to main content

1. Get an API key

1

Sign in

Go to developers.coinversa.ai and sign in (Privy — email, wallet, or social).
2

Create a key

Open Keys in the portal sidebar and click Create key. Give it a name (e.g. “local-dev”). Copy the key now — it’s shown once.
3

Pick a tier

All accounts start on Free (30 req/min, 1,000 req/day). Upgrade later in Billing if you need higher limits — see pricing.

2. Make your first request

curl https://api.coinversa.ai/api/public/v1/pulse/stats \
  -H "X-API-Key: YOUR_API_KEY"
import httpx

r = httpx.get(
    "https://api.coinversa.ai/api/public/v1/pulse/stats",
    headers={"X-API-Key": "YOUR_API_KEY"},
)
print(r.json())
const res = await fetch("https://api.coinversa.ai/api/public/v1/pulse/stats", {
  headers: { "X-API-Key": process.env.COINVERSAA_API_KEY },
});
console.log(await res.json());
req, _ := http.NewRequest("GET", "https://api.coinversa.ai/api/public/v1/pulse/stats", nil)
req.Header.Set("X-API-Key", os.Getenv("COINVERSAA_API_KEY"))
resp, _ := http.DefaultClient.Do(req)
defer resp.Body.Close()
io.Copy(os.Stdout, resp.Body)
You should see global market stats (total traders, total volume, data coverage period). If you get a 401, your key is wrong or inactive. If you get a 429, check the rate-limit headers — see authentication.

3. (Optional) Wire it into your AI agent

If you’re building an AI agent rather than calling the API directly, the MCP server gives Claude, Cursor, and Perplexity tool access using the same key — no HTTP code on your side. Building an app, dashboard, or script instead? You’re done after step 2; skip to What’s next. Not sure which fits? See Choose your path. Pick your client:

Claude.ai (web)

Custom connector — paste URL + key.

Claude Desktop

Edit claude_desktop_config.json.

Cursor

One-click deeplink install.

Perplexity

Custom connector — URL + header.

What’s next

  • Browse the API reference — every endpoint has a “Try it” panel.
  • Read concepts to understand symbol formats, cohort tiers, and the cross-market asset model.
  • See authentication for rate-limit behavior, tier gates, and error shapes.