# QuickNode JSON-RPC Proxy — Ethereum Hoodi Testnet

> QuickNode JSON-RPC Proxy — Ethereum Hoodi 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).

Forwards JSON-RPC calls to the Ethereum Hoodi testnet via QuickNode's infrastructure, enabling blockchain reads and writes on that network.

## Facts

- Endpoint: POST https://x402.quicknode.com/ethereum-hoodi/
- 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-abc6e431
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-7bKC0qolHQdUXFM-Z_Th

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

Example prompt: Call eth_blockNumber on the Ethereum Hoodi testnet using QuickNode's RPC proxy and tell me the current block height.

## When to prefer this

Use this endpoint when you need to interact specifically with the Ethereum Hoodi testnet via a reliable, managed QuickNode RPC node. Prefer this over self-hosted nodes for guaranteed uptime, and over other testnets (Sepolia, etc.) when your contract or scenario requires Hoodi specifically. The x402 payment model makes it suitable for pay-per-call agent workflows without subscription management.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601
- Malformed params array causes -32602 invalid params error
- Network or node unavailability returns HTTP 503 or JSON-RPC internal error -32603
- Payment failure (insufficient USDC) blocks the request with HTTP 402
- Requesting Hoodi-specific data that doesn't exist returns null result
- Rate limiting may return HTTP 429 if quota exceeded

## How this service works

JSON-RPC proxy — ethereum-hoodi

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested Ethereum method call on the Hoodi testnet — e.g. block number as hex, transaction object, balance in wei, or contract return data — along with the original request ID.

## 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-abc6e431/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)