# QuickNode JSON-RPC Proxy — Sonic Mainnet

> QuickNode JSON-RPC Proxy — Sonic 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 Sonic blockchain mainnet, enabling agents to query chain state, send transactions, and interact with smart contracts via standard Ethereum-compatible RPC methods.

## Facts

- Endpoint: POST https://x402.quicknode.com/sonic-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-d53d960f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iHfFAv5QhoeNKTt9p9kX8

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

Example prompt: What is the current block number on Sonic mainnet? Use the eth_blockNumber JSON-RPC method with no params and request ID 1.

## When to prefer this

Choose this endpoint when you need reliable, low-latency access to the Sonic mainnet blockchain via standard Ethereum-compatible JSON-RPC methods, especially when you want a pay-per-call model via x402 without managing API key subscriptions. Prefer over self-hosted nodes when infrastructure management is undesirable.

## 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 attached or insufficient USDC returns 402 Payment Required
- Network congestion may cause timeout on slow or pending transactions
- Calling non-existent contract address returns empty result rather than an error

## How this service works

JSON-RPC proxy — sonic-mainnet

## Output

A standard 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, or account balance), or an error object if the method failed or params were invalid.

## 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-d53d960f/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)