Will this block good bots like search crawlers?

Only if you tell it to. Rupt names the category behind every request, so search crawlers, uptime monitoring, partner integrations and customer AI agents doing authorized work are identified as what they are. You set the policy per type. Nothing is blocked by default because it happens to be automated.

Do we have to show a captcha?

No. Rupt classifies from the browser engine, the automation driver, the network it arrives on and the timing between actions, so the decision is made on the request itself. Real users never see a puzzle, and a solver farm has nothing to solve.

How do you detect an AI agent specifically?

By fingerprinting the framework it runs on. Computer Use, Browser Use, Browserbase, AgentQL, Selenium, Puppeteer and Playwright each leave their own marks, and Rupt reads them alongside headless markers, idle time and input behavior. You get the framework, the version and a confidence score, not just the word bot.

What if the traffic comes through a residential proxy?

Network is one of four signals, never the whole case. A residential exit hides the datacenter IP and changes nothing about the automation driver, the spoofed canvas, the zero mouse events or the perfectly spaced timing. Automation has to get all four right, and it does not.

Does it slow the request down?

No. Classification takes under 20ms and a policy verdict comes back in under 50ms, so you can wrap a login, a signup or a checkout without your users noticing.

Can I allow an agent on one endpoint and block it on another?

Yes, and most teams do. Wrap the actions you care about with rupt.evaluate() and the same identification reaches every one of them. A shopping agent can read your catalog, get challenged at the cart, and be blocked at the login. Same intelligence, your rules.

Bot detection software

1Advanced

Incredibly accurate bot and AI agent detection.

Rupt takes a request apart down to the browser engine, the automation driver, the network it arrives on and the timing between keystrokes. Automation has to get every one of those right to pass as human, and it does not.

Traffic /POST /api/login

Live

Request teardown

Browser engineChrome 141, headless

Automation driverPlaywright

Network originDatacenter range

Canvas and WebGLSpoofed

Input timingNo human variance

Session historyFirst contact

Then Automated

Automation seen today

GPTBotAI crawlerDeclared

GooglebotSearch crawlerDeclared

Uptime monitorHealth checkDeclared

Headless ChromeScraperUndeclared

Selenium gridCredential stuffingUndeclared

Detection catalog

AddedAgent signature, new assistant2h ago

UpdatedHeadless markers, Chrome 1411d ago

AddedResidential proxy ranges2d ago

UpdatedCanvas spoofing technique4d ago

AddedAutomation framework build6d ago

surfaces checked: 40+ surfaces checked
to classify: <20ms to classify
confidence: 99% confidence

2Rich

Far more than a yes or no on bots.

Rupt tells you which agent it is, whether it declares itself, and what it came to do. That surrounding detail is what lets you welcome the automation you want and stop the rest, instead of blocking both.

Traffic /Agents

Live

Request teardown

Browser engineChrome 141, headless

Automation driverPlaywright

Network originDatacenter range

Canvas and WebGLSpoofed

Input timingNo human variance

Session historyFirst contact

Then Automated

Automation seen today

GPTBotAI crawlerDeclared

GooglebotSearch crawlerDeclared

Uptime monitorHealth checkDeclared

Headless ChromeScraperUndeclared

Selenium gridCredential stuffingUndeclared

Detection catalog

AddedAgent signature, new assistant2h ago

UpdatedHeadless markers, Chrome 1411d ago

AddedResidential proxy ranges2d ago

UpdatedCanvas spoofing technique4d ago

AddedAutomation framework build6d ago

agents identified: 5 agents identified
allowed through: 3 allowed through
denied: 2 denied

3Current

We do the research so you do not have to.

New frameworks, new evasion techniques and new agents show up every week. The detection catalog updates continuously, so your protection keeps moving without you shipping anything.

Traffic /Catalog

Live

Request teardown

Browser engineChrome 141, headless

Automation driverPlaywright

Network originDatacenter range

Canvas and WebGLSpoofed

Input timingNo human variance

Session historyFirst contact

Then Automated

Automation seen today

GPTBotAI crawlerDeclared

GooglebotSearch crawlerDeclared

Uptime monitorHealth checkDeclared

Headless ChromeScraperUndeclared

Selenium gridCredential stuffingUndeclared

Detection catalog

AddedAgent signature, new assistant2h ago

UpdatedHeadless markers, Chrome 1411d ago

AddedResidential proxy ranges2d ago

UpdatedCanvas spoofing technique4d ago

AddedAutomation framework build6d ago

since last update: 2h since last update
changes this week: 5 changes this week
releases from you: 0 releases from you

Detect

Act

Free tools

By use case

By industry

Developers

Learn

Advanced bot and AI agent detection.

Rupt takes every request apart and inspects it layer by layer, catching the automation behind scraping, click fraud, credential stuffing, and fake signups.

Extremely advanced bot and automation detection.

Incredibly accurate bot and AI agent detection.

Far more than a yes or no on bots.

We do the research so you do not have to.

Not every bot is bad. Rupt tells you which one this is.

AI agents

Scrapers and crawlers

Credential stuffers

Click farms

Fake-account bots

SMS pumpers

Engagement bots

Four signal types. One identification.

Device and browser

Velocity and timing

Network and origin

Behavioral coherence

Questions teams ask about bot and AI agent detection:

Find out how much of your traffic is automated.