xAI · Other AI
xAI-Grok
Set this token beside GrokBot and almost nothing separates the two. Same vendor, same claimed era, same absent documentation, and the strings circulating for them differ only in the order of the two words and in the host their trailing URL points at, the consumer product domain for one and the corporate domain for the other. That is a formatting difference, not evidence of a second crawler. No xAI page distinguishes this token from GrokBot, from xAI-Bot, or from the bare product name, so its function is unestablished and it is the strongest duplicate-pair candidate in the whole set.
- Operated by
- xAI
- Purpose
- Other AI
- robots.txt token
- xAI-Grok
- Verification
- User agent only
AI-adjacent traffic that does not fit the three purposes above.
How to verify xAI-Grok
xAI publishes no list of IP addresses for xAI-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 xAI-Grok. Requests are identified by the xAI-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 xAI-Grok
Block
User-agent: xAI-Grok
Disallow: /Allow
User-agent: xAI-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 xAI-Grok costs you
Unquantifiable on its own, because the entry it duplicates is itself undocumented. The practical guidance here is hygiene rather than cost: if you write a rule for one of the pair, write it for both, since there is no basis for predicting which of the two strings a real request would carry and a rule matching only the other one sits inert without ever telling you. Should your own logs show one of the two and never the other, that observation outweighs anything published about either: for a token in this state, your access log is better evidence than the entire secondary literature.
Vendor documentation
xAI does not publish documentation for xAI-Grok that we could find. Everything on this page comes from what they do publish elsewhere and from observed behaviour, so treat it accordingly.