CryptosBeginner

Learn · DeFi infrastructure

Best RPC node providers, compared honestly

Updated 21 October 2026 · Reviewed for CryptosBeginner

Every time your wallet shows a balance or a DeFi app quotes a swap, an RPC endpoint did the fetching. Here are the seven providers worth knowing, compared on the things they actually publish: price, free tiers, chains, and what is hiding in the fine print.

Alex Rivera · Crypto researcher, CryptosBeginner

Every review is research-led: specs, fees, and availability are checked against official sources before publication and re-checked on every update. Affiliate links never influence verdicts. Last reviewed 21 October 2026.

MakeCryptosBeginnerpreferred on

Quick picks

Short on time? These three cover most people. The full reviews below explain the trade-offs, and the pricing table further down has the numbers.

Best for beginners

Alchemy

Friendly dashboard, strong documentation, 30M free compute units a month, and pay as you go after that. The easiest first endpoint to set up.

Best free tier

dRPC

210M compute units a month free on public nodes, roughly ten million typical calls. Ankr's Freemium plan (200M credits, 65+ chains) is a close second.

Best multi-chain

Ankr

65+ chains on the free Freemium plan and 100+ across the platform, with flat per-request pricing. Chainstack is the pick if predictable billing matters more.

What is an RPC node, in plain English?

A blockchain is kept by thousands of computers called nodes. Each node holds a copy of the ledger: every balance, every transaction, every smart contract. Your wallet is not a node. It is a small app on your phone or browser, and it cannot store or check that ledger by itself.

So your wallet asks a node to do it. The asking happens through an RPC endpoint, which is just a web address connected to someone else's node. Think of it as a waiter between you and the kitchen. You say "what is my balance?" The waiter carries the question to the kitchen, the kitchen checks its records, and the waiter brings the answer back. When you send a swap, the same waiter carries your signed order in.

An RPC provider is a company that runs a lot of these waiters and kitchens, and rents you an address. Instead of buying hardware and keeping a node synced around the clock, you paste their URL into your wallet or app and get on with your day.

Flow diagram showing a wallet or DeFi app sending a request through an RPC endpoint to blockchain nodes and receiving the answer back
Every balance check and swap quote follows this path. The endpoint in the middle is the part you can choose.

Why your RPC choice matters, even if you never write code

Most people meet their RPC provider by accident. Your wallet came pre-connected to one, probably Infura if you use MetaMask, and it worked, so you never thought about it again. Fair enough. But the endpoint quietly shapes three things you do notice.

How fresh your wallet feels

A slow or congested endpoint means balances that lag a block behind, prices that look stale, and a wallet that feels broken when the chain is fine. During a busy NFT mint or a market crash, public endpoints are the first thing to buckle.

Whether swaps go through

When a DeFi app cannot reach its endpoint, quotes fail, transactions time out, or the app shows a price that has already moved. People often blame the DEX or the chain when the real problem is a rate-limited RPC in the middle.

Who sees your activity

Your endpoint can log your IP address alongside the wallet addresses you ask about. That does not put your funds at risk, but it does link your identity to your addresses in someone's database. Privacy-conscious users pick providers, or run setups, that log less.

Changing the endpoint in a wallet like MetaMask is a settings change, not a migration. Your funds, addresses and history stay exactly where they are. You are just choosing a different waiter.

Endpoint types, explained

Providers sell the same data through four kinds of endpoint. The differences are who shares the node, how hard you can push it, and what it costs.

Comparison graphic of public, shared, private and dedicated RPC endpoints showing cost, speed and limits for each type
The four endpoint types side by side. Most readers will live in the middle two.
TypeHow it worksCostBest for
PublicOpen endpoints anyone can call, no account or keyFreeTesting, light personal wallet use
SharedYour requests share a pool of nodes with other customers, separated by your API keyFree tier, then paid plansMost apps and most people
PrivateA paid endpoint with your own key, higher limits and priority over public trafficMonthly plan or per-request billingProduction apps, active traders
DedicatedA node (or cluster) provisioned only for you, in a region you choosePriced per node, often $1,000/month and upExchanges, indexers, heavy workloads

One naming warning: providers use these words loosely. A "private" endpoint at one company can be the same shared pool as another company's standard plan, just with your own key. Read the requests-per-second and quota numbers, not the label.

How we compared these providers

Our method, stated plainly

We read each provider's official documentation and pricing page on 21 October 2026 and recorded what they publish: chain coverage, free tier allowances, entry prices, how usage is billed, archive access and WebSocket support. Every figure in this guide traces back to one of those pages, linked in the sources section.

We did not run load tests, and we are not going to dress up other people's benchmarks as our own. You will find no latency or error-rate league table here, because we cannot stand behind numbers we did not measure. Where a provider's own pages disagreed with each other, we say so and use the more conservative figure.

