Guide updated
Implemented from official v2 usage, OpenAPI and billing documentation reviewed on 2026-10-17. Real-team credentials, signed-in navigation, privileges and reconciliation await user testing. No login, crawl, top-up or permission changes were performed.
- Required credentials
- Firecrawl API key for the intended team (fc- prefix)
- Monitoring unit
- Credits · team work units, not currency (XXX)
- What is monitored
- Reported team work Credits remaining · not cash
- Only fixed GET https://api.firecrawl.dev/v2/team/credit-usage with Bearer authentication, no query/body or redirects. firecrawlCredits.remainingCredits is the authenticated key's team allowance. planCredits excludes coupon/PAYG additions: never subtract to infer usage or a percentage. Cash, cost, monetary budget, runway and API availability fields are null.
Check team Credits without hosting a key
- Sign in to the Firecrawl app and select the team actually used by your application.
- Open Billing and inspect team Credits, plan and additional allowances separately—not cash or a single-key cap.
- Reconcile the actual period and async settlement; do not guess missing dates or sum shared keys.
Connect Firecrawl · team work Credits to Quota Monitor
Select the correct Firecrawl team
Open the official app, select the team used by your application, then open API Keys. A personal account, another team or a Quota Monitor project name cannot substitute for that scope.
Inspect the existing plan and team Credits in Billing first. Do not buy a plan or enable PAYG for monitoring; reconcile the official capability of your existing team.
Create a dedicated key and store it privately
Use the new-key action on API Keys and name the separate credential QuotaMonitorCredits (Rename is available in the key menu). Save the full fc- secret privately, not a key ID or masked suffix. Signed-in creation navigation still requires user verification.
Ordinary keys can execute paid work; no quota-only read scope is published. Avoid a critical application key. If hosting this risk is unacceptable, use manual Billing below without submitting a secret.
Understand the real permission boundary
The existing key menu's Set limit can cap daily/weekly/monthly Credit spending, but a cap is not read-only access. You need not change caps or privileges for this connection; preserve existing security settings.
Enterprise Restrictions limit endpoint groups/output formats; /v2/team/* metadata remains reachable. No account-only configuration is documented. An empty allowlist is unrestricted, not deny-all; no permission JSON is invented. Do not upgrade or request access for this feature.
Choose the work-Credits connection in your project
In your Quota Monitor project, add a connection, select Firecrawl · team work Credits and enter a name. MCP-generated secure setup links use the same provider. Never send the key in AI conversations or tool arguments.
There are no currency, team/project/key filters or monetary budget settings. XXX means non-currency, not USD. A Quota Monitor project does not create a Firecrawl wallet or divide the team's allowance.
Paste the complete key only into the masked field
Paste the full fc- monitoring secret into the secure form's password input and save. Do not add Bearer, a URL or JSON. Credentials are encrypted; other views show only the last four characters. Syntax validation does not prove the correct team or privileges.
The help drawer reuses this public guide without reading or submitting input. Close it to continue; clear cancelled input. Never include a secret in a screenshot, support ticket or chat.
Refresh and reconcile the original fields
Wait for the first sync or use the quota refresh action, then check a new successful-query time. remainingCredits is primary; planCredits and reported dates are separate. Missing optional fields mean unknown, not zero.
remainingCredits=7500 and planCredits=5000 can be valid: do not display negative usage or 150% remaining. Balance, cost, percentageRemaining and providerAvailable stay null; there is no USD conversion.
Compare with Billing for the same team
Return to that team's Billing. Compare remaining Credits, plan and extra allowances, plus the latest successful time separately. The endpoint does not report independent balances for each addition type, so their difference cannot identify them.
billingPeriodStart/billingPeriodEnd are reported cycle boundaries, not a promise that every Credit resets/expires together. Retry later while asynchronous jobs settle; never substitute calendar month-start, a guessed time zone or top-up date for missing dates.
Troubleshoot and rotate safely
For 401/403, check the complete key, selected team, revocation and existing access. For 404 check official endpoint availability; wait before retrying 429. Do not run a paid crawl to test. Request/schema failures retain the old successful snapshot/time, not a fresh query.
Rotate only the dedicated monitoring key through the secure update form. Confirm success before retiring that old monitoring credential; leave application keys alone. Never provide login Cookies, top up, elevate roles or alter permissions to debug; share only non-secret error codes.
What Quota Monitor reads from Firecrawl · team work Credits
- Keys, tools and Quota Monitor projects share the team allowance; this is not a single-key cap. Do not sum duplicate connections or convert work units into dollars or refundable funds.
- remainingCredits may exceed planCredits. The latter excludes coupon/PAYG additions; individual purchased, bonus or coupon balances cannot be inferred from their difference.
- Only reported billingPeriodStart/billingPeriodEnd are shown; missing/null means unknown. Actual renewal, annual monthly cycles and specific rollover rules differ from a universal expiry/reset of all extra Credits.
- Async work may settle later, so fetch time is not a settlement watermark. Zero/negative Credits do not prove all work is blocked under PAYG or other billing rules. No low-cash or monetary runway alerts apply.
- Credits and billing dates are reported snapshots, not a settlement watermark. Missing dates stay unknown; period end is not a universal reset/expiry date. Failed refreshes retain the old value and time.
Firecrawl · team work Credits FAQ and troubleshooting
- Why is this not a cash balance?
- Credits are work units for tasks such as crawling. This reads team remainingCredits, not a wallet, invoice or rated cost. No universal dollar conversion applies. A key spend limit is also separate from team Credits.
- Is remaining above the plan an error?
- Not necessarily. planCredits excludes coupon/PAYG additions, so the scopes differ. Values are reported without deriving usage, percentages or an individual extra balance from subtraction.
- Can the key be made read-only?
- No applicable account-only scope was found. Normal keys can execute paid work; spend caps are not read-only. Empty Enterprise allowlists are not deny-all. Do not invent permission JSON, upgrade or change privileges to experiment.
- Does period end reset all Credits?
- No. Only billingPeriodStart/billingPeriodEnd are reported; missing dates stay null/unknown. Renewal, specific rollover, purchases and coupons follow different rules. Period end is not a universal expiry date.
- Do zero/negative Credits or old values mean downtime?
- Not necessarily. PAYG and delayed async settlement affect usable work; providerAvailable remains unknown. Failed sync keeps the previous value and time. Check official team Billing as well.
- How do I handle 401, 403, 404, 429 or malformed data?
- Check the complete fc- key for the same team and existing access. Wait for 429; report persistent non-secret codes to official support. Missing remainingCredits or invalid dates/numbers fails instead of becoming zero. Never submit Cookies, run paid crawls or change roles.
Official Firecrawl · team work Credits references
- Official reference · docs.firecrawl.dev/api-reference/endpoint/credit-usage(opens in a new tab)
- Official reference · docs.firecrawl.dev/api-reference/v2-openapi.json(opens in a new tab)
- Official reference · docs.firecrawl.dev/billing(opens in a new tab)
- Official reference · docs.firecrawl.dev/features/key-restrictions(opens in a new tab)
- Official reference · docs.firecrawl.dev/api-reference/introduction(opens in a new tab)
- Official reference · docs.firecrawl.dev/introduction(opens in a new tab)
Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.