Compare

How do I keep Crawlbase's site tiers from surprising my bill?

Read the tier Crawlbase reports on every billed response (the X-Domain-Complexity header) and send the domains it prices above standard, plus the requests it couldn't complete, to UpRock. Crawlbase sets each site's tier itself, from 1 to 20 times the base rate, and JavaScript doubles it, so at 100,000 pages a month 1,000 pages cost $0.76 on a standard site and up to $30.56 on its top tier with JavaScript. UpRock is $0.50 per 1,000 pages on any site.

Updated · Read as markdown

What Crawlbase does well

Crawlbase, around since 2017, sells one credit balance across its Crawling API, an asynchronous Enterprise Crawler, a residential proxy endpoint (Smart AI Proxy) and Cloud Storage. The Crawling API renders JavaScript, returns HTML, JSON or GitHub-flavored markdown (with an optional readability pass), takes screenshots and PDFs, and runs more than 100 built-in scrapers that return JSON at the price of a page. There are SDKs for Python, Node, Ruby, PHP, Go, Java and C#, integrations with LangChain, Zapier, n8n and Make, and an MCP server you can run yourself or use hosted. Pay as you go has no monthly fee, bills only successful requests and supports a hard spend cap.

If most of your pages are on ordinary sites and your volume is high, Crawlbase is hard to beat on price. Keep it.

What the tiers do to a page's price

Pay as you go runs on a graduated ladder: each month, the first 1,000 requests cost $3.00 per 1,000, the next 10,000 $2.00, the next 100,000 $0.60, the next million $0.50, the next 10 million $0.10, falling to $0.02. On top of that, Crawlbase puts every site in one of eight tiers: standard ×1, moderate ×1.5, complex ×2, complex I ×3, complex II ×4.5, extreme ×9, extreme I ×13.5 and extreme II ×20. JavaScript rendering doubles any tier.

