AI AGENT DETECTION

AI agents now browse, buy, and fill out your forms. Know which ones to trust.

ChatGPT Agent, Claude and AWS AgentCore act for real users. Selenium, headless Chromium and proxy farms act against you. TrustSig identifies every request as a human, a verified AI agent, or a bad bot, then hands your backend one signed verdict.

Free forever tier. No credit card, no sales call.

0 msAdded latency, runs out-of-band
SignedCryptographic agent identity
FreeFull detection, free tier
No inline proxy0 ms added latencyGDPR-nativeWeb Bot Auth ready
01 THE NEW TRAFFIC MIX

Three kinds of traffic. One of them is new.

Your old defenses see two buckets, human or bot. Agentic traffic broke that model. TrustSig sorts every request into the bucket that actually matters.

Serve normally

Humans

Real people on real browsers. No CAPTCHA, no challenge, no friction. They never know TrustSig ran.

Let them through

Verified AI agents

ChatGPT Agent, Claude and AWS AgentCore acting for your customers. Cryptographically signed and identified, so you can serve, rate-limit or bill them on purpose.

Block on sight

Bad bots

Selenium, headless Chromium and residential-proxy farms wearing a browser costume. Caught by signal, not by guesswork.

02 WHY IT MATTERS

Blocking every bot now blocks your customers' agents.

Agentic traffic is no longer an edge case. Treating it all as abuse, or waving it all through, both cost you.

0

Verified AI agents wrongly blocked when you classify by signed identity instead of challenging every agent with a CAPTCHA it will fail. The real ones pass. The forgeries don't.

Selenium

Automation frameworks driving a real browser engine, flagged by behavior and signal, not by a checkbox they can click.

Proxies

Residential-proxy and datacenter VMs rotating IPs to look human, surfaced the moment they touch an endpoint.

Signed

Agents that present a cryptographic identity, verified against the issuer so you can trust, and act on, who is calling.

03 HOW IT WORKS

Four signals. One verdict.

No inline proxy, no traffic rerouted through us. A lightweight signal is captured at the edge and resolved against TrustSig out-of-band.

01Capture fingerprintA tamper-resistant device and network signal is collected client-side. No cookies, no PII.
02Check agent signatureSigned agents (Web Bot Auth, AWS AgentCore) are verified against the issuing provider.
03ClassifyHuman, verified AI agent, or bad bot, with a confidence score and bot type.
04Return BOT_INFOYour backend reads one JSON verdict and decides: allow, rate-limit, or block.
Signals we readtls_fingerprint, headless_markers, proxy_topology, agent_signature, plugin_surface, navigator_integrity

Verdicts resolve in milliseconds, out-of-band. Your page never waits on TrustSig and your users never see a challenge.

04 THE BOT_INFO API

One call tells you exactly who is knocking.

Query TrustSig for any request and get a structured verdict, the same response that powers the live monitor above. Signed agents come back identified, down to the provider and confidence.

BOT_INFO response
// GET /checkout · POST /api/order
{
  "bot": "good",
  "bot_type": "chatgpt_agent",
  "bot_info": {
    "category": "ai_agent",
    "provider": "OpenAI",
    "name": "ChatGPT Agent",
    "identity": "signed",
    "confidence": "high"
  },
  "fingerprint": "f3a9c1b4e72b",
  "verdict": "allow"
}
Decide per verdictallow: humans, allow: verified agents, rate-limit: unknown bots, block: bad bots

Fail-closed by design: act only on an explicit verdict. Unknown traffic is yours to throttle or challenge, never silently trusted.

05 WHY TRUSTSIG

Detection that fits how agents actually work.

Built for a web where your best traffic might not be human.

01

Identity, not interrogation

CAPTCHAs ask every visitor to prove they are human, and modern agents and bots both pass. TrustSig reads a signed identity and a hardware signal instead, so verdicts hold even when the user-agent string lies.

02

Invisible to everyone

No challenge, no checkbox, no redirect. Humans and legitimate agents flow straight through while the work happens out-of-band on your backend.

03

Built for agentic traffic

First-class support for Web Bot Auth and signed-agent standards. As providers ship agent identity, you already speak it.

04

EU-hosted and GDPR-native

Cookieless, PII-free signals hosted in the EU. Bot defense that does not create a privacy problem of its own.

06 Pricing

Start free. Stay free until you grow.

No card. EU-hosted on every tier.

Starter

€0free

For personal projects and sites getting started with bot protection.

  • 50,000 requests / month2 domains
  • Full threat protection suite
  • Bot farm blocking
  • No CAPTCHAs for visitors
  • Community support

Business

€63/mo · billed yearly

For established companies needing high-volume protection and priority SLA.

  • 750,000 requests / month25 domains • €5 per 100k extra reqs
  • Full threat protection suite
  • Bot farm blocking
  • No CAPTCHAs for visitors
  • Priority support

Enterprise: unlimited volume · SLAs · on-prem · dedicated support.

What counts as a check?

One check is a single verification request: a page view, form submit, or login attempt that TrustSig evaluates. You only spend a check when traffic actually hits a protected surface, so bot floods do not quietly drain your quota.

07 FAQ

AI agent detection, answered.

Legitimate agents like ChatGPT Agent and AWS AgentCore present a cryptographic signature, using Web Bot Auth and provider-specific standards. TrustSig verifies that signature against the issuing provider, so a forged user-agent string is not enough to pass as a verified agent. Everything unsigned is classified on device and network signals instead.

Stop guessing who is on the other end.

Identify every human, verified agent and bad bot in real time. Free to start, no CAPTCHA, no inline proxy.