> ## 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.

# Authentication

> Authenticate to the HypeDexer MCP server with your existing API key.

Every request to the MCP server must be authenticated with a **Bearer token**.

```
POST /mcp
Host: mcp.hypedexer.com
Authorization: Bearer <your_api_key>
```

## Your API key is the bearer token

The bearer **is your HypeDexer API key** — the same key you already use for the REST API. There is no separate MCP token to generate, and existing API keys work as-is.

You can create and manage keys in your [dashboard](https://www.app.hypedexer.com/).

## There is no anonymous access

A request without a bearer is refused with **401**. Every tier needs a key — including for tools that return public Hyperliquid data.

```json theme={null}
{
  "jsonrpc": "2.0",
  "error": {
    "code": -32000,
    "message": "Unauthorized: send your HypeDexer API key as \"Authorization: Bearer <key>\". Get one at https://www.app.hypedexer.com/."
  },
  "id": null
}
```

## Verify your setup

The health endpoint is public and needs no key — use it to check that the server is reachable from your network:

<CodeGroup>
  ```bash Health check theme={null}

  curl -X 'GET' \
    'https://mcp.hypedexer.com/health'

  ```
</CodeGroup>

```json theme={null}
{ "ok": true, "name": "hypedexer-mcp", "protocol": "stateless" }
```

To confirm your key itself works, list the tools directly over HTTP:

<CodeGroup>
  ```bash List tools theme={null}

  curl -X 'POST' \
    'https://mcp.hypedexer.com/mcp' \
    -H 'Authorization: Bearer YOUR_API_KEY' \
    -H 'Content-Type: application/json' \
    -H 'Accept: application/json, text/event-stream' \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

  ```
</CodeGroup>

A valid key returns the tool catalog. A missing or invalid one returns the 401 above — see [Errors](/mcp/errors) for the full list of failure modes.

## Key types

Most keys are regular **Data API keys**: they work both for direct REST calls on `api.hypedexer.com` and through the MCP server.

Some keys are restricted to the hosted MCP server. Using one for a direct REST call returns **403** with the reason `mcp_only_key` — use a Data API key for direct REST integrations, and for the [local stdio server](/mcp/clients#local-stdio-alternative).

<Info>
  Rate limits and credits are enforced per key, exactly as they are for REST. See [Rate limits & quotas](/guides/rate-limits-and-quotas).
</Info>