RPC overview
The Solana JSON-RPC surface over HTTP, with WebSocket subscriptions and explicit method limits.
rpc edge exposes a Solana JSON-RPC surface over HTTP, plus WebSocket subscriptions, on performance-tuned Frankfurt infrastructure. The RPC product is included because trading systems need live reads, simulations, and transaction submission. It is not positioned as an archive RPC or a broad account-scan product on shared plans.
What is Solana RPC?
Definition
Solana RPC is the JSON-RPC API that applications use to read on-chain state and submit transactions
to the network. Over HTTP you make one-shot calls like getAccountInfo, getMultipleAccounts,
simulateTransaction, and sendTransaction; over WebSocket you subscribe to account, log, and
signature updates. rpc edge scopes this surface to trading workloads and protects the streaming fast
path with explicit limits.
HTTP vs WebSocket
| Transport | Use for |
|---|---|
| HTTP JSON-RPC | live reads, simulations, transaction submission |
| WebSocket | account, program, log, slot, block, and signature subscriptions |
Common methods
getAccountInfo- read a single account.getMultipleAccounts- read several accounts in one call, weighted by account count.getBalance- read an account's lamport balance.getLatestBlockhash- fetch a fresh blockhash for signing.simulateTransaction- dry-run a transaction for logs, compute units, and errors.sendTransaction- submit a signed transaction through the rpc edge sender path where enabled.getSignatureStatuses- check whether a transaction landed.getLeaderSlots- rpc edge extension for upcoming leaders and route quality.
See rate limits for method classes, disabled methods, and account-read unit limits, errors and troubleshooting for status codes and 429 handling, and the leader slot API for route-aware sender planning.
When to stream instead
Polling adds latency. For live state at scale, prefer Yellowstone gRPC over fanning out WebSocket subscriptions, and decoded shreds for pre-execution transaction intent.