Prices and free tiers in this industry change often, sometimes monthly. Treat the numbers below as a snapshot from October 2026 and check the linked pricing page before you commit to anything.

The 7 providers, reviewed

Each review follows the same shape: what the provider is like to use, a parameter table from its published material, and two honest strengths and limitations.

Alchemy

Best for beginners

Alchemy is the name most Ethereum developers learn first, and it earned that spot with good documentation and a dashboard that does not assume you already know everything. If you are setting up your first endpoint, this is the gentlest on-ramp of the seven.

Pricing runs on compute units. A simple call might cost 10 units, a heavy one 100 or more, and Alchemy's own docs suggest budgeting around 27 units for an average request. The free plan's 30M units a month works out to roughly a million typical requests, which is plenty for learning and small projects.

ChainsDozens of networks: Ethereum, Solana, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche and more
Free tier30M compute units per month
Entry pricePay as you go, no monthly minimum; $0.525 per 1M compute units
Pricing modelCompute units, weighted by method
Archive accessYes, full and archive nodes offered
WebSocketYes

Strengths

  • + Beginner-friendly dashboard, docs and tutorials
  • + Pay as you go with no monthly fee once you outgrow free

Limitations

  • - Compute unit weights make bills hard to forecast exactly
  • - Extra throughput capacity is sold in blocks on top of usage

Official site: Alchemy · Pricing page

Infura

The default inside MetaMask

Infura is owned by Consensys and is the default RPC provider inside MetaMask, which means millions of people already use it without knowing its name. That default status is its biggest strength: battle-tested at wallet scale, with a long track record on Ethereum.

Infura bills in credits, with each method assigned a credit cost. The free Core plan carries a daily credit quota (3M credits a day in the pricing table), and paid plans start at $50 a month for the Developer tier. Its focus stays close to Ethereum and the major EVM networks rather than chasing every chain.

ChainsEthereum-first: Ethereum and major EVM networks, plus file storage APIs
Free tierCore plan, free, with a daily credit quota (3M credits/day per the pricing table)
Entry price$50/month (Developer plan)
Pricing modelCredits, weighted by method
Archive accessListed as a plan feature; availability depends on tier
WebSocketYes

Strengths

  • + Proven at huge scale as MetaMask's default provider
  • + Simple plan ladder if your needs stay inside the EVM world

Limitations

  • - Narrower chain coverage than the multi-chain specialists
  • - Committed uptime SLAs sit on the custom Enterprise plan

Official site: Infura · Pricing page

QuickNode

Best toolkit around the endpoint

QuickNode sells more than raw node access. Streams (blockchain data pipelines), webhooks and a marketplace of add-ons sit around the core RPC product. If your project grows into that tooling, having it under one account is genuinely convenient.

Billing uses API credits, calculated as method responses multiplied by a method multiplier, so a heavy call costs more than a light one. The free trial includes 10M credits, and the Build plan at $49 a month raises that to 80M credits with 50 requests per second.

ChainsDozens of chains across EVM networks and Solana
Free tierFree trial with 10M API credits, 15 requests/second
Entry price$49/month (Build plan)
Pricing modelAPI credits: responses multiplied by method multipliers
Archive accessYes, listed across plans
WebSocketYes

Strengths

  • + Streams, webhooks and add-ons in the same account
  • + Lets you pay in crypto on paid plans

Limitations

  • - Method multipliers mean two similar apps can see very different bills
  • - The extra tooling only pays off if you actually use it

Official site: QuickNode · Pricing page

Chainstack

Most predictable billing

Chainstack's pitch is calm, predictable infrastructure, and its billing matches the pitch. One standard request costs one request unit. Archive requests cost two. That is the easiest pricing on this page to model in a spreadsheet before you spend anything.

The free Developer plan includes 3M request units a month at 25 requests per second, with WebSockets included. Archive data starts on the Growth plan at $49 a month. Chainstack also sells dedicated nodes if you later need hardware of your own.

Chains25+ protocols, including Ethereum, Solana, BNB Chain, Polygon and Base
Free tier3M request units per month, 25 requests/second
Entry price$49/month (Growth plan)
Pricing modelRequest units: 1 per standard request, 2 per archive request
Archive accessPaid plans (Growth and up); not on the free plan
WebSocketYes, included on the free plan

Strengths

  • + Flat, easy to predict pricing with no method weight surprises
  • + Dedicated node upgrade path inside the same platform

Limitations

  • - Free plan has no archive access
  • - Chain list is shorter than GetBlock or dRPC

Official site: Chainstack · Pricing page

Ankr

Best multi-chain value

Ankr casts the widest free net. Its public endpoints need no sign-up at all, and the Freemium plan adds 200M API credits a month across 65+ chains once you create an account. If you hop between ecosystems, that breadth is hard to beat at zero cost.

