Read state
Read SOL balances, token accounts and current account data. Use existing Solana SDKs with your endpoint and token.
Solana RPC
Read state. Look up transactions. Submit signed transactions.
JSON-RPC / HTTP
Your application
getSlot · getBalance · sendTransactionRequest + token ↓
Frankfurt RPC
Authentication · request budgetResult or error ↑
On-demand reads and signed transactions.
The lookup layer for your app.
Standard Solana JSON-RPC for balances, account state, transaction lookups and signed transaction submission. Served from Frankfurt, with WebSocket included in every Bundle.
Use RPC when your app needs a specific answer. Add a stream when it needs to follow changes continuously.
A familiar request path.
Standard Solana JSON-RPC methods. Heavy methods consume more request units.
The shared endpoint is in Frankfurt. Solana RPC provides two days of replay.
Explore methods and parameters ↗Your applicationJSON-RPC + token
Frankfurt RPCChecks auth and budget
JSON responseResult or error
Choose your commitment
processed
The node has processed the block. State can roll back.
confirmed
The block has been voted on by a supermajority of stake.
finalized
The block has reached maximum lockout.
After sendTransaction returns a signature, track its status on RPC to check confirmation and execution errors.
Methods, budgets and limits.
One call can use
more than one unit.
Your RPS budget measures weighted request units. These documented weights are the same on every Bundle tier.
Size a read workload
Static example: BUILD has 200 RPS units. getAccountInfo costs 2 units per call. 200 / 2 = 100 calls/s average.
100 calls/s average
Illustrative budget calculation. It allocates the entire request budget to this method; RPC calls, WS commands and gRPC filter updates share that budget.
| Method | RPS units / call |
|---|---|
| getProgramAccounts | 30 |
| getTransaction | 10 |
| getTokenAccountsByOwner | 10 |
| getTokenAccountsByDelegate | 10 |
| getTokenLargestAccounts | 10 |
| getAccountInfo | 2 |
| getTokenAccountBalance | 2 |
| Other standard read methods* | 1 |
*getMultipleAccounts has documented batch-dependent weights: 5 units per 100 accounts in the high-throughput pattern, or 2 units per account in the standard pattern. Confirm the pattern before sizing a batch workload.
Transaction sending has a separate TPS ceiling. When a rate limit is exceeded, expect HTTP 429. Back off and retry with transaction validity and confirmation in mind.
Read the complete limits reference ↗Price & access.
Solana
RPC + WebSocket
STARTER · entry BundleFor apps with a defined account list and modest request volume.
- 15 RPS · 5 TPS
- 10 WebSocket connections
- 100 subscriptions / connection · 1,000 total
- RPC + WebSocket
From $40
/ 30 days
Free trial up to 24h on request; our team confirms availability and setup. Solana wallet and USDC portal balance for purchase.
Bundle capacity by tier.
RPC is sold inside a Solana Bundle. Every tier includes WebSocket. Higher tiers add gRPC and, on GROW and PROFESSIONAL, ShredStream Raw.
On small screens, scroll the table to compare every quota and choose a plan.
| Bundle | RPS units/s | TPS | WS connections | gRPC | Raw shreds |
|---|---|---|---|---|---|
| STARTER | 15 | 5 | 10 | Not included | Not included |
| FOCUS | 25 | 10 | 20 | 1 stream | Not included |
| BUILD | 200 | 30 | 30 | 10 streams | Not included |
| GROW | 300 | 50 | 40 | 20 streams | FRA |
| PROFESSIONAL | 500 | 100 | 70 | 50 streams | FRA |
Crypto prepaid · 30-day periods
No per-request fee within plan limits.
RPS is shared by RPC calls, WS subscribe/unsubscribe and gRPC SubscribeRequest updates. Measured over a 10-second sliding window.
WebSocket is included. What are its other limits?
| Limit | STARTER | FOCUS | BUILD | GROW | PROFESSIONAL |
|---|---|---|---|---|---|
| Subscriptions / connection | 100 | 100 | 100 | 500 | 1,000 |
| Total subscriptions / plan | 1,000 | 5,000 | 5,000 | 10,000 | 25,000 |
Total subscriptions is an independent hard cap. Keep the connection alive with pings at most 60 seconds apart; idle timeout is 10 minutes. Some high-traffic subscriptions are blocked on shared WS. Check WS restrictions or explore WebSocket.
Send your first request.
- Sign in with a Solana wallet.Sign a message. No seed phrase is required.
- Choose a tier and request a trial.Our team confirms trial availability and setup for up to 24 hours. To buy a 30-day period, use your portal USDC balance on Solana.
- Save the token and connect.The token is shown once on issue. Use the endpoint and authentication instructions in Docs.
curl https://fra.sol.supanode.xyz:8899 \
-H 'Content-Type: application/json' \
-H 'x-token: YOUR_TOKEN' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "getSlot",
"params": [{"commitment": "confirmed"}]
}'{"jsonrpc":"2.0","result":350000000,"id":1}Illustrative response.
Before you connect.
A shared RPC endpoint handles on-demand requests. These details help you decide whether it fits the rest of your system.
Can I use this for continuous live updates?
WebSocket subscriptions are included in every Bundle. For filtered account and transaction streams at higher volume, compare Yellowstone gRPC, included from FOCUS. RPC remains useful alongside a stream for lookups.
How much replay does RPC provide?
Solana RPC provides two days of replay. For decoded analytical history with separate table coverage and retention, explore the Solana Indexer and check its data coverage.
How do tokens and authentication work?
Activate a paid Bundle in the portal, or request a free trial up to 24 hours from our team. Trial availability and setup are confirmed separately. Copy the token shown on issue. Send x-token or Authorization: Bearer with each RPC request. Missing or invalid tokens return HTTP 401. The Bundle token covers RPC, WS and included gRPC; other products have their own access procedures. Keep the token on your backend.
What happens when my trial ends?
Trial access ends at the agreed time. Purchase a paid 30-day Bundle in the portal to continue. Trials run for up to 24 hours on request, with availability and setup confirmed by our team. No credit card is required.
Will sendTransaction confirm my transaction?
After submission, track getSignatureStatuses or a signature subscription. Check execution errors, handle blockhash expiration and select the commitment your application needs.
When should I request Dedicated?
Consider Dedicated when shared plan capacity, the Frankfurt region or shared-node configuration does not fit. Hardware, region, capacity and pricing are agreed per deployment.