# QuickNode JSON-RPC Proxy — zkEVM Mainnet

> QuickNode JSON-RPC Proxy — zkEVM Mainnet 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 Polygon zkEVM mainnet blockchain network via QuickNode's infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/zkevm-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/quicknode-2a4ead9a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_La9onzTn_iVAyPzVpsop4

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

Example prompt: Call eth_getBalance on zkEVM mainnet for address 0xAbCd1234... at the latest block — use QuickNode's zkEVM mainnet JSON-RPC endpoint.

## When to prefer this

Choose this endpoint when you need to interact specifically with the Polygon zkEVM mainnet — reading contract state, fetching balances, submitting transactions, or querying blocks on that L2 network. Prefer this over generic Ethereum endpoints when your target contract or address is deployed on zkEVM mainnet rather than Ethereum L1 or other L2s.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 method not found
- Malformed params array returns error -32602 invalid params
- Network congestion or node unavailability returns HTTP 503 or timeout
- Unsupported method for zkEVM returns error indicating method not supported
- Payment failure or insufficient USDC balance results in HTTP 402 before request is processed

## How this service works

JSON-RPC proxy — zkevm-mainnet

## Output

A JSON-RPC 2.0 response object containing the result field with the requested blockchain data (e.g. balance in hex wei, block object, transaction receipt, contract return value) or an error object with code and message if the call fails.

## 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-2a4ead9a/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)