New: monitor which AI crawlers actually visit your site with Sona Agent Analytics  |  See the platform →

ChatGLM-Spider

The least documented token in this directory - even its operator and purpose are unconfirmed attributions.

Reference reviewed by Sona

The operator publishes little or no documentation for this token. Details here come from community crawler registries and observed behavior, not vendor confirmation.

OperatorZhipu AI (attributed)
PowersGLM model family, per community attribution
PurposeModel training
User-agent tokenChatGLM-Spider
Respects robots.txtMostly

ChatGLM-Spider is the thinnest entry here, and it is worth being straight about how thin. The community ai.robots.txt registry lists its operator as unclear and its purpose as undocumented. The attribution to Zhipu AI - the Chinese lab behind the GLM model family and the ChatGLM assistant - is a reasonable inference from the token name, and it is what other crawler directories report, but no operator has confirmed it.

So treat everything on this page as provisional. If the name is honest, this crawler collects content for GLM models, a significant open-weight family used widely in Chinese enterprise and research deployments. If the name is not honest, this is an unknown scraper borrowing a plausible identity - and there is no published information that would let you tell the difference.

There is no crawler documentation page, no purpose statement, no compliance policy, no IP feed, and no verification method of any kind. Community registries list robots.txt compliance as unclear, which here reflects an absence of observation rather than mixed results.

Given that, the practical stance is simple. Add the robots.txt rule if you want it gone, but assume nothing enforces it, and use edge filtering if the block matters. An unidentifiable crawler with no accountable operator is a reasonable thing to block by default.

How ChatGLM-Spider behaves

  • Operator is a community attribution, not a confirmed fact - registries list it as unclear.
  • Purpose is undocumented; the training-crawler reading is inferred from the token name.
  • No IP feed, reverse-DNS convention, or operator documentation of any kind.
  • robots.txt compliance listed as unclear, reflecting absent observation rather than mixed behavior.

Allow ChatGLM-Spider

If the attribution holds, your content can inform GLM models and how ChatGLM describes your brand to a large user base.

User-agent: ChatGLM-Spider
Allow: /

Block ChatGLM-Spider

You cannot identify the operator, verify the traffic, or hold anyone accountable - which for many sites is reason enough.

User-agent: ChatGLM-Spider
Disallow: /

How to verify ChatGLM-Spider

No published verification method

Nothing is published: no IP feed, no reverse-DNS convention, no operator crawler page. This is the weakest verification position in the directory, because the usual fallback of checking traffic against a known operator's network does not apply when the operator itself is only an attribution. Treat this user-agent as an unidentified crawler and filter on the string alone.

Check an IP against this bot

Commonly confused with ChatGLM-Spider

TongyiBot

Both are thinly documented Chinese-operator tokens, but Alibaba's ownership of TongyiBot is established while this token's operator is not.

Kimi-User

Also a Chinese AI product token with limited documentation - but Moonshot AI's connection to Kimi-User is at least clear.

ChatGLM-Spider FAQs

Who operates ChatGLM-Spider?

Not confirmed. Community registries list the operator as unclear. Zhipu AI is the widely reported attribution and a reasonable inference from the token name, but no operator has publicly claimed the crawler.

Should I just block it?

For many sites, yes. You cannot identify the operator, verify the traffic, or hold anyone accountable for its behavior. An unidentifiable crawler with no published documentation is a defensible default block.

Will a robots.txt rule stop it?

Unknown. Compliance is listed as unclear, which here reflects a lack of observation rather than mixed results. Add the rule, but use edge filtering if the block actually matters to you.

Why is this page less detailed than the others?

Because the available information genuinely is thinner. There is no operator crawler page, purpose statement, compliance policy, or verification method - and inventing specifics to fill the gap would make this page less useful, not more.

Can ChatGLM-Spider read your page right now?

Test any URL and see exactly what AI crawlers receive.

Check my site