# NodeFlare Sonic RPC (Chain 146)

> NodeFlare Sonic RPC (Chain 146) is a paid API for AI agents from rpc.nodeflare.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Provides full JSON-RPC access to the Sonic EVM chain (chain ID 146) including archive, trace, and debug methods, paid per-request in USDC via x402.

## Facts

- Endpoint: POST https://rpc.nodeflare.app/sonic/x402
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nodeflare-sonic-rpc-chain-146-de4efb2f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c0STraZmOLHu6gnjV6gQV

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 nodeflare-sonic-rpc-chain-146-de4efb2f -d '<json body>'
```

Example prompt: Call eth_getLogs on the Sonic chain (chain 146) to fetch all Transfer events from contract 0xABC...123 between blocks 1000000 and 1001000 — pay per request, no API key needed.

## When to prefer this

Choose this endpoint when you need permissionless, no-account-required RPC access to the Sonic EVM chain (chain 146) and want to pay only for what you use in USDC. Especially valuable for AI agents that need archive data, eth_getLogs for event indexing, trace/debug methods for simulation, or automated workflows where managing API keys is impractical. Prefer over free public RPCs when reliability, archive depth, or heavy query volume matters.

## Known failure modes

- Insufficient USDC balance causes payment failure and request rejection
- Invalid JSON-RPC method name returns error code -32601
- Malformed params array returns error code -32602
- Block range too large for eth_getLogs may be rejected or timed out
- Requesting non-existent transaction hash returns null result
- Network congestion on Sonic chain may increase latency

## How this service works

Sonic RPC (chain 146): JSON-RPC over HTTPS on NodeFlare's own bare-metal nodes. Pay per request in USDC, no account or API key - built for AI agents. All methods including eth_getLogs, eth_call, trace, and debug (archive) - good for indexing, event queries, and simulation. Simple calls $0.001; heavy calls priced by compute units. One of the first independent x402 RPC providers for this chain.

## Output

Standard JSON-RPC 2.0 response object containing either a 'result' field with the requested data (block info, logs, call return value, trace, etc.) or an 'error' field with code and message. Archive and debug methods return full historical state and execution traces respectively.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": [
    "number",
    "string"
   ]
  },
  "method": {
   "type": "string"
  },
  "params": {
   "type": "array"
  },
  "jsonrpc": {
   "type": "string",
   "const": "2.0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nodeflare-sonic-rpc-chain-146-de4efb2f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rpc.nodeflare.app](https://www.zero.xyz/host/rpc.nodeflare.app/llms.txt)