# QuickNode JSON-RPC Proxy — Kaia Mainnet

> QuickNode JSON-RPC Proxy — Kaia 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 Kaia blockchain mainnet, enabling queries and interactions with the Kaia network via standard JSON-RPC 2.0 methods.

## Facts

- Endpoint: POST https://x402.quicknode.com/kaia-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-9b40501f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e5YZ4_jiPaP2Za__UKjhA

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

Example prompt: What's the current block number on the Kaia mainnet? Use the eth_blockNumber JSON-RPC method to look it up.

## When to prefer this

Use this endpoint when you need to interact specifically with the Kaia mainnet blockchain via JSON-RPC — e.g., reading on-chain state, submitting transactions, or calling smart contracts on Kaia. Prefer this over generic Ethereum endpoints when the target chain is Kaia. Use the sibling kaia-kairos endpoint for testnet operations.

## Known failure modes

- Invalid JSON-RPC method name returns an error response with code -32601
- Malformed params array causes a -32602 invalid params error
- Network congestion or node unavailability may return a timeout or -32603 internal error
- Payment failure (insufficient USDC) results in 402 Payment Required before the call is processed
- Unsupported method for Kaia chain returns method not found error

## How this service works

JSON-RPC proxy — kaia-mainnet

## Output

A JSON-RPC 2.0 response object containing the result of the requested method call — such as block data, transaction receipts, account balances, smart contract return values, or network state — along with the original request ID and jsonrpc version field.

## 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-9b40501f/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)