Request cost

ScrapeIt bills in credits. Output formats and CSS extractRules do not change the price; options only a browser can serve (screenshot, waitFor, jsScenario, captureNetwork) make the request a render.

Price list

Credits per request. Every price is flat. The Playground estimate and cost.estimated_credits always show the live numbers for your workspace.

What the request uses	Credits
Fetch + datacenter proxy	4
Browser render + datacenter proxy	30
Fetch + residential proxy	15
Browser render + residential proxy	50
proxyType: "auto"	the price of the tier that served the request (datacenter or residential)
Screenshot (screenshot: true)	the render price, nothing on top
AI extraction (aiExtractRules)	+40 on top
Any of the above served from the cache	half, rounded up - see cache hits

With jsRendering omitted or "auto", a request costs the fetch price when the fetch answered and the render price when the page was rendered. jsRendering: true is always priced as a render. A screenshot is a render and costs exactly the render price: 30 on a datacenter proxy, 50 on a residential one, whether or not you also set jsRendering.

Site APIs are sold at one flat price per request - proxy and rendering are included:

Site API	Credits per request
Amazon Search, Amazon Product	15
Amazon Best Sellers	30*
Walmart Search / Product	40
Zillow Listing / Property	30
Allegro Listing / Offer	30
Google SERP	30
Google Maps Search / Place	30*
Booking.com Search / Hotel	30*
Yelp Search / Business	40
Redfin Property	30*
Airbnb Search	40*
Airbnb Listing	50*
Tripadvisor Search / Place	40*
Yellow Pages Search / Business	30*
eBay Search / Item	15*
Glassdoor Listing / Job	15*
Glassdoor Companies / Company	30*
Apartments.com Listing / Property	50

* Introductory price for a new product; it may change. The dashboard Pricing page always shows the current price.

include_html: true - the page the data was read from, returned in html - adds 4 credits to a site API request.

A no-code job of a site scraper is charged per page it fetched, at these per-request prices, and reports every credit it spent - see each product page for what counts as a page.

Renders skip images, fonts and media unless you set blockResources yourself or ask for a screenshot. Set blockResources: false when a target needs the page to load in full.

Estimate vs charged

Every response separates the pre-execution estimate from the final charge:

{
  "request_metadata": {
    "executed_runtime": "browser",
    "proxy_traffic_bytes": 840000,
    "credits_breakdown": {
      "base": 4,
      "rendering": 26,
      "proxy_traffic": 20,
      "proxy_tier": "residential"
    }
  },
  "cost": { "estimated_credits": 15, "charged_credits": 50 }
}

• estimated_credits - computed before the request runs, at the price of the runtime it starts on (the fetch, for an auto request).
• charged_credits - the credits charged for the request; about half on a cache hit.
• request_metadata.proxy_traffic_bytes and request_metadata.credits_breakdown - the traffic the request moved (for information; it does not change the price) and how charged_credits splits into the base price (with the AI extraction add-on, when charged), the render add-on and the proxy add-on, plus proxy_tier - the tier of the exit that served the request (datacenter or residential). Both are null on cache hits.

The dashboard Playground and the Batch Scraping form show the price live as you change the form, so you can see it before running - for example, residential + screenshot shows 50, datacenter + aiExtractRules shows 44.

Reducing cost

• Leave jsRendering on "auto" (the default): pages that are in the initial HTML stay at the fetch price. Set true only for targets you know need a browser, to skip the fetch attempt.
• Prefer datacenter proxies; use residential only for targets that block them.
• Turn on caching for repeated URLs - half price on hits.
• Trim work with blockResources: true, includeOnlyTags and removeBase64Images - faster and less likely to time out.

Monitoring spend

• Dashboard Usage page and GET /api/v1/usage/me - per-period consumption.
• Batch and crawler jobs expose credits_spent per job and per item, so you can attribute cost to a single URL.

Related pages

• Billing & credits - plans and credit allowances.
• Caching - the half-price discount.
• Concurrency & limits - plan credit allowance and resets.