Every available method we document, with limits read straight from the gateway configuration. On Pro and Ultra two ceilings apply to each call: the plan's shared budget, and for some methods a separate per-second counter. Enterprise has neither. How enforcement works
Enterprise runs on 16 dedicated cores with no per-method counter and no shared cap. Total throughput lands around ~100,000 requests per second, though the real figure depends on the methods you call. Talk to sales
Snapshot 2026-08-28 · Solana mainnet
| Transactions and signatures11Sending, simulating, and confirming. The hot path for most trading systems. | ||||
|---|---|---|---|---|
| send | 50 RPS | 200 RPS | Unlimited | 4× |
| simulate | 50 RPS | 100 RPS | Unlimited | 2× |
| confirm | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | 50 RPS | 100 RPS | Unlimited | 2× |
| get | 50 RPS | 100 RPS | Unlimited | 2× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | 10 RPS | 50 RPS | Unlimited | 5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| Jito bundles and tips5Bundle submission and status. Ultra lifts every counter in this group. | ||||
| send | 10 RPS | 50 RPS | Unlimited | 5× |
| simulate | 10 RPS | 50 RPS | Unlimited | 5× |
| get | 20 RPS | 50 RPS | Unlimited | 2.5× |
| get | 20 RPS | 50 RPS | Unlimited | 2.5× |
| get | 20 RPS | 50 RPS | Unlimited | 2.5× |
| Accounts and program state7Account reads run on the shared limit. Scans are metered separately because they are expensive. | ||||
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | 10 RPS | 30 RPS | Unlimited | 3× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| Tokens5Balance and supply lookups are shared. Owner and largest-holder scans are metered. | ||||
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | 10 RPS | 30 RPS | Unlimited | 3× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | 10 RPS | 30 RPS | Unlimited | 3× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| Blockhashes and fees8Everything you need to build and price a transaction. All shared, no separate counters. | ||||
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| is | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| Blocks12Block and range fetches carry the tightest counters here. Metadata calls run several times higher on both plans. | ||||
| get | 10 RPS | 30 RPS | Unlimited | 3× |
| get | 10 RPS | 30 RPS | Unlimited | 3× |
| get | 10 RPS | 30 RPS | Unlimited | 3× |
| get | 50 RPS | 100 RPS | Unlimited | 2× |
| get | 50 RPS | 100 RPS | Unlimited | 2× |
| get | 50 RPS | 100 RPS | Unlimited | 2× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| minimum | Shared 200 | Shared 500 | Unlimited | 2.5× |
| Slots and leaders8Slot tracking and leader schedule lookups. All shared, poll them freely. | ||||
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| Cluster, epoch, and inflation13Health checks and chain metadata. Only inflation rewards carries its own counter. | ||||
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
| get | 50 RPS | 100 RPS | Unlimited | 2× |
| get | Shared 200 | Shared 500 | Unlimited | 2.5× |
Only methods currently available on these plans are shown, and the Enterprise column is hidden on narrow screens because every row reads Unlimited. Limits apply to Solana JSON-RPC only. WebSocket subscriptions, Yellowstone gRPC streams, and Shredstream are counted separately, and those allowances are on the pricing page.
A call to a metered method has to satisfy its own per-second counter and the shared global limit. Whichever runs out first is the one that returns a 429.
A method with no separate counter draws on whatever is left of the shared budget: 200 RPS on Pro, 500 RPS on Ultra.
One budget covers the whole gateway user. Issuing more API keys splits the same allowance rather than adding to it.
Enterprise runs on 16 dedicated cores with no per-method limit and no shared cap. Total throughput lands around ~100,000 requests per second, but the real number depends on which methods you call: a getProgramAccounts scan costs far more per request than a getSlot.
The Pro and Ultra numbers are plan defaults. A user-specific override replaces them for that account, so a single heavy method can be raised without moving tier.
On Ultra, sendTransaction is metered at 200 RPS and getLatestBlockhash has no separate counter. Send 200 transactions a second and you are at the method ceiling, with 300 RPS of the shared 500 still free for blockhashes, account reads, and status polling. Push blockhash polling to 310 RPS and the shared limit runs out first, so your sends start failing even though sendTransaction is not exceeding its 200 RPS method cap.
Send us your method mix and peak requests per second. We will tell you whether Pro covers it, whether Ultra is the honest answer, or whether you want a per-method override instead.