Skip to main content
AI assistants are LLM chat applications that can answer questions, summarize information, and make requests to websites to gather information. When an AI assistant is making a request to a website, Fingerprint can detect these requests and identity the assistant category, provider and identity. The most common AI assistants are ChatGPT, Gemini, and Claude.ai. Fingerprint’s AI assistant detection lets you detect and verify AI assistants visiting your website or using your APIs and distinguish them from malicious bots. It uses Web Bot Auth, IP, and DNS checks to verify AI assistant identity. When Fingerprint detects an assistant, it returns structured metadata, including the assistant’s provider, name, and the identity verification status in the bot_info field of the event. This lets you make precise access decisions: allow authorized assistants, block unverified automation, or apply different logic based on assistant category and provider.

​
How identity verification works

Fingerprint will use all available methods to verify the assistant identity and will also detect spoofing / impersonation attempts. The identity value reflects the outcome of the verification:

​
Event payload

When Fingerprint detects a bot, the event can include the following fields. You get them in v4 events whether you use the Server API, webhooks, or Sealed Client Results. The bot_info object contains: bot_info is present only when Fingerprint recognizes the AI tool or bot, and isn’t available in v3. For the full schema, see the Server API reference. For the full list of bots, see the Bot Directory.

​
Supported AI assistants

For the full list of all detectable AI tools and bots, see the Bot Directory.

​
Using detection results

The bot field (good, bad, not_detected) is a legacy signal. For AI assistants and other recognized bots, use bot_info.identity instead, as it provides more precise, actionable information. Note that identity is only available for well-known bots and assistants in the Bot Directory. Some generic browser automation tools (Selenium, Playwright, headless Chrome, etc.) will not have a bot_info entry and should be handled using the bot: bad signal.

​
Next steps

Bot Directory

Full list of detectable bots and agents

AI agent detection

Detect and verify AI agents

Submit your assistant to Fingerprint directory

Submit your assistant or bot to the Fingerprint Bot Directory