Skip to main content

What is ShieldLabs AI agent detection?

ShieldLabs AI agent detection identifies supported AI traffic visiting your website. It returns the detected client category, provider name when available and identity verification evidence, helping you distinguish recognized AI clients from risky automation. AI agents use large language models (LLMs) to plan and perform tasks on someone’s behalf. An agent can research products, navigate a website or complete a form. Some agents control a browser; others retrieve information without opening an interactive page.

AI agent and AI assistant detection results

The result depends on how the AI client accesses your content: This page explains agent traffic using supported browser platforms. AI assistant detection explains direct content retrieval and the AI Bot result. The bot directory lists supported clients in both categories.

How ShieldLabs verifies AI-agent traffic

ShieldLabs recognizes a supported platform and checks the identity evidence available on the identification. For Browserbase and Cloudflare Browser Run, this includes signed requests that identify the browser infrastructure.
  1. The browser platform signs its request.
  2. ShieldLabs checks the signature against the platform’s public keys.
  3. A successful check can establish the platform attribution and produce ai_browser: true.
The signature confirms the browser platform. It does not identify the person, customer or AI model controlling that browser. Use the browser integration to collect identifications and read the AI detection result on your backend.

Event payload

A scored webhook returns the detection and provider in its data object. This shortened, illustrative example shows recognized Browserbase traffic:
The excerpt shows fields inside data of an identification.scored event. All detection flags are booleans; unshown fields are omitted here for readability. Verify the webhook signature and deduplicate deliveries by the envelope’s event_id. The webhook reference shows the complete event structure.

Read the scope of verification

When supplied, client_identity.verified describes what ShieldLabs could establish. Each entry has a subject, a value_id and references to its supporting evidence. For example, this shortened attribution identifies Browserbase infrastructure:
An identity claim alone does not establish verified infrastructure. Read the verified entries rather than treating a name or a User-Agent header as proof.

Supported AI-agent platforms

ShieldLabs supports the following platforms. The AI browser result requires successful identity verification on the observed request. The bot directory also lists supported AI assistants and crawlers. A browser platform name does not reveal which assistant or model uses it.

Using AI agent detection results

Use the detected platform and its verified attribution alongside the action your application is protecting. Recognized AI browsers belong to the dashboard’s Good bot group and score 0. Apply identity verification results to your access policy and validate the expected account, domain and protected action on your backend.

View AI-agent traffic in the dashboard

Open an identification in Analytics to inspect its signals. The provider appears alongside AI Browser when available. Good bot groups AI browsers, AI bots and search bots in the aggregate views. Use a scored webhook for ai_browser and ai_browser_owner. History can include optional client_identity, but it does not return those two fields. See bot results in webhooks and History.

Next steps

AI assistant detection

Recognize AI assistants fetching pages and AI crawlers collecting content.

Bot directory

Find supported browser platforms, AI bots and crawlers.