Back to Browse
Laevitas Hyperliquid Node Fills
x402
Laevitas Hyperliquid Node Fills is a paid API for AI agents from apiv2.laevitas.ch, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).
Retrieves trade fill records from the Hyperliquid node, filterable by wallet, instrument, market type, time range, and notional size.
Price / call$0.1
Success—
StatusUnknown
How this service works
Professional market data API for crypto derivatives, spot markets, prediction markets, Hyperliquid HyperCore data, proprietary volatility surfaces, and analytics. ## Authentication Use an API key for authenticated REST requests: ```http X-API-Key: your-api-key-here ``` Most data endpoints also support x402 pay-per-request without an API key. | Resource | Path | | --- | --- | | OpenAPI JSON | `GET /openapi.json` | | x402 discovery | `GET /.well-known/x402` | | Changelog | `GET /api/v1/changelog` | | WebSocket docs | `GET /websocket` | ## REST Surfaces | Surface | Examples | | --- | --- | | Instruments | Cross-market contract reference data | | Futures | OHLCVT, trades, tickers, orderbook, liquidations, carry | | Perpetuals | OHLCVT, trades, funding, open interest, orderbook, liquidations | | Options | OHLCVT, trades, Greeks, volatility, flow, dealer GEX | | Vol Surface | Proprietary surface snapshots, slices, strikes, term structure, risk | | Spot | OHLCVT, ticker, trades, volume, L2 orderbook, snapshots | | Predictions | Polymarket instruments, categories, trades, ticker history | | Hyperliquid - HyperCore | Node-derived fills, liquidations, positions, funding, TWAPs, resting orders, L2 books | | Analytics | Realized volatility and derived metrics | ## Pagination Paginated endpoints return the cursor at `meta.next_cursor`. Pass that value back as the `cursor` query parameter to fetch the next page. ## WebSocket Streaming Real-time streams are documented at `/websocket`. | Data | Channel pattern | | --- | --- | | Trades | `trades.{market}.{exchange}.{instrument}` | | OHLC ticker | `ohlc.ticker.{market}.{exchange}.{instrument}.{timeframe}` | | OHLCVT | `ohlc.vt.{market}.{exchange}.{instrument}.{timeframe}` | Variables: `market` is one of `perpetuals`, `futures`, `options`, or `spot`; `timeframe` is one of `1m`, `5m`, `15m`, `1h`, `4h`, or `1d`. ## Quick Start ```bash curl "https://apiv2.laevitas.ch/api/v1/futures/ohlcvt?exchange=deribit&instrument_name=BTC-PERPETUAL" \ -H "X-API-Key: your-api-key-here" ```
Output
Returns a JSON object with a success flag and a data array containing fill records for the queried wallet and filters. Each fill includes trade details such as timestamps, notional values (buy, sell, net), realized PnL, and trade count, depending on the applied resolution and sort order.
Example use cases
Track whale wallet trading activity
“Give me the recent Hyperliquid perpetual fills for wallet 0x742d35Cc6634C0532925a3b844Bc57e94f4e0bC6, sorted by notional size descending, so I can see what this whale is trading and at what scale.”
Monitor Hyperliquid prediction market fills
“Show me all the Hyperliquid prediction market fills from the last week for wallet 0x8ba1f109551bD432803012645Ac136ddd64DBA72, filtered to only trades above $500, so I can analyze their prediction market strategy.”
Analyze realized PnL across instruments
“Pull Hyperliquid spot and perpetual fills for my wallet over the past month, filter by trades over $2000 notional, and sort by realized PnL so I can see which instruments are actually profitable for me.”
Technical details
Endpoint
GEThttps://apiv2.laevitas.ch/api/v1/hyperliquid/node/fillsWhen to prefer
Use this endpoint when you need granular on-chain trade fill data specifically from the Hyperliquid node (HyperCore), including support for perp_hip3 and prediction market types. Prefer this over generic exchange fill endpoints when the user is tracking a specific wallet's trading activity, PnL, or flow on Hyperliquid's decentralized infrastructure.
Side effects
- Missing required wallet parameter returns empty data array
- Invalid market_type enum value causes request rejection
- limit exceeding 1000 returns validation error
- Invalid time range format for start/end causes parsing failure
- Unauthorized request without valid API key or x402 payment returns 402 or 401 error
- Unknown instrument_name returns empty data with success:true
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"data": [],
"success": true
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"