Bot and AI crawler control
Agentscan sorts every visitor into people, verified crawlers, AI agents and bot scripts, then applies your rule to each. Install it as a WordPress plugin, a Cloudflare Worker or at your proxy.
Verified crawlers always passNo card
Speed
Every check answers in 50 to 100 ms, so your pages and signups never wait on it.
How it works
The WordPress plugin, the Cloudflare Worker, or a plugin for Traefik, Caddy or nginx. No changes to your app.
Your dashboard splits traffic into people, verified crawlers, AI agents and scripts, with the networks they come from.
Allow, flag or block. Blocking runs on credits, and your free credits cover it to start.
Use cases
Allow the answer engines you want indexed and block training scrapers, without nuking Googlebot.
Stop headless automation hammering pricing, inventory and ticket endpoints.
Add friction to credential-stuffing and signup abuse driven by automation from masked IPs.
Decide per crawler whether GPTBot, ClaudeBot, Perplexity and the rest may read your pages.
Integrations
Pick where your site runs. Each install reports to the same dashboard.
Every request, sorted
Humans, verified crawlers, AI agents and scripts, told apart by the network, the browser and what each operator publishes.

Verdicts
Every request lands in exactly one class with a confidence and a recommended action.
A real person in a real browser, so the request is allowed.
A verified good bot such as Googlebot or Bingbot that is allowed and never accidentally blocked.
An identified AI fetcher such as GPTBot or ClaudeBot that you flag and decide on per policy.
Headless automation with no good identity, often from a masked origin, so the request is blocked.
Under the hood
Agentscan fuses the shared IP engine with request-level fingerprints and a verified allowlist.
Starts from the engine verdict of datacenter, VPN, proxy or clean residential, because masked origin changes everything.
Detects HeadlessChrome, Playwright, Puppeteer, Selenium and scripted clients from the User-Agent plus client-side signals like webdriver.
A TLS client fingerprint that survives a spoofed User-Agent, separating real browsers from impostors.
Scores how browser-like the header set is, since real browsers send Accept, Accept-Language and Accept-Encoding together.
Googlebot, Bingbot and friends are confirmed by forward-confirmed reverse DNS rather than by a spoofable User-Agent string.
Knows GPTBot, ClaudeBot, PerplexityBot, Google-Extended and more, so you can allow or block them by name.
For your developers
Call it from the edge with signals collected by the snippet. Verdicts are Redis-cached for low latency.
curl -X POST 'https://ipscanner.io/v1/agentscan/check' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"ip":"198.51.100.7","user_agent":"Mozilla/5.0 HeadlessChrome/120","ja4":"t13d1516h2_8daaf6152771_...","headless_flags":{"webdriver":true},"headers":{"Accept":"*/*"}}'Your 25,000 free credits cover 2,500 checks. Call it from your server: the key does not belong in a browser.
FAQ
Install it, watch your traffic sorted by class, then choose what to block.
No credit card to start