Skip to main content

Getting started

Create an account in the console, open API Keys and click Create API Key. No approval step. Step by step in Generate API key, first request in the Quickstart.
Three ways, all equivalent: the X-API-Key header, Authorization: Bearer <key>, or the api_key query parameter. The same key works for REST, WebSocket and the MCP server. Details in Authentication.
Yes, 5,000 credits a month, renewed every 30 days, no card required. See Rate Limits & Pricing.
One URL, https://api.hypedexer.com. A global load balancer routes you to the nearest region. Quotas and prices are identical on both.

Billing

At least 1 credit, and 1 credit per 25 rows returned on paginated endpoints. Batch endpoints cost 3 credits per wallet. Failed requests (status 400 and above) are free.
Every response carries X-Credit-Cost (credits charged) and X-Credit-Balance (what is left). No need to poll a usage endpoint.
Ten delivered events count as one credit, pooled with your REST credits.

Data coverage

Fills of every user run continuously from 18 November 2024. Candles start on 22 March 2025 for the main perp markets, and at each dex’s launch for HIP-3. Per-dataset detail, including which fields are populated in which period, is in the Historical Trade Archive.
Older fills carry fewer fields. dir, oid, hash and startPosition are populated from 22 March 2025, fee and tid from 25 May 2025. The table in the Historical Trade Archive gives the exact periods. If you compute fees or match both sides of a trade by tid, start on 25 May 2025.
Yes: spot fills alongside perp fills on the same endpoints (filter on typeTrade), HIP-3 dexs with their assets, auctions, OHLCV and oracle stats, and HIP-4 prediction markets. HyperEVM blocks, transactions, logs and bridge events are indexed too.
Yes, both levels: L2 (aggregated by price) and L4 (every resting order with its owner), over REST and over WebSocket. See Live data.

Using the API

Always bound it with start_time and end_time. On an active address a five-minute window answers in well under a second, while an unbounded request has to count the whole history first. Then follow next_cursor until has_more is false.
It depends on the endpoint: fills and liquidations use cursor, most other lists use offset. Each endpoint’s parameters are listed on its reference page. See Pagination.
The server sends {"type":"ping","ts":<ms>} every 60 seconds and expects {"method":"pong"} back. Without an answer it closes the socket with code 4000. See the WebSocket overview.
No. A stream resumes at the present moment. Backfill any gap over REST, using the timestamp of the last frame you processed.
/fills/ and /fills/user/{address} return both. Filter on typeTrade (perp or spot), or use the spot-only endpoints.

AI agents

Yes, through our hosted MCP server at mcp.hypedexer.com/mcp, 78 read-only tools, authenticated with the same API key. See AI Agents (MCP).
No, it draws on the same credit balance as REST. One tool call can trigger several API requests.

Something else

Ask on Telegram or at contact@hypedexer.com. Early-stage teams and public goods projects can also look at For Builders.