ScraperAPI has acquired Traject Data

Firecrawl vs ScraperAPI: In-depth comparison and live tests

Firecrawl vs ScraperAPI: In-depth comparison and live tests

Deciding between Firecrawl and ScraperAPI comes down to your required data output and the cost structure per request.

Firecrawl is a web data API for AI agents. It has endpoints for Search, Scrape, Map, Crawl, Interact, Agent, Monitor, and Parse, returns markdown or schema-based JSON at one credit per page, ships an MCP server and a CLI, and publishes an open-source core.

ScraperAPI is web data infrastructure that runs the whole pipeline as one vendor. Its products cover each step:

  • ScraperAPI’s Crawler: finds pages by following links from a start URL.
  • ScraperAPI’s Scraping API: unblocks pages and returns HTML, markdown, JSON, or CSV.
  • ScraperAPI’s Async Scraper: scales to large batches of URLs.
  • ScraperAPI’s DataPipeline: schedules collection and sends results to a webhook.
  • ScraperAPI’s Structured Data Endpoints: return parsed JSON for Amazon, Google, ChatGPT, Walmart, eBay, Redfin, and more.

ScraperAPI acquired Traject Data, whose Rainforest API for Amazon, SerpWow API for Google and Bing, BlueCart API for Walmart, Countdown API for eBay, and RedCircle API for Target add purpose-built depth on the hardest sources.

This guide compares them on features, anti-bot handling, AI agent tools, security, and pricing. We also ran live tests: the same five URLs went through both tools, and we recorded the credits each request used.

Key takeaways

  • Firecrawl suits teams that want markdown or schema JSON from any URL for agents and RAG. The trade-off is that credits rise when JSON or other formats are switched on, and some sites, such as Reddit, are declined.
  • Neither tool is cheaper on every page, so the answer depends on what you scrape. Across four test runs on 5 November 2026, Firecrawl charged 1 credit on the JavaScript page, the Cloudflare test page, and the Amazon product page as markdown, against ScraperAPI’s 10, 10, and 5. On the JavaScript page, Firecrawl returned an empty page in three of the four runs.
  • ScraperAPI was cheaper on the static page and on typed Amazon JSON, returned all 10 quotes from the JavaScript page with render=true in every run, and returned a Reddit thread in four of four runs that Firecrawl declined.
  • ScraperAPI’s credits cost about half as much at the same plan size ($0.49 against $0.99 per 1,000 credits), which is why 5 ScraperAPI credits for the full Amazon product object cost less than 5 Firecrawl credits for two fields.

Firecrawl vs ScraperAPI at a glance

Criteria Firecrawl (prices checked in November 2026) ScraperAPI
Default output Markdown HTML (markdown, text, CSV, or JSON on request)
Entry paid plan Hobby, $19 a month for 5,000 credits Hobby, $49 a month for 100,000 credits
Price per 1,000 credits at 100,000 credits, monthly billing $0.99 (Standard, $99) $0.49 (Hobby, $49)
Free tier 1,000 credits a month, plus a keyless tier Free plan with 1,000 credits, plus a 7-day free trial with 5,000 credits
JavaScript pages Rendered in Chromium on every scrape render=true, 10 credits
Anti-bot handling Enhanced proxy at the same credit cost Four levels, from plain to ultra_premium, with published credit costs
Structured data JSON by schema on any URL, +4 credits Parsed JSON for Amazon, Google, Walmart, eBay, Home Depot, and Redfin
AI search results Not listed ChatGPT, Perplexity, Gemini, and Google AI Mode, 25 credits per prompt
Crawling Crawl at 1 credit per page, and Map at 1 credit per call Crawler with depth and credit-budget limits
Scheduling and batches Batch scrape, Monitor Async Scraper, DataPipeline, Crawler schedules
MCP server Yes Yes
Open source AGPL-3.0 core, self-hostable Hosted service

Why you might need a Firecrawl alternative?

Most teams look for Firecrawl alternatives with a specific limit in mind, not because the product is broken.

  • Credits multiply when you chain features: A basic scrape is one credit, but JSON extraction adds four credits per page, and Search adds two credits per 10 results plus the scrape cost of every result you scrape (Firecrawl billing).

