# QuickNode JSON-RPC Proxy — Hyperliquid Mainnet

> QuickNode JSON-RPC Proxy — Hyperliquid 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-14).

Proxies JSON-RPC calls to the Hyperliquid (hype) mainnet blockchain via QuickNode's infrastructure, enabling on-chain reads and writes.

## Facts

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

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-728527cc -d '<json body>'
```

Example prompt: Can you check the latest block number on Hyperliquid mainnet using a QuickNode JSON-RPC call with method eth_blockNumber and empty params?

## When to prefer this

Use this endpoint when you specifically need to interact with the Hyperliquid (hype) mainnet blockchain via a reliable, paid QuickNode RPC node. Prefer this over free public RPC endpoints when you need reliability, higher rate limits, and low latency for production workloads on Hyperliquid.

## Known failure modes

- Invalid JSON-RPC method name returns error object with code -32601
- Malformed params array causes -32602 invalid params error
- Payment not provided or insufficient results in 402 Payment Required
- Network congestion or node unavailability causes timeout or 503
- Unsupported method for Hyperliquid chain returns error

## How this service works

JSON-RPC proxy — hype-mainnet

## Output

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

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "jsonrpc",
  "method"
 ],
 "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"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "error": {
   "type": "object",
   "properties": {
    "code": {
     "type": "integer"
    },
    "message": {
     "type": "string"
    }
   }
  },
  "result": {
   "description": "RPC result (type varies by method)"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quicknode-728527cc/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)