Paid usage is pay as you go at $0.10 per 1M credits. Ankr keeps its per-request prices flat by chain family rather than by method weight: an EVM request costs 200 credits ($0.00002), a Solana request 500. Ankr also states that archive access is included on every tier, free included, which is unusual.

Chains65+ chains on Freemium; 100+ across the platform
Free tierPublic endpoints free with no sign-up (20 requests/second); Freemium adds 200M credits/month
Entry pricePay as you go; $0.10 per 1M API credits
Pricing modelAPI credits, flat per request by chain family
Archive accessIncluded on every tier, per Ankr
WebSocketYes

Strengths

  • + Widest free multi-chain coverage on this list
  • + Flat per-request pricing is simpler than method weights

Limitations

  • - Free tiers run at modest requests-per-second caps
  • - The full SLA and dedicated setup are Enterprise conversations

Official site: Ankr · Pricing page

GetBlock

Widest chain catalogue

GetBlock has run nodes since 2019 and lists 130+ blockchains, including plenty of networks the bigger names skip. For a wallet or app that needs an unusual chain, it is often the first place that has it.

It bills in compute units, where heavy methods like eth_getLogs cost more than simple lookups. The free plan renews daily at 50,000 compute units, and paid shared plans start at $49 a month. Dedicated nodes are priced publicly from $1,000 a month, which is refreshingly upfront for this market.

Chains130+ blockchains, EVM and non-EVM
Free tier50,000 compute units per day
Entry price$49/month (Starter shared plan)
Pricing modelCompute units, weighted by method and chain
Archive accessOn selected networks; broader access on paid plans
WebSocketYes

Strengths

  • + Huge chain catalogue, including less common networks
  • + Public pricing for dedicated nodes, no sales call needed

Limitations

  • - Daily free quota does not roll over, so bursty testing eats it fast
  • - Archive coverage varies by network rather than applying everywhere

Official site: GetBlock · Pricing page

dRPC

Best free tier, decentralised routing

dRPC does not run one big fleet of nodes. It routes your request across a network of independent node providers (60+ of them, across 8 geographic clusters) behind a load balancer. If one operator stumbles, traffic moves to another. That design makes it a natural backup provider as well as a main one.

Its pricing is the simplest here after Chainstack: every request costs a flat 20 compute units on the paid Growth plan, any method, any chain, archive and trace included, at $6 per 1M requests with no monthly commitment. The free tier is generous too, 210M units a month served from public nodes.

Chains130+ chains across 230+ networks
Free tier210M compute units per month on public nodes, 100 requests/second
Entry pricePay as you go; $6 per 1M requests
Pricing modelFlat 20 compute units per request, any method
Archive accessYes, at the same flat rate as normal calls
WebSocketYes

Strengths

  • + Routing across many operators removes a single point of failure
  • + Flat pricing covers archive and trace calls, no method weight maths

Limitations

  • - Free tier runs on public nodes and skips some advanced methods
  • - You do not choose which operator answers a given request

Official site: dRPC · Pricing page

Pricing snapshot

The headline numbers, side by side. Remember that a "unit" means something different at every provider, so the free tier column compares each company's own allowance, not a converted equivalent.

ProviderFree tier (published)First paid stepHow you are billed
Alchemy30M compute units/monthPay as you go, $0.525 per 1M unitsCompute units, weighted by method
InfuraFree Core plan, daily credit quota$50/month (Developer)Credits, weighted by method
QuickNodeFree trial, 10M API credits$49/month (Build)API credits, method multipliers
Chainstack3M request units/month$49/month (Growth)Request units, 1 per standard call
AnkrPublic free; Freemium 200M credits/monthPay as you go, $0.10 per 1M creditsCredits, flat per request by chain
GetBlock50,000 compute units/day$49/month (Starter)Compute units, weighted by method
dRPC210M compute units/month (public nodes)Pay as you go, $6 per 1M requestsFlat 20 units per request, any method

Snapshot taken from official pricing pages on 21 October 2026. Providers adjust quotas and prices without much warning, so confirm before you build a budget on these numbers.

Five budget traps to check before you pay

Nobody gets surprised by the monthly plan price. They get surprised by these.

Method weight multipliers

A plan that advertises millions of units can drain fast if your app leans on heavy methods like eth_getLogs or trace calls. Check the provider's weight table against your three most common calls before comparing headline quotas.

Low requests-per-second on free tiers

A generous monthly quota with a 15 to 25 requests-per-second cap still fails a busy app. Bursts matter more than monthly totals for anything user-facing.

Archive sold as an add-on

Historical state queries often sit behind a higher plan or a per-call premium (Chainstack charges 2 units for an archive call; its free plan has none). If your tool reads old blocks, price that in from the start.