A research step that searches, scrapes 10 results, and extracts JSON from each costs 2 + 10 × (1 + 4) = 52 credits by that arithmetic. At that rate, the 5,000 credits on Hobby cover about 96 such steps a month, where the same credits would cover 5,000 plain single-page scrapes.

The same table prices x.com at 30 credits per request and LinkedIn pages at 5 to 40 credits, because third-party providers answer them.

  • Agent sessions can use credits faster than you expect: An agent decides how many searches and scrapes to make, so spend isn’t visible until the plan runs low.

A user running a local research agent said one session with 20 to 30 fetches and searches used most of their free credits, and a Firecrawl employee replied that they didn’t understand why light use would use that many credits and asked for the call log (r/hermesagent).

The practical point for a variable-cost agent is to check the per-call credits in the dashboard before you leave it running, because the free plan has no pay-as-you-go and returns HTTP 402 when credits run out.

  • Some sites are declined on purpose: In our test, Firecrawl returned “we do not support this site” (HTTP 403) for a Reddit thread. In the Web Data Frontier Benchmark, a Firecrawl engineer wrote that the company blocks 10 of the benchmark sites, and Firecrawl passed 10 of 40 requests across eight social platforms (String’s comparison; String sells a competing product). If your pipeline needs social platforms, forums, or reviews, no Firecrawl plan fixes that, and you need a second tool for those sources.
  • Cached copies can be up to two days old: Firecrawl serves a cached copy of a page by default when it is newer than two days (maxAge of 172,800,000 ms), and setting maxAge: 0 to force a fresh fetch makes the request slower and, in Firecrawl’s words, “more likely to fail” (Firecrawl docs).

For price tracking, stock levels, or news monitoring, a two-day-old page is a wrong answer delivered quickly, so you have to decide per job whether to accept stale data or a slower, less reliable request.

  • The self-hosted build is not the Cloud product: The core is open source under AGPL-3.0, but Agent, Browser, managed dashboards, enhanced proxy paths, and enterprise controls are Cloud-only, and advanced anti-bot services need additional configuration (Firecrawl docs).

That makes self-hosting free in licence fees but not in effort, because you run the proxies, the browsers, and every upgrade. One r/LocalLLaMA user who had self-hosted for a year said an upgrade broke the MCP server and desktop-browser crawling, and that rolling back was “not easy and reliable”.

AGPL also asks anyone who runs a modified version as a network service to offer its source, so check with your legal team before building it into a product.

How we compared Firecrawl and ScraperAPI

We compared both tools on five criteria, then checked each against the vendor’s own pages and a live test.

Criteria Question it answers Where we checked it
Features What does one request return, and what else is included? Firecrawl and ScraperAPI docs, live tests
Anti-bot performance What does it cost to get a protected page? Credit tables, live tests, two public benchmarks
AI agents and integrations How do you connect it to an agent or workflow? Docs for both tools
Open source, security, and support Can you self-host, and what is promised? Pricing and docs pages
Pricing What does a page really cost? Pricing pages, response headers

Firecrawl vs ScraperAPI: Key features

Output formats

Firecrawl returns markdown by default and JSON, HTML, links, screenshots, or a summary on request. ScraperAPI returns HTML by default, and output_format switches any URL to markdown or text, while autoparse=true returns JSON or CSV for supported sites.

Output Firecrawl ScraperAPI
Markdown Default output_format=markdown
Raw HTML Yes Default
Typed JSON from any URL Schema or prompt, +4 credits AI Parser
JSON from named sites Not applicable Structured Data Endpoints and autoparse
CSV Not listed output_format=csv with autoparse

We tested markdown output on a static page and on a JavaScript page with ScraperAPI, and JSON on an Amazon product page with both tools. Firecrawl’s schema extraction returned the title and price we asked for, at five credits. ScraperAPI’s Amazon Product endpoint returned the full product object (32 fields, including name, pricing, availability, and images), also at five credits.

Terminal-style capture of the Amazon product test: Firecrawl JSON extraction returned 2 fields for 5 credits and ScraperAPI's Amazon Product endpoint returned 32 fields for 5 credits

 

