How many credits does a JSON page cost?
Structured JSON costs nothing extra on 4 APIs (Crawlbase, ScraperAPI, Scrappa and ZenRows), whose parsers cover the sites they support. AI extraction of any page to the fields you name costs more: from 4 credits on top of the HTML price (Firecrawl and ScrapeGraphAI) to 25 credits (ScrapeOps), and 5 credits on 4 of the 9 APIs that price it that way. On each API's smallest purchase, 1,000 AI-extracted pages cost from $0.70 (WebScraping.AI) to $38.00 (Browsable).
Worked out from each vendor's own pricing page; each vendor page on this site shows the day its price was read. Credits are for a plain request; JavaScript rendering or premium proxies add their own credits on top.| API | The page as HTML | The page as JSON | How the JSON is made | 1,000 JSON pages, smallest purchase |
|---|---|---|---|---|
| Crawlbase | 1 credit | 1 credit | Built-in scrapers, for the sites they cover | $0.50 on Starter |
| Diffbot | — | 1 credit | AI extraction of any page | $1.20 on Startup |
| ScraperAPI | 1 credit | 1 credit | Built-in parser, for the sites it supports | $0.49 on Hobby |
| Scrappa | 1 credit | 1 credit | Its endpoints answer in JSON | $0.30 on Starter credit pack |
| ZenRows | 1 credit | 1 credit | Automatic extraction | $0.42 on Build B1 |
| Firecrawl | 1 credit | 5 credits | AI extraction to your schema | $19.00 on Hobby |
| ScrapeGraphAI | 1 credit | 5 credits | AI extraction to your schema | $10.00 on Starter |
| Hyperbrowser | 1 credit | 6 credits | AI extraction to your schema | $6.00 on Startup |
| ScrapingBee | 1 credit | 6 credits | AI extraction to your schema | $1.18 on Freelance |
| ScrapingBot | 1 credit | 6 credits | AI extraction | $1.09 on Starter |
| WebScraping.AI | 1 credit | 6 credits | AI extraction to your fields | $0.70 on Personal |
| Browsable | 1 credit | 10 credits | AI-built scraper, 80 credits to create | $38.00 on Starter |
| Search1API | — | 10 credits | Extract endpoint (beta) | $7.60 on Basic |
| ScrapingDog | 1 credit | 11 credits | AI parser | $2.20 on Lite |
| ScrapeOps | 1 credit | 26 credits | AI extraction | $9.36 on 25,000 credits |
| ScrapingAnt | 1 credit | varies with the page | AI extraction, priced by the page's length | — |
A built-in parser returns the fields its authors chose, for the sites they support; AI extraction returns the fields you ask for, from any page, which is what the extra credits pay for. Markdown, which most AI pipelines want, costs no more than HTML on most of these APIs; the output formats page lists each one's formats and charges.
Two ways to get JSON, priced differently
A scraping API can turn a page into JSON in two ways. A built-in parser is code the vendor wrote for a known site, an Amazon product page or a Google results page, that returns a fixed set of fields; most vendors include it in the request price, but it works only on the sites it was written for. AI extraction sends the page to a language model with the fields you ask for, so it works on any page, and vendors charge for the model’s work with extra credits on each request.
What the extra credits buy
The extra charge covers the model reading the page, so it rises with how much the vendor’s model does: a fixed surcharge per page on most APIs, a charge by page length on others. The table counts the credits for a plain request. JavaScript rendering and premium proxies add their own credits, so a rendered page sent through AI extraction costs the rendering credits plus the extraction credits on most of these APIs.
When to pay for it
If a built-in parser covers your sites, use it: the JSON costs nothing extra. If your pages are varied, AI extraction saves writing and maintaining a parser for each site, and the per-page surcharge is the price of that. For large jobs on a few site layouts, fetching the HTML and parsing it yourself is usually cheaper than paying the surcharge on every page; the AI scraping API page prices extraction jobs at any volume.