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

DuckAssistBot

DuckDuckGo · AI search crawlers · json

User-agent: DuckAssistBot
Disallow: /


robots.txt token	`DuckAssistBot`
User-agent contains	`DuckAssistBot`
Operator	DuckDuckGo
Category	AI search crawlers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

Fetches pages so DuckAssist can generate and cite answers inside DuckDuckGo.

What blocking it costs you

No DuckAssist answers or citations from your site. Ordinary DuckDuckGo results are unaffected.

Full user-agent string

Mozilla/5.0 (compatible; DuckAssistBot/1.0; +https://duckduckgo.com/duckassistbot)

Allow it instead

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

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