RPC Providers

List of public RPC endpoints for the NEAR Protocol.

NEAR Protocol exposes a JSON-RPC API for interacting with the network. You can use any of the providers below or run your own node.

RPC Providers

FastNear maintains a comprehensive dashboard with response times for most of the available endpoints.

Mainnet

Provider	Endpoint	Public Endpoint	Archival Node	Free Tier	Free Tier Limit	Paid Plan
FASTNEAR	https://free.rpc.fastnear.com	✅	Paid Only	✅	Not published	✅
NEAR	https://archival-rpc.mainnet.near.org	✅	✅	Severely rate limited	Not published	❌
1RPC	https://1rpc.io/near	✅	❌	✅	200 req/day	✅
All That Node	N/A	❌	✅	✅	500K CU/day	✅
Ankr	https://rpc.ankr.com/near	❌	❌	✅	~30 req/s	✅
BlockPI Network	https://near.blockpi.network/v1/rpc/public	✅	❌	✅	20 req/s	✅
dRPC	https://near.drpc.org	✅	❌	✅	~2,100 CU/s	✅
GetBlock	https://go.getblock.io/{api-key}	❌	❌	✅	50K CU/day	✅
Intear RPC	https://rpc.intea.rs	✅	❌	✅	Not published	❌
Lava Network	N/A	❌	✅	❌	—	✅
Lavender.Five Nodes	N/A	❌	❌	✅	Not published	✅
node101	N/A	❌	Paid Only	❌	—	✅
NodeReal	https://near-mainnet.nodereal.io/v1/{api-key}	❌	❌	✅	100M CU/month	✅
NOWNodes	https://near.nownodes.io/{api-key}	❌	❌	✅	100K req/month	✅
QuickNode	N/A	❌	✅	✅	15 req/s	✅
Shitzu	https://rpc.shitzuapes.xyz	✅	❌	✅	Not published	❌
Tatum	N/A	❌	❌	✅	3 req/s	✅
ZAN	https://api.zan.top/node/v1/near/mainnet/	✅	❌	✅	~20 req/s	✅
Zeeve	N/A	❌	✅	❌	—	✅

Testnet

Provider	Endpoint	Public Endpoint	Archival Node	Free Tier	Free Tier Limit	Paid Plan
FASTNEAR	https://test.rpc.fastnear.com	✅	Paid Only	✅	Not published	✅
NEAR	https://archival-rpc.testnet.near.org	✅	✅	Severely rate limited	Not published	❌
All That Node	N/A	❌	✅	✅	500K CU/day	✅
dRPC	https://near-testnet.drpc.org	✅	❌	✅	~2,100 CU/s	✅
Intear RPC	https://testnet-rpc.intea.rs	✅	❌	✅	Not published	❌
Lava Network	N/A	❌	✅	❌	—	✅
node101	N/A	❌	Paid Only	❌	—	✅
QuickNode	N/A	❌	✅	✅	15 req/s	✅
Tatum	N/A	❌	❌	✅	3 req/s	✅
ZAN	https://api.zan.top/node/ws/v1/near/testnet	❌	❌	✅	~20 req/s	✅
Zeeve	N/A	❌	❌	❌	—	✅

[!NOTE]

Free Tier Limit values link to each provider's own pricing/docs page as the source. Limits are reported in the units each provider publishes (req = requests, CU = compute units), so they are not directly comparable across providers and may change at any time — always confirm on the linked page. "Not published" means the endpoint is free but has no documented numeric limit.

For live latency benchmarks across these providers, see OpenChainBench — p50/p90/p99 measured every 60 seconds from US-East, EU-West and Singapore.

Making requests

Send JSON-RPC 2.0 requests with POST to the root of the provider endpoint. Put the method and parameters in the JSON request body.

curl -X POST https://rpc.mainnet.near.org/ \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":"status","method":"status","params":[]}'

Send one request object per HTTP request. nearcore does not support JSON-RPC batch requests. If the body is a JSON array, a nearcore node rejects the whole request with HTTP 400 and error code -32700 (Parse error), and none of the requests in the array run.

[!WARNING]

Never load test a shared public endpoint. Run performance tests only against a node you operate or an endpoint whose operator has explicitly authorized the test.

Run your own node

To run a local RPC node, follow the NEAR node documentation.

[!NOTE]

Testnet tokens have no real value and can be obtained from the NEAR Faucet.