Solana RPC credits and rate limits

RPC usage has two separate limits: credits measure consumption over a billing cycle, while rate limits control how quickly you can send requests. Check both when sizing a workload.

​

Credits per call

Older archive aliases (getConfirmedBlock, getConfirmedBlocks, getConfirmedTransaction, getConfirmedSignaturesForAddress, and getConfirmedSignaturesForAddress2) also cost 10 credits. Use the current method pages for supported request shapes. DAS pricing covers asset, proof, owner, authority, creator, group, search, signature, token account, and NFT edition queries. The V2 account queries cost 1 credit rather than 10. Check their pagination and response structure before replacing a standard method; they are not identical request and response formats.

​

Limits by plan

The Free plan has a €1 one-time charge and includes 500,000 credits. RPS means requests per second; the WebSocket column is the connection limit. Requests above your rate limit return HTTP 429 Too Many Requests. Slow the request queue and retry reads with bounded exponential backoff and jitter. Increasing concurrency does not increase the plan limit.

​

Keep usage predictable

• Use V2 program queries and V2 owner queries when their response format fits your app.
• Reuse results when freshness permits. Choose a cache lifetime based on the data and commitment level.
• Fetch several accounts with getMultipleAccounts when appropriate. Do not assume a JSON-RPC batch is charged as one method call.
• Use WebSocket subscriptions for live changes and HTTP to load or recover state.
• Track consumption in the RPC dashboard.

​

Billing cycle and upgrades

Credits reset at the start of each billing cycle; unused credits do not roll over. Upgrades apply the new allowance and limits immediately and restart the subscription. Review the dashboard before changing your plan. For account-specific billing or custom capacity, contact support.