How to get your Firecrawl API usage, balance and spend programmatically
What the Firecrawl API exposes
| Signal | Firecrawl |
|---|---|
| Balance | Yes. GET /v2/team/credit-usage |
| Spend history | No |
| Cost breakdown | No |
| Plan and quota | Yes |
| Cost on each response | No |
| Rate-limit headers | None |
| Credential | API key |
Call it yourself
Credential. A normal Firecrawl API key (fc-…).
Credits
curl https://api.firecrawl.dev/v2/team/credit-usage \ -H "Authorization: Bearer $FIRECRAWL_API_KEY"
{
"success": true,
"data": {
"remainingCredits": 1742,
"planCredits": 3000,
"billingPeriodStart": "2026-10-01T00:00:00Z",
"billingPeriodEnd": "2026-11-01T00:00:00Z"
}
}Trimmed to the fields Argus reads. Values are examples.
Gotchas
- Credits aren't dollars. One credit is roughly one page.
- There's no pay-as-you-go. Without auto-recharge packs, every call returns 402 once credits hit zero.
- Firecrawl also has /v2/team/credit-usage/historical. Argus doesn't need it; burn comes from the hourly remainingCredits series.
How Firecrawl charges
Monthly subscription credits (1 credit ≈ 1 page); no pure pay-per-use. Optional auto-recharge credit packs roll over.
| Plan | Monthly price |
|---|---|
| Free | $0 |
| Hobby | $19 |
| Standard | $99 |
| Growth | $399 |
Free allowance. 1,000 a month.
At zero. 402. No PAYG; without auto-recharge packs, hard stop when credits run out.
- 500 requests per minute, per team. Per-team, per-plan; 10 (Free) → 7,500 (Scale).
Or let Argus track it
Paste the key once. Argus keeps the ledger, and your coding agent reads it through the MCP server.
- Reads the Firecrawl balance every hour and keeps the series, so you get burn per day (top-ups never count as negative spend) and days until it hits zero.
- Tracks the plan: the allowance, what's used this period, the reset date, and when you cross into overage.
- With the SDK, itemizes each call by endpoint and prices it at Firecrawl's per-operation rates.
- Emails you on low balance, days to zero, a spend spike, or projected overage.
- Hands all of it to your coding agent over MCP, so it can ask what a run cost or how much runway is left without leaving the editor.
> what has firecrawl cost today, and how long until it runs out?
get_overview → firecrawl: mtd spend, burn per day, days to zero
get_request_costs { "provider": "firecrawl", "limit": 25 }
get_advisories → credits_low, spend_spike, rate_limit_low …Questions
- Does Firecrawl have an API for its balance?
- Yes. GET https://api.firecrawl.dev/v2/team/credit-usage returns remaining credits, the plan's credits and the billing period.
- Can I get Firecrawl spend per day from the API?
- Not as a series. Derive it from how much the balance drops each day, ignoring top-ups.
- What happens when Firecrawl credits run out?
- Requests fail with HTTP 402. No PAYG; without auto-recharge packs, hard stop when credits run out. Auto-recharge is available.
- What key does Argus need for Firecrawl?
- A normal Firecrawl API key (fc-…).
Related
What each provider actually exposes over its API, how to put balances, daily spend and plan quotas on one ledger, and where you'll have to estimate.
A runaway loop, a forgotten cron, a retry storm: how to find the call that's draining a balance, from the burn rate down to the endpoint.
The balance endpoint, auth header and response field for every major metered API, and the ones that only show a balance in the console.
Days to zero is balance over burn rate. The hard part is the burn rate: top-ups, daily buckets and credits that aren't dollars.
The balance call for each provider, side by side.
Pricing and limits verified 2026-07-20 against firecrawl.dev/pricing, docs.firecrawl.dev/rate-limits. Endpoints are the ones the Argus Firecrawl connector calls.
Connect a provider key, point Claude Code or Cursor at the Argus MCP server, and ask what the last run cost.