xAI · Other AI
Grok
The product name, not an agent token: every xAI page fetched uses this word to mean the assistant itself, and none binds it to a fetching program. Its function as a user agent is therefore unestablished, and a bare inbound request carrying it is unattributable by construction. It earns a directory entry chiefly because it appears in crawler lists, and from there in robots.txt files, where the string behaves in a way none of the fully-specified tokens do.
- Operated by
- xAI
- Purpose
- Other AI
- robots.txt token
- Grok
- Verification
- User agent only
AI-adjacent traffic that does not fit the three purposes above.
How to verify Grok
xAI publishes no list of IP addresses for Grok, so nobody (us included) can prove that a request carrying this user agent really came from xAI. The name is trivial to copy. Treat it as a claim the visitor is making about itself, not as an identity anyone has checked.
There is no range list to confirm. This entry was last reviewed against xAI's own documentation on .
User agent
xAI has not published a full user-agent string for Grok. Requests are identified by the Grok product token appearing in the User-Agent header; we match that token rather than a whole string, because the rest of the header varies and matching it would miss real traffic.
robots.txt for Grok
Block
User-agent: Grok
Disallow: /Allow
User-agent: Grok
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking Grok costs you
The hazard here is over-match, not lost visibility. RFC 9309 matches on product tokens, but implementations vary between exact and substring comparison, so a bare User-agent: Grok group may silently capture GrokBot and Grok-DeepSearch as well (or match nothing whatsoever), and the operator who wrote it cannot predict which. That makes the cost of this single line indeterminate and potentially far larger than intended: you may believe you have published one rule and have in fact published three. If you want the siblings covered, name them explicitly; if you do not, know that this line may cover them anyway.
Vendor documentation
xAI does not publish documentation for Grok that we could find. Everything on this page comes from what they do publish elsewhere and from observed behaviour, so treat it accordingly.