Free Zircuit RPC Endpoint
Chain ID 48900 · ETH · one configured primary region
Zircuit (Chain ID 48900) is a zk-rollup with sequencer-level security screening. NodeFlare operates a Zircuit node for JSON-RPC access.
Public endpoint — no API key
HTTPS
https://rpc.nodeflare.app/zircuit/publicNeed higher limits? Use a keyed endpoint https://rpc.nodeflare.app/zircuit/v1/{YOUR_KEY} — get a free key →
Connect to Zircuit
curl -s -X POST https://rpc.nodeflare.app/zircuit/public \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'import { ethers } from "ethers";
const provider = new ethers.JsonRpcProvider(
"https://rpc.nodeflare.app/zircuit/public"
);
const block = await provider.getBlockNumber();import { createPublicClient, http } from "viem";
const client = createPublicClient({
transport: http("https://rpc.nodeflare.app/zircuit/public"),
});
const block = await client.getBlockNumber();from web3 import Web3
w3 = Web3(Web3.HTTPProvider(
"https://rpc.nodeflare.app/zircuit/public"
))
print(w3.eth.block_number)Add Zircuit to your wallet
Network details for MetaMask, Rabby, or any EVM wallet — Zircuit chain ID 48900 (0xbf04).
| Network name | Zircuit |
| RPC URL | https://rpc.nodeflare.app/zircuit/public |
| Chain ID | 48900 |
| Currency symbol | ETH |
| Block explorer | https://explorer.zircuit.com |
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/zircuit/v1/{YOUR_KEY} instead. A free key allows 10 requests per second, and the dashboard adds Zircuit to MetaMask with that URL in one click. Get a free key →
Built for Zircuit
Early DeFi and security-conscious apps building on Zircuit. Requests use configured regional preferences and available upstreams. Plan rate limits, compute units and method-specific concurrency limits apply.
Zircuit node coverage and routing
A NodeFlare-operated primary node region. No public third-party RPC backstop is configured. 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.
Zircuit RPC — FAQ
What is Zircuit's chain ID?
Zircuit's chain ID is 48900 (hex 0xbf04). Its native currency is ETH and its block explorer is explorer.zircuit.com. You can connect with NodeFlare's free public RPC at https://rpc.nodeflare.app/zircuit/public — no API key required.
How do I add Zircuit to MetaMask?
In MetaMask, open the network menu → "Add a network" → "Add a network manually", then enter — Network name: Zircuit; Chain ID: 48900; Currency symbol: ETH; Block explorer URL: https://explorer.zircuit.com; New RPC URL: your keyed NodeFlare URL, https://rpc.nodeflare.app/zircuit/v1/{YOUR_KEY}. A free key allows 10 requests per second. The keyless URL https://rpc.nodeflare.app/zircuit/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 Zircuit RPC URL?
NodeFlare's public Zircuit RPC URL is https://rpc.nodeflare.app/zircuit/public over HTTPS. No API key is required for the public endpoint.
Is the Zircuit RPC free?
Yes. The public Zircuit 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 Zircuit 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 Zircuit RPC provider?
NodeFlare operates its own primary Zircuit nodes. A NodeFlare-operated primary node region. No public third-party RPC backstop is configured. 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 Zircuit 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. No public third-party RPC backstop is configured. Historical state and traces must be checked for your specific methods and block ranges; a key does not guarantee complete archive coverage.
Go deeper
- Full Zircuit API reference → — supported methods, WebSocket, regions
- Rate limits & compute-unit costs → — what each method costs against your quota
- Pay per request with x402 → — Zircuit calls in USDC from $0.001, no account:
POST /zircuit/x402 - RPC for trading bots → and indexers → — low-latency, eth_getLogs-heavy workloads
- Guide: Free Zircuit RPC Endpoint →
- Zircuit honeypot checker → — transfer simulation, holder concentration and ownership for any Zircuit token; also as an API
- Compare Zircuit gas prices → — live gas price and transaction cost next to the other chains, and a free token approval checker →
- Moving Zircuit traffic from another provider? Compare NodeFlare with Alchemy, Infura and QuickNode →
- Onchain tools for AI agents → — token-safety, wallet intelligence and RPC over MCP / x402
Build on Zircuit with a free key
Higher limits and an authenticated endpoint — every supported chain included. No credit card.
Get your free API key →Zircuit RPC methods
Per-method docs for Zircuit — parameters, compute-unit cost, and copy-paste examples.