/api/v1/hyperliquid/node/wallet-flow
GET /api/v1/hyperliquid/node/wallet-flow is an endpoint of the Laevitas API V2 API, listed on Proxygate by Laevitas. HyperCore Wallet Flow AI agents call it per request through a transparent proxy and pay $0.0010 per request in USDC on Solana, with no subscription and no API key to manage.
$0.0010 / request
GET
USDC on Solana
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| end | string | No | End date in ISO 8601 format (UTC) |
| limit | number | No | Maximum number of records to return (1-1000) |
| start | string | No | Start date in ISO 8601 format (UTC). Defaults to 24 hours ago when omitted. |
| cursor | string | No | Pagination cursor for fetching the next page of results. Use the value returned in meta.next_cursor from the previous response. |
| wallet | string | No | Wallet address. |
| currency | string | No | Base currency (e.g. BTC, NVDA, BASED). |
| sort_dir | string | No | Sort direction by event time. Defaults to DESC for node history endpoints. |
| resolution | string | No | Aggregation resolution. Source table is 1-minute wallet flow. |
| market_type | string | No | Hyperliquid node market type. |
| instrument_name | string | No | Normalized instrument name (e.g. BTC-USD, xyz:NVDA-USD, BASED_USDC). |
| instrument_name_raw | string | No | Raw Hyperliquid node coin (e.g. BTC, xyz:NVDA, @305, #40). |
Call /api/v1/hyperliquid/node/wallet-flow with an AI agent
# Call this endpoint with the Proxygate CLI
proxygate proxy laevitas-api-v2 /api/v1/hyperliquid/node/wallet-flow -X GET// Call it from an AI agent over the Proxygate MCP server
call_api({
listing_id: "6df653d9-425e-44f8-81af-1f71681b2e84",
method: "GET",
path: "/api/v1/hyperliquid/node/wallet-flow"
})Laevitas API V2 /api/v1/hyperliquid/node/wallet-flow: frequently asked questions
HyperCore Wallet Flow
It costs $0.0010 per request, settled in USDC on Solana. There is no subscription and no monthly minimum: an agent pays per call from a single prepaid balance.
The agent calls GET /api/v1/hyperliquid/node/wallet-flow through the Proxygate gateway with the Proxygate CLI, SDK, or MCP server. Proxygate routes the request to the upstream provider, injects the provider key server-side, and returns the response with a signed receipt.
No. The upstream provider key never leaves the Proxygate gateway. Your agent authenticates once to Proxygate; the key is injected server-side per request and is never shared with or exposed to the agent.