From 26943d6c15e1d5ba461f801b6c4761ecb2dca0f6 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 15 Sep 2026 12:12:23 +0000 Subject: [PATCH 1/4] Document API key spend limits and key names on the billing page Add an "API key spend limits" section to billing.mdx. It covers renaming a key, setting a per-key credit limit, the day, week and month intervals, who can set a limit, and the search carve-out. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_017gT8R64Yuvq8jQszkLdtQo --- billing.mdx | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/billing.mdx b/billing.mdx index 1e98afa5e..6ca14ff66 100644 --- a/billing.mdx +++ b/billing.mdx @@ -169,6 +169,23 @@ For example, a limit of 25 USD allows five increments each month. A limit of 22 Credits that you buy manually do not count toward this limit. +## API key spend limits {#api-key-spend-limits} + +A spend limit caps the credits that one API key can use. The cap applies to that key alone, whatever your team balance is. Use it to stop one key from spending the whole team balance. + +You can also rename any API key. This includes the key named **Default** that Firecrawl creates with your team. + +The key owner or a team admin can do both. Open the [API keys page](https://www.firecrawl.dev/app/api-keys) in the dashboard, then open the menu on the key. + +- Click **Rename** to change the **Key Name**. +- Click **Set limit** to open **Set a spend limit**. Enter a **Credit limit**, pick **per day**, **per week** or **per month**, then click **Save**. + +A limit is a number of credits, not an amount of money. A limit of `1` means one credit per period. Click **Remove limit** to clear the limit. + + +**A spend limit does not cap search.** The limit applies to credit usage. The Search endpoint bills a separate search credit meter, so search usage does not count toward a credit limit. + + ## Upgrading and Downgrading - **Upgrades** take effect immediately. You are charged the full new-plan price today (no proration), and your billing cycle resets. Your next renewal is one month or one year from the upgrade date. Any unused credits from your previous plan carry over, and your new credit allotment and concurrency limits apply right away. From f1cc780ddc3036e72b41c93275d1bab1f7ac7fec Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 15 Sep 2026 12:59:36 +0000 Subject: [PATCH 2/4] Soften the search carve-out in the spend limit note The note said flatly that a spend limit does not cap search. Verification against live billing data proved the mechanism, not the absolute claim: search is metered on a separate search credit meter and does not count toward a key's credit limit, but search overflow into the main credit balance is untested against the cap. The note now states that search does not stop at the limit, and that search still spends credits: the search allowance first, then the main balance. No heading, anchor or other copy changes. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_017gT8R64Yuvq8jQszkLdtQo --- billing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/billing.mdx b/billing.mdx index 6ca14ff66..27008068c 100644 --- a/billing.mdx +++ b/billing.mdx @@ -183,7 +183,7 @@ The key owner or a team admin can do both. Open the [API keys page](https://www. A limit is a number of credits, not an amount of money. A limit of `1` means one credit per period. Click **Remove limit** to clear the limit. -**A spend limit does not cap search.** The limit applies to credit usage. The Search endpoint bills a separate search credit meter, so search usage does not count toward a credit limit. +**A spend limit applies to credit usage and does not stop Search.** Search requests are metered on a separate search credit meter, so they do not count toward a key's credit limit. Search still consumes your credits: it draws from your search credit allowance first, then from your main credit balance. ## Upgrading and Downgrading From 91a769c3922c1f3ef14a133fb755d25b4781e265 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 15 Sep 2026 13:28:45 +0000 Subject: [PATCH 3/4] Drop the search note from the spend limit section Autumn confirmed that a per-key credit limit applies to search and to every other endpoint. Two orgs reconcile exactly: org credit usage equals the sum of billed credits, search included. The earlier carve-out evidence was invalid, because that org's month-interval counter did not cover the search date and the org held a separate search grant. The note is removed, not reversed. The section states what a limit does and does not need to list endpoints. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_017gT8R64Yuvq8jQszkLdtQo --- billing.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/billing.mdx b/billing.mdx index 27008068c..a8bfcda62 100644 --- a/billing.mdx +++ b/billing.mdx @@ -182,10 +182,6 @@ The key owner or a team admin can do both. Open the [API keys page](https://www. A limit is a number of credits, not an amount of money. A limit of `1` means one credit per period. Click **Remove limit** to clear the limit. - -**A spend limit applies to credit usage and does not stop Search.** Search requests are metered on a separate search credit meter, so they do not count toward a key's credit limit. Search still consumes your credits: it draws from your search credit allowance first, then from your main credit balance. - - ## Upgrading and Downgrading - **Upgrades** take effect immediately. You are charged the full new-plan price today (no proration), and your billing cycle resets. Your next renewal is one month or one year from the upgrade date. Any unused credits from your previous plan carry over, and your new credit allotment and concurrency limits apply right away. From 3a444f0aa2bb3ab3196ba65780b1eb5776d9df48 Mon Sep 17 00:00:00 2001 From: Gaurav Chadha <65453826+Chadha93@users.noreply.github.com> Date: Tue, 15 Sep 2026 13:34:32 -0400 Subject: [PATCH 4/4] Update billing.mdx