# QuickNode Ethereum Mainnet JSON-RPC Proxy

> QuickNode Ethereum Mainnet JSON-RPC Proxy 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 Ethereum mainnet via QuickNode's infrastructure, billed per call via x402 micropayments

## Facts

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

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

Example prompt: Use QuickNode to call eth_blockNumber on Ethereum mainnet so I can see what the latest block is right now.

## When to prefer this

Use this endpoint when you need reliable, low-latency access to Ethereum mainnet JSON-RPC without managing your own node, and are comfortable paying per-call via x402 USDC micropayments. Prefer it over self-hosted nodes for on-demand agent workloads, and over free public RPCs when uptime and rate limits matter.

## Known failure modes

- Invalid JSON-RPC method name returns an error object with code -32601
- Malformed params array causes -32602 invalid params error
- Insufficient x402 payment credits results in 402 Payment Required response
- Network congestion or node unavailability may cause timeout or 503 error
- Calling a method not supported by Ethereum mainnet returns -32000 server error

## How this service works

Payment for credits to access Quicknode Core API

## Output

A JSON-RPC 2.0 response object containing the result of the requested Ethereum method call — e.g. block number as a hex string, account balance in wei, transaction receipt object, or smart contract return data — along with the matching 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/x402-quicknode-com-b2c32a89/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)