Hyperliquid

Five tools front Allium’s Hyperliquid proxy. They mirror Hyperliquid’s own info API surface but run through Allium’s infrastructure, so you aren’t subject to Hyperliquid’s per-IP rate limits.

Available tools

Tool	Description
`realtime_info`	Account, market, and exchange information by request `type`
`realtime_fills`	Fills for a user address
`realtime_order_history`	Order history for a user address
`realtime_order_status`	Status of one order by `oid`
`realtime_orderbook_snapshot`	Complete orderbook snapshot for all pairs

These tools carry the realtime_ prefix because they share the Realtime API surface, but they only cover Hyperliquid. For Hyperliquid’s on-chain historical data, query the Hyperliquid schemas with SQL instead.

The general-purpose tool

realtime_info is the catch-all: type selects which Hyperliquid info request to make, and the other fields depend on that type.

{
  "name": "realtime_info",
  "arguments": {
    "type": "clearinghouseState",
    "user": "0x0000000000000000000000000000000000000000"
  }
}

Before using it, read the full list of supported request types:

{
  "name": "browse_docs",
  "arguments": { "path": "api/developer/hyperliquid/info.md" }
}

The specialized tools

Three tools cover the request types you’ll reach for most, with explicit schemas.

Fills
Order history
Order status

{
  "name": "realtime_fills",
  "arguments": {
    "type": "userFillsByTime",
    "user": "0x0000000000000000000000000000000000000000",
    "startTime": 1767225600000,
    "endTime": 1769904000000,
    "aggregateByTime": true
  }
}

type and user are required. Timestamps are Hyperliquid-style epoch milliseconds.startTime and endTime only apply when type is userFillsByTime — with type: "userFills" they’re ignored. aggregateByTime and twapMode apply to both.

{
  "name": "realtime_order_history",
  "arguments": {
    "type": "historicalOrders",
    "user": "0x0000000000000000000000000000000000000000",
    "startTime": 1767225600000
  }
}

{
  "name": "realtime_order_status",
  "arguments": {
    "type": "orderStatus",
    "user": "0x0000000000000000000000000000000000000000",
    "oid": 123456789
  }
}

All three fields are required.

Orderbook snapshot

Takes no arguments and returns every pair at once.

{ "name": "realtime_orderbook_snapshot", "arguments": {} }

This is a full snapshot across all pairs and can be large. Have your agent filter to the pairs it needs rather than holding the whole payload in context.

Documentation paths

Each tool’s description carries its browse_docs path — the authoritative reference for parameters and response shape.

Tool	Docs path
`realtime_info`	`api/developer/hyperliquid/info.md`
`realtime_fills`	`api/developer/hyperliquid/fills.md`
`realtime_order_history`	`api/developer/hyperliquid/order-history.md`
`realtime_order_status`	`api/developer/hyperliquid/order-status.md`
`realtime_orderbook_snapshot`	`api/developer/hyperliquid/orderbook-snapshot.md`

Hyperliquid API

The REST endpoints behind these tools

Hyperliquid data

Historical Hyperliquid schemas for SQL

Realtime data

Prices, balances, holdings, and tokens

Billing & limits

These tools consume Developer Units

Assistant

MCP

Machine Payments

Available tools

The general-purpose tool

The specialized tools

Orderbook snapshot

Documentation paths

Hyperliquid API

Hyperliquid data

Realtime data

Billing & limits

​Available tools

​The general-purpose tool

​The specialized tools

​Orderbook snapshot

​Documentation paths

​Related resources

Hyperliquid API

Hyperliquid data

Realtime data

Billing & limits

Available tools

The general-purpose tool

The specialized tools

Orderbook snapshot

Documentation paths

Related resources