# QuickNode JSON-RPC Proxy — X Layer Mainnet

> QuickNode JSON-RPC Proxy — X Layer 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 X Layer (OKX) mainnet blockchain via QuickNode's node infrastructure

## Facts

- Endpoint: POST https://x402.quicknode.com/xlayer-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-6698b977
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2i3tVENRK7HyyctZ0Nwwv

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

Example prompt: What is the current block number on X Layer mainnet? Use the QuickNode JSON-RPC proxy with method eth_blockNumber and an empty params array.

## When to prefer this

Use this endpoint when you need to interact with the X Layer (XLayer) mainnet specifically — an EVM-compatible Layer 2 built by OKX. Prefer this over generic Ethereum RPC endpoints when your target contract or transaction is deployed on XLayer, not Ethereum mainnet or other L2s. QuickNode's infrastructure provides reliable, low-latency node access compared to public RPCs.

## 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 returns HTTP 402 Payment Required
- Network congestion or node unavailability returns HTTP 503 or timeout
- Calling a non-existent contract address returns empty result (0x)

## How this service works

JSON-RPC proxy — xlayer-mainnet

## Output

A JSON-RPC 2.0 response object containing the result field with the requested blockchain data (e.g. block number as hex, transaction object, call return value, balance in wei), or an error object with code and message 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-6698b977/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)