firecrawl-rate-limits

# Firecrawl Rate Limits ## Overview Firecrawl enforces rate limits per API key measured in requests per minute and concurrent connections. When exceeded, the API returns `429 Too Many Requests` with a `Retry-After` header. This skill covers backoff strategies, request queuing, and proactive throttling. ## Rate Limit Tiers | Plan | Scrape RPM | Crawl Concurrency | Credits/Month | |------|-----------|-------------------|---------------| | Free | 10 | 2 | 500 | | Hobby | 20 | 3 | 3,000 | | Standard | 50 | 5 | 50,000 | | Growth | 100 | 10 | 500,000 | | Scale | 500+ | 50+ | Custom | Concurrent crawl jobs count against concurrency limits. If the queue is full, new jobs are rejected with 429. ## Instructions ### Step 1: Exponential Backoff with Jitter ```typescript import FirecrawlApp from "@mendable/firecrawl-js"; const firecrawl = new FirecrawlApp({ apiKey: process.env.FIRECRAWL_API_KEY!, }); async function withBackoff<T>( operation: () => Promise<T>, config = { maxRetries: 5, baseDelayMs: 1000, maxDelayMs: 32000 } ): Promise<T> { for (let attempt = 0; attempt <= config.maxRetries; attempt++) { try { return await operation(); } catch (error: any) { if (attempt === config.maxRetries) throw error; const status = error.statusCode || error.status; // Only retry on 429 (rate limit) and 5xx (server error) if (status && status !== 429 && status < 500) throw error; // Exponential delay with random jitter to prevent thundering h...