Botcard publishes short cards about AI crawler tokens. Each card names the vendor page it was checked against and the date it was read. Vendors change those pages. The card is right only as of that date.
The cards are not legal advice, not a permit to fetch a site, and not a way to get around a disallow rule. robots.txt is a request from the site owner. You decide what to do with it.
The checker reports an RFC 9309 match for each token in the pasted file. It is not a promise that a vendor will obey that file. Some cards say robots.txt may not apply, or that the fetcher generally ignores the file. The PerplexityBot card records a recommendation to allow the token so a site appears in search. That recommendation does not say a Disallow removes the site. The Applebot card says Apple respects robots.txt on general search crawls aimed at that token, does not follow crawl-delay, and follows a Googlebot group only when the file does not mention Applebot. The checker does not apply that fallback. The CCBot card says Common Crawl's page gives User-agent: CCBot and Disallow: / as the way to prevent the crawl, and that some crawlers falsely use that name. A separate post names an Opt-Out Ledger of legal requests. The checker reports that ledger and does not apply it. The checker does not fetch any website. tools/call with name check_robots, and list_crawlers and get_crawler, do the same work and also do not fetch a host.
Amazon says Amzn-User may not follow all robots.txt directives, and that Amzn-SearchBot follows other search bots when the file does not name it. The checker does not apply that fallback. Meta says Meta-ExternalFetcher may bypass robots.txt. DuckDuckGo says a DuckAssistBot disallow takes effect after 72 hours.
The JSON and pages are provided as-is, with no warranty. Google's crawler documentation is used under the terms stated on that page (CC BY 4.0, except as Google notes). Other vendor pages are cited, not copied in full.
Payments are not open.