curl -s https://www.pathwren.workers.dev/crawler/baiduspider.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

Baiduspider

Baidu · Search engines · json

User-agent: Baiduspider
Disallow: /


robots.txt token	`Baiduspider`
User-agent contains	`Baiduspider`
Operator	Baidu
Category	Search engines
robots.txt	obeys robots.txt (documented)
Verify by	reverse DNS

What it is

Baidu's search crawler, and the ingest path for Baidu's Ernie-backed answers.

What blocking it costs you

Removal from Baidu Search, which matters only if you want Chinese-language traffic.

Full user-agent string

Mozilla/5.0 (compatible; Baiduspider/2.0; +http://www.baidu.com/search/spider.html)

Allow it instead

User-agent: Baiduspider
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=baiduspider&s=client-dossiers'

/tools/verification-methods?crawler=baiduspider
How do I prove a request really is Baiduspider? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://help.baidu.com/question?prod_id=99&class=0&id=3001
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility