ERPC - Enhanced Solana RPC Endpoint

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, and the base rate is 42 tokens per method. 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. Put the api-key in the URL as a query parameter, not in an Authorization or other HTTP header. ERPC reads the key only from the URL, so a key sent in a header is ignored and the endpoint returns a 401.

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.

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. 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.