`Baiduspider-image`

Baidu's FAQ lists Baiduspider-image as the image-search user-agent. It shows a robots.txt that disallows Baiduspider and allows Baiduspider-image on /image/. The FAQ says different user-agents can have different rules, and it does not put this token in the exceptions for Baiduspider-video, Baiduspider-cpro, or Baiduspider-ads. The same page says blocking Baiduspider blocks all crawling from Baidu. This check matches the whole token and does not treat Baiduspider as a prefix.

robots.txt token: Baiduspider-image
Operator: Baidu
Kind: search
robots.txt: obeys. The vendor says this crawler obeys robots.txt on automatic crawls.
HTTP user-agent: The English FAQ names this robots.txt token and does not publish a full HTTP user-agent string.
IP list: None on the cited page. The FAQ does not publish an IP list for this token. The verification section is about Baiduspider hostnames ending in .baidu.com or .baidu.jp. Botcard does not copy the example addresses.
Source: FAQs of Baiduspider. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/baiduspider-image

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Baiduspider-image on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Baiduspider-image\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["baiduspider-image"]}}}'

That call returns fetched_target false. This row is disallow via group Baiduspider-image, rule Disallow: /.