What is cohere-ai? AI crawler guide
cohere-ai is a crawler or fetcher associated with Cohere. See source-graded user-agent, robots.txt, verification, and observation guidance.
What is cohere-ai?
cohere-ai is a reported crawler or fetcher string associated with Cohere, but current operator evidence is incomplete. Cohere token reported for retrieving data in response to user-initiated prompts.
Evidence status
| Field | Value |
|---|---|
| Evidence | Reported, not operator verified |
| Lifecycle | Status uncertain |
| Purpose | interaction |
| robots.txt posture | honors |
| Source checked | 2026-06-11 |
Reported user-agent
cohere-ai
Allowing cohere-ai only creates the possibility of retrieval. To find out whether your pages are selected, measure which answer engines actually cite your pages using a stable query set.
robots.txt allow example
User-agent: cohere-ai Allow: /
robots.txt block example
User-agent: cohere-ai Disallow: /
What the rule can and cannot do
Robots.txt expresses an access policy to compliant automated crawlers. It does not authenticate the sender, remove content already collected, or guarantee that a model will use or not use content.
How to verify a request
- Match the complete documented user-agent where one exists. A match is only a clue.
- Look for operator-published IP ranges, reverse DNS, or signed-request guidance. None is attached to this record.
- Keep the observed request, operator documentation, and any inference as separate fields.
Observed in Trakkr connected-site data
| Measure | Value |
|---|---|
| Matching signature | cohere-ai |
| Classified requests | 10342 |
| Sites in sample | 85 |
| Window | 2026-07-18 through 2026-08-17 |
| Method | Finalized daily crawler summaries from connected Trakkr sites, grouped by the crawler signature detected in each request. |
| Limits | This is a connected-site sample, not a representative sample of the web. A matching user-agent or signature does not prove that the named operator sent the request. Counts describe classified request signatures, not market share or unique pages crawled. |
JavaScript behavior
The cited operator material does not verify JavaScript rendering. Serve useful HTML before client-side JavaScript where possible.
Related bots
- Google-Agent: Also tracked as a live fetcher.
- Claude-Code: Also tracked as a live fetcher.
- Google-Gemini-CLI: Also tracked as a live fetcher.
- Meta-ExternalFetcher: Also tracked as a live fetcher.
- Claude-User: Also tracked as a live fetcher.
- AmazonBuyForMe: Also tracked as a live fetcher.
- Claude-Web: Also tracked as a live fetcher.
- NovaAct: Also tracked as a live fetcher.
- Google-GeminiNotebook: Also tracked as a live fetcher.
- Cohere: cohere-ai connects this operator term to its crawler behavior.
- Robots.txt: Robots.txt is the control file used to allow or block cohere-ai.
Frequently Asked Questions
What is cohere-ai?
cohere-ai is a reported, not operator verified crawler or fetcher record associated with Cohere.
What user-agent does cohere-ai use?
cohere-ai. Check the evidence status before attributing a matching request.
Can cohere-ai be blocked in robots.txt?
The record identifies cohere-ai as the token to review. Robots.txt is a request policy, not proof of model use or non-use.
How can I verify a cohere-ai request?
Treat the user-agent as a clue and look for operator-published IP, reverse-DNS, or signature guidance.
Data & Sources
- cohere-ai source reference - Source used to verify cohere-ai.