# YaK

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

| field | value |
|---|---|
| operator | Meltwater |
| category | Corpus and dataset builders |
| robots.txt token | `YaK` |
| user-agent contains | `YaK` |
| robots.txt | operator publishes no robots.txt statement |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://www.meltwater.com/en/suite/consumer-intelligence |
| last reviewed | 2026-09-14 |

## 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
```

## Block it

```
User-agent: YaK
Disallow: /
```

## Allow it

```
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.

- **How do I prove a request really is YaK?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=yak&s=client-dossiers'`  
  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.

JSON: https://www.pathwren.workers.dev/crawler/yak.json · index: https://www.pathwren.workers.dev/llms.txt