One scraping API for fetch, render, screenshot, and unlock
Web Scraping API
Scrape public pages with BrowserSolver without running proxies, browsers, or anti-bot vendors yourself. Start on cheap HTTP, escalate to rendering or unlock when the target fights back, and keep one balance across every mode.
- One credential for crawler, render, screenshot, and unlock
- HTML ready for your parsers, selectors, or LLM chunkers
- AntiBot probes before you burn unlock credits
- Dashboard logs when a domain flips protection overnight
4
scrape modes
1
API key
AntiBot
pre-flight
Allowlist
unlock lane
Cheapest mode that still returns data
- Step 1
Fetch
Website Crawler for static HTML.
- Step 2
Render
Website Rendering when the DOM needs JavaScript.
- Step 3
Unlock
WebUnlocker on allowlisted domains after AntiBot.
Scraping without owning the stack
Point jobs at BrowserSolver instead of stitching proxy sheets, Chrome pools, and unlock vendors. Routing, retries, and challenge lanes stay on our side.
- Crawler for static HTML, Rendering for SPAs, WebUnlocker for hardened allowlisted domains
- AntiBot probes before you burn unlock credits
- Dashboard logs for blocked URL debugging
- Same API key and credit balance across BrowserSolver scrape modes
Parser-ready outputs for production jobs
Ship HTML, screenshots, or unlock responses into the same pipelines you already run for catalogs, SERP, and monitoring. Built for production jobs that need predictable access before brittle parsing.
- Stable REST shapes documented beside the endpoint library
- Mode hints from AntiBot when pass rates drop overnight
- Credit-based billing across fetch, render, and unlock
- Same API key and credit balance across BrowserSolver scrape modes
One scraping API, four ways past the wall
Pick the cheapest mode that still returns usable HTML for each URL.
Fetch + render
HTTP first, headless when the DOM needs JS.
JS-ready HTML
Wait for selectors before you extract.
Unlock lane
Allowlisted domains when vendors block.
One balance
Same credits for every scrape mode.
Parser HTML
Bodies ready for XPath, CSS, or LLMs.
Job-scale
Your queue, our egress and browsers.
Mode ladder
HTTP → render → unlock without new vendors
Zero ops
No proxy sheets or Chrome pools
Detect first
AntiBot before expensive unlock
One bill
Shared credits across scrape modes
WAF unlock guides
Runbooks for clearing common WAF and bot vendors with BrowserSolver.
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Is Web Scraping a separate endpoint?
Web Scraping is your starting product for public-page collection. Under the hood you pick Crawler, Rendering, Screenshot, or WebUnlocker depending on how hard the target is.
Do I need a proxy vendor?
No. Routing and unlock lanes are included. You keep parsers, storage, and orchestration.
When should I escalate from Crawler to Rendering?
Escalate when the HTML is empty, incomplete, or clearly challenge-gated after JS. Keep Crawler for static or API-backed pages that already return usable markup.
Where do I start?
Create a free account, open the API library, and start on Crawler. Escalate modes only when responses are empty or challenged.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes