Structured Web Extraction APIs: Compare Parsers & Output Contracts

HTML, JSON, markdown, PNG

For this task: A CSS parsing schema defines extracted fields separately from the formats array. Match selectors to the target page and choose rendering independently; requesting a JSON response alone does not define a field schema.[1][4]

Formats

The formats array selects HTML, Markdown, Base64 PNG screenshots and response headers.[1]

Rendering

render defaults to false; true enables JavaScript and auto lets Nimble select the configuration.[1]

Parsing and actions

CSS parsing schemas, browser actions and network-capture rules are supported.[1]

Async processing

Async and batch submissions return before processing finishes; poll task or batch progress for completion.[2]

Billing

Extraction Tools are listed at USD 1 per 1,000 URLs, with charges only for successful requests.[3]

Successful URL extractions; public API pricing lists USD 1 per 1,000 URLs for Extraction Tools.

HTML, JSON, PNG

For this task: Dedicated supported targets accept parse=true for parsed fields. A universal page fetch does not establish automatic parsing for every site; check the supported source and target before choosing a schema.[1]

Authentication

Use a Web Scraper API user's username and password with HTTP Basic authentication, rather than dashboard credentials.[1]

Rendering and parsing

render=html enables JavaScript rendering. Dedicated supported targets accept parse=true for structured JSON.[1]

Delivery choices

Realtime keeps the connection open; Push-Pull retrieves jobs asynchronously; Proxy Endpoint offers a proxy interface.[2]

Batch size

Push-Pull accepts up to 5,000 query or URL values per batch; Realtime and Proxy Endpoint do not support batch.[2]

Screenshots

render=png returns a Base64-encoded screenshot.[2]

Product-specific plan and target rates; exact costs and failed-request rules were not verified in this pilot.

HTML, JSON, markdown, screenshot

For this task: The LLM extraction path supports JSON output and page-type schema hints. llm_extract adds 25 credits to the underlying fetch cost; this is separate from receiving an ordinary JSON response wrapper.[4][1]

Billing outcomes

The credit policy counts both HTTP 200 and 404 responses as successful, billable requests.[1]

Rendering costs

Standard rendering costs 10 credits; residential plus rendering costs 25; render_js_cheap costs 5 using a limited provider set.[1]

Extraction add-on

llm_extract adds 25 credits on top of base proxy costs.[1]

Cheaper rendering tradeoff

render_js_cheap is intended for simpler sites and does not provide the full upstream provider pool.[2]

Response options

The feature list documents screenshot capture and JSON or Markdown LLM extraction responses.[3]

Monthly API credits determined by target and options; HTTP 200 and 404 responses consume credits.

HTML, JSON

For this task: autoparse=true and dedicated structured-data endpoints work with supported sites and target types. An ordinary URL fetch does not promise a general parser for arbitrary websites.[1][4]

Rendering

render=true returns HTML after JavaScript execution; wait_for_selector requires rendering.[1]

Credit examples

The documented parameter table lists 10 credits for rendering, 25 for premium plus rendering, and 75 for ultra-premium plus rendering.[2]

Billable outcomes

HTTP 200 and 404 responses are charged, as are client-cancelled requests when the client allows less than 70 seconds.[2]

Cost inspection

The account/urlcost endpoint estimates request cost and the sa-credit-cost response header reports actual credits.[2]

Concurrency

Concurrency is plan-dependent; the Async API supports batch requests.[3]

Structured extraction

autoparse=true and dedicated structured-data endpoints parse supported sites and target types; ordinary URL fetching is not a universal field-extraction contract.[1][4]

API credits determined by target domain and request options.

HTML, JSON, screenshot

For this task: Integrated extraction accepts extraction_model, extraction_prompt or extraction_template. These select model, prompt and template approaches with different output contracts; choose the mechanism and required fields for the target.[3]

Rendering and actions

render_js enables browser rendering; js_scenario defines page interactions before results return.[1]

Result handling

Examples return scraped content and browser data through the API result rather than exposing a browser connection.[1]

Credit model

A scrape can consume multiple credits depending on browser, proxy and protection configuration.[2]

Concurrency examples

Published monthly plans list 5 concurrent requests for Discovery, 20 for Pro, 50 for Startup and 100 for Enterprise.[2]

Quota expiry

Unused subscription quota does not roll over to the next subscription period.[2]

Integrated extraction

extraction_model, extraction_prompt and extraction_template select documented model, prompt and template extraction approaches within a scrape.[3]

API credits per scrape; proxy network, rendering and protection settings affect consumption.

HTML, JSON, markdown, text, screenshot

For this task: CSS extract_rules defines the fields to extract. AI extraction rules are a separate option with additional credit requirements; choose the extraction mechanism before comparing costs.[1]

Rendering default

render_js defaults to true. HTML, page text, Markdown and screenshots are documented output options.[1]

Request credits

Classic requests cost 1 credit without rendering or 5 with it; premium with rendering costs 25 and stealth with rendering costs 75.[1]

Extraction and interaction

CSS extract_rules and js_scenario support structured extraction and page interactions.[1]

Custom proxy

The own_proxy parameter supports a user-supplied proxy provider.[1]

Automatic cost control

GET-only mode=auto chooses a successful rendering/proxy tier; max_cost caps eligible tiers and all-failed auto attempts cost zero.[1]

Monthly API credits; rendering and proxy tier determine base credits, with AI extraction add-ons.

HTML, JSON, screenshot

For this task: Choose a typed extraction output such as product or article. Returned HTML and a JSON response envelope are separate from these extracted objects; select the page type and extraction source for the workload.[3]

HTTP output

httpResponseBody=true returns the response body Base64-encoded; decode it before parsing.[1]

Browser output

Browser requests return rendered HTML, screenshots or both, and support browser actions and network capture.[2]

Structured extraction

The API supports dedicated extraction types including articles, products, job postings and SERPs.[3]

Billing

Unsuccessful and rate-limited responses are free; browser actions, screenshots and extraction can add costs.[4]

Request model

The /v1/extract endpoint blocks until its single-URL result is ready.[3]

Successful responses, priced by target and HTTP/browser tier, with feature add-ons.