LiveRobinhood Chain now served from Frankfurt, Chicago and Singapore — a node on three continents.
sonic

Free Sonic RPC Endpoint

Chain ID 146 · S · one configured primary region

Sonic (Chain ID 146) is the high-performance EVM L1 from the former Fantom team, with sub-second blocks and near-instant finality. NodeFlare serves Sonic RPC from dedicated European bare-metal.

Public endpoint — no API key

HTTPS

https://rpc.nodeflare.app/sonic/public

Need higher limits? Use a keyed endpoint https://rpc.nodeflare.app/sonic/v1/{YOUR_KEY} — get a free key →

Connect to Sonic

curl -s -X POST https://rpc.nodeflare.app/sonic/public \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

Add Sonic to your wallet

Network details for MetaMask, Rabby, or any EVM wallet — Sonic chain ID 146 (0x92).

Network name
Sonic
RPC URL
https://rpc.nodeflare.app/sonic/public
Chain ID
146
Currency symbol
S
Block explorer
https://sonicscan.org

A wallet polls its RPC continuously. The keyless URL above allows 50 requests per 10 seconds per IP and has a daily cap per IP: enough to try the network in a wallet, but a wallet left open can reach the cap. For daily use, enter your keyed URL https://rpc.nodeflare.app/sonic/v1/{YOUR_KEY} instead. A free key allows 10 requests per second, and the dashboard adds Sonic to MetaMask with that URL in one click. Get a free key →

Built for Sonic

High-frequency DeFi and latency-sensitive apps on Sonic. Requests use configured regional preferences and available upstreams. Plan rate limits, compute units and method-specific concurrency limits apply.

Sonic node coverage and routing

A NodeFlare-operated primary node region. A public third-party RPC backstop is configured after our own nodes. Region labels describe routing configuration rather than a guarantee that every gateway has a local node. A standard API key uses shared infrastructure with its own plan limits; dedicated capacity is scoped separately. Historical state, tracing and WebSocket support vary by chain and node.

On successful HTTP RPC responses, nf-region: fallback identifies an external backstop and nf-region: cache identifies a cached response. See our routing disclosure and availability terms.

Dedicated SonicRPC node — options & SLA →

Guide: Dedicated Sonic RPC node — full method access on our own bare-metal →

Sonic RPC — FAQ

What is Sonic's chain ID?

Sonic's chain ID is 146 (hex 0x92). Its native currency is S and its block explorer is sonicscan.org. You can connect with NodeFlare's free public RPC at https://rpc.nodeflare.app/sonic/public — no API key required.

How do I add Sonic to MetaMask?

In MetaMask, open the network menu → "Add a network" → "Add a network manually", then enter — Network name: Sonic; Chain ID: 146; Currency symbol: S; Block explorer URL: https://sonicscan.org; New RPC URL: your keyed NodeFlare URL, https://rpc.nodeflare.app/sonic/v1/{YOUR_KEY}. A free key allows 10 requests per second. The keyless URL https://rpc.nodeflare.app/sonic/public is enough to try the network in a wallet: it allows 50 requests per 10 seconds per IP and has a daily cap per IP, which a wallet left open can reach.

What is the Sonic RPC URL?

NodeFlare's public Sonic RPC URL is https://rpc.nodeflare.app/sonic/public over HTTPS. No API key is required for the public endpoint.

Is the Sonic RPC free?

Yes. The public Sonic endpoint is free with no sign-up. A free API key provides higher rate limits and 3,000,000 compute units per month, no credit card. Heavy HTTP methods depend on node support and are subject to compute-unit and concurrency limits.

What are the Sonic RPC rate limits?

The public endpoint is limited to 50 requests per 10 seconds per IP. A free key gives 10 requests/second; standard paid plans scale to 1500 req/s. Every plan includes all 17 supported chains.

Is NodeFlare a good Sonic RPC provider?

NodeFlare operates its own primary Sonic nodes. A NodeFlare-operated primary node region. A public third-party RPC backstop is configured after our own nodes. A free key provides 3,000,000 CU per month and higher limits. Method support and historical coverage depend on the node and requested block.

Is there a dedicated Sonic RPC node?

A standard key gives an authenticated endpoint on shared NodeFlare infrastructure, with plan-specific limits. Dedicated capacity is scoped separately by inquiry. A NodeFlare-operated primary node region. A public third-party RPC backstop is configured after our own nodes. Historical state and traces must be checked for your specific methods and block ranges; a key does not guarantee complete archive coverage.

Go deeper

Build on Sonic with a free key

Higher limits and an authenticated endpoint — every supported chain included. No credit card.

Get your free API key →