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

YaK

Meltwater · Corpus and dataset builders · json

User-agent: YaK
Disallow: /


robots.txt token	`YaK`
User-agent contains	`YaK`
Operator	Meltwater
Category	Corpus and dataset builders
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Meltwater's crawler, feeding the live data stream behind its media-monitoring and consumer-intelligence suite.

What blocking it costs you

Your content stops appearing in Meltwater's media monitoring — which is how PR teams find out you were mentioned. Some publishers want to be in it.

Full user-agent string

YaK

Allow it instead

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

/tools/verification-methods?crawler=yak
How do I prove a request really is YaK? 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://www.meltwater.com/en/suite/consumer-intelligence
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · block-datasets · maximum-ai-visibility