Rate Limits
The Burn & Claim API enforces per-tier rate limits to ensure fair usage and platform stability.
Tiers
Your rate limit tier is determined by your Burn & Claim subscription plan.
| Tier | Plan | Requests/minute | Monthly quota |
|---|---|---|---|
| Spark | Free | 30 | 10,000 |
| Flame | Flame | 120 | 100,000 |
| Blaze | Blaze | 300 | 500,000 |
| Inferno | Inferno | 600 | Unlimited |
Rate limits apply per API key. If you have multiple keys, each has its own limit.
Response headers
Every API response includes rate limit headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests per minute for your tier |
X-RateLimit-Remaining | Requests remaining in the current 1-minute window |
Retry-After | Seconds until the rate limit resets (only on 429 responses) |
429 Too Many Requests
When you exceed either the per-minute rate limit or the monthly quota, the API returns:
{
"statusCode": 429,
"message": "Rate limit exceeded",
"error": "Too Many Requests"
}The Retry-After header tells you how many seconds to wait before retrying:
HTTP/1.1 429 Too Many Requests
Retry-After: 12
X-RateLimit-Limit: 30
X-RateLimit-Remaining: 0Monthly quota
Each tier includes a monthly request quota. When the quota is exhausted, all requests return 429 until the next calendar month. The message field distinguishes rate limiting from quota exhaustion:
"Rate limit exceeded"— per-minute throttle"Monthly quota exceeded"— monthly cap reached
Tips
- Batch operations. Use
buildTransactionswith multiple items in a single call rather than one call per item. - Cache read-only endpoints.
getStatsandgetLeaderboardchange infrequently. Cache responses for 30-60 seconds. - Monitor your usage. The Burn & Claim Dashboard shows your current usage and remaining quota.
The TypeScript SDK handles 429 retries automatically.
Last updated on