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

# Tool catalog

> The 78 read-only MCP tools exposed by HypeDexer, grouped by domain.

The server exposes **78 tools**, all **read-only** — they query indexed and live Hyperliquid data, and never place orders or modify state. Tools are named by group prefix, so an agent can find the right one from the domain it needs.

## Groups

| Group                  |  Tools | What it covers                                                                |
| ---------------------- | -----: | ----------------------------------------------------------------------------- |
| `hip3`                 |     11 | HIP-3 auctions, dexs, assets, deployers                                       |
| `hip4`                 |     10 | HIP-4 prediction markets, providers, deployers, questions, settlements, fills |
| `public`               |      8 | Keyless Hyperliquid public data — mids, metas, L2 book, candles, funding      |
| `evm`                  |      8 | HyperEVM blocks, transactions, stats                                          |
| `live`                 |      8 | Bounded-window snapshots of live WebSocket channels — fills, BBO, order books |
| `user`                 |      5 | Profiles, coin distribution                                                   |
| `stream`               |      5 | Bounded-window snapshots of indexed WebSocket channels                        |
| `analytics`            |      3 | Fills, liquidations and priority-fee statistics                               |
| `vault` / `vaults`     |      3 | Vault data                                                                    |
| `builder` / `builders` |      3 | Builder data                                                                  |
| `twaps` / `twap`       |      3 | TWAP data                                                                     |
| `fills`                |      2 | Fill search and counts                                                        |
| `market`               |      2 | 24h snapshot, daily series                                                    |
| `traders`              |      2 | Leaderboard, active traders                                                   |
| `completed`            |      2 | Completed trades and their fills                                              |
| `funding`              |      2 | Predicted and historical funding                                              |
| `liquidations`         |      1 | Liquidation data                                                              |
| **Total**              | **78** |                                                                               |

<Info>
  The `public` group exposes Hyperliquid data that is keyless upstream — but reaching the hosted MCP server still requires a HypeDexer API key. See [Authentication](/mcp/authentication).
</Info>

<Warning>
  The `live` and `stream` groups return **bounded-window snapshots**, not live pushes: MCP tools are request/response. For continuous streaming, use the WebSocket APIs directly.
</Warning>

To see the exact tool list your key can reach, call `tools/list` — see [Client configuration](/mcp/clients#any-mcp-client).

## How results are shaped

The tools are built for agents rather than for dashboards, so responses are designed to keep an agent on track instead of filling its context window.

* **Pagination is explicit.** List tools return a pagination handle with a `hint` naming the exact next call to make, so the agent can page through results without guessing.
* **Responses are truncated at a token budget.** Instead of flooding the agent's context, a large result is cut and carries a steering note explaining what was left out and how to narrow the query.
* **Errors say how to recover.** A failed call explains the fix — add a filter, top up credits, use a different key — rather than returning a bare status code. See [Errors](/mcp/errors).

## Credits

Each tool call bills credits from your account balance, exactly like a direct REST call. One tool call can fan out into several API requests, so it may cost more than a single REST call — the 24h market snapshot, for instance, calls five endpoints.