RPC swap in about 30 seconds

Switch your wallet to a faster Base.

Same Base, same dApps, same chainId. For most wallets it’s one edited URL on the Base entry you already have. Revert anytime.

The URL you’ll switch to

https://rpc.baseazul.dev

Copy this, you’ll paste it in step 2. chainId 8453 0x2105· single region (us-east-1 (Virginia)).

Set it in your wallet

Pick your wallet. For most it’s one move: open the Base network, edit its RPC URL, paste Azul’s. A couple differ; each card shows the exact move.

MetaMask

Most common browser wallet. Base is already in your default network list, you edit its RPC URL, not add a new chain.

Base is already in your wallet. You are editing the existing entry, not adding a new network.

  1. Open the MetaMask extension and click the network dropdown at the top.
  2. Click "Edit networks", then the pencil icon next to "Base".
  3. In "Default RPC URL", paste: https://rpc.baseazul.dev
  4. Click "Save". MetaMask validates by pinging the endpoint for chainId.
  5. Open any dApp on Base, reads now route through Azul.
MetaMask Mobile: tap the menu (top-left) → Settings → Networks → tap “Base” → edit the RPC URL field, paste the URL above, and save. The app re-validates chainId on save.
Don’t have MetaMask?

What doesn’t change

  • Your address, your funds, your seed phrase
  • The chain itself, chainId 8453
  • Every dApp you already use

What does change

  • Only which server answers when your wallet reads a balance, nonce, or gas price
  • Revert anytime by pasting back the public URL https://mainnet.base.org

Confirm it’s live

Saved the URL? Make sure your wallet is actually pointing at Azul before you trade on it.

Read the chain your browser wallet is on right now. This runs entirely in your browser. We never see it.
Manual cross-check
  1. In your wallet’s Base network settings, confirm the RPC URL reads https://rpc.baseazul.dev.
  2. Open any Base dApp and watch your balance load. The first read goes through your new RPC.
  3. Cross-check the latest block against the explorer; the tip should track within a block or two (Base blocks land every 2s).
Open basescan.orgHow we measure

Once that field reads https://rpc.baseazul.dev, you’re set. Switching the RPC only changes which server answers reads, your funds, keys, and seed phrase were never touched. Revert anytime by pasting back the public URL.

Straight answers

Is Azul free?
Yes. Azul is free for public use. No API key, no signup. Anonymous traffic is rate-limited at 100 req/s per IP (10 req/s for heavy methods like eth_getLogs). API-key users bypass these limits.
Does Azul log my IP or wallet address?
No. Azul does not log IP addresses, request bodies, or wallet addresses on the RPC path. There are no cookies and no third-party trackers on the RPC endpoint. The marketing site (this domain) uses Vercel Analytics for aggregate page views only and never runs on the RPC path.
Where is it served from?
One region: us-east-1 (Virginia). The honest answer is "one server, tuned by hand." This is not multi-region anycast. Multi-region and a signed SLA are on Edge.
Can I use Azul for production traffic?
Sure, but pair it with a fallback. Azul is a single-region service with no SLA. For production, use it as a primary and fall back to a paid provider on error or timeout.
Why "private"? What's the threat model?
Wallets and dApps you use hit an RPC for every read (balance, tx history, gas estimate). Default providers can tie your IP to your wallet address. Azul does not. The privacy claim is scoped to "we do not log," which the actual log configuration backs up.
When free isn’t enough

When your volume gets fill-sensitive, there’s Edge.

Free runs in a single region (us-east-1 (Virginia)). Desks that need multi-region routing, a signed SLA, and a pre-confirmation feed run Edge.

See Edge

Want the occasional product update? Drop us your email →