Hyperliquid module
Reference for the Hyperliquid intelligence module — what it provides, where it shows up in Axe, and how to wire it.
The Hyperliquid intelligence module — codename HLQ — is the search and provenance layer that powers Axe's Hyperliquid surface. It is not a separate product; it is the module Axe uses when it needs to reason over historical Hyperliquid state.
This page is a reference for operators and integrators who need to know what the module exposes and how to wire it.
What the module provides
- Replayable search over historical Hyperliquid state
- Provenance-oriented result assembly — every claim has a source, a timestamp, and a hash
- CLI and MCP integration points so the cockpit, agents, and external tools can all read it
- A backend contract that runs locally by default and remotely via
HLQ_BACKEND_URL - A web preview surface at
/searchon the landing page
Where it shows up in Axe
| Surface | Module role |
|---|---|
| Cockpit research rail | Background search for session framing and post-mortems |
| Cockpit markets rail | Provenance attached to historical reads (funding regimes, OI curves, basis history) |
| Watches | Historical context for tripwire calibration |
| Runbooks | Replay-grounded patterns operators ship to the protocol |
Backend contract
The module is reachable two ways:
The contract is documented in detail under Search harness, Bridge, and CLI reference.
Why it has its own name
The module is large enough — its own search harness, its own bridge artifacts, its own MCP server, its own provenance schema — that giving it an internal codename keeps the technical surface manageable. From an operator's seat in the Axe cockpit, you should rarely need to think about it as separate. From an integrator's seat, the module name is how you find the right docs.
The Polymarket module follows the same pattern: a peer module with its own internal name, surfaced through the cockpit as part of the unified market layer.