portal_hyperliquid_query_fills
Retrieve raw Hyperliquid fill records filtered by trader, coin, direction, builder, or fee token, including PnL and builder context.
Instructions
Query raw individual Hyperliquid fills with trader, coin, fee, PnL, and builder context.
COMMON USER ASKS:
Recent BTC fills
WHEN TO USE:
You need raw fill records on Hyperliquid.
You want to filter by trader, coin, direction, builder, or fee token.
DON'T USE:
You want the big picture, top traders, grouped aggregates, or candles instead of raw fill rows.
EXAMPLES:
Recent BTC fills: {"network":"hyperliquid-fills","timeframe":"1h","coin":["BTC"],"limit":20}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dir | No | Trade direction: "Open Long", "Close Long", "Open Short", "Close Short" | |
| coin | No | Asset symbols (e.g., "ETH", "BTC", "SOL") | |
| user | No | Trader wallet addresses (0x-prefixed, lowercase) | |
| cloid | No | Client order IDs (0x-prefixed hex) | |
| limit | No | Max fills to return (default: 50, max: 200) | |
| cursor | No | Continuation cursor from a previous response | |
| builder | No | Builder addresses (0x-prefixed, lowercase) | |
| network | No | Network name (default: 'hyperliquid-fills'). Optional when continuing with cursor. | hyperliquid-fills |
| to_block | No | Ending block number | |
| fee_token | No | Fee token symbols | |
| timeframe | No | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. | |
| from_block | No | Starting block number (use this OR timeframe) | |
| include_pnl | No | Include closedPnl and startPosition fields | |
| to_timestamp | No | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | No | Only query finalized blocks | |
| from_timestamp | No | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| response_format | No | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for aggregate stats or 'full' when you truly need every fill field. | |
| include_builder_info | No | Include builder and builderFee fields |