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

Free Avalanche RPC Endpoint

Chain ID 43114 · AVAX · multiple configured routing regions

Avalanche C-Chain (Chain ID 43114) is an EVM-compatible chain with sub-second finality. NodeFlare provides multi-region Avalanche RPC for DeFi and gaming workloads.

Public endpoint — no API key

HTTPS

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

WSS

wss://rpc.nodeflare.app/avax/ws/public

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

Connect to Avalanche

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

Add Avalanche to your wallet

Network details for MetaMask, Rabby, or any EVM wallet — Avalanche chain ID 43114 (0xa86a).

Network name
Avalanche
RPC URL
https://rpc.nodeflare.app/avax/public
Chain ID
43114
Currency symbol
AVAX
Block explorer
https://snowtrace.io

A wallet polls its RPC continuously. The keyless URL above allows 1 request per 10 seconds per IP: enough to confirm the network details, too low for daily wallet use. For a wallet, enter your keyed URL https://rpc.nodeflare.app/avax/v1/{YOUR_KEY} instead. A free key allows 10 requests per second, and the dashboard adds Avalanche to MetaMask with that URL in one click. Get a free key →

Built for Avalanche

DeFi, gaming, and high-frequency apps on Avalanche C-Chain. Requests use configured regional preferences and available upstreams. Plan rate limits, compute units and method-specific concurrency limits apply.

Avalanche node coverage and routing

NodeFlare-operated primary nodes in 2 configured routing regions. 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 AvalancheRPC node — options & SLA →

Avalanche RPC — FAQ

What is Avalanche's chain ID?

Avalanche's chain ID is 43114 (hex 0xa86a). Its native currency is AVAX and its block explorer is snowtrace.io. You can connect with NodeFlare's free public RPC at https://rpc.nodeflare.app/avax/public — no API key required.

How do I add Avalanche to MetaMask?

In MetaMask, open the network menu → "Add a network" → "Add a network manually", then enter — Network name: Avalanche; Chain ID: 43114; Currency symbol: AVAX; Block explorer URL: https://snowtrace.io; New RPC URL: your keyed NodeFlare URL, https://rpc.nodeflare.app/avax/v1/{YOUR_KEY}. A free key allows 10 requests per second. The keyless URL https://rpc.nodeflare.app/avax/public answers a test call, but it allows 1 request per 10 seconds per IP, which is too low for a wallet that polls the network continuously.

What is the Avalanche RPC URL?

NodeFlare's public Avalanche RPC URL is https://rpc.nodeflare.app/avax/public over HTTPS and wss://rpc.nodeflare.app/avax/ws/public over WSS. No API key is required for the public endpoint.

Is the Avalanche RPC free?

Yes. The public Avalanche 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 Avalanche RPC rate limits?

The public endpoint is limited to 1 request 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 Avalanche RPC provider?

NodeFlare operates its own primary Avalanche nodes. NodeFlare-operated primary nodes in 2 configured routing regions. 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 Avalanche RPC node?

A standard key gives an authenticated endpoint on shared NodeFlare infrastructure, with plan-specific limits. Dedicated capacity is scoped separately by inquiry. NodeFlare-operated primary nodes in 2 configured routing regions. 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 Avalanche with a free key

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

Get your free API key →