# 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.

- 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
- Source: https://help.baidu.com/question?prod_id=99&class=0&id=3001 (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 https://whosthatbot.com/mcp. Send `Content-Type: application/json` and `Accept: application/json, text/event-stream`. 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: /.

Each card paraphrases the linked vendor page and was checked on source.retrieved. This is not legal advice. robots.txt is a request from the site owner. Botcard does not fetch third-party sites and does not suggest ways around a disallow rule.