Solana JSON-RPC
Standard Solana JSON-RPC for reads and signed transactions, served from Frankfurt and included in every Bundle.
- All standard JSON-RPC methods
- Commitment: processed · confirmed · finalized
- IP-allowlist auth, 1 IP per Bundle
- RPS shared with gRPC, 10s window
- In every tier, STARTER → PROFESSIONAL
- Endpoint
- fra.supanode.xyz:8899 (Frankfurt)
- RPS — STARTER / FOCUS
- 15 / 25
- RPS — BUILD / GROW / PROFESSIONAL
- 200 / 300 / 500
- TPS by tier
- 5 → 100
- Aggregation window
- 10-second sliding window
- Heaviest method weight
- getProgramAccounts — 30 RPS units
- Auth
- IP allowlist, no x-token header
How is Supanode Solana RPC authenticated?
By IP allowlist — one IP per Bundle subscription. There is no x-token header on RPC. Requests from IPs outside the allowlist are rejected at the gateway.
What are the RPC rate limits?
RPS scales by tier: STARTER 15, FOCUS 25, BUILD 200, GROW 300, PROFESSIONAL 500, Dedicated unlimited. TPS scales from 5 to 100. RPS is shared between RPC HTTP calls and gRPC subscribe updates, measured over a 10-second sliding window.
Do all methods cost the same against my limit?
Most methods cost 1 RPS unit. Some cost more — getProgramAccounts is 30, getTransaction and getTokenAccountsByOwner are 10. Weights are identical on every plan; only the RPS budget changes.
What is a Solana RPC endpoint?
The HTTP gateway your application uses to talk to Solana: read balances and account state, fetch transactions and blocks, simulate calls, and submit signed transactions. Supanode serves the standard JSON-RPC API from Frankfurt, so existing Solana SDKs work after swapping the URL.
Does the Bundle include WebSocket subscriptions?
Yes. Every Bundle pairs HTTP RPC with standard Solana WebSocket subscriptions, scaling from 10 concurrent connections on STARTER to 70 on PROFESSIONAL. Subscribe and unsubscribe calls count against the same RPS budget as RPC requests.
Can I query historical Solana data over RPC?
Recent history, yes — getSignaturesForAddress plus getTransaction cover lookbacks within what the network retains; there is no separate archival tier. For deep DEX history, the Supanode Indexer holds normalized swap data since 2024-01-11, queryable with ClickHouse SQL.
What happens when I hit my rate limit?
Requests over budget return HTTP 429 — nothing is queued or extra-billed. Limits are measured over a 10-second sliding window, so short bursts above the per-second average are absorbed. Regular 429s are the signal to move up a tier or to a dedicated node.
How much does Solana RPC cost?
RPC ships inside the five flat Bundle plans, STARTER through PROFESSIONAL, billed per 30 days — every tier includes WebSocket, and gRPC joins from FOCUS up. Billing is crypto-only and prepaid, each tier carries an up-to-48-hour free trial, and exact rates live on the Solana pricing page.
When should I move from shared RPC to a dedicated node?
Shared tiers cover most workloads up to 500 RPS. Move to dedicated when you need unlimited RPS and TPS, single-tenant hardware, or a region other than Frankfurt — it is quoted per deployment within 24 hours.
Get Solana JSON-RPC.
Set up over Telegram with an engineer — endpoint, allowlist, tuning.