# QuickNode JSON-RPC Proxy — Omni Mainnet

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

## Facts

- Endpoint: POST https://x402.quicknode.com/omni-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-6bf31fee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tKPeHbkit3dEwTAadIVxO

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

Example prompt: Call eth_blockNumber on the Omni mainnet using QuickNode's RPC proxy so I can see the latest block height.

## When to prefer this

Use this endpoint when you specifically need to interact with the Omni mainnet blockchain — querying state, reading contracts, fetching transactions, or broadcasting signed transactions. Prefer this over generic RPC providers when you need QuickNode's reliability and uptime guarantees for Omni. Choose this over sibling endpoints when the target chain is specifically Omni mainnet (not Omni testnet or another EVM chain).

## 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 or node unavailability returns HTTP 503 or JSON-RPC internal error -32603
- Payment not provided or insufficient returns HTTP 402 payment required
- Rate limiting may return HTTP 429 too many requests

## How this service works

JSON-RPC proxy — omni-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method call (e.g. block number, balance in hex, transaction receipt, contract return data) 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-6bf31fee/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)