LiveRobinhood Chain now served from Frankfurt, Chicago and Singapore — a node on three continents.
All posts
·5 min read·NodeFlare Team

How to Add a Custom RPC Endpoint to MetaMask

Step-by-step guide to adding a custom RPC to MetaMask for Ethereum, Base, Arbitrum, Optimism, BNB Chain, HyperEVM, and Avalanche, with network details and the right NodeFlare URL for wallet use.

ℹ

Plan allowance update, 2 October 2026: NodeFlare monthly CU bundles increased by 50%. See current pricing and dated provider comparisons.

MetaMask ships with built-in RPC endpoints for the major networks, but you can replace them with a faster, more reliable provider in about 30 seconds. Here's exactly how — with copy-paste URLs for the seven most-used chains NodeFlare serves — the same pattern works for every chain: swap the chain slug.

Why add a custom RPC?

The defaults MetaMask ships with are shared public infrastructure: busy, rate-limited, and sometimes slow at peak hours. Your own keyed RPC URL gives you:

  • Your own rate limit: requests count against your key, not against a pool shared with every other wallet user
  • Regional routing: requests follow configured regional preferences and available upstreams
  • A choice of provider: you decide which infrastructure your wallet reads from and sends transactions through

How to add a network in MetaMask

  1. Open MetaMask and click the network selector at the top-left (shows the current network name).
  2. Click Add network.
  3. Click Add a network manually at the bottom of the list.
  4. Fill in the fields from the tables below for the chain you want.
  5. Click Save.

MetaMask will switch to the new network immediately.

To update an existing network's RPC (for example, to replace the default Ethereum endpoint):

  1. Network selector → ⋮ next to the network → Edit.
  2. Change New RPC URL to the NodeFlare endpoint below.
  3. Save.

NodeFlare endpoints for MetaMask

A wallet polls its RPC continuously, so use a keyed URL in MetaMask: create a free key (no credit card, 10 requests/second) and replace /public with /v1/YOUR_KEY in the URLs below. The keyless /public URLs shown in the tables answer without an account, but they allow 1 request per 10 seconds per IP. That is enough to check that the network details are right, and too low for daily wallet use.

Ethereum Mainnet

FieldValue
Network nameEthereum Mainnet
New RPC URLhttps://rpc.nodeflare.app/eth/public
Chain ID1
Currency symbolETH
Block explorer URLhttps://etherscan.io

Full Ethereum RPC reference →

Base

FieldValue
Network nameBase
New RPC URLhttps://rpc.nodeflare.app/base/public
Chain ID8453
Currency symbolETH
Block explorer URLhttps://basescan.org

Full Base RPC reference →

Arbitrum One

FieldValue
Network nameArbitrum One
New RPC URLhttps://rpc.nodeflare.app/arb/public
Chain ID42161
Currency symbolETH
Block explorer URLhttps://arbiscan.io

Full Arbitrum RPC reference →

Optimism

FieldValue
Network nameOP Mainnet
New RPC URLhttps://rpc.nodeflare.app/op/public
Chain ID10
Currency symbolETH
Block explorer URLhttps://optimistic.etherscan.io

Full Optimism RPC reference →

BNB Smart Chain

FieldValue
Network nameBNB Smart Chain
New RPC URLhttps://rpc.nodeflare.app/bnb/public
Chain ID56
Currency symbolBNB
Block explorer URLhttps://bscscan.com

Full BNB Chain RPC reference →

HyperEVM (Hyperliquid)

FieldValue
Network nameHyperEVM
New RPC URLhttps://rpc.nodeflare.app/hl/public
Chain ID999
Currency symbolHYPE
Block explorer URLhttps://purrsec.com

Full HyperEVM RPC reference →

Avalanche C-Chain

FieldValue
Network nameAvalanche Network
New RPC URLhttps://rpc.nodeflare.app/avax/public
Chain ID43114
Currency symbolAVAX
Block explorer URLhttps://snowtrace.io

Full Avalanche RPC reference →

Use a keyed endpoint for higher limits

The public endpoints allow 1 request per 10 seconds per IP: fine for a test call, not for a wallet. A free NodeFlare API key gives you:

  • 3,000,000 compute units/month, no credit card
  • 10 requests/second on an authenticated endpoint, on shared infrastructure with plan-specific limits
  • Heavy methods such as eth_getLogs where the node supports them, within compute-unit and concurrency limits

The endpoint format with a key:

https://rpc.nodeflare.app/{chain}/v1/YOUR_KEY

For example, Ethereum with a key: https://rpc.nodeflare.app/eth/v1/YOUR_KEY

To get your key: visit nodeflare.app, sign up, and copy the key from the dashboard. Swap the URL in MetaMask — nothing else changes.

Troubleshooting

"Could not fetch chain ID" — Check the RPC URL for typos. The chain slug must be exact: eth, base, bnb, arb, op, hl, or avax.

"Chain ID does not match" — Make sure the Chain ID field matches exactly. Common mistake: confusing Arbitrum One (42161) with Arbitrum Sepolia (421614).

Requests failing with HTTP 429, or balances not loading: the keyless endpoint allows 1 request per 10 seconds per IP and a wallet exceeds that quickly. Switch the RPC URL to your free keyed URL. See the rate limits reference for per-method compute unit weights.

What's next

Once the network is added in MetaMask, the same endpoint works in code — paste the URL into an ethers.js JsonRpcProvider, a viem http() transport, or a web3.py HTTPProvider. One key, every chain, the same URL format.