From 208e0a51be94ae41120a62ee03e47fd6f29b3fd4 Mon Sep 17 00:00:00 2001 From: "firecrawl-spring[bot]" <254786068+firecrawl-spring[bot]@users.noreply.github.com> Date: Fri, 15 May 2026 15:03:28 +0000 Subject: [PATCH] docs(rate-limits): remove off-topic Billing Model section The Billing Model section discusses auto-recharge, credits, and plan downgrades, which don't belong on a rate limits page. Removing it keeps the page focused on rate and concurrency limits. Co-Authored-By: micahstairs --- rate-limits.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/rate-limits.mdx b/rate-limits.mdx index a6b02fc2..f02b9315 100644 --- a/rate-limits.mdx +++ b/rate-limits.mdx @@ -7,12 +7,6 @@ og:description: "Rate limits for different pricing plans and API requests" Rate limits cap how many requests your team can make per minute, while concurrency limits cap how many jobs can run in parallel. Both are set by your plan; exceeding either returns a `429` response. See [Errors](/api-reference/errors) for the full error catalog and a retry-with-backoff snippet. -## Billing Model - -Firecrawl uses subscription-based monthly plans. There is no pure pay-as-you-go model, but the **auto-recharge feature** provides flexible scaling. Once you subscribe to a plan, you can automatically purchase additional credits when you dip below a threshold. Larger auto-recharge packs offer better rates. To test before committing to a larger plan, start with the Free or Hobby tier. - -Plan downgrades take effect at the next renewal. Unused-time credits are not issued. - ## Concurrent Browser Limits Concurrent browsers control how many pages Firecrawl can process for you in parallel. Your plan sets the ceiling; any jobs beyond it wait in a queue until a browser frees up.