Solana Public RPC Endpoints

Solana Mainnet Public RPC Endpoint

Mainnet is the live Solana network using real SOL. The public JSON-RPC endpoint is https://api.mainnet-beta.solana.com. It is shared and rate-limited, so use it for quick reads, transaction simulation, and low-volume dApp calls, not sustained production traffic.

You can test basic connectivity with a JSON-RPC call such as: curl https://api.mainnet-beta.solana.com -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"getSlot"}'

For OnFinality managed Solana endpoints and network details, see the Solana network page.

• HTTP and WebSocket access to standard Solana JSON-RPC methods.
• No API key required, but IP-based rate limits apply.
• Shared capacity; heavy methods such as getProgramAccounts may be throttled.
• Use api.mainnet-beta.solana.com for mainnet; verify current limits in official Solana documentation.

Solana Devnet Public RPC Endpoint

Devnet is for development and testing only; it uses test SOL and is not production. The public endpoint is https://api.devnet.solana.com. You can get test SOL from the official faucet at https://faucet.solana.com or via Solana CLI (solana airdrop).

Do not send real SOL to Devnet addresses. Use Devnet to test transactions, smart contracts, and RPC methods without risking mainnet funds.

See Solana Devnet guide and Devnet network page for setup and cluster details.

• Endpoint: https://api.devnet.solana.com
• Faucet: https://faucet.solana.com
• Test SOL has no real market value.
• Local option: run solana-test-validator for a private local cluster during early development.

Public RPC Rate Limits

Public endpoints enforce rate limits to protect shared infrastructure. Limits are applied per IP address and can change without notice. Do not assume a fixed request-per-second number; check the current Solana cluster documentation before integrating.

When you exceed the limit, the endpoint may return HTTP 429 Too Many Requests or HTTP 403 Forbidden, or drop the connection. Handle these errors with exponential backoff, caching, and reduced polling.

WebSocket subscriptions also share capacity and may be disconnected under load.

• Rate limits apply to HTTP and WebSocket connections.
• HTTP 429 and 403 are common signals of shared capacity exhaustion.
• Apply backoff and retry logic for transient errors.
• Cache expensive calls such as getProgramAccounts and getSignaturesForAddress.
• Consider batching multiple JSON-RPC calls in one request where the endpoint supports it.

When Public RPC Is Enough

Public RPC endpoints are suitable for prototypes, learning exercises, one-off scripts, hackathons, and low-volume development. They work well when occasional failures or latency spikes do not affect user experience.

For CI and automated tests, use a local validator (solana-test-validator) or Devnet to avoid consuming public endpoint quota. Public endpoints are also fine for small private betas with limited traffic.

• Local scripts and manual balance checks.
• Development and testing on Devnet.
• Hackathons and short-lived demos.
• Low-traffic personal wallets or dashboards where temporary unavailability is acceptable.

Why Public RPC Is Not Recommended for Production

Public endpoints are shared by all users, so another team's traffic spike can degrade your response times. There is no capacity guarantee, no SLA, and no one to contact when the endpoint becomes unavailable.

Public RPCs generally do not provide archive depth, so historical state queries may fail. WebSocket subscriptions can drop, and heavy methods may be throttled without warning. For production workloads, a dedicated Solana node or managed RPC service is required to isolate your traffic and provide predictable performance.

• No uptime guarantee or support contract.
• Rate limits can change at any time.
• Archive data is usually not available on public nodes.
• WebSocket connections may be unstable or limited.
• Shared infrastructure creates noisy-neighbor performance risk.

Public RPC vs Managed Solana RPC

Managed Solana RPC services provide private or higher-tier shared endpoints with defined capacity, HTTP/WebSocket access, archive support, and operational visibility. OnFinality offers managed Solana RPC endpoints and dedicated Solana nodes for teams that need isolated resources.

For detailed provider criteria, see the best Solana RPC provider guide. The table below compares the main decision factors.

• Managed services may offer dedicated nodes and archive support; verify current plan details.

Frequently Asked Questions