Skip to main content
Our API uses a credit-based system where different operations consume different amounts of credits. Most calls cost 1 credit, while resource-intensive operations cost 10 credits.

Credit Costs

Standard API Calls (1 Credit)

Most RPC methods cost 1 credit per call, including:
  • Account queries (getAccountInfo, getBalance, etc.)
  • Block queries (getLatestBlockhash, getBlockHeight, etc.)
  • Transaction submission (sendTransaction)
  • Priority Fee API calls
  • All other methods not listed below

Archival Data Calls (10 Credits)

Historical blockchain data retrieval costs 10 credits per call:
  • getTransaction - Transaction details
  • getBlock - Block information
  • getBlocks - Multiple blocks
  • getBlockTime - Block timestamps
  • getInflationReward - Inflation rewards
  • getConfirmedBlock - Confirmed block data
  • getConfirmedBlocks - Multiple confirmed blocks
  • getConfirmedTransaction - Confirmed transaction details
  • getConfirmedSignaturesForAddress2 - Confirmed signatures (v2)
  • getConfirmedSignaturesForAddress - Confirmed signatures
  • getSignaturesForAddress - All signatures for an address

Program Account Queries

  • getProgramAccounts - 10 credits per call
  • getTokenAccountsByOwner - 10 credits per call
  • getProgramAccountsV2 - 1 credit per call (custom optimized method)
  • getTokenAccountsByOwnerV2 - 1 credit per call (custom optimized method)
Use getProgramAccountsV2 and getTokenAccountsByOwnerV2 instead of their standard counterparts to reduce credit consumption by 90%.

Digital Asset Standard (DAS) API (10 Credits)

All DAS API methods cost 10 credits per call:
  • getAsset - Asset details
  • getAssetProof - Merkle proof for compressed NFTs
  • getAssetsByOwner - Assets by owner address
  • getAssetsByAuthority - Assets by update authority
  • getAssetsByCreator - Assets by creator address
  • getAssetsByGroup - Assets by collection
  • searchAssets - Search assets by criteria
  • getSignaturesForAsset - Transaction history for an asset
  • getTokenAccounts - Token account information
  • getNFTEditions - NFT edition details

Rate Limits by Plan

PlanMonthly CreditsGeneral RPSSend Transaction RPSgetProgramAccounts RPSDAS API RPSWebSocket Connections
Free500,000101122
Developer15,000,000605151025
Business100,000,000225502550100
Professional220,000,00050010050100250
Rate limits are enforced per second. Requests exceeding your plan limits return a 429 Too Many Requests error.

Optimize Your Credit Usage

Use Custom Methods

Replace expensive calls with optimized alternatives:
  • Use getProgramAccountsV2 instead of getProgramAccounts
  • Use getTokenAccountsByOwnerV2 instead of standard token account queries

Cache Responses

Store frequently accessed data to reduce redundant API calls. Implement caching for:
  • Static account data
  • Historical transactions
  • NFT metadata

Implement WebSockets

Subscribe to account or program updates instead of polling:
  • Real-time updates without repeated API calls
  • More efficient than polling for changes
  • Lower credit consumption

Batch Operations

Group multiple queries when the API supports batching to reduce overhead.

Monitor Usage

Track credit consumption in your dashboard to identify optimization opportunities and prevent overages.

Frequently Asked Questions

Requests exceeding your rate limit receive a 429 Too Many Requests HTTP error. Implement exponential backoff and retry logic in your application.
No. Credits reset at the start of each billing cycle and do not accumulate.
Yes. Upgrades take effect immediately with the new credit allowance and rate limits. This will restart your subscription.
View real-time credit consumption and rate limit usage in your account dashboard.
V2 methods like getProgramAccountsV2 are custom optimized implementations that provide the same functionality as standard methods but consume 90% fewer credits (1 credit vs 10 credits).

Need Help?

Contact our support team at [email protected] for questions about your specific use case or to discuss custom plans.
⌘I