Web Data API Directory: Scraping, SERP & Browser APIs

browser session

Framework support

Official documentation lists Playwright, Puppeteer and Selenium.[1]

Managed infrastructure

The service handles proxy rotation, browser fingerprints, CAPTCHA handling and session recovery.[1]

PAYG rate

The public PAYG plan lists USD 8 per GB with no monthly commitment and built-in proxies and unlocking.[3]

Concurrency

The public pricing page advertises unlimited concurrent sessions.[3]

Setup

Create a Browser API zone and retrieve its connection details from the Overview tab.[2]

Transferred traffic in GB on paid plans; built-in proxy management and unblocking included.

JSON, HTML

Result format

Add brd_json=1 to the search URL for parsed JSON; the REST example otherwise returns HTML.[1]

Asynchronous delivery

Enable asynchronous requests on the SERP zone, submit with async=1, then retrieve using the response ID.[1]

Billing

Failed requests are not charged. In asynchronous mode, collection calls are free.[2][1]

PAYG rate

The public PAYG plan lists USD 1.50 per 1,000 requests, without a monthly commitment.[2]

Successful requests; asynchronous result collection is not separately billed.

browser session

Custom proxies

Supports custom HTTP/HTTPS proxies, built-in residential proxies and domain-based routing rules.[1]

Location behavior

Built-in proxy geolocation is best effort; the closest available location may be used.[1]

Billing increments

Browser time is billed by the minute and proxy traffic by the MB, with a one-minute and one-MB minimum per session.[2]

Concurrency

Current published limits are 3 sessions on Free, 25 on Developer and 100 on Startup.[2]

Reconnection

A timeout extends duration but a normal session ends on disconnect; keepAlive enables reconnection.[3]

Browser time plus built-in proxy traffic, with plan allowances and overages.

browser session

Time metering

Each started 30-second browser interval costs one unit, including idle time.[1]

Built-in proxy costs

Residential traffic costs 6 units per MB and datacenter traffic 2 units per MB, in addition to browser time.[1]

Custom proxy costs

Third-party proxies configured through --proxy-server do not consume Browserless proxy units; their own provider may bill separately.[1]

Failures

Pre-start validation or queue rejections consume no browser units; failures after startup consume elapsed time and transferred proxy traffic.[1]

Session timeout

The documented default timeout is 30 seconds; a custom timeout can be set on the connection.[1]

Units for browser time, built-in proxy bandwidth and successful CAPTCHA solves.

HTML, JSON

Token types

Normal tokens fetch static responses; JavaScript tokens enable browser rendering. javascript=true can switch a normal-token request to the JavaScript path.[1]

Browser controls

JavaScript requests support page_wait, ajax_wait, scroll and css_click_selector.[1]

Extended scrolling

The first 8 seconds of page-load plus scrolling count as one request; each additional started 5-second interval adds one billed request.[1]

HTTP-method limitation

POST is supported with the normal token only; JavaScript-rendered requests use GET.[1]

Successful requests; JavaScript request configuration and extended scrolling affect billed usage.

HTML, JSON

HTTP integration

The official Dify guide sends POST requests to https://scraper-api.decodo.com/v2/scrape using Basic authentication and a JSON body.[1]

JavaScript rendering

The documented payload uses headless=html to receive HTML after rendering.[1]

Proxy selection

The request can select proxy_pool=premium.[1]

Cost model

The current pricing page separates standard and premium proxies, with and without JavaScript rendering.[2]

Request credits vary by request complexity, including proxy pool and JavaScript rendering.

HTML, JSON, markdown, PNG

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

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.

browser session

Session lifetime

sessionTTL defaults to 180 seconds. The guide recommends a maximum of 900 seconds while noting longer values can be set.[1]

Custom proxies

proxyURL accepts a custom proxy and overrides other proxy parameters; this feature requires a subscription.[1]

Recording

sessionRecording enables replay of a completed session and is disabled by default.[1]