Same Amazon product page through both tools. Source: our test

JavaScript rendering and browser actions

Firecrawl renders every page in Chromium and offers Interact and Agent for multi-step browsing. ScraperAPI renders on request with render=true, and its Rendering Instruction Set clicks, types, scrolls, and waits.

We tested ScraperAPI’s Rendering Instruction Set on Wikipedia by typing a search term, clicking search, and waiting for the results container. ScraperAPI returned the results page for 10 credits, the same as a plain render. ScraperAPI recommends three to four instructions per request, and screenshot=true turns on rendering and returns a PNG link in the sa-screenshot header. A ScraperAPI screenshot request cost 10 credits in our test, the price of a render.

Terminal-style capture of the Rendering Instruction Set test: three instructions typed a search term, clicked search and waited for results, and the response started with the Cowboy boot article for 10 credits

 

ScraperAPI Rendering Instruction Set on wikipedia.org. Source: our test

Search, crawl, and map

Firecrawl’s Search costs two credits per 10 results, Crawl costs one credit per page, and Map costs one credit per call, however many URLs it returns (Firecrawl docs). ScraperAPI’s Google Search endpoint returns parsed results, and ScraperAPI’s Crawler follows links on its own.

Firecrawl homepage with the headline Give your AI agents web data and beyond, and tabs for Search, Scrape, Map and Crawl

 

Firecrawl homepage. Source: firecrawl.dev

ScraperAPI’s Crawler starts from a URL, skips duplicate pages, stops at a link-depth or ScraperAPI credit-budget limit, posts results to a webhook, and runs on a schedule from hourly to monthly on paid plans. The free plan is limited to depth one. We started a Crawler job through the API and cancelled it. ScraperAPI’s Google Search endpoint returned eight organic results and eight related searches for 25 credits.

Structured data for named sources

Firecrawl extracts JSON from any page you describe, while ScraperAPI ships ready-made endpoints for the sources people scrape most. The difference is who writes and maintains the parser.

ScraperAPI’s Structured Data Endpoints cover Amazon (Product, Search, Offers), Google (Search, News, Jobs, Shopping, Maps), Walmart (Product, Search, Category, Reviews), eBay (Product, Search), Home Depot (Product, Reviews, Search), and Redfin (Agent, For Sale, For Rent, Search).

We tested Amazon, Google Search, Google News, Walmart, eBay, and Redfin, and each returned JSON at 5 to 25 ScraperAPI credits per request. On 5 November, Google News returned HTTP 500 on the first attempt without a charge and succeeded on a retry.

For deeper Amazon, Google, Walmart, eBay, and Target data, the Traject Data products that ScraperAPI acquired (Rainforest, SerpWow, BlueCart, Countdown, and RedCircle) return fields such as Buy Box owners, sellers, and deals.

Terminal-style capture of six Structured Data Endpoint tests, all HTTP 200, costing 5 credits for Amazon, Walmart and eBay, 10 for Redfin and 25 for Google Search and News

 

ScraperAPI Structured Data Endpoints. Source: our test

AI search results

ScraperAPI returns what ChatGPT, Perplexity, Gemini, and Google AI Mode answer for a prompt, with sources, as JSON. Firecrawl’s pricing page lists no endpoint that does this.

ScraperAPI’s AI Results endpoints cost 25 credits per prompt, or 75 with required sources on ChatGPT. We tested all four with the prompt “what is a web scraping api” on 5 November 2026, and each returned HTTP 200 for 25 credits on the first attempt: Perplexity with 10 sources, Google AI Mode with six, and ChatGPT and Gemini with none, which happens when the model answers without searching the web for that prompt.

Results vary by prompt and by day. In earlier tests on 26 October, Perplexity and Gemini each returned HTTP 500 on the first attempt and succeeded on a retry, and on 27 October Perplexity returned HTTP 500 twice for a different prompt, so build retries into any pipeline that depends on these endpoints.

They suit AI visibility tracking and answer monitoring.

Terminal-style capture of the AI Results test: ChatGPT, Perplexity, Gemini and Google AI Mode each returned HTTP 200 for 25 credits, with 1, 10, 0 and 6 sources

 

