Use case
Keep rogue AI agents and AI-driven attackers out
Attackers use language models to scan your app, write exploits and try stolen passwords faster than any team could. Some AI agents scrape what they should not and abuse signups. Others are your customers' assistants doing a job. camada judges each one by what it does.
The pattern
What it looks like in your traffic
- Automation in the browser: webdriver set, headless signs, no input events across a session.
- Probes for secrets and admin panels: /.env, /.git, wp-config.php, /phpmyadmin.
- Injection payloads in query strings, many families from one client.
- Signups and logins in bursts from fresh sessions on cloud networks.
Detection
How camada scores it
| What camada looks for | Score |
|---|---|
| webdriver true or automation globals present | +60 |
| Browser beacon user agent differs from the header user agent | +40 |
| Secret or config file probe (/.env, /.git, wp-config.php, *.sql) | +30 per path, up to 60 |
| Web shell or exploit-kit path | +60 |
| Injection payloads, per distinct family | +15, up to 45 |
| Beacon with real input events within 10 seconds | -30 |
The triage model and the investigation agent read the requests behind a score, plus the facts you recorded about your site, before anything is blocked. Each verdict says why.
A sample of the rules, with their default weights. The full pipeline and more rules are on how it works.
Setup
Set it up
- Install the SDK for your framework, and add the beacon to your HTML pages. Framework quickstarts →
- Allow-list the agents you trust, and choose what each category does. Rules and list entries →
- Record facts about your site, such as a partner that calls your API from a cloud network, so the agent does not flag it. Memory →
Limits
What camada does not do
- camada does not check cryptographic signatures from AI agents today, so it cannot vouch for an agent you want to let in. Your allow-list does that.
- An agent that behaves like one careful human may not stand out. camada acts on behaviour, not on who sent the agent.
- API clients cannot solve a challenge. On API calls camada can only signal your app with a response header.
Questions
Common questions
Does camada block all AI agents?
No. camada keeps bad actors out, not bots. Customers, verified search engines and allow-listed agents get in. A rogue agent is judged by the same evidence as any other attacker: what it requests and how.
Can attackers using AI look exactly like customers?
Per request, often yes: real browsers, home IPs, valid requests. Across a session they still probe paths customers never visit, fail logins on many accounts or never run JavaScript. camada scores the whole session, the IP and the TLS fingerprint where it is visible.
Is an AI model deciding to block my traffic?
Models write verdicts, with guardrails. A block needs a malicious verdict at 80% confidence or more by default, each new project starts in a learning window that only recommends, and a person on your team turns enforcement on.
Other attacks camada handles: Credential stuffing · Scraping · CVE exploit scans. Plans and the 14-day trial: pricing.