# Pocket Network – Hyperliquid HyperEVM JSON-RPC

> Pocket Network – Hyperliquid HyperEVM JSON-RPC is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Provides read-only Ethereum-compatible JSON-RPC access to the Hyperliquid HyperEVM blockchain via Pocket Network's decentralised node supplier set, paid per-request in USDC.

## Facts

- Endpoint: POST https://agent.pocket.network/v1/hyperliquid?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pocket-network-hyperliquid-hyperevm-json-rpc-2db80047
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CSOE4ZcVZHvD0YordEkQk

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 pocket-network-hyperliquid-hyperevm-json-rpc-2db80047 -d '<json body>'
```

Example prompt: What's the current ETH balance of wallet 0xAbC...123 on Hyperliquid HyperEVM? Use eth_getBalance and give me the result in wei.

## When to prefer this

Choose this endpoint when you need decentralised, censorship-resistant read access to the Hyperliquid HyperEVM chain without an API key or account setup, and you are willing to pay micro-amounts per request in USDC. Prefer it over centralised RPC providers when trust-minimisation or Pocket Network's multi-node redundancy matters. Use it for any standard eth_* or debug_* read query against HyperEVM.

## Known failure modes

- Invalid or unsupported JSON-RPC method returns a JSON-RPC error with code -32601
- Malformed params cause a -32602 invalid params error
- Block or transaction not found returns null result
- Insufficient USDC payment triggers a 402 Payment Required response
- Network congestion or node unavailability may cause timeouts or 503 errors
- Write methods (eth_sendRawTransaction) are rejected as this is a read-only endpoint

## How this service works

Pay-per-call access to Pocket Network services. No account, no API key.

## Output

A standard Ethereum JSON-RPC response object containing the `result` field with the requested on-chain data (balance, block, transaction, receipt, logs, gas estimate, etc.) or a JSON-RPC `error` object if the call fails. Responses match the Ethereum JSON-RPC specification applied to the HyperEVM chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "examples": [
    "debug_getBadBlocks",
    "debug_getRawBlock",
    "debug_getRawHeader",
    "debug_getRawReceipts",
    "debug_getRawTransaction",
    "eth_accounts",
    "eth_blobBaseFee",
    "eth_blockNumber",
    "eth_call",
    "eth_chainId",
    "eth_coinbase",
    "eth_createAccessList",
    "eth_estimateGas",
    "eth_feeHistory",
    "eth_gasPrice",
    "eth_getBalance",
    "eth_getBlockByHash",
    "eth_getBlockByNumber",
    "eth_getBlockReceipts",
    "eth_getBlockTransactionCountByHash",
    "eth_getBlockTransactionCountByNumber",
    "eth_getCode",
    "eth_getFilterChanges",
    "eth_getFilterLogs",
    "eth_getLogs",
    "eth_getStorageAt",
    "eth_getTransactionByBlockHashAndIndex",
    "eth_getTransactionByBlockNumberAndIndex",
    "eth_getTransactionByHash",
    "eth_getTransactionCount",
    "eth_getTransactionReceipt",
    "eth_getUncleByBlockHashAndIndex",
    "eth_getUncleByBlockNumberAndIndex",
    "eth_getUncleCountByBlockHash",
    "eth_getUncleCountByBlockNumber",
    "eth_maxPriorityFeePerGas",
    "eth_newBlockFilter",
    "eth_newFilter",
    "eth_newPendingTransactionFilter",
    "eth_simulateV1",
    "eth_syncing",
    "eth_uninstallFilter",
    "net_listening",
    "net_peerCount",
    "net_version",
    "web3_clientVersion",
    "web3_sha3"
   ],
   "description": "JSON-RPC read method, e.g. eth_getBalance"
  },
  "params": {
   "description": "Parameters per the Ethereum JSON-RPC spec"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": 1,
   "result": false,
   "jsonrpc": "2.0"
  },
  "portal": {
   "serviceId": "hyperliquid",
   "provenance": "third-party-supplier",
   "schemaCheck": "passed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pocket-network-hyperliquid-hyperevm-json-rpc-2db80047/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.pocket.network](https://www.zero.xyz/host/agent.pocket.network/llms.txt)
