Pricing Overview
Firecrawl CLI is a fully open-source command-line tool distributed under a permissive license at no cost. The CLI itself has zero licensing fees, no paid tiers, and no premium upgrades. You install it via npm (npm install -g firecrawl-cli) or through the one-line skill installer (npx -y firecrawl-cli@latest init --all --browser), and every feature ships in the same free package.
However, Firecrawl CLI is a client for the Firecrawl API platform. While the CLI binary costs nothing, every scrape, search, map, crawl, and browser session it executes consumes credits on your Firecrawl API account. The real cost of using Firecrawl CLI depends entirely on which Firecrawl API plan you subscribe to and how many credits you burn through.
Firecrawl's API platform offers four tiers:
| Plan | Monthly Price | Credits / Month | Overage Rate |
|---|---|---|---|
| Free | $0 | 500 | Not available |
| Hobby | $16 | 3,000 | $0.01 per extra credit |
| Standard | $83 | 50,000 | Tiered overage |
| Growth | $333 | 500,000 | Tiered overage |
The self-hosted option sidesteps API credits entirely. By running Firecrawl on your own infrastructure and pointing the CLI at your local instance (firecrawl --api-url http://localhost:3002 scrape), you pay nothing beyond your own compute costs.
Plan Comparison
Because Firecrawl CLI exposes the full API surface regardless of plan, the differentiator across tiers is volume and concurrency, not feature gating. Every plan gets access to scrape, search, map, crawl, browser sandbox, and all output formats.
| Feature | Free | Hobby ($16/mo) | Standard ($83/mo) | Growth ($333/mo) |
|---|---|---|---|---|
| Scrape, Search, Map | Yes | Yes | Yes | Yes |
| Browser Sandbox | Yes | Yes | Yes | Yes |
| All Output Formats | Yes | Yes | Yes | Yes |
| Monthly Credits | 500 | 3,000 | 50,000 | 500,000 |
| Concurrency Limit | Low | Moderate | Higher | Up to 100 parallel jobs |
| Overage Allowed | No | Yes | Yes | Yes |
| Self-Hosted Option | Yes | Yes | Yes | Yes |
| Priority Support | No | No | Yes | Yes |
The CLI itself adds no restrictions. If your API key has access to a capability, the CLI can use it. The firecrawl --status command shows your real-time credit balance and concurrency ceiling so you always know where you stand.
Hidden Costs and Considerations
Credit burn rate varies by operation. A simple markdown scrape of a single URL costs one credit. But operations like firecrawl search "query" --scrape --scrape-formats markdown first perform a web search (consuming credits per result) and then scrape each result page. A search with 10 results that also scrapes each one could consume 11 credits in a single command.
Browser sessions are credit-intensive. Launching a cloud browser session with firecrawl browser launch-session and executing commands within it consumes credits for each interaction. If you chain multiple execute calls for navigation, clicking, and scraping, costs accumulate quickly.
AI agent usage multiplies consumption. Firecrawl CLI is designed to be used by AI coding agents like Claude Code, Antigravity, and OpenCode. When an agent autonomously decides to scrape, search, or browse, it can issue dozens of CLI calls in a single session without human oversight. Setting a credit budget or monitoring usage through firecrawl --status is essential.
Self-hosting trades API credits for infrastructure costs. Running your own Firecrawl instance eliminates per-credit charges but requires maintaining servers, handling scaling, and managing browser dependencies. For teams doing fewer than 50,000 operations per month, the Standard plan at $83/month is likely cheaper than running dedicated infrastructure.
No vendor lock-in. The CLI is open source, so you can fork it, modify it, or replace the backend. Switching between the hosted API and a self-hosted instance requires changing only the --api-url flag or an environment variable.
Cost Estimates by Team Size
| Team Size | Typical Usage Pattern | Recommended Plan | Monthly Cost |
|---|---|---|---|
| Solo developer | Light scraping, occasional search | Free | $0 |
| Solo developer (heavy) | Daily scraping and search workflows | Hobby | $16/mo |
| Small team (3-5) | Multiple agents running scrape/search tasks | Standard | $83/mo |
| Mid-size team (6-15) | Continuous crawling, browser automation, research workflows | Growth | $333/mo |
| Large team (15+) | High-volume pipelines, multiple concurrent agents | Self-hosted or Enterprise | Custom |
For a solo developer running a few dozen scrapes per day, the Free tier's 500 credits cover about 16 scrapes per day across a 30-day month. A small team with three AI agents each running 50 operations per day would need roughly 4,500 credits per month, making the Standard plan at $83/month the cost-effective choice.
How Firecrawl CLI Pricing Compares
Firecrawl CLI occupies a unique position: the tool itself is free, but the underlying API service drives real costs. This model differs from most developer tools in the same category.
| Tool | Pricing Model | Starting Price | Free Tier |
|---|---|---|---|
| Firecrawl CLI | Open Source (API credits) | $0 (CLI) / $16 (Hobby API) | 500 credits/month |
| Retool | Freemium | $0 | Yes |
| Appsmith | Freemium | $0 | Yes, then $15/mo |
| Claude Usage Tracker | Freemium | $4/user/month | Yes |
Retool and Appsmith are internal tool builders rather than web scraping CLIs, so direct price comparison has limited value. The more relevant comparison is against other scraping solutions. Firecrawl CLI's advantage is that the CLI layer is genuinely free and open source -- you only pay for API consumption when using the hosted service. Teams that self-host pay nothing beyond their own server costs.
The credit-based model rewards efficiency. If your scraping patterns are well-defined and your agents are configured to minimize redundant requests, the effective per-page cost on the Standard plan works out to roughly $0.0017 per credit. For teams already invested in AI agent workflows, Firecrawl CLI provides a low-friction entry point with predictable scaling costs tied directly to usage volume.