# QuickNode JSON-RPC Proxy — Hype Testnet

> QuickNode JSON-RPC Proxy — Hype Testnet 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 Hype blockchain testnet, enabling read and write interactions with smart contracts, accounts, and blockchain state.

## Facts

- Endpoint: POST https://x402.quicknode.com/hype-testnet/
- 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-d8af70e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-wiCSMNpGgPeNxgnzlkDX

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

Example prompt: Call eth_blockNumber on the Hype testnet using QuickNode's JSON-RPC proxy so I can see the current block height.

## When to prefer this

Use this endpoint when you need to interact specifically with the Hype testnet blockchain via JSON-RPC — for example, to test smart contracts, query testnet state, or simulate transactions before mainnet deployment. Prefer this over generic RPC providers if you need QuickNode's reliable infrastructure and are already using x402 payment flow.

## Known failure modes

- Invalid JSON-RPC method returns error code -32601 method not found
- Malformed params array returns error code -32602 invalid params
- Payment not included or insufficient returns 402 Payment Required
- Network congestion or node unavailability returns 503 or timeout
- Unsupported method for Hype testnet returns method not supported error

## How this service works

JSON-RPC proxy — hype-testnet

## Output

A standard JSON-RPC 2.0 response object containing the result field with blockchain data (e.g. block number, balance in hex, transaction receipt, contract return value) or an error object with code and message 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-d8af70e7/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)