# QuickNode JSON-RPC Proxy — Hyperliquid (hype-mainnet)

> QuickNode JSON-RPC Proxy — Hyperliquid (hype-mainnet) is a paid API for AI agents from x402.quicknode.com, paid per call via x402, $10/call, status unknown (last checked 2026-09-15).

Provides paid JSON-RPC access to the Hyperliquid mainnet blockchain via QuickNode's infrastructure, accepting per-request micropayments via x402.

## Facts

- Endpoint: POST https://x402.quicknode.com/hype-mainnet/hypercore
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-6afe8841
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BDf2FR_Pnmgm3a3qlT0GO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability quicknode-6afe8841 -d '<json body>'
```

Example prompt: Call eth_blockNumber on the Hyperliquid mainnet using QuickNode's x402 RPC endpoint and tell me the current block height.

## When to prefer this

Choose this endpoint when you need programmatic, pay-per-request RPC access to the Hyperliquid mainnet without managing a dedicated node or long-term subscription. Ideal for agents that make sporadic or bursty blockchain queries and want micropayment billing via x402 protocol.

## Known failure modes

- Payment insufficient or not provided — 402 Payment Required
- Invalid JSON-RPC method name — method not found error
- Malformed params array — invalid params error
- Network congestion or node unavailability — 503 or timeout
- Unsupported method for Hyperliquid network — method not supported error
- Expired or invalid SIWX credentials — 401 Unauthorized

## How this service works

Payment for Quicknode RPC access. Options: per-request ($0.001/request), nanopayment ($0.0001/request via Circle Gateway), or credit drawdown with SIWX authentication.

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method call (e.g. block data, transaction receipt, contract return value) or an error object if the call failed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ],
   "description": "Request identifier"
  },
  "method": {
   "type": "string",
   "description": "JSON-RPC method name (e.g., eth_blockNumber, eth_call)"
  },
  "params": {
   "type": "array",
   "description": "Method parameters"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quicknode-6afe8841/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.quicknode.com](https://www.zero.xyz/host/x402.quicknode.com/llms.txt)