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

YandexCalendar

Yandex · User-triggered fetchers · json

User-agent: YandexCalendar
Disallow: /
robots.txt tokenYandexCalendar
User-agent containsYandexCalendar
OperatorYandex
CategoryUser-triggered fetchers
robots.txtignores the * group; obeys rules named for its own token
Verify byreverse DNS

What it is

Downloads calendar files a user subscribed to. Yandex notes these files are often in directories that are disallowed for indexing, which is why the general rules are not applied.

What blocking it costs you

Users who subscribed to a calendar you publish stop receiving updates.

Full user-agent string

Mozilla/5.0 (compatible; YandexCalendar/1.0; +http://yandex.com/bots)

Allow it instead

User-agent: YandexCalendar
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=yandexcalendar&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 · block-all-ai · allow-ai-search-only · maximum-ai-visibility