Understand and handle Firecrawl HTTP error codes and rate limits

Documented steps

1. Authenticate every request with 'Authorization: Bearer fc-...'; a missing/invalid key returns 401.
2. StatusCode semantics: 200 success, 400 invalid parameters, 401 missing/invalid key, 402 payment required (insufficient credits), 404 resource not found, 408 request timeout, 429 rate/concurrency limit exceeded, 5xx server error.
3. For 408 or 5xx, inspect the specific errorCode Firecrawl returns, e.g. SCRAPE_TIMEOUT, SCRAPE_ALL_ENGINES_FAILED, SCRAPE_SSL_ERROR, SCRAPE_SITE_ERROR, SCRAPE_DNS_RESOLUTION_ERROR, SCRAPE_ACTION_ERROR, SCRAPE_UNSUPPORTED_FILE_ERROR.
4. On SCRAPE_TIMEOUT retry with a larger timeout parameter (max 60000ms). On SCRAPE_SSL_ERROR set skipTlsVerification:true. On SCRAPE_UNSUPPORTED_FILE_ERROR the file type is unsupported or exceeds the 10MB limit.
5. On 429, back off and retry later — you have exceeded your plan's rate or concurrency limits; check the rate-limits doc for your plan's caps.
6. On 402, top up credits; the job cannot be re-run until payment is resolved.