Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.fingerprint.com/llms.txt

Use this file to discover all available pages before exploring further.

AI assistant detection requires a Flow worker deployment.
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 Server API response. 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:
ValueMeaning
verifiedIdentity verified
unknownAssistant recognized, but the identity couldn’t be verified
spoofedAssistant presented an identity that failed verification

​
API response

When Fingerprint detects a bot, the Server API response includes the following fields:
FieldTypeDescription
botstringgood, bad, or not_detected
bot_typestringAdditional classification, e.g. ai_assistant
bot_infoobjectExtended metadata for recognized assistants, agents, and bots
The bot_info object contains:
FieldDescription
categoryai_assistant
providerThe organization that operates the assistant, e.g. OpenAI or Anthropic
nameHuman-readable assistant name, e.g. ChatGPT-User
identityVerification status: verified, unknown or spoofed
bot_info is available in Server API v4 and only when Fingerprint recognizes the AI tool or a bot. See the Server API reference for the full schema. The full list of bots is available here: full list.

​
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.
ScenarioSuggested action
bot_info.identity: verifiedAllow: assistant identity is confirmed and safety verified
bot_info.identity: unknownApply custom logic: assistant is recognized but unverified
bot_info.identity: spoofedReview: verification failed, which may indicate misconfiguration or malicious spoofing
bot is bad, no bot_info (legacy)Review or Block: unrecognized and potentially malicious automation

​
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