ScraperAPI AI Results endpoints. Source: our test

Parsing any site with AI

ScraperAPI’s AI Parser turns a page layout into a reusable parser. You send up to three example URLs of the same page type, and it generates a parser that extracts the fields from similar pages on that site.

The first parser on an account is free, and each extra parser, added field or modified field costs 30,000 ScraperAPI credits, up to five parsers on paid plans. Parsing a URL costs only the standard ScraperAPI scraping credits. Firecrawl’s schema extraction needs no training step, but charges four extra credits on every page.

Geotargeting, sessions, and devices

ScraperAPI’s country_code parameter routes a request through a proxy in that country, and the countries available depend on the plan.

Hobby and Startup cover the US and Europe, and Business and above add individual countries. session_number keeps one proxy for 15 minutes, device_type switches between mobile and desktop user agents, and Amazon ZIP code targeting is supported. Firecrawl also supports location: its location object takes an ISO country code and preferred languages, defaults to the US, and uses an appropriate proxy where one is available (Firecrawl docs), so check that your target country is supported before you rely on it.

Scale, scheduling, and delivery

ScraperAPI’s Async Scraper keeps retrying a job for up to 24 hours, takes batches of up to 50,000 URLs, and delivers to a webhook. ScraperAPI’s DataPipeline schedules projects of up to 100,000 URLs, keywords, ASINs, or Walmart IDs.

We submitted a ScraperAPI Async job for a static page, and the first status poll returned the finished result for one ScraperAPI credit. ScraperAPI’s DataPipeline returns HTML, JSON, or CSV through a webhook or download and keeps results for 30 days. Firecrawl offers batch scraping, concurrency by plan (5 to 100 browsers), and Monitor for change tracking. Readers on Reddit asked for alerts when scheduled jobs return nothing, and ScraperAPI’s dashboard shows error logs and success rates by domain. See ScraperAPI’s Async Scraper and DataPipeline guides.

Terminal-style capture of the Async API test: the job was submitted with status running, the first poll returned running, and the second poll returned finished for 1 credit

 

ScraperAPI Async API on docs.python.org. Source: our test

Firecrawl vs ScraperAPI: Anti-bot performance and success rates

Both tools unblock protected pages, but they price it differently. Firecrawl bills one credit and escalates its proxy automatically. ScraperAPI lets you choose the level and publishes what each one costs.

Firecrawl states that its enhanced proxy costs the same one credit as a basic request. ScraperAPI’s levels are plain (1 credit), render=true (10), premium=true (10), and ultra_premium=true (30). Domains protected by Cloudflare, DataDome, PerimeterX, or Akamai are unblocked automatically and cost 10 credits per scrape (credit table). Requests with ultra_premium=true can return a cached copy no older than 10 minutes, and cache_control=no-cache forces a live fetch. For a Cloudflare walkthrough, see how to bypass Cloudflare with ScraperAPI.

ScraperAPI credits and request costs table showing 1 credit for normal requests, 5 for ecommerce, 25 for SERP and 30 for social media

 

ScraperAPI credits and requests costs documentation. Source: docs.scraperapi.com

Two public benchmarks compare the tools, and they disagree on the size of the gap. Scrapeway measured average success of 81.2% for Firecrawl and 60.1% for ScraperAPI across 11 targets in October 2026. The Web Data Frontier Benchmark, run on 30 October 2026 on 100 protected sites, measured 81.2% for Firecrawl (sixth of 17) and 76.4% for ScraperAPI (ninth of 17). String built that benchmark and sells a competing product. In String’s September run, ScraperAPI scored 84.0% (third) and Firecrawl 80.2%, and String says ScraperAPI’s score rose from 64.2% in August after it corrected its own adapter.

A gap of 5 points in one benchmark and 21 in another, plus an order that flipped between runs, tells you the result depends on the targets and the setup, so we don’t quote a success rate here. Our own results are in the live tests below.

Firecrawl vs ScraperAPI: AI agents and integrations

Both tools connect to agents through an MCP server and a CLI. ScraperAPI adds a plugin, framework integrations, no-code nodes, and SDKs.

