Scraping API PricesAll products / Crawlbase
Crawlbase pricing
What Crawlbase Crawling API returns, how domain complexity and requests affect billing, where the current source conflicts, and priced alternatives.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Crawlbase counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
Crawlbase does not bill failed fetches, so failures cost nothing here.
- ?
Cash per month
Priced by quote
No published self-serve offer covers this volume, so the chain stops here rather than guessing a total.
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
By quote. No self-serve price covers this workload.
The vendor prices this volume by conversation, so no published total exists to check.
This is a finding about what Crawlbase publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.
Published exact bills for comparable products
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Crawlbase plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Crawling API Pay as you go | Not published | n/a | n/a | 20,000 request | n/a |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.basic | 1 request | request | source |
| request.js_render | 1 request | request | source |
What Crawlbase does not publish
- The dynamic calculator's numeric domain-complexity rates were not obtainable from the static page.
- General Crawling API concurrency was not published.
- Annual pricing does not apply to the public pay-as-you-go offer.
Product scope and returned result
Crawlbase Crawling API accepts a target URL and retrieves page content through rotating proxy and browser infrastructure. It offers a normal request path and a JavaScript-rendered path, and the response exposes a domain_complexity field that identifies the target tier Crawlbase assigned. The enterprise Crawler adds asynchronous bulk crawling, retries, webhook delivery, queue monitoring, and custom throughput, but keeps per-request billing aligned with Crawling API rates. (Crawlbase pricing and Crawling API documentation, retrieved 2026-07-26).
This scope is narrower than a general browser-control service and broader than a bare proxy. It returns retrieved page content rather than an interactive remote browser, while Crawlbase operates the proxy rotation and optional rendering. (Crawlbase pricing, retrieved 2026-07-26).
Every recorded meter
The stored record has two replacement meters: one basic request per basic request and one JavaScript-rendered request per JavaScript request. It also states that Crawlbase chooses a domain-complexity tier, and that the response field identifies which tier was billed. Billing applies only when page content is delivered successfully; failed and blocked retrievals are not charged. (Crawling API documentation and Crawlbase pricing, retrieved 2026-07-26).
There is an unresolved record contradiction. The record’s billing summary says JavaScript requests consume two request credits, while both structured meter entries store one request. The currently loaded static pricing page does not expose the numeric domain-tier rates, so this page cannot honestly choose a JavaScript multiplier or print a dollar rate. That conflict is in data/vendors/crawlbase.json, which is outside this content lane. (Crawlbase pricing and Crawling API documentation, retrieved 2026-07-26).
Contract path, minimum, and evaluation
The self-serve path starts with up to 20,000 free requests and no credit card. A buyer enters target domains into Crawlbase’s interactive estimator, chooses regular or JavaScript requests, and then starts free. There is no published monthly subscription floor for Crawling API. The exact paid unit price depends on the domain-complexity assignment, but the numeric rate was not present in the static source available to this record. (Crawlbase pricing, retrieved 2026-07-26).
For large asynchronous programs, Crawlbase directs buyers crawling over one billion pages per month to sales. A buyer should bring the target-domain list, expected URLs per month, regular versus JavaScript mix, required throughput, webhook and delivery requirements, and SLA or dedicated-support needs. The public page describes 30 URLs per second out of the box, with higher throughput handled case by case. (Crawlbase pricing, retrieved 2026-07-26).
Price status and why there is no fixed published price
Crawlbase does not expose one universal monthly price because the commercial unit is a successful request whose rate varies by assigned domain complexity. The pricing page does offer an interactive estimator, but the loaded static source did not reveal the numeric tier schedule. Stating an estimated rate from another site would be less accurate than leaving it unknown. (Crawlbase pricing, retrieved 2026-07-26).
Priced alternatives
- ScrapeNinja Basic starts at $0 per month, with separate JavaScript and non-JavaScript quotas. (ScrapeNinja pricing, retrieved 2026-07-26).
- WebScrapingAPI Starter starts at $19 per month for a page-retrieval API allowance. (WebScrapingAPI pricing, retrieved 2026-07-26).
- Scrape.do Hobby starts at $29 per month for successful-result credits and rendering or proxy modes. (Scrape.do pricing, retrieved 2026-07-26).
Answer
What Crawlbase costs, what it publishes, and what it does not. Every figure sourced and dated.
Recorded 2026-07-26 from the vendor's own pricing page.The published price on this page matched the vendor page when it was rechecked.