SLAs reserved for Enterprise

The uptime guarantee and the fast support response usually live on custom contracts. Self-serve plans are best-effort, however polished the marketing page looks.

Regional throttling

Endpoints are served from specific regions. An app whose users are in Asia but whose endpoint sits in the US will feel slow no matter the plan. Check where you can deploy before you pay.

How to choose, by what you actually do

Casual DeFi user

You probably need nothing new

Your wallet's default endpoint is fine for checking balances and the odd swap. If it feels slow at peak times, add a free Ankr or dRPC public endpoint as an alternative network RPC in your wallet settings. Cost: zero.

Hobby developer

Start on Alchemy or Chainstack free

Alchemy if you want the best tutorials and dashboard while you learn. Chainstack if you want billing you can predict to the unit. Both free tiers are big enough to build and launch a small project.

Active trader or bot

Pay for headroom, keep a backup

Requests per second and WebSocket stability matter more than monthly quota. A paid QuickNode or Chainstack plan near your users, with dRPC set up as automatic failover, covers both speed and the day your main provider has an outage.

Risk checklist before you commit

  • Vendor lock-in: provider-specific APIs (enhanced token or NFT endpoints) are handy and sticky. Plain JSON-RPC calls move between providers in minutes; proprietary extras do not.
  • No failover: one endpoint means one point of failure. Keep a second provider's URL configured, even on a free tier, so an outage is an inconvenience rather than downtime.
  • Single region: if all your traffic routes through one continent, latency and regional outages both hit harder. Prefer providers that let you pick or spread regions.
  • Key exposure: an API key pasted into frontend code or a public repo will be found and abused, and the usage lands on your bill. Restrict keys by domain or IP where the provider allows it.
  • Privacy: your provider sees your IP and the addresses you query. That is inherent to the service. If it matters to you, say so in your choice rather than discovering it later.

None of this makes RPC providers risky in the way a shady exchange is risky. They cannot touch your funds. The risks are operational: downtime, surprise bills, and building on features you cannot take with you.

Frequently asked questions

What is an RPC node provider?+

An RPC node provider runs blockchain nodes and sells or gives away access to them through an endpoint URL. Your wallet or app sends requests to that URL (what is my balance, send this transaction, what is the price in this pool) and the provider's node answers from the blockchain's records. You get the data without running a node yourself.

Do I need an RPC provider if I only use a wallet?+

You already use one. MetaMask and most other wallets ship connected to a default provider, usually Infura. You only need to think about it if your balance loads slowly, swaps keep failing, or you want a provider that does not log as much about your activity. Changing the RPC URL in your wallet settings takes about a minute.

What is the best free RPC provider?+

For raw free volume, dRPC's free tier offers 210M compute units a month on public nodes, and Ankr's Freemium plan offers 200M API credits a month across 65+ chains. For learning and building, Alchemy's free plan (30M compute units a month) pairs a decent quota with the friendliest dashboard and docs. Chainstack's free 3M request units are the easiest to understand because one standard request costs one unit.

Why do providers charge in compute units or credits instead of requests?+

Because requests are not equal. Reading a balance is cheap; scanning a year of event logs is expensive. Providers weight each method so heavy calls cost more units. That keeps light users from subsidising heavy ones, but it also makes your bill harder to predict. Before paying, check the provider's method weight table for the calls your app makes most.

What is archive access, and do I need it?+

A normal full node can tell you the current state and recent history. An archive node can answer questions about any past block, such as what an address held two years ago. Most DeFi users and most apps never need it. Analytics tools, tax software, and researchers do. Several providers charge extra for it or only include it on paid plans.

Can I use more than one RPC provider?+

Yes, and serious projects do. A second endpoint acts as a backup when the first one slows down or goes offline. Some tools, including dRPC, are built to route requests across several node operators automatically. For a personal wallet, keeping a spare RPC URL noted down is enough.

Is a public RPC endpoint safe to use?+

It is safe in the sense that an RPC provider cannot move your funds; it only reads data and relays the transactions you sign. The trade-offs are privacy and reliability. The provider can see your IP address and the addresses you query, and public endpoints slow down or drop requests when the network is busy.

What does RPC stand for?+

Remote Procedure Call. It is an old computing term for asking another computer to do something and send back the result. In crypto, your app calls a function on a node (get balance, get block, send transaction) and the node returns the answer, usually in JSON format, which is why you will also see the term JSON-RPC.

Sources

All pricing, free tier and feature claims in this guide come from the providers' official pages, checked on 21 October 2026:

Last updated 21 October 2026. Educational content only, not financial advice. Providers change pricing and quotas over time; verify on the official pricing page before paying. For more on how DeFi apps fit together, see our guide to RWA crypto projects and the rest of the Learn hub.