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

# Plans & limits

> v3 rate limits and credit allowances, and how the granular call pattern changes consumption.

## Plans

| Plan       | Price / mo | Price / yr | Rate limit (req/min) | Credits / month |
| ---------- | ---------- | ---------- | -------------------- | --------------- |
| Sandbox    | \$0        | \$0        | 10                   | 10,000          |
| Basic      | \$29       | \$290      | 30                   | 100,000         |
| Advanced   | \$149      | \$1490     | 60                   | 600,000         |
| Pro        | \$475      | \$4750     | 100                  | 2,000,000       |
| Business   | \$949      | \$9490     | 200                  | 5,000,000       |
| Enterprise | Custom     | Custom     | Custom               | Custom          |

See the [pricing page](https://cryptorank.io/public-api/pricing) for the authoritative, current figures.

## What changed from v2

**Monthly credit allowances are unchanged.** If you were on Basic, you still have 100,000/month.

**Rate limit (RPM) changed.** v2 applied a flat 100 req/min on every plan. v3 sets a per-plan RPM, from 10 (Sandbox) to 200 (Business).

<Warning>
  The per-minute rate limit is now plan-specific. it may be lower or higher than
  before.
</Warning>

## How the new pattern affects consumption

Because a single screen or workflow now maps to several granular calls instead of one `full-metadata` response. You pay for only the info you actually use.

<Tip>
  Use [`GET /v3/status`](/api-reference/system/api-plan-&-usage-status) to read
  your current plan, RPM, and credit usage for the active billing period. Poll
  it to monitor quota and build adaptive throttling.
</Tip>