# QuickNode JSON-RPC Proxy (Multi-Network)

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

Provides paid JSON-RPC access to a specified blockchain network via QuickNode, accepting standard Ethereum-compatible and network-specific RPC method calls.

## Facts

- Endpoint: POST https://x402.quicknode.com/%7Bnetwork%7D
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-quicknode-com-0ab17b50
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rsCN0yw6Yt16d-YhSIFCh

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 x402-quicknode-com-0ab17b50 -d '<json body>'
```

Example prompt: Call eth_blockNumber on the Ethereum mainnet QuickNode RPC endpoint — use jsonrpc 2.0 with id 1 and no params — and tell me the latest block number.

## When to prefer this

Choose this endpoint when you need reliable, low-latency JSON-RPC access to a specific blockchain network and want a pay-per-call model without committing to a subscription. Especially useful for agents that need to query multiple different blockchains (Ethereum, LTC, NEAR, Cosmos, etc.) via a single unified interface. Prefer over free public nodes when reliability and uptime guarantees matter.

## Known failure modes

- Unsupported network identifier in URL path returns 404 or routing error
- Invalid JSON-RPC method name returns JSON-RPC error code -32601 (method not found)
- Malformed params array causes JSON-RPC error -32602 (invalid params)
- Payment not provided or insufficient USDC results in HTTP 402 rejection
- Rate limit exceeded returns 429 too many requests
- Network-specific method called on wrong network returns unsupported method error

## How this service works

Paid blockchain RPC access for the selected network via QuickNode.

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested blockchain method call, which may include block data, transaction details, contract return values, account balances, or other network state depending on the method invoked.

## 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/x402-quicknode-com-0ab17b50/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)