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

# Errors

> Failure modes of the HypeDexer MCP server and how to recover from them.

Errors returned by the MCP server explain how to recover, so an agent can usually correct itself without human help.

## Status codes

|  Status | Meaning                                                            | Recommended action                                              |
| ------: | ------------------------------------------------------------------ | --------------------------------------------------------------- |
| **401** | Missing or invalid bearer                                          | Send a valid HypeDexer API key as `Authorization: Bearer <key>` |
| **402** | Insufficient credits                                               | Top up your account balance                                     |
| **403** | `mcp_only_key` — this key only works through the hosted MCP server | Use a Data API key for direct REST calls                        |
| **429** | Rate limit exceeded                                                | Back off and honour `Retry-After`                               |

## 401 — no anonymous access

There is no keyless access to the hosted server: every tier needs a key, and the bearer is your regular HypeDexer API key.

```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
}
```

See [Authentication](/mcp/authentication) for the full setup.

## 402 — insufficient credits

MCP usage bills credits from the same balance as REST. Because one tool call can fan out into several API requests, a balance that looks sufficient for a handful of REST calls can run out faster through an agent. Top up in your [dashboard](https://www.app.hypedexer.com/).

## 403 — `mcp_only_key`

Some keys are restricted to the hosted MCP server. They are refused on direct REST calls to `api.hypedexer.com`, and they do not work with the [local stdio server](/mcp/clients#local-stdio-alternative), which calls the Data API directly. Use a regular Data API key for those.

## 429 — rate limits

Rate limits are enforced per key, exactly as for REST. Back off and honour the `Retry-After` header. See [Rate limits & quotas](/guides/rate-limits-and-quotas) for the general policy.

***

Need Help ?

<Columns cols={2}>
  <Card title="Telegram" icon="telegram" href="https://t.me/EnigmaValidatorCommunity/1" />

  <Card title="Discord" icon="discord" href="https://discord.com/invite/cbKncMeZ52" />

  <Card title="Email" icon="envelope" href="mailto:contact@hypedexer.com" />

  <Card title="Twitter" icon="twitter" href="https://x.com/hypedexer" />
</Columns>