Integration Firecrawl ScraperAPI
MCP server Yes, with setup guides for Claude and Claude Code, ChatGPT and Codex, Cursor, Grok Build, Hermes Agent, OpenClaw, OpenCode, Amp, Windsurf, and Google Antigravity Remote server at mcp.scraperapi.com or a local one on Python or Docker, for Claude Code, Claude Desktop, Cline, Cursor, and Windsurf
CLI Yes (search, scrape, parse, crawl, map, interact, agent, and monitor commands) sapi CLI (scrape, cost, jobs, structured, crawler, pipeline, account)
Agent plugin and skills Skills for Codex, Claude Code, Cursor, and OpenCode, installed by the CLI Plugin with MCP tools and agent skills on the Claude Plugin Hub and ClawHub
Agent frameworks LangChain, LlamaIndex, CrewAI, CAMEL-AI, Praison AI, Neuron AI, Vercel AI SDK, and Mastra LangChain and LlamaIndex
No-code and workflow automation Zapier, Make, n8n, and Pipedream, plus the visual builders Dify, Langflow, and Flowise n8n node with templates and a Zapier app (beta)
SDKs Python, Node.js, Go, Java, Ruby, Rust, .NET, PHP, and Elixir Python, Node.js, PHP, Ruby, and Java

We used ScraperAPI’s MCP server while researching this guide to run Google searches, Amazon searches, and page scrapes from an agent. For a comparison of MCP, CLI, and skills, read MCP vs CLI vs skills. Firecrawl also lists app-builder and platform integrations (Replit, Lovable, Stripe Projects, and Vercel Marketplace) and Composio as a tool layer.

Firecrawl vs ScraperAPI: Open source, security, and support

Firecrawl is the one to pick if you need to self-host the core, and ScraperAPI is a hosted service.

Area Firecrawl ScraperAPI
Licence and hosting AGPL-3.0 core, self-hostable, with Cloud-only features Hosted service
Compliance SOC 2 Type 2, DPA on Standard and above GDPR and CCPA compliant
Support Community on Free, Basic on Hobby, Standard on Standard, Priority on Growth and Scale, and Dedicated on Enterprise; a shared Slack channel from Growth Priority support from Professional, and a dedicated support team and Slack support on Enterprise

Firecrawl states its AGPL-3.0 licence on its own comparison page. If you want a free self-hosted crawler without a vendor, Crawl4AI is the usual choice, but you run the proxies, browsers, and anti-bot layer yourself (String).

Firecrawl vs ScraperAPI: Pricing

Firecrawl pricing starts lower, at $19 a month, but ScraperAPI gives more credits per dollar at the same plan size. What a page costs depends on the feature, the target, and the plan, so compare the cost per 1,000 pages for your own URLs.

Firecrawl’s plans (prices checked in November 2026):

Plan Monthly price Annual price per month Credits per month Concurrent browsers
Free $0 $0 1,000 2
Hobby $19 $16 5,000 5
Standard $99 $83 100,000 25
Growth $399 $333 500,000 50
Scale $749 $599 1,000,000 100
Enterprise Custom Custom Custom Custom
Firecrawl pricing page showing Free, Hobby, Standard and Growth plans with credits per month and concurrent requests

 

Firecrawl pricing page. Source: firecrawl.dev/pricing

ScraperAPI’s plans:

Plan Monthly price Annual price per month ScraperAPI credits per month Concurrent threads
Free plan $0 $0 1,000 5
Hobby $49 $44.10 100,000 20
Startup $149 $134.10 1,000,000 50
Business $299 $269.10 3,000,000 100
Scaling $475 $427.50 5,000,000 200
Professional $975 $877.50 10,500,000 300
Advanced $1,975 $1,777.50 21,500,000 500
Enterprise Custom Custom 22,000,000 and above 500 and above
ScraperAPI pricing page showing Hobby, Startup, Business, Scaling and Professional plans with credits and concurrent threads

 

ScraperAPI pricing page. Source: scraperapi.com/pricing

ScraperAPI’s 7-day trial includes 5,000 credits and needs no card. The billing rules differ in ways that change the bill:

