🚦Solana RPC Limits

A reference guide to Shyft's RPC rate limits, supported methods, common errors, and how to resolve them.

Everything you need to know about Shyft RPC in production — plan rate limits, method restrictions, common error codes, and troubleshooting guidance. If something isn't working, start here.

Plan Rate Limits

Shyft enforces separate rate limits for standard RPC calls and index-heavy calls. Index calls — such as getProgramAccounts, getTokenAccountsByOwner, getTokenLargestAccounts, and getTokenAccountsByDelegate — are significantly more resource-intensive and are rate-limited separately from standard RPC calls.

Unlimited RPC Plan Limits

Feature	FREE	BUILD	GROW	ACCELERATE
Total Credits	Unlimited	Unlimited	Unlimited	Unlimited
RPC req/sec	10	100	150	400
Index req/sec	0	10	20	40
sendTransaction/sec	1	20	40	80
Jito simulateBundle	✓	✓	✓	✓
Staked Connections	—	✓	✓	✓

Legacy RPC Plan Limits

Feature	FREE	HACK	LAUNCH	SCALE
Total Credits	Default	10 million	100 million	500 million
RPC req/sec	10	50	150	400
Index req/sec	0	10	20	20
sendTransaction/sec	1	10	40	80
Jito simulateBundle	✓	✓	✓	✓
Staked Connections	—	✓	✓	✓

Frequently Asked Questions

What happens when credits run out on limited plans?

On all paid plans — Build, Grow, and Accelerate — credits are unlimited, so you will never run out. Credits only apply to legacy limited plans. If you are on HACK plan and exhaust your credits, requests stop until the next billing cycle. Calls do not stop on LAUNCH & SCALE, as these plans have overages. Overage pricing is available on select legacy plans — please check out Shyft pricing for details.

Are other Jito RPC methods available besides simulateBundle?

Currently, only simulateBundle is supported on Shyft RPC. Other Jito-specific methods — including sendBundle, getBundleStatuses, getInflightBundleStatuses, and getTipAccounts — are not available. simulateBundle allows you to preview the effects of a bundle of transactions before submission, including account state changes and compute unit consumption, without executing it on-chain. If you need to send bundles, you will need to route those calls directly to the Jito Block Engine.

Why am I getting rate limited even though I am within my RPC req/sec limit?

Shyft enforces separate rate limits for standard RPC calls and index calls. If you are making calls like getProgramAccounts, getTokenAccountsByOwner, getTokenLargestAccounts, or getTokenAccountsByDelegate, these are counted against your index req/sec limit — which is lower than your standard RPC req/sec limit. Similarly, sendTransaction has its own separate limit. Check which method is triggering the 429 and compare it against the correct limit for that method type.

Is a Solana devnet RPC endpoint available?

Yes. Shyft provides a devnet RPC endpoint at:

https://devnet-rpc.shyft.to/?api_key={your_api_key}

Use your standard Shyft API key to authenticate. Devnet is useful for testing integrations before deploying to mainnet.

Why am I getting no response or a timeout on getProgramAccounts calls?

getProgramAccounts is one of the most resource-intensive calls on Solana. Shyft enforces a 1-second timeout on gPA calls, and unfiltered gPA calls are blocked entirely. If your call is timing out, the most likely cause is an insufficiently filtered query returning too large a result set. We have recently released an update that brings getProgramAccounts response times to under 10ms for supported programs. Coverage for all major DEXes is being rolled out progressively.

How do I handle 429 rate limit errors?

You are likely hitting your plan's rate limit for standard RPC, index, or sendTransaction calls — each has a separate limit. To resolve this: separate your index calls from standard RPC calls and rate-limit them independently, cache responses where possible to reduce total call volume, or upgrade to a higher plan if you are consistently hitting limits. If you are running a bot, many popular tools such as Metis have built-in rate limit configuration — reducing the request rate in your bot's settings is often the fastest fix.

Where do I reach out in case of any questions?

For any queries, you can reach out via the support chat on your Shyft dashboard or join the Shyft Discord. The team is happy to help with plan questions, integration issues, or anything else.