Solana RPC, on the same interface as every other chain.
Iteradian provides a managed Solana Mainnet RPC endpoint. It accepts Solana JSON-RPC 2.0 methods such as getSlot and getLatestBlockhash, and routes them across a pool of managed Solana nodes with an enforced rate limit, fall-forward failover and per-request usage analytics.
POST https://api.iteradian.com/rpc/v1/sol-mainnet
- Slug
- sol-mainnet
- Aliases
- sol-mainnet, solana-mainnet
- Status
- No healthy node right now — see status
- Verified
Why use a managed Solana endpoint?
Solana uses its own JSON-RPC method set rather than the eth_* dialect, and its high throughput makes endpoint stability the dominant factor in client-side reliability. Iteradian runs periodic health checks on every node in the pool and moves a request forward to the next healthy node when one stops answering.
How do I connect to Solana?
- 01
Create an API key
Sign up for Iteradian and create a key in the dashboard. Production keys are prefixed
itrd_live_and test keysitrd_test_. The plaintext key is shown exactly once, so store it in a secret manager — never in source control. - 02
Send a JSON-RPC 2.0 request
cURL curl -X POST https://api.iteradian.com/rpc/v1/sol-mainnet \ -H "Content-Type: application/json" \ -H "X-Api-Key: itrd_live_YOUR_KEY" \ -d '{"jsonrpc":"2.0","id":1,"method":"getSlot","params":[]}'TypeScript const res = await fetch("https://api.iteradian.com/rpc/v1/sol-mainnet", { method: "POST", headers: { "Content-Type": "application/json", "X-Api-Key": process.env.ITERADIAN_API_KEY!, }, body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "getSlot", params: [], }), }); const { result } = await res.json();Python import os, requests res = requests.post( "https://api.iteradian.com/rpc/v1/sol-mainnet", headers={"X-Api-Key": os.environ["ITERADIAN_API_KEY"]}, json={"jsonrpc": "2.0", "id": 1, "method": "getSlot", "params": []}, ) print(res.json()["result"]) - 03
Handle throttling
Requests past your plan’s per-second rate or concurrency ceiling return HTTP 429 with JSON-RPC error code
-32005and aretryAftervalue inerror.data. Past the monthly allowance, requests run as metered overage until the plan’s overage cap, then return 429 with-32007. Throttled requests are recorded in your usage and request log too — nothing is dropped silently.
Common Solana RPC methods
| Method | Description |
|---|---|
| getSlot | Returns the slot that has reached the configured commitment level. |
| getBalance | Returns the lamport balance of an account. |
| getAccountInfo | Returns all information associated with an account. |
| getLatestBlockhash | Returns the latest blockhash, required to build a transaction. |
| sendTransaction | Submits a signed transaction to the cluster. |
Solana RPC pricing
| Plan | Price | Included |
|---|---|---|
| Free RPC | $0/mo | 25 requests per second · 10 concurrent connections · 3,000,000 requests per month included · 3 API keys · Hard cap at the monthly allowance, no overage billed |
| Developer RPC | $39/mo | 250 requests per second · 100 concurrent connections · 25,000,000 requests per month included · 10 API keys · Overage $0.005 per 1,000 requests, capped at $150 per billing period |
| Professional RPC | $169/mo | 500 requests per second · 500 concurrent connections · 80,000,000 requests per month included · 25 API keys · Overage $0.003 per 1,000 requests, capped at $350 per billing period |
| Dedicated RPC | Custom | Custom requests per second · Custom concurrent connections · Unlimited monthly requests · Unlimited API keys · Dedicated infrastructure |
Solana RPC FAQ
01How do I get a Solana RPC endpoint?
Create an Iteradian account, generate an API key, and send JSON-RPC 2.0 requests to https://api.iteradian.com/rpc/v1/sol-mainnet with the key in an X-Api-Key header (Authorization: Bearer also works). New organizations start with a 7-day free trial.
02What happens if I exceed the Solana rate limit?
The request receives HTTP 429 with a JSON-RPC error body. Code -32005 means your organization's per-second rate or concurrency limit — retry after `error.data.retryAfter` seconds. Code -32006 means the monthly quota is used up (`error.data.resetsAt` says when it resets) and -32007 means the overage spend cap is reached; retrying either cannot succeed until the period resets or the plan changes. Limits are shared by all of the organization's keys.
03What happens if a Solana node goes down?
The gateway fails a request over to another healthy Solana node automatically, across up to 3 nodes. Transaction submissions are sent to one node and never retried or replayed by the gateway, so it cannot broadcast a transaction twice. If every node fails, the response is HTTP 503.
04Which Solana RPC methods are supported?
Iteradian forwards JSON-RPC 2.0 requests to the Solana node, so the methods available are the methods that node exposes. Batch requests are supported (a batch of N calls counts as N requests). Subscriptions work over the WebSocket endpoint wss://rpc.iteradian.com/ws/v1/sol-mainnet with the same API key.