Browsers
Run county searches in real Chrome.
Connect over CDP from your own code.
County court portals block automated searches. Driver runs yours on
real, trusted devices, so screenings don’t stall on CAPTCHAs.
3,142 US counties · searched in real Chrome
Trusted by Devs at



Court record searches from datacenter IPs and headless browsers get flagged mid-batch. Driver runs each search on a real device, at a human pace.
Requests to one county portal
Scraper on a cloud VM
Datacenter IP · headless
Driver
Real device · consumer ISP
Portals block cloud IP addresses on sight. Driver uses consumer ISP addresses.
Headless browsers give themselves away. Ours run on real devices with real input.
Scrapers flood a portal and hit rate limits. Driver paces each portal the way a person would.
Every search is logged with the device, IP and page it ran on. Signed records with packet capture are available on request.
Signed record
Maricopa County, AZ
req_7Kq2Vn9xT4 · 14:02:07 UTC
Signature verified
ed25519 · 9f3a…c21e
Every record names the device, rack and address that ran it.
Keep the raw traffic, not just a log line.
Signed records where any edit breaks the signature.
Browsers and ISP Network if you own the search logic. Managed Data Feed if you only want results.
Run county searches in real Chrome.
Connect over CDP from your own code.
Send a portal URL, get the rendered page.
No browser to run, no pipeline to babysit.
Driver runs real Chromium on real devices. No spoofing, no stealth patches and nothing to explain to a regulator.
Evasion browsers Driver
| What an auditor asks | Evasion browsers | Driver |
|---|---|---|
| Browser build | Stealth-patched Chromium | Real Chromium |
| Device signals | Spoofed in software | True, from real hardware |
| IP origin | Rotating pool, unknown owner | Leased IPv4, documented |
| Proof per request | Logs, if kept | Logged, signed on request |
| Bot checks | Evaded | Nothing to evade |
| Reverse engineering | Ongoing, per detector | None, nothing to reverse |