# QuickNode JSON-RPC Proxy — 0G Mainnet

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

## Facts

- Endpoint: POST https://x402.quicknode.com/0g-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-2c272e7a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fFGcSwkY8Zd5hTA-FzAlR

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

Example prompt: Call eth_blockNumber on the 0G mainnet to get the latest block number — use JSON-RPC 2.0 with request ID 1 and no params.

## When to prefer this

Use this endpoint when you need to interact specifically with the 0G (zero-gravity) mainnet blockchain via standard JSON-RPC 2.0 calls. Prefer this over generic Ethereum-compatible endpoints when the target contract or data lives on the 0G network. QuickNode's infrastructure provides reliable, low-latency node access without managing your own node.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601 (method not found)
- Malformed params array causes -32602 (invalid params)
- Payment not included or insufficient returns HTTP 402
- Network congestion or node unavailability causes timeout or HTTP 503
- Unsupported method for 0G chain returns error response

## How this service works

JSON-RPC proxy — 0g-mainnet

## Output

A standard JSON-RPC 2.0 response object containing the result of the requested method call (e.g. block number, transaction receipt, contract return value) 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-2c272e7a/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)