# YandexOntoDB

Yandex says YandexOntoDB is the information card robot and that it takes the general rules in robots.txt into account. YandexOntoDBAPI is a different token that downloads dynamic data and does not take those general rules into account. The robot list says an agreement between Yandex and the site owner can override some robots.txt restrictions. This check does not apply that agreement.

- Operator: Yandex
- Kind: search
- robots.txt: obeys. The vendor says this crawler obeys robots.txt on automatic crawls.
- HTTP user-agent: Mozilla/5.0 (compatible; YandexOntoDB/1.0; +http://yandex.com/bots) The table publishes this string. YandexOntoDBAPI is a different token on the next row.
- IP list: none on the cited page
- Source: https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots (retrieved 2026-10-18)

## JSON

`curl -s https://whosthatbot.com/v1/crawlers/yandexontodb`

## Check this token

tools/call with name check_robots is the same check at https://whosthatbot.com/mcp. Send `Content-Type: application/json` and `Accept: application/json, text/event-stream`. The pasted file disallows YandexOntoDB on `/docs` and allows `*`. The call does not fetch a host.

```
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: YandexOntoDB\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["yandexontodb"]}}}'
```

That call returns fetched_target false. This row is disallow via group YandexOntoDB, rule Disallow: /.

Each card paraphrases the linked vendor page and was checked on source.retrieved. This is not legal advice. robots.txt is a request from the site owner. Botcard does not fetch third-party sites and does not suggest ways around a disallow rule.