Rule Firecrawl ScraperAPI
Pay-as-you-go Every paid plan, in $5 increments up to a monthly limit you set Scaling plan ($475) and above, at a fixed per-credit rate up to a monthly cap
Credit rollover Annual Scale only, for one month None, credits reset at renewal
Failed or blocked pages A page that returns 403 or 404 still costs 1 credit, a scrape that returns no result is not charged A 404 costs credits because it is a real result: the site was reached and said the page does not exist. A 403 or 500 is not charged, because the request did not succeed. Requests cancelled before 70 seconds are charged
Spend controls Spend limits per API key, crawl limit max_cost per request, cost estimator, auto-upgrade on Hobby to Professional

Firecrawl’s rules come from its billing page.

For a full plan comparison, see ScraperAPI pricing.

How to avoid wasting credits

Check the cost before you scale, and cap it per request. ScraperAPI returns the cost of every request in the sa-credit-cost header, and its /account/urlcost endpoint returns the cost of a URL without scraping it. In our tests, it returned 5 for an Amazon product page and 30 for a LinkedIn company page.

max_cost caps a single request. We set max_cost=5 on a request that would have cost 10 ScraperAPI credits and got an HTTP 403 with no charge. ScraperAPI’s dashboard analytics page shows credits by domain, success rate, and error logs. Firecrawl’s per-key spend limits and monthly pay-as-you-go limit do the same job at the account level. Either way, price your own target list on both tools before choosing a plan.

Terminal-style capture of the cost-control tests: max_cost=5 with render=true returned HTTP 403, the urlcost endpoint returned 5 credits for Amazon and 30 for LinkedIn

 

ScraperAPI cost controls. Source: our test

Firecrawl vs ScraperAPI: Live test results on five URLs

We tested the same five URLs through both tools, four runs each on 5 November 2026, and read the credits and the returned page from each tool’s response. Firecrawl charged less on three of the five, but on the JavaScript page it returned an empty page in three of the four runs, and ScraperAPI returned the one page Firecrawl declined.

Terminal-style table of the five-URL test: credits per request for Firecrawl and four ScraperAPI levels across four runs. Firecrawl used 1 credit on four pages, returned an empty page on the JavaScript test in three of four runs, and was declined on Reddit; ScraperAPI used 1 to 30 credits depending on the level

 

The same five URLs through Firecrawl and ScraperAPI, four runs. Source: our test
URL Firecrawl ScraperAPI plain ScraperAPI render=true ScraperAPI premium=true ScraperAPI ultra_premium=true
docs.python.org/3 (static page) 1 credit, 200 1 credit, 200 10 credits, 200 10 credits, 200 30 credits, 200
quotes.toscrape.com/js (JavaScript page) 1 credit, empty page in 3 of 4 runs, all 10 quotes in 1 of 4 1 credit, empty page 10 credits, all 10 quotes 10 credits, empty page 30 credits, empty page
scrapingcourse.com/cloudflare-challenge 1 credit, passed 10 credits, passed in 2 of 4 runs 20 credits, passed in 2 of 4 runs 20 credits, passed in 2 of 4 runs 30 credits, passed in 4 of 4 runs
amazon.com/dp/B088NRLMPV (product page) 1 credit 5 credits 5 credits 5 credits 5 credits
Reddit thread in r/LocalLLaMA HTTP 403, site not supported, no charge 10 credits, partial page 20 credits, full thread in 4 of 4 runs 20 credits, partial page 30 credits, partial page

Static page

Both tools returned the page for one credit in all four runs. ScraperAPI’s plain request is the cheapest option here, and render, premium=true, and ultra_premium=true add cost without changing the result.

JavaScript page

Firecrawl charged one credit per run, but it returned the empty page without the quotes in three of the four runs and all 10 quotes in one. Three single requests a few minutes later returned all 10 quotes, so Firecrawl’s result on this page varies from run to run.

ScraperAPI’s plain request returned an empty shell without the quotes, and render=true returned all 10 quotes for 10 credits in all four runs. Firecrawl’s price is lower, and ScraperAPI’s result was the same every time.

Cloudflare test page

