# QuickNode JSON-RPC Proxy — Sophon Mainnet

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

## Facts

- Endpoint: POST https://x402.quicknode.com/sophon-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-09469f81
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9FG_a8XP52ydfM7_z_Ams

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

Example prompt: Call eth_blockNumber on the Sophon mainnet blockchain and tell me the current block height.

## When to prefer this

Use this endpoint when you need to interact specifically with the Sophon mainnet blockchain via JSON-RPC — reading chain state, calling contracts, fetching transactions, or broadcasting signed transactions. Prefer this over other QuickNode chain endpoints when your target network is Sophon mainnet specifically.

## 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 results in HTTP 402 payment required
- Network congestion or node unavailability returns HTTP 503 or timeout
- Unsupported method for Sophon chain returns RPC error

## How this service works

JSON-RPC proxy — sophon-mainnet

## Output

Returns a standard JSON-RPC 2.0 response object containing the result of the requested method (e.g. block number, transaction data, contract call output) or an error object with code and message if the call fails.

## 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-09469f81/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)