curl -s https://www.pathwren.workers.dev/crawler/yandexadditional.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
Yandex · AI training crawlers · json
User-agent: YandexAdditional Disallow: /
| robots.txt token | YandexAdditional |
| User-agent contains | YandexAdditional |
| Operator | Yandex |
| Category | AI training crawlers |
| robots.txt | ignores the * group; obeys rules named for its own token |
| Verify by | reverse DNS |
The token that controls whether already-indexed pages may appear in Search with Yandex AI answers. Yandex's table says it makes no indexing requests of its own — it exists so a site can opt out of the generative answer without leaving the index.
You disappear from Yandex's AI answers while staying in Yandex Search. This is Yandex's equivalent of Google-Extended, and it is the cheap opt-out most people are looking for.
Mozilla/5.0 (compatible; YandexAdditional/1.0; +http://yandex.com/bots)
User-agent: YandexAdditional Allow: /
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=yandexadditional&s=client-dossiers'
/tools/verification-methods?crawler=yandexadditionalEvery 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://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots
Machine copies: json ·
markdown
Policies that name this crawler:
allow-all · block-ai-training · block-all-ai · maximum-ai-visibility