AI assistant detection requires a Flow worker deployment.
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. Theidentity value reflects the outcome of the verification:
API response
When Fingerprint detects a bot, the Server API response includes the following fields:
The
bot_info object contains:
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
Thebot 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