Here's the blended cost of 1,000 pages at four monthly volumes, worked out the way Crawlbase's own estimator does it (the month's ladder total, times the tier, times 2 for JavaScript), with prices checked 25 Oct 2026:

Pages a monthStandardStandard, JavaScriptComplex, JavaScript (×4)Extreme, JavaScript (×18)Extreme II, JavaScript (×40)UpRock
10,000$2.10$4.20$8.40$37.80$84.00$0.50
100,000$0.76$1.53$3.06$13.75$30.56$0.50
1 million$0.53$1.06$2.11$9.50$21.10$0.50
10 million$0.15$0.29$0.59$2.65$5.89$0.50

Subscriptions swap the ladder for a monthly block of credits: Starter is $99 for 200,000 (about $0.50 per 1,000), Growth $599 for 2 million (about $0.30). The tiers come out of that block too. A standard page with JavaScript uses 2 credits and an extreme II page with JavaScript 40, so Starter covers 100,000 of the first or 5,000 of the second.

Three things the table can't show. You learn a site's tier from the X-Domain-Complexity header of a billed response, unless the site is one of the 356 in Crawlbase's Cookbook, which lists most at one credit and a few at 1.5 to 20. The docs name only three values for that header (standard, moderate and complex) while the pricing page lists eight tiers, so treat anything other than standard as a price you didn't plan for. And the pricing page says a tier multiplies "a group's whole ladder total" without spelling out how a month that mixes tiers fills the brackets, so the table assumes every page sits in one tier.

How Crawlbase reports a page it couldn't get

Crawlbase answers with three signals: the HTTP status of your request, a cb_status header with Crawlbase's verdict (formerly pc_status, which is still sent and is the only one on a 401), and original_status with the site's own answer. A crawl that failed comes back as HTTP 520 and isn't charged. Here's how we'd route each case, from Crawlbase's status-code docs (checked 25 Oct 2026):

What you seeWhat it meansSend to UpRock?
200, cb_status 200, original_status 200The pageNo: use it
200, cb_status 200, original_status 404 or 410The page is gone (billed)No: it's the site's answer
200, cb_status 207The site sent an empty body (billed)Yes (Crawlbase suggests its JavaScript token)
520, cb_status 705 or 706The site answered 403 or 429Yes
520, cb_status 503Crawlbase recognised a block or challenge pageYes
520, cb_status 704The site answered another error, in original_statusOnly if it's a 5xx
520, cb_status 599 or another 5xx to 7xxAn internal or site-specific failureYes
520, cb_status 595A css_click_selector wasn't on the pageNo: fix the selector
429, 500, 503, 504Concurrency limit (20 per token by default), an internal error, unavailable, or timed outYes
402, 403Your workspace spend cap or account limitYes, or raise the cap
401A missing or invalid tokenFix the token (the code sends it to UpRock meanwhile)
400A bad requestNo: fix it

Crawlbase and UpRock side by side

CrawlbaseUpRock
Price per 1,000 pages$3.00 down to $0.02 on the pay-as-you-go ladder, times the site tier and JavaScript (table above); subscriptions $99 to $599 a month$0.50 by card or USDC, $0.40 with UPT
Site tiersEight, from ×1 to ×20, set by Crawlbase; JavaScript ×2None: every page is one credit
Failed requestsNot billed; 404 and 410 areNot documented yet
Countries22 listed, and it may override the one you pass63, or a region
Where requests come fromResidential or datacenter exit nodes, chosen automatically; the docs we read don't say how the residential IPs are sourcedDevices whose owners opted in
Scrapers, screenshots, storage, async crawlsYesNo. One page per call
Concurrency20 requests per token by defaultNot published yet
MCP serverLocal or hostedYes, remote (streamable HTTP)
VideoScrapers for TikTok profiles, products and shop pagesSearch public video by moment, $1 per 1,000 searches
To try it1,000 free credits, up to 5,000 with setup steps, no cardPrepaid credits

Where Crawlbase is better: very low prices for standard sites at high volume, scrapers and storage on the same balance, failed requests that cost nothing, no monthly minimum, SDKs in seven languages and a free allowance. Where UpRock fits: the domains Crawlbase prices above standard, the requests it couldn't complete, countries outside its list, and a price you know before you send the request.

The fallback, in TypeScript and Python

Every version ask Crawlbase for markdown in the country you pass, read the three signals and the tier, and keep a set of domains Crawlbase billed above standard: from then on, those go straight to UpRock. Failures worth a second network go to UpRock too; a 404, a 410 or a bad request raises an error. They use Crawlbase's normal token, which costs one credit times the tier; add javascript: "true" to render pages, which doubles it. The TypeScript version uses Crawlbase's Node SDK, which keeps the headers on any status. The Python version calls the HTTP API with requests, because the Python SDK drops the headers on a non-2xx response. UpRock gets one POST /v1/crawl request with your key in an Authorization: Bearer header; the MCP and CLI tabs do the same through UpRock's MCP server (TypeScript) or CLI (Python).

// npm i crawlbase   (Node 18+)   env: CRAWLBASE_TOKEN, UPROCK_API_KEYimport { CrawlingAPI } from "crawlbase";​// Crawlbase asks for a client timeout of at least 90 s.const crawlbase = new CrawlingAPI({  token: process.env.CRAWLBASE_TOKEN ?? "",  timeout: 90_000,});​// Crawlbase reports each domain's price tier on billed responses (X-Domain-Complexity).// A domain billed at any other tier goes straight to UpRock from then on.const ACCEPTED_TIERS = new Set(["standard"]);const uprockDomains = new Set<string>(); // save it somewhere if you want it to persist​// HTTP statuses worth a second network: a bad token (401), your spend cap or account// limit (402, 403), the concurrency limit (429), errors and timeouts (500, 503, 504).const TRY_UPROCK_HTTP = new Set([401, 402, 403, 429, 500, 503, 504]);​// cb_status (crawlbase.com/docs/status-codes, checked 25 Oct 2026): 704 is the site's own// error, worth a second try only if it's a 5xx; 595 is a click selector to fix; 503 (a// block page), 705 (the site said 403), 706 (429) and other 5xx to 7xx codes are worth it.function worthUpRock(http: number, cb: number, site: number) {  if (cb === 704) return site >= 500;  if (cb === 595) return false;  return cb >= 500 || TRY_UPROCK_HTTP.has(http);}​async function viaUpRock(url: string, country: string) {  // One call: UpRock loads the page on a real device in that country, tries a fresh device  // every 7 s (up to 3 tries) and returns markdown. Failed calls aren't billed.  const res = await fetch("https://edge.uprock.com/v1/crawl", {    method: "POST",    headers: {      Authorization: `Bearer ${process.env.UPROCK_API_KEY}`,      "Content-Type": "application/json",    },    body: JSON.stringify({ url, country }),    signal: AbortSignal.timeout(90_000),  });  const page = await res.json();  if (!res.ok) throw new Error(`UpRock ${res.status} ${page.code}: ${page.error}`);  return page.markdown ?? "";}​async function viaCrawlbase(url: string, country: string) {  try {    const res = await crawlbase.get(url, { format: "md", country });    const header = (name: string) => String(res.headers[name] ?? "");    return {      http: Number(res.statusCode),      cb: Number(header("cb_status") || header("pc_status")), // pc_status: the old name      site: Number(header("original_status")),      tier: header("x-domain-complexity") || header("domain_complexity"),      body: String(res.body),    };  } catch (err) {    console.warn(`Crawlbase unreachable or timed out (${err}); trying UpRock`);    return null;  }}​export async function read(url: string, country = "US") {  const domain = new URL(url).hostname;  const r = uprockDomains.has(domain) ? null : await viaCrawlbase(url, country);  if (r) {    if (r.tier && !ACCEPTED_TIERS.has(r.tier)) {      uprockDomains.add(domain); // this page is billed already; the next ones aren't      console.warn(        `Crawlbase bills ${domain} as "${r.tier}"; using UpRock from now on`,      );    }    if (r.http === 200 && r.cb === 200) {      // 404 and 410 are the site's answer (and billed): a second crawler will see the same.      if (r.site === 404 || r.site === 410)        throw new Error(`The page is gone (${r.site})`);      return { via: "crawlbase", markdown: r.body };    }    if (r.cb !== 207 && !worthUpRock(r.http, r.cb, r.site))      throw new Error(        `Crawlbase ${r.http}, cb_status ${r.cb}: ${r.body.slice(0, 200)}`,      );    console.warn(`Crawlbase ${r.http}, cb_status ${r.cb}; trying UpRock`);  }  return { via: "uprock", markdown: await viaUpRock(url, country) };}​// node read.ts https://developer.mozilla.org/en-US/docs/Web/HTTP DEconst [url = "https://developer.mozilla.org/en-US/docs/Web/HTTP", country = "US"] =  process.argv.slice(2);const page = await read(url, country);console.log(page.via, page.markdown.slice(0, 200));

Tested 25 Oct 2026 against the live UpRock API with an invalid Crawlbase token: Crawlbase answered HTTP 401 with pc_status: 401 and no cb_status, and both versions fell back to UpRock. Without an account we couldn't see a real X-Domain-Complexity header, so the tier check follows Crawlbase's docs, and the cost table follows its pricing page and estimator. On 6 Nov 2026 we ran the HTTP and MCP versions again with an UpRock API key in an Authorization header: with an invalid Crawlbase key, each fell back to UpRock and got the page.

FAQ

How does Crawlbase decide a site's tier?

Itself. Its pricing page says heavily defended sites carry a higher tier, applied automatically, from standard (×1) through moderate, complex, complex I, complex II, extreme and extreme I to extreme II (×20), and JavaScript doubles any tier. Its Cookbook shows the tier for 356 sites, most at one credit, and notes that a tier can change. For any other site, you see the tier in the response after you've been billed.

Does Crawlbase charge for failed requests?

No. Its docs bill only responses with cb_status 200 or 207 where the site answered 200, 201, a redirect, 404 or 410. A block, a timeout, or a site's own 403, 429 or 5xx costs nothing.

Why doesn't the Python example use Crawlbase's SDK?

On any non-2xx response, the Python SDK returns only the status code, with empty headers and body. A failed crawl arrives as HTTP 520 with the reason in the cb_status header, so the SDK loses it. We checked the SDK's source and called it with an invalid token, and it returned status 401 with no headers. The Node SDK keeps the headers.

Which countries can Crawlbase fetch from?

Its Crawling API docs list 22 countries, and say Crawlbase may override the country you pass to pick a proxy for the URL unless you ask support to turn that off. UpRock covers 63 countries, or a region, and loads the page on a device in the country you choose.

Does Crawlbase have an MCP server?

Yes, an open-source one you run with npx, and a hosted one at mcp.crawlbase.com/mcp that takes your token as a bearer header.

Other use cases to explore

References

Get started

Add UpRock in one paste.

Paste this into Claude Code, Codex, Cursor or any agent with a terminal. It reads our docs, sets up the MCP server or CLI, and tells you the cost before it spends anything.

Set up UpRock for me: read https://uprock.ai/agents.md, connect the UpRock MCP server, and run one test crawl. Tell me what it costs before you spend anything.

How do I keep Crawlbase's site tiers from surprising my bill? | UpRock AI