Catch common scraper clients
Voidek recognizes Python requests, curl, wget, axios, node-fetch, Selenium, Playwright, Puppeteer, HeadlessChrome, and bare Chromium patterns.
Scraper protection
Lightweight scraper protection for sites that need crawler friction without a heavy enterprise security migration.
Voidek recognizes Python requests, curl, wget, axios, node-fetch, Selenium, Playwright, Puppeteer, HeadlessChrome, and bare Chromium patterns.
The browser snippet collects lightweight proof such as language, timezone, webdriver, plugins, screen, and token continuity so middleware can separate static fetches from real browser sessions.
Use decision logs and usage summaries to see which user agents, paths, and actions are most common before turning on stricter blocking rules.
Detection proof
Use these examples as rollout checks: start in monitor mode, confirm the log rows, then enforce only the classes that match your protected routes.
Rollout path
Voidek is meant to start quietly: save the runtime key, run a controlled test, then raise friction only where live logs support it.
Create a personal account on the Free plan, add one protected site, and save the runtime key before turning on scraper protection.
Copy the test request, export VOIDEK_API_KEY, then confirm the GPTBot row appears in Analytics with path, action, and score.
Add the decision API at middleware or backend boundaries, then tune Selenium detection after live rows look clean.
FAQ
Yes, so Voidek does not rely only on user-agent strings. It combines user-agent classification with browser signals, headers, route patterns, and recent request pressure.
No. Voidek is a crawler and scraper decision layer. It can challenge suspicious traffic, but its main job is to classify, log, and block automated requests before protected content is served.
First setup
Create a personal account, add one protected site, copy the runtime key, and run one test decision before enforcing scraper protection.