What's available

Solana JSON-RPC methods supported on Supanode, with method weights for the RPS budget.

// updated 2026-06-04

Supanode implements the standard Solana JSON-RPC specification and supports every method that isn't on the Restrictions list.

For the full method reference with parameters and response shapes, see the official Solana RPC docs.

Method categories

Category	Sample methods	Notes
Account state	`getAccountInfo`, `getMultipleAccounts`, `getBalance`, `getProgramAccounts`	`getProgramAccounts` is heavy - see weights
Transactions (read)	`getTransaction`, `getSignaturesForAddress`, `getSignatureStatuses`	Historical lookups
Transactions (send)	`sendTransaction`, `simulateTransaction`	Counted as TPS, not RPS
Slots and blocks	`getSlot`, `getBlock`, `getBlocks`, `getBlockHeight`, `getLatestBlockhash`
Tokens	`getTokenAccountsByOwner`, `getTokenAccountBalance`, `getTokenSupply`, `getTokenLargestAccounts`
Network info	`getEpochInfo`, `getEpochSchedule`, `getInflationRate`, `getInflationGovernor`, `getVersion`
Validators	`getVoteAccounts`, `getLeaderSchedule`

Some methods cost more than 1 RPS unit per call. The weight table is the same on every plan - only your RPS budget changes.

Method	Cost (RPS units)
`getProgramAccounts`	30
`getTransaction`	10
`getTokenAccountsByOwner`	10
`getTokenAccountsByDelegate`	10
`getTokenLargestAccounts`	10
`getMultipleAccounts`	5 RPS units per 100 accounts (high-throughput batched) or 2 RPS units per account (standard)
`getAccountInfo`	2
`getTokenAccountBalance`	2
All others	1

For detailed RPS limits per plan, see Limits.

All methods support three commitment levels via the commitment parameter:

If you don't pass commitment, the default is finalized.

RPS budget and method weights.

Edge cases and the method-weight budget.

Code in 4 languages.