curl -s https://www.pathwren.workers.dev/crawler/petalbot.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

PetalBot

Huawei · Search engines · json

User-agent: PetalBot
Disallow: /


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

What it is

Huawei's crawler for Petal Search, shipped as the default search on Huawei devices.

What blocking it costs you

Removal from Petal Search. Frequently blocked for volume rather than for policy.

Full user-agent string

Mozilla/5.0 (Linux; Android 7.0;) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36 (compatible; PetalBot;+https://webmaster.petalsearch.com/site/petalbot)

Allow it instead

User-agent: PetalBot
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=petalbot&s=client-dossiers'

/tools/verification-methods?crawler=petalbot
How do I prove a request really is PetalBot? 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://aspiegel.com/petalbot
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility