Permissionless API & MCP

Perplog's data layer is open: read-only, no API key, no login. Point Claude, Cursor, or ChatGPT at these endpoints — traders are developers. Every value derives from public Hyperliquid state or open-source perplog-core reconstruction.

Live endpoints

GET/api/data/markets

Live HL perp universe — name, mark, 24h change, funding. Sorted by 24h volume.

GET/api/data/briefing

Funding extremes, 24h movers, open interest, HLP exposure, premium/discount — ranked in perplog-core.

GET/api/data/journal?wallet=0x…

Round-trip trades + stats (win rate, profit factor, hold time) reconstructed from any wallet's public HL fills.

GET/api/data/review?wallet=0x…

Weekly performance snapshot + sizing discipline for any wallet.

Try it — no key, no login

curl https://perplog.com/api/data/journal?wallet=0x42c1…c20

MCP server — Claude / Cursor

A thin MCP wrapper exposes these as read-only tools so Claude can analyze trades, draft a weekly review, or detect patterns — never execute, never touch keys. Add to claude_desktop_config.json:

{
  "mcpServers": {
    "perplog": {
      "command": "npx",
      "args": ["-y", "@perplog/mcp"],
      "env": { "PERPLOG_BASE": "https://perplog.com" }
    }
  }
}

Read-only by construction: no write path, no auth, no wallet access. Cypherpunk transparency — audit it without an NDA, an API key, or a login.