# QuickNode JSON-RPC Proxy — Arbitrum Nova Mainnet

> QuickNode JSON-RPC Proxy — Arbitrum Nova 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-15).

Proxies JSON-RPC calls to the Arbitrum Nova mainnet blockchain network via QuickNode's infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/nova-mainnet/
- Price: $10/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quicknode-9ea564e2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yiDhZc1CSp27KuXLbmd-c

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

Example prompt: What's the current block number on Arbitrum Nova mainnet? Call eth_blockNumber with jsonrpc 2.0 and request id 1.

## When to prefer this

Choose this endpoint when you need to interact specifically with the Arbitrum Nova mainnet blockchain — querying state, calling contracts, or broadcasting transactions — and require a reliable, high-availability RPC node without managing your own infrastructure. Prefer this over generic Ethereum RPC endpoints when your target contracts or assets are specifically deployed on Arbitrum Nova (not Arbitrum One or other L2s).

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 Method not found
- Malformed params array returns error code -32602 Invalid params
- Network congestion may cause timeout or increased latency
- Payment of $10 USDC required per call; insufficient funds results in 402 Payment Required
- Unsupported method on Nova network returns error
- Invalid transaction data on eth_sendRawTransaction returns execution error

## How this service works

JSON-RPC proxy — nova-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number as hex, transaction object, account balance in wei, smart contract return data) or an error object 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-9ea564e2/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)