Both tools passed the Cloudflare challenge page. Firecrawl used one credit in all four runs. ScraperAPI’s plain request cost 10 credits, the price of the automatic bypass on Cloudflare-protected domains, and render=true and premium=true passed at 20, the level price plus the bypass price.

In two of the four runs, ScraperAPI’s plain, render, and premium requests each returned HTTP 500 and were not charged, while ultra_premium=true passed at 30 in all four runs. The other two runs passed at every level, so treat the first level you try as a starting point and retry or escalate when a request fails.

Amazon product page

Firecrawl returned the product page as markdown for one credit, and ScraperAPI returned it for five, the ecommerce rate. The size of ScraperAPI’s markdown varied between runs, from about 38,000 to about 211,000 characters, while the credits stayed at five. For typed data the cost evens out. Firecrawl’s schema extraction cost five credits for two fields, and ScraperAPI’s Amazon Product endpoint cost five credits for the full product object.

Reddit thread

Firecrawl declined the Reddit thread in all four runs with HTTP 403 and no charge. ScraperAPI’s plain request returned a partial page for 10 credits, and render=true returned the full thread in all four runs for 20 credits.

What the credits cost in dollars

The cost per 1,000 requests depends on the plan. This table uses Firecrawl Standard at $99 a month and ScraperAPI Hobby at $49 a month, which both include 100,000 credits.

Target Firecrawl Standard ScraperAPI Hobby
Static page $0.99 $0.49
JavaScript page $0.99 $4.90
Cloudflare test page $0.99 $4.90
Amazon product page as markdown $0.99 $2.45
Amazon product as typed JSON $4.95 $2.45

Firecrawl’s $0.99 for the JavaScript page counts every run, including the three that returned the empty page, because Firecrawl charged one credit each time.

On annual billing the credit prices fall to $0.83 per 1,000 for Firecrawl Standard and about $0.44 for ScraperAPI Hobby. Larger plans change the picture. ScraperAPI Business ($299 for 3,000,000 credits) brings a 10-credit render to about $1.00 per 1,000 requests, and Firecrawl Scale ($749 for 1,000,000 credits) costs $0.75 per 1,000 pages. A ScraperAPI AI Results prompt costs 25 credits, about $12.25 per 1,000 prompts on Hobby.

What the live tests do not show

The tests show what each request cost on five URLs, not how often each tool succeeds on your targets. Four runs of five URLs can’t produce a success rate, and the two public benchmarks above show how far results move with the target mix.

Run the test on your own URLs before you pick a plan. A Firecrawl engineer and a ScraperAPI account holder each gave the same advice on Reddit, which is to take 20 to 50 of the URLs your current setup misses and compare completeness, cost, and time. This script sends one URL to both tools, reads the credits from each response, and keeps your keys in environment variables.

import os
import requests

url = "https://quotes.toscrape.com/js/"

firecrawl = requests.post(
    "https://api.firecrawl.dev/v2/scrape",
    headers={"Authorization": f"Bearer {os.environ['FIRECRAWL_API_KEY']}"},
    json={"url": url, "formats": ["markdown"]},
    timeout=120,
).json()
meta = firecrawl["data"]["metadata"]
print("firecrawl", "credits =", meta["creditsUsed"], "chars =", len(firecrawl["data"]["markdown"]))

for label, extra in [("scraperapi plain", {}), ("scraperapi render", {"render": "true"})]:
    r = requests.get(
        "https://api.scraperapi.com",
        params={"api_key": os.environ["SCRAPERAPI_API_KEY"], "url": url, "output_format": "markdown", **extra},
        timeout=120,
    )
    print(label, "credits =", r.headers.get("sa-credit-cost"), "chars =", len(r.text))

On the JavaScript test page this prints:

firecrawl credits = 1 chars = 1505
scraperapi plain credits = 1 chars = 178
scraperapi render credits = 10 chars = 1609

Firecrawl vs ScraperAPI: Which should you choose?

Choose Firecrawl for markdown and schema JSON from arbitrary URLs, and ScraperAPI for parsed data from named sources, AI search results, and scheduled pipelines. Many teams use both.