Frameworks and state

Playwright and Puppeteer are supported; Profiles provide login-state reuse with configurable persistence.[2]

Billing dimensions

The Crawl introduction states its runtime-plus-proxy-bandwidth billing model is shared with Browser.[3]

Browser runtime and proxy bandwidth; exact plan-specific rates were not verified.

HTML, JSON, markdown, screenshot

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

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

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

Rendering and response

The /v2/general endpoint returns plain HTML. browser defaults to true; return_page_source skips JavaScript rendering while using the browser.[1]

Timeout

Request timeout defaults to 60 seconds and can be set from 5 to 60 seconds.[1]

Credit examples

Simple datacenter requests cost 1 credit; JavaScript-rendered datacenter requests cost 10; rendered residential requests cost 125.[2]

Usage inspection

The Ant-credits-cost response header reports request credit consumption; unused credits expire at the subscription boundary.[2]

API credits based on browser use and proxy network.

JSON, HTML

Authentication

Send the API key as an Authorization Bearer token.[1]

Request mode

light_request defaults to true. Light mode omits the browser and may return less data; disabling it selects regular mode.[1]

Search controls

Select country, desktop/mobile device and search type. News search is not supported with mobile device selection.[1]

HTML and pagination

add_html can include page HTML. The pages parameter supports up to ten pages; the provider recommends at most three for reliability.[1]

Documentation distinguishes light requests at 10 credits from regular requests at 15 credits. Confirm the selected mode; credits are not USD.

HTML, JSON, markdown, text, screenshot

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.

browser session

Default session

The configuration guide specifies a desktop, headful session with a five-minute timeout; proxies and CAPTCHA solving are off by default.[1]

Custom proxies

Use useProxy.server or proxyUrl; proxyUrl takes precedence over useProxy.[1]

Idle release

inactivityTimeout can release a session before its total timeout; CDP commands and remote input reset the idle timer.[1]

Stored state

sessionContext supplies cookies/storage, while profiles preserve browser state across sessions.[1]

Browser connection

Attach Playwright or Puppeteer using the session ID and API key on the Steel WebSocket endpoint.[2]

Session time; exact plan rates and proxy add-on prices were not verified.

HTML, PNG

Request interface

The official example posts form-encoded fields to universalapi.thordata.com/request with a Bearer token.[1]

Rendering

js_render=True enables JavaScript rendering for dynamic content.[1]

Output

The type parameter selects HTML or PNG; HTML is the documented default.[1]

Resource controls

block_resources restricts fetched resources; country selects the scraping proxy location.[1]

Not verified; request multipliers, failed-request billing and plan pricing require further evidence.

HTML, JSON, screenshot

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.

browser session

Connection

The CDP endpoint accepts Playwright, Puppeteer and other CDP-compatible libraries.[1]

Session lifetime

ttl defaults to 60 seconds and accepts values from 15 to 3,600 seconds.[1]

Billing

Session units are the larger of navigation count and duration rounded up to 15-second intervals, using the first target's browser price tier.[1]

Continuity

A connection has its own IP and cookie jar; separate CDP connections cannot reuse that session automatically.[1]

Access requirements

CDP requires a subscription or PAYG spending limit plus business verification; free trials cannot use it.[1]

Target-tier units: the greater of page.goto calls or started 15-second session intervals; residential overages can add charges.

JSON, HTML

Endpoint and authentication

POST to /v1/search using the API key as the Basic-auth username and an empty password.[1]

Output selection

The include option selects organic results, HTML or both. Parsed results carry rank, title and URL; snippet is optional.[3][1]

Result quantity

maxResults accepts multiples of ten from 10 to 100, with a default of 10. Request weight increases with result count.[2]

Targeting

Use engine-native query parameters or generic geolocation and locale options. Unsupported search domains return HTTP 400.[2]

Request weight increases with maxResults: max(1, maxResults / 10). A USD rate was not established from the reviewed search documentation.