Rate Limits

​

Billing Model

Firecrawl uses subscription-based monthly plans. We do not offer a pure pay-as-you-go model, but our auto-recharge feature provides flexible scaling—once you subscribe to a plan, you can automatically purchase additional credits when you dip below a threshold, with better rates on larger auto-recharge packs. For testing before committing to a larger plan, start with the Free or Hobby tier. Plan downgrades are scheduled to take effect at the next renewal, and unused-time credits are not issued.

​

Concurrent Browser Limits

Concurrent browsers represent how many web pages Firecrawl can process for you at the same time. Your plan determines how many of these jobs can run simultaneously - if you exceed this limit, additional jobs will wait in a queue until resources become available. Note that time spent waiting in the queue counts against the request’s timeout parameter, so you can set a lower timeout to fail fast instead of waiting. You can also check current availability via the Queue Status endpoint.

​

Current Plans

Each team has a maximum number of jobs that can be waiting in the concurrency queue. If you exceed this limit, new jobs will be rejected with a 429 status code until existing jobs complete. For larger plans with custom concurrency limits, the max queued jobs is 2,000 times your concurrency limit, capped at 2,000,000. If you require higher concurrency limits, contact us about enterprise plans.

​

Extract Plans (Legacy)

​

API Rate Limits

Rate limits are measured in requests per minute and are primarily in place to prevent abuse. When configured correctly, your real bottleneck will be concurrent browsers.

​

Current Plans

These rate limits are enforced to ensure fair usage and availability of the API for all users. If you require higher limits, please contact us at help@firecrawl.com to discuss custom plans.

​

Extract Endpoints

The extract endpoints share limits with the corresponding /agent rate limits.

​

Batch Scrape Endpoints

The batch scrape endpoints share limits with the corresponding /crawl rate limits.

​

Browser Sessions

While the /browser endpoint is in preview, each team can have up to 20 active browser sessions at a time. If you exceed this limit, new session requests will return a 429 status code until existing sessions are destroyed.

​

FIRE-1 Agent

Requests involving the FIRE-1 agent requests have separate rate limits that are counted independently for each endpoint:

​

Extract Plans (Legacy)