All products / Zyte API

Zyte API pricing

How Zyte bills successful HTTP and browser responses by target difficulty, then adds extraction and output meters.

ExactPrice recorded on 2026-07-26Older price from 2026-07-26; excluded from rankings2 vendor sourcesSee the calculation
Available volumes

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

Workload100,000 pages per month
JavaScript renderingrequired
Bills failed fetchesno
per 1,000 pages kept$1.00

What Zyte API counts

1pages: 0.0001 usd per request on $100 minimum commitment
2request.js_render: 0.00075 usd per request on $100 minimum commitment
=You consume100,000 request

What you pay

$100.00ExactEvery figure is published; the arithmetic below is checkable.$100 minimum commitment, monthly list price
  1. Successes you want

    100,000 pages

    Your stated workload. Every vendor on this site is priced against this same number.

  2. × 1

    Attempts you are billed for

    100,000 requests

    Zyte API does not bill failed fetches, so failures cost nothing here.

  3. × 1

    What the meter counts

    100,000 requests

    One attempt is one billed unit for this workload.

  4. =

    Cash per month

    $100.00 /mo

    $100 minimum commitment. Cheapest of every eligible purchase option, not the first plan that fits.

Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.

100,000 pages divided by 95% success 100,000 request $100 minimum commitment $100.00/mo = $1.00 per 1,000 pages kept

The arithmetic, line by line
  1. pages: 0.0001 usd per request on $100 minimum commitmentsource
  2. request.js_render: 0.00075 usd per request on $100 minimum commitmentsource
  3. consumes 100,000 request per month
  4. cheapest way to buy that: $100 minimum commitment, $100.00 minimum against $75.00 of usage = $100.00 per monthsource

Cheaper for this job

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 Zyte API plan

Published plans, with the offer this workload actually selects marked
PlanMonthlyIf billed yearlyPrepaid packIncludedSimultaneous sessions
Pay as you goNot publishedn/an/an/an/a
$100 minimum commitment your job$100.00n/an/a100 usdn/a
$200 minimum commitment$200.00n/an/a200 usdn/a
$350 minimum commitment$350.00n/an/a350 usdn/a
$500 minimum commitment$500.00n/an/a500 usdn/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.

Every published way Zyte API charges
OperationCostsPerSource
request.basic0.00013 usdrequestsource
request.js_render0.00101 usdrequestsource
request.screenshot0.002 usdrequestsource
request.ai_extraction0.001 usdrequestsource
extract.token_in0.000002 usdtokensource
extract.token_out0.00001 usdtokensource

What Zyte API does not publish

What Zyte API is

Zyte API is a managed web retrieval and extraction service with HTTP and browser-rendered modes. It handles proxy selection, browser execution, blocking countermeasures, screenshots, actions, and automatic extraction for supported data types. It is for engineering and data teams that need either page content or structured items while outsourcing the access layer. Sources: Zyte API and Zyte pricing, retrieved 2026-07-26.

Oxylabs Web Scraper API, Bright Data Web Unlocker, and ZenRows are the nearest named competitors. Oxylabs publishes target-family result rates, Bright Data Web Unlocker foregrounds a successful-request unit with major access features included, and ZenRows uses replacement request credits plus a separate browser formula. Zyte’s distinguishing public model assigns the target to one of five difficulty tiers, selects an HTTP or browser rate within that tier, and then adds metered outputs such as screenshots or extraction. Sources: Oxylabs pricing, Bright Data Web Unlocker pricing, ZenRows pricing, and Zyte pricing documentation, retrieved 2026-07-26.

How billing works

One base unit is one successful API response, with the rate selected by target-difficulty tier and by HTTP or browser mode. Screenshots and automatic extraction can add usage, and AI extraction can add input- and output-token meters. Extended residential geolocation can add bandwidth charges. Higher spending commitments reduce the tier rates but allow billable use beyond the commitment up to a higher spending limit. Zyte treats API HTTP 200 as successful even when the target reports a non-ban bad status, a browser action fails, extraction properties are missing, or returned content does not match the buyer’s expectation. The common buying mistake is to equate billable HTTP 200 with a useful business result, or to budget every domain at the easiest HTTP tier while also ignoring add-ons. Sources: Zyte pricing documentation and Zyte error documentation, retrieved 2026-07-26.

What Zyte does not publish consistently

  • One universal combination rule covering target tier, browser mode, screenshots, automatic extraction, AI tokens, and geolocation bandwidth. Source reviewed: Zyte pricing documentation, retrieved 2026-07-26.
  • Plan-level concurrency. The documentation publishes a standard rate limit instead. Source reviewed: Zyte pricing documentation, retrieved 2026-07-26.
  • One consistent commitment table. The public pricing page omits a commitment level that remains present in the pricing documentation. Sources reviewed: Zyte pricing and pricing documentation, retrieved 2026-07-26.
  • Whether the public trial requires a payment card. Source reviewed: Zyte pricing, retrieved 2026-07-26.

Who it suits

Zyte API suits teams that can sample their target mix, separate HTTP from browser work, and monitor extraction and output add-ons. It is less suitable for a buyer who requires one fixed request rate or counts only useful business records as billable successes. The reason is that target difficulty and requested outputs are legitimate cost drivers, while API success is broader than content usefulness. Sources: Zyte pricing, pricing documentation, and error documentation, retrieved 2026-07-26.

Answer

Zyte API's dated 2026-07-26 price snapshot gives $100.00 for 100,000 JavaScript-rendered pages on its $100 minimum commitment offer. This older figure is excluded from rankings; check the vendor before buying.

Recorded 2026-07-26 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.