> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypedexer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Short answers to the questions we are asked most often, with links to the page that goes deeper.

## Getting started

<AccordionGroup>
  <Accordion title="How do I get an API key?">
    Create an account in the [console](https://app.hypedexer.com), open **API Keys** and click **Create API Key**. No approval step. Step by step in [Generate API key](/api/generate-api-key), first request in the [Quickstart](/quickstart).
  </Accordion>

  <Accordion title="How do I send my key?">
    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](/mcp/authentication). Details in [Authentication](/guides/authentication-and-api-keys).
  </Accordion>

  <Accordion title="Is there a free tier?">
    Yes, 5,000 credits a month, renewed every 30 days, no card required. See [Rate Limits & Pricing](/guides/rate-limits-and-quotas).
  </Accordion>

  <Accordion title="Which base URL should I use for Europe or Japan?">
    One URL, `https://api.hypedexer.com`. A global load balancer routes you to the nearest region. Quotas and prices are identical on both.
  </Accordion>
</AccordionGroup>

## Billing

<AccordionGroup>
  <Accordion title="What does one request cost?">
    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.
  </Accordion>

  <Accordion title="How do I know what a call cost me?">
    Every response carries `X-Credit-Cost` (credits charged) and `X-Credit-Balance` (what is left). No need to poll a usage endpoint.
  </Accordion>

  <Accordion title="How are WebSocket events billed?">
    Ten delivered events count as one credit, pooled with your REST credits.
  </Accordion>
</AccordionGroup>

## Data coverage

<AccordionGroup>
  <Accordion title="How far back does the data go?">
    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](/guides/historical-trade-archive).
  </Accordion>

  <Accordion title="Why are `fee`, `oid` or `dir` empty on old fills?">
    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](/guides/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.
  </Accordion>

  <Accordion title="Do you cover spot, HIP-3 and HIP-4?">
    Yes: spot fills alongside perp fills on the same endpoints (filter on `typeTrade`), [HIP-3](/hip-3/index) dexs with their assets, auctions, OHLCV and oracle stats, and [HIP-4](/hip-4/overview) prediction markets. [HyperEVM](/evm/index) blocks, transactions, logs and bridge events are indexed too.
  </Accordion>

  <Accordion title="Can I get the order book?">
    Yes, both levels: L2 (aggregated by price) and L4 (every resting order with its owner), over REST and over WebSocket. See [Live data](/live-data/index).
  </Accordion>
</AccordionGroup>

## Using the API

<AccordionGroup>
  <Accordion title="A fills query is slow. What should I do?">
    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.
  </Accordion>

  <Accordion title="Cursor or offset?">
    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](/guides/pagination-filters-and-sorting).
  </Accordion>

  <Accordion title="My WebSocket connection drops after about three minutes.">
    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](/websocket/overview).
  </Accordion>

  <Accordion title="Is there replay on the WebSocket?">
    No. A stream resumes at the present moment. Backfill any gap over REST, using the timestamp of the last frame you processed.
  </Accordion>

  <Accordion title="Why does my spot query return perp rows?">
    `/fills/` and `/fills/user/{address}` return both. Filter on `typeTrade` (`perp` or `spot`), or use the spot-only endpoints.
  </Accordion>
</AccordionGroup>

## AI agents

<AccordionGroup>
  <Accordion title="Can I plug this into Claude or Cursor?">
    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)](/mcp/overview).
  </Accordion>

  <Accordion title="Does MCP usage cost extra?">
    No, it draws on the same credit balance as REST. One tool call can trigger several API requests.
  </Accordion>
</AccordionGroup>

## Something else

Ask on [Telegram](https://t.me/EnigmaValidatorCommunity/1) or at [contact@hypedexer.com](mailto:contact@hypedexer.com). Early-stage teams and public goods projects can also look at [For Builders](/guides/for-builders).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.