If you need Choose Why
Markdown or typed JSON from any URL for an agent or RAG pipeline Firecrawl Markdown by default, schema extraction, one credit per page on the pages we tested
Documentation crawling with search and scrape under one key Firecrawl Crawl, Map, Search, and Interact in one API
To self-host the core Firecrawl AGPL-3.0 source, with Cloud-only extras
Parsed JSON for Amazon, Google, Walmart, eBay, Home Depot, or Redfin ScraperAPI Structured Data Endpoints from 5 credits, and Rainforest, SerpWow, BlueCart, Countdown, and RedCircle from Traject Data, which ScraperAPI acquired, for more depth
ChatGPT, Perplexity, Gemini, or Google AI Mode answers and sources ScraperAPI AI Results endpoints at 25 credits per prompt
Batch or scheduled collection at volume ScraperAPI Async Scraper (50,000 URLs per batch), DataPipeline, and Crawler schedules
Control over rendering, proxies, geotargeting, and cost per request ScraperAPI render, premium, ultra_premium, country_code, max_cost, and the cost estimator
Pages that Firecrawl declines ScraperAPI Reddit returned with render=true in four of four test runs

If you use both, send documentation and general pages to Firecrawl and the sources with endpoints, or the pages Firecrawl declines, to ScraperAPI. Other Firecrawl competitors cover different jobs, and ScraperAPI’s Apify alternatives and Bright Data alternatives guides compare them, so Firecrawl vs Apify readers can start there. More head-to-head pages are in ScraperAPI comparisons.

Firecrawl vs ScraperAPI FAQs

How much does Firecrawl cost to use for scraping data?

Firecrawl has a free plan with 1,000 credits a month, and paid plans from $19 a month (Hobby, 5,000 credits) to $749 a month (Scale, 1,000,000 credits), with a basic scrape costing one credit (Firecrawl pricing, checked in November 2026). JSON and similar formats add four credits per page.

Is there a free alternative to Firecrawl?

Yes. Crawl4AI, Crawlee, and Scrapy are free and open source, but you run proxies and anti-bot handling yourself. Among hosted tools, ScraperAPI’s free plan includes 1,000 credits and a 7-day trial adds 5,000 credits with no card, and Firecrawl’s free plan includes 1,000 credits a month.

Is Firecrawl expensive?

It depends on the features you use. A basic scrape is one credit, but JSON, Question, and Highlights formats add four credits per page, and a Search that scrapes its results adds the scrape cost of each one. Compare the cost per 1,000 successful pages on your own URLs rather than the headline plan price.

What are some alternatives to Firecrawl?

ScraperAPI is the alternative for parsed JSON from named sources, AI search results, and scheduled collection. Crawl4AI is the free self-hosted option, Apify offers ready-made scrapers, and Bright Data and Zyte cover enterprise unblocking. See the Apify alternatives guide for more.

What are the limitations of Firecrawl?

Credits rise with JSON and other formats, and an agent’s chained searches and scrapes can use a plan quickly. Firecrawl declines some sites on purpose, and our Reddit test returned “we do not support this site”. Cached copies up to two days old are returned by default, and the self-hosted build lacks the Cloud-only features.

Is Firecrawl open source?

The Firecrawl core is open source under AGPL-3.0 and can be self-hosted. Agent, Browser, managed dashboards, enhanced proxy paths, and enterprise controls are Cloud-only, and advanced anti-bot services need separate setup (Firecrawl docs).

Which scraping service is the best?

No single service wins on every target. Public benchmarks put the gap between Firecrawl and ScraperAPI anywhere from 5 to 21 points, so the best service is the one that returns your URLs at the lowest cost per successful page. Test 20 to 50 of your own URLs on each.

Start a free ScraperAPI trial with 5,000 credits and run your own URLs through the script above.

About the author

Picture of Sofi Grigoryan

Sofi Grigoryan

Sofi Grigoryan is a content marketer at ScraperAPI who turns technical web scraping topics into clear, practical guides. Sofi enjoys finding the simple way to explain proxies, data collection and the tools behind them, so developers and data teams can get to the answer faster.

Related Articles

Talk to an expert and learn how to build a scalable scraping solution.