Free

€0
- 4,200,000 Monthly Tokens
- 5 Requests/sec
- Refills at the start of each month
ERPC gives wallets, DeFi apps, analytics, and production Solana systems a low-latency Solana RPC endpoint through an optimized global proxy. Each request is routed toward a nearby network entry point, helping projects interact with Solana through stable, short network paths.

The region matters. But a city name alone is not a network path. Even in the same city, external transit and extra hops can add latency. ERPC selects data centers close to Solana servers, then keeps routes short with no external transit and sustained turbo boost.
ERPC premium route
no external transit
minimum RTT

Pick a region near your trading system or backend; add /eth or /ava to the URL for Ethereum or Avalanche C-Chain. Supported RPC calls use no ERPC tokens and have no per-request rate limit, monthly credit quota or burst throttling. For other Solana RPC methods, use ERPC Edge.

€0

42M Monthly Tokens
Hourly pricing unavailable

420M Monthly Tokens
Hourly pricing unavailable

2,420M Monthly Tokens
Hourly pricing unavailable

Hourly pricing unavailable

Hourly pricing unavailable

Hourly pricing unavailable

Hourly pricing unavailable

Hourly pricing unavailable
gRPC Standard Plan
1 IP Whitelist · Max 10 Stream Connections
Direct Shreds Standard Plan
1 IP Whitelist · Max 10 Stream Connections

ERPC Developer Plan
42M Monthly Tokens
Hourly pricing unavailable

ERPC Business Plan
420M Monthly Tokens
Hourly pricing unavailable

ERPC Pro Plan
2,420M Monthly Tokens
Hourly pricing unavailable

Hourly pricing unavailable

ERPC continuously improves platform speed, stability, and overall quality based on user feedback and measurement data. For Solana workloads in particular, we pursue the highest network quality with low latency and stability through bare-metal and VPS servers deployed on the same network, hardware selection that exceeds industry standards, and data center selection with substantial stake.
FAQ
To get a low-latency Solana RPC endpoint with ERPC, sign up in the ERPC Web Dashboard at dashboard.erpc.global and your API key is issued instantly. You get a managed Solana RPC endpoint with HTTP and WebSocket access over ERPC's own global network. This network routes every request along the shortest network path. Calls are counted in tokens: a standard Solana method uses 42 tokens per call, and heavier methods use more, such as 124 for getTransaction and 420 for getBlock. The tokens for each method are in the FAQ "How many tokens does each method consume?" at erpc.global/en/faq/how-to-start/general, and the tokens each plan includes are on erpc.global/en/price. Copy your key and add it to the endpoint as a query parameter: https://edge.erpc.global?api-key=YOUR_KEY, or for WebSocket wss://edge.erpc.global?api-key=YOUR_KEY. For HTTP requests, you can also send the key in the header Authorization: Bearer YOUR_KEY instead of the query parameter. For WebSocket, the key goes in the URL.
Pick a dedicated Solana RPC endpoint if you cannot tolerate slowdowns or rate limits under load, and a shared endpoint when you are getting started or testing. A shared endpoint is used by many customers at once, so as traffic grows requests can queue, latency becomes less consistent, and you can hit rate limits. A dedicated endpoint makes you the sole user, so other customers' traffic never slows you down. A dedicated endpoint can also connect over plain HTTP without TLS, and skipping the TLS handshake saves around 20ms for an extra speed gain.
Unlimited Endpoints are designed for low-latency standard Solana RPC calls. Supported methods are getSlot, getBlockHeight, getLatestBlockhash, getBalance, getAccountInfo, getMultipleAccounts, getTransaction, sendTransaction, simulateTransaction, getSignatureStatuses, getRecentPrioritizationFees, getHealth, getVersion, getEpochInfo, getBlock. For other methods, use https://edge.erpc.global?api-key=YOUR_KEY.
Add history=true to HTTP requests to edge.erpc.global to look up older blocks and transactions, for example https://edge.erpc.global?api-key=YOUR_KEY&history=true. Except for getTransactionsForAddress, a request without it is answered from the recent range each node holds at the regular price, so older blocks may return an error and older transactions may return null. A lookup for older blocks or transactions may take much longer than a regular request, in some cases seconds. History access is a separate option that keeps such lookups apart, so that regular requests stay fast. A call answered by history access costs 640 + 82 × N tokens in total, in place of its regular price. N is 1 for every method except two, so getBlock costs 722. N is the number of signatures for getSignatureStatuses (10 signatures cost 1,460) and the number of transactions fetched for getTransactionsForAddress in full mode (100 transactions cost 8,840); see History Access at erpc.global/en/doc/rpc/general. Calls answered from recent data keep the regular price, even with history=true. Free allowances have a limit for history access.
ERPC runs nodes in Frankfurt, Amsterdam, London, New York, Chicago, Tokyo, Singapore, and Sydney. Every request enters at the nearest of more than 300 Cloudflare-powered edge locations, then is forwarded to the optimal ERPC node, so the request always takes the shortest possible network path. For slot-level targeting you can use the Leader Slot API (getLeaderSlots) to follow which region holds the leader and route toward it.
ERPC WebSocket runs on the same Solana RPC endpoint as HTTP with the same API key, using wss://edge.erpc.global instead of https://edge.erpc.global. You can stream real-time Solana updates such as account and slot changes over one connection, so your app receives them as soon as they happen. This makes WebSocket the simplest streaming option to integrate.
Pair a dedicated RPC node with a Bare Metal server on the same network. With no public-internet hop between the node and the server, round-trip ping is around 0.1ms, which makes being first to land on each Solana slot achievable. Latency otherwise depends on the method and your environment, so TypeScript and Rust tools let you measure it in your own setup.
Based on consistent customer feedback, the typical speed order is Direct Shreds first, then Geyser gRPC, then WebSocket. WebSocket on the Solana RPC endpoint is the simplest to integrate, while Geyser gRPC and Direct Shreds are dedicated streaming products for teams that need to act first, with Direct Shreds delivering data as early as possible. To pick the right one, compare them in your own environment.
Crypto payments are available when your registered billing address country is one of the EU member countries. If every payment card registered on your account was issued outside the EU, crypto payments are not available. From the ERPC Web Dashboard you can use SOL, USDC, or EURC to buy ERPC Credits, then apply those credits to activate or continue your Solana RPC plan. Supported countries: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden. For countries not on the list, please pay by credit card.
Issue an API key and test low-latency RPC, Geyser gRPC, and Direct Shreds. Measure first, then expand into Dedicated Nodes, VPS, or Bare Metal when your production path is clear.