Rate limits and account tiers
Understand 20, 60 and 300 RPM tiers, output limits and the shared card-plus-crypto top-up limit.
Limits apply across your keys
Creating another key does not grant another account allowance. These are launch configuration values; final enforcement is subject to gateway verification.
| Tier | RPM | Max output / request | Top-up / rolling 24h |
|---|---|---|---|
| T0 | 20 | 8,192 tokens | $100.00 |
| T1 | 60 | 32,768 tokens | $500.00 |
| T2 | 300 | 131,072 tokens | $2,000.00 |
How tiers change
- T0: a new account.
- T1: at least USD 50 lifetime paid, at least 7 days old and no disputes.
- T2: at least USD 500 lifetime paid, at least 30 days old and no disputes.
- Custom limits: arranged manually with support.
Tier review is periodic, so eligibility does not guarantee an immediate promotion.
Output limits are enforced by the service
Omitting an output limit does not bypass the server limit. Requests exceeding it are clamped or rejected according to the verified gateway behaviour. A higher token limit does not guarantee that a model will produce that much output.
One top-up limit for card and crypto
Pending and completed checkouts count together within the rolling 24-hour window. A pending checkout can therefore temporarily reduce the amount you can add. Spending credit accumulated over previous days is allowed. This is a top-up limit, not a daily spending cap.
Prepaid balance and in-flight requests
The gateway reserves quota before forwarding requests and settles actual usage afterwards. Concurrent or in-flight requests can cause a small negative balance. Launch acceptance requires measured exposure no worse than USD 1 per user across all keys; this is a bounded exposure target, not an absolute zero-overspend guarantee.