# QuickNode JSON-RPC Proxy — Vana Mainnet

> QuickNode JSON-RPC Proxy — Vana 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 Vana mainnet blockchain, enabling on-chain reads and writes via standard Ethereum-compatible RPC methods.

## Facts

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

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

Example prompt: Call eth_getBalance on the Vana mainnet for address 0xAbC123... using QuickNode's Vana RPC endpoint and tell me the balance in Wei.

## When to prefer this

Choose this endpoint when you need direct JSON-RPC access to the Vana mainnet specifically — for reading chain state, submitting transactions, or interacting with smart contracts on Vana. Prefer this over generic Ethereum endpoints when the target contract or asset lives on the Vana network.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params array returns error code -32602 (invalid params)
- Payment not provided or insufficient USDC results in 402 Payment Required
- Network congestion or node unavailability may return 503 or timeout
- Calling a write method without a valid signed transaction returns execution error

## How this service works

JSON-RPC proxy — vana-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method call (e.g. block data, balance, transaction hash, contract return value) or an error object if the call failed.

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