APIs-GoogleGoogle's special-case crawlers page says these crawlers are used where there is an agreement between the site and the product. The robots.txt token is APIs-Google. The page says the global user agent (*) is ignored. Crawling preferences for this token affect delivery of push notification messages by Google APIs. The list is not exhaustive. This check matches the whole token and still reports the RFC 9309 decision.
owner_requestedignores_star. The vendor says this robot does not take the general User-agent: * rules in robots.txt into account.APIs-Google (+https://developers.google.com/webmasters/APIs-Google.html) The page prints this string as the HTTP user agent. The robots.txt token is the same string, APIs-Google.curl -s https://whosthatbot.com/v1/crawlers/apis-google
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows APIs-Google 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: APIs-Google\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["apis-google"]}}}'
That call returns fetched_target false. This row is disallow via group APIs-Google, rule Disallow: /.