> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solanatracker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Credits and Rate Limits

> Credit costs, monthly quotas, and rate limits for Solana Tracker dedicated RPC plans — including per-method weights and concurrent request limits.

<Tip>
  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.
</Tip>

## 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. Some names below are compatibility aliases or older Solana method names; use the method pages in this docs site for the exact supported request shape.

* `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)
* `getTokenAccountsByOwners` - **1 credit per call** (custom optimized method)

<Tip>
  Use `getProgramAccountsV2` and `getTokenAccountsByOwnerV2` instead of their standard counterparts to reduce credit consumption by 90%.
</Tip>

### 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

| Plan             | Monthly Credits | General RPS | Send Transaction RPS | getProgramAccounts RPS | DAS API RPS | WebSocket Connections |
| ---------------- | --------------- | ----------- | -------------------- | ---------------------- | ----------- | --------------------- |
| **Free**         | 500,000         | 10          | 1                    | 1                      | 2           | 2                     |
| **Developer**    | 15,000,000      | 60          | 5                    | 15                     | 10          | 25                    |
| **Business**     | 100,000,000     | 225         | 50                   | 25                     | 50          | 100                   |
| **Professional** | 220,000,000     | 500         | 100                  | 50                     | 100         | 250                   |

<Note>
  Rate limits are enforced per second. Requests exceeding your plan limits return a `429 Too Many Requests` error.
</Note>

## 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

See the [Solana RPC WebSocket methods](/solana-rpc/accountsubscribe) or [Yellowstone gRPC guides](/yellowstone-grpc/index) when you need live updates.

### 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

<AccordionGroup>
  <Accordion title="What happens when I exceed my rate limit?">
    Requests exceeding your rate limit receive a `429 Too Many Requests` HTTP error. Implement exponential backoff and retry logic in your application.
  </Accordion>

  <Accordion title="Do unused credits roll over?">
    No. Credits reset at the start of each billing cycle and do not accumulate.
  </Accordion>

  <Accordion title="Can I upgrade mid-month?">
    Yes. Upgrades take effect immediately with the new credit allowance and rate limits. This will restart your subscription.
  </Accordion>

  <Accordion title="How do I track credit usage?">
    View real-time credit consumption and rate limit usage in your account dashboard.
  </Accordion>

  <Accordion title="What's the difference between V2 methods and standard methods?">
    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).
  </Accordion>
</AccordionGroup>

## Need Help?

Contact our support team at [contact@solanatracker.io](mailto:contact@solanatracker.io) for questions about your specific use case or to discuss custom plans.