Base · chainId 8453
Base RPC endpoint — free, private, fast.
A no-logging, no-key Base JSON-RPC endpoint backed by op-reth + op-node. Coinbase’s OP-Stack L2 — home to millions of onchain users.
Base
chainId 8453https://rpc.baseazul.devLatency
—
Pinging endpoint…
Block height
—
Querying…
Status
Checking
Endpoint launching soon
One-click MetaMask · Rabby · Frame · any EIP-1193 wallet
For users
Add to your wallet
One-click for MetaMask, Rabby, Coinbase Wallet. Step-by-step for everything else.
Rabby
The power-user wallet — best transaction previews on Base / OP.
- 1Open Rabby and click the gear icon (bottom-right of the popup).
- 2Click "More" → "Modify RPC URL".
- 3Search for "Base" and click it.
- 4Replace the RPC URL with
https://rpc.baseazul.devand click "Save". - 5Rabby will ping the endpoint to verify chainId; done when you see a green check.
Or use the one-click flow
RPC URL
https://rpc.baseazul.devManual network parameters
If your wallet wants you to paste them in by hand.
| Network name | Base |
|---|---|
| New RPC URL | https://rpc.baseazul.dev |
| WebSocket URL | wss://rpc.baseazul.dev |
| Chain ID | 8453 (0x2105) |
| Currency symbol | ETH |
| Block explorer URL | https://basescan.org |
For developers
Base infrastructure
Real numbers, real limits, real method coverage. No SLA, no nonsense.
Throughput
≥ 10,000req/s
Aggregate, fair-use
Block time
2s
Network TPS ≈ 60–120
p50 latency
30ms
From major regions
p99 latency
180ms
p95: 95ms
JSON-RPC method support
eth_* | Full | All standard reads, writes, filters, subscriptions |
net_* | Full | |
web3_* | Full | |
txpool_* | Full | Mempool inspection enabled |
debug_* | Partial | traceTransaction, traceCall, traceBlock — available on request |
trace_* | Off | Parity-style traces not exposed; use debug_trace* |
admin_* | Off | Operator-only namespace, never exposed publicly |
Limits & capabilities
- eth_getLogs range
- 10,000 blocks per call
- Batch size
- 100 requests per batch
- Max response
- 50 MB
- Node mode
- Full (recent ~hours of state)
- WebSocket
- Yes — subscribe to newHeads, logs
- Regions
- iad1 (Virginia) · sfo1 (San Francisco) · fra1 (Frankfurt)
- Rate limits
- None per-client — fair-use only
- CORS
- Permissive — works from any origin
- Authentication
- None — no API key, no token
Endpoints
HTTPS
https://rpc.baseazul.devWebSocket
wss://rpc.baseazul.devHealth probe
https://rpc.baseazul.devPOST eth_chainId — expect HTTP 200 + matching chainId
Production best practices
- Pair Azul with a fallback (e.g.
mainnet.base.org). viem supports this withfallback([...])— first transport wins, second takes over on error. - Use batched JSON-RPC for fan-out reads (multicall, indexer warmup). One TLS handshake, lower tail latency.
- Subscribe via WebSocket for tip-follow loops instead of polling eth_blockNumber. Lower latency, less load on both sides.
- For
eth_getLogsover wide ranges, chunk to 10,000-block pages and parallelize. - Treat Azul as a public RPC — no SLA, no per-customer reservation. Run a backup endpoint behind a circuit breaker for any production read-path.
Code samples
Plug Azul into the most common Ethereum libraries.
curl -X POST https://rpc.baseazul.dev \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Compare
Why Azul over mainnet.base.org?
The default public RPC works in a pinch. For anything that hits it more than once a minute — wallets, indexers, dashboards — you’ll feel the difference.
| Provider | No logs | No API key | No rate limit | Archive | WebSocket | Cost |
|---|---|---|---|---|---|---|
Azul You are here | Yes | Yes | Yes | Partial | Yes | Free |
mainnet.base.org (Coinbase default) Operator privacy policy reserves the right to log | No | Yes | No | Partial | No | Free |
Infura / Alchemy / QuickNode (free tier) IP + wallet logging per published privacy policy | No | No | No | Yes | Yes | Free w/ key |
Other community RPCs Quality varies — chainlist score reflects this | Partial | Yes | Partial | Partial | Partial | Free |
Comparison reflects each provider’s publicly stated privacy and ToS posture as of publication. We do not audit third-party providers; verify their current policy before relying on it.
FAQ
Frequently asked
Everything you’d want to know before pointing production traffic at a free public RPC.
What is the Base RPC URL?
The Azul Base RPC endpoint is https://rpc.baseazul.dev. It serves JSON-RPC over HTTPS on chainId 8453.
Is Azul free?
Yes. Azul is free for public use. No API key, no signup, no rate-limit gate behind a billing page.
Does Azul log my IP or wallet address?
No. Azul does not log IP addresses, request bodies, wallet addresses, or any user-identifiable data. There are no cookies, no API keys, no third-party trackers on the RPC endpoint. The marketing site uses privacy-respecting Vercel Analytics, which is scoped to the marketing domain and never runs on the RPC path.
What's the latency of Azul?
Azul is served from geo-distributed infrastructure. Most users see sub-50ms round-trip from major regions. Live latency is shown on this page once your browser pings the endpoint.
How fresh is the block tip on Azul?
Azul tracks the canonical Base tip with no artificial delay. The displayed block height matches mainnet.base.org within one block.
Does Azul support archive methods?
The endpoint supports the full standard JSON-RPC method set including eth_getLogs, eth_call, and eth_getBlockByNumber with historical block numbers. Trace methods may be available on request.
Is Azul open source?
The underlying Base node software (op-reth, op-node) is open source. The routing layer in front of it is currently private.
Can I use Azul for production traffic?
Yes, with the usual caveat that any free public endpoint should be paired with a fallback. Azul is designed to be production-grade, but no SLA is offered for the free tier.