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

Yeti

Naver · Search engines · json

User-agent: Yeti
Disallow: /


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

What it is

Naver's crawler. Naver is South Korea's largest search portal and runs its own index and its own generative answers.

What blocking it costs you

Removal from Naver, which is most of Korean search.

Full user-agent string

Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd)

Allow it instead

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

/tools/verification-methods?crawler=yeti
How do I prove a request really is Yeti? 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://searchadvisor.naver.com/guide/seo-basic-crawl
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility