Name the WAF and challenge before you burn unlock credits
Website AntiBot
Probe a URL through a live BrowserSolver session and learn which vendor, challenge type, and fingerprint gap will block your scraper. Route to Crawler, Rendering, or WebUnlocker with evidence instead of guesswork.
- Vendor classification for Cloudflare, DataDome, Akamai, Imperva, and peers
- TLS, header, and browser signal breakdown for fingerprint tuning
- Mode hints that point to Crawler, Rendering, or allowlisted unlock
- One URL per probe, same API shape as production scrapes
Pre-flight
probe
Vendor
classification
TLS
signal audit
Mode
routing hints
Detect, decide, then scrape
- Step 1
Probe
Send one representative URL through AntiBot.
- Step 2
Read the vendor
Use classification and TLS signals in your runbook.
- Step 3
Pick a mode
Crawler, Rendering, or WebUnlocker based on the hint.
Detect before you scale, or before you burn unlock credits
Blocking is the scraper's real bill. AntiBot probes one URL through BrowserSolver egress and returns vendor, challenge type, and a suggested next mode so you do not guess between Crawler, Rendering, and WebUnlocker.
- One URL per probe call, same HTTP API shape as your production scrapers
- Vendor signatures for Cloudflare, DataDome, Akamai, Imperva, PerimeterX, and peers
- Mode hints point to Crawler, Rendering, or allowlisted WebUnlocker
- Same API key and credit balance across BrowserSolver scrape modes
Runbook JSON for scraping teams
Use probe output in tickets, compliance reviews, and pipeline branching, then feed the same URL list into the mode AntiBot recommends.
- TLS and header signals when fingerprint coherence is the issue
- Pair with Website Technology to correlate stack depth and access difficulty
- Re-probe when pass rates drop overnight, vendors change protection without notice
- Same API key and credit balance across BrowserSolver scrape modes
Diagnose before you scale
Pick the right mode before you scale unlock traffic.
Stack ID
Name the vendor and challenge family.
Fingerprint scan
Surface browser and TLS mismatches.
Challenge map
See JS, CAPTCHA, or rate limits.
Vendor DB
Signatures for major bot vendors.
TLS profile
Highlight JA3/JA4 expectations.
Mode hint
Suggested Crawler, Render, or Unlock path.
Detect first
Know the wall before you scale
Vendor ID
Cloudflare, DataDome, Akamai, and more
TLS audit
JA3/JA4 and header coherence clues
Mode hint
Suggested next scrape lane
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.
Does AntiBot bypass challenges?
No. It maps protection layers. Switch to Rendering for JS-heavy pages or WebUnlocker on an allowlisted domain once you know which defenses are active.
When should I run AntiBot?
Run it when a new domain returns unexpected 403s, CAPTCHA interstitials, or empty HTML, or when overnight pass rates collapse.
Is AntiBot required before every unlock?
Not required, but it saves credits when you are unsure whether cheap HTTP, render, or unlock is the right next step.
Can I automate branching on the response?
Yes. Feed vendor and mode-hint fields into your job runner to route URLs without manual triage.
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