Skip to Content
Rate Limits

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.

TierPlanRequests/minuteMonthly quota
SparkFree3010,000
FlameFlame120100,000
BlazeBlaze300500,000
InfernoInferno600Unlimited

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:

HeaderDescription
X-RateLimit-LimitMaximum requests per minute for your tier
X-RateLimit-RemainingRequests remaining in the current 1-minute window
Retry-AfterSeconds 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: 0

Monthly 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 buildTransactions with multiple items in a single call rather than one call per item.
  • Cache read-only endpoints. getStats and getLeaderboard change 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