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

YandexDirect

Yandex · Tools and frameworks · json

User-agent: YandexDirect
Disallow: /
robots.txt tokenYandexDirect
User-agent containsYandexDirect
OperatorYandex
CategoryTools and frameworks
robots.txtignores the * group; obeys rules named for its own token
Verify byreverse DNS

What it is

Reads the content of Yandex Advertising Network partner pages to work out their topic so relevant ads can be matched. Documented as not taking the general robots.txt rules into account.

What blocking it costs you

Ads on your pages become less relevant and earn less. Relevant only if you monetise with Yandex's network.

Full user-agent string

Mozilla/5.0 (compatible; YandexDirect/3.0; +http://yandex.com/bots)

Allow it instead

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

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://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots
Machine copies: json · markdown
Policies that name this crawler: allow-all · maximum-ai-visibility