Bot Directory Record
kagi-fetcher
Review firstkagi-fetcher is an AI search crawler from Kagi used for AI search indexing, answer retrieval, citation discovery; it appears in server logs as `kagi-fetcher`.
User-Agent Signal
Kagikagi-fetcher
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: kagi-fetcher
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.
kagi-fetcher is used for AI search indexing, answer retrieval, citation discovery, and page freshness checks.
Intelligence Details
Public record fields- Operator
- Kagi
- Family
- Kagi
- Type
- Ai
- Purpose
- Ai Search
- Identity type
- Observed
- Confidence
- Medium
- Last verified
- 2026-06-20
- Last checked
- 2026-06-20
- Source type
- Observed
- Verification
- Verify kagi-fetcher by matching `kagi-fetcher` to Kagi evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- kagi-fetcher has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- kagi-fetcher is an AI search crawler from Kagi used for AI search indexing, answer retrieval, citation discovery, and page freshness checks.
- Its primary user-agent pattern is
kagi-fetcher. - kagi-fetcher is not independently verified with Medium confidence. The identity type is Observed, and the evidence basis is observed traffic patterns and user-agent evidence.
- kagi-fetcher does not have confirmed robots.txt behavior in the available public evidence.
- kagi-fetcher should be handled according to the site owner’s AI crawler policy, with allow, block, or rate-limit rules applied deliberately.
Evidence and Source
- Verify kagi-fetcher by matching `kagi-fetcher` to Kagi evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- kagi-fetcher traffic is primarily detected by the `kagi-fetcher` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Kagi infrastructure before trusting the traffic.
- kagi-fetcher is used for AI search indexing, answer retrieval, citation discovery, and page freshness checks.
- kagi-fetcher has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Use in Botcrawl Edge
Botcrawl EdgeMatch this signal against live requests, related datacenter traffic, and rule actions in Edge.