Bot intelligence record
Known Agent
Review firstUse the Known Agent identifier to separate Known Agents AI crawler, assistant, or AI search traffic from normal visitor requests in server logs.
- Operator
- Known Agents
- Family
- Known Agents
- Type
- Ai
- Source type
- Verified Directory
- Last checked
- 2026-05-20
User-Agent Pattern
Known AgentsKnown Agent
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Known Agent Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
AI crawling, assistant retrieval, AI search, or model-supporting discovery depending on the user-agent.
Record Details
Structured data- Operator
- Known Agents
- Family
- Known Agents
- Type
- Ai
- Purpose
- Ai Assistant
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-19
- Last checked
- 2026-05-20
- Source type
- Verified Directory
- Verification
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
Known Agent is listed in the Botcrawl directory as an AI agent from Known Agents. The primary identifier for log review is Known Agent.
Identification
- User-agent pattern:
Known Agent - Family: Known Agents
- Type: AI
- Kind: Agent
Common use
AI crawling, assistant retrieval, AI search, or model-supporting discovery depending on the user-agent.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.
Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: No.
Evidence and Source
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Match `Known Agent` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
- AI crawling, assistant retrieval, AI search, or model-supporting discovery depending on the user-agent.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.