AI Crawler Checker — Robots.txt Policy for Six Bots avatar

AI Crawler Checker — Robots.txt Policy for Six Bots

Pricing

from $1.20 / 1,000 crawler policy checkeds

Go to Apify Store
AI Crawler Checker — Robots.txt Policy for Six Bots

AI Crawler Checker — Robots.txt Policy for Six Bots

AI crawler checker: declared robots.txt permissions for six fixed AI bots at a URL path, without fetching the page. $0.0015 per path; start extra; usage included; failed results uncharged.

Pricing

from $1.20 / 1,000 crawler policy checkeds

Rating

0.0

(0)

Developer

Logan Parker

Logan Parker

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 hours ago

Last modified

Share

AI crawler checker reports declared robots.txt permissions for GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot and Amazonbot at each supplied public URL path, without impersonating bots or fetching the tested page. AI agents can call and pay through Apify MCP. List event rates are $0.0015 per path; start is extra, usage is included and failed results are uncharged.

Example result

Example record for the minimal input under How to use it, as this Actor returned it on 2026-10-31 in a run of its production image; the record is kept unchanged with the release.

{
"robotsStatus": 200,
"robotsSha256": "e62876aa4593da0024f896868ea789201cf929606aebcc56dcda88592017209f",
"crawlers": [
{
"crawler": "GPTBot",
"allowed": true
},
{
"crawler": "ClaudeBot",
"allowed": true
},
{
"crawler": "Google-Extended",
"allowed": true
},
{
"crawler": "PerplexityBot",
"allowed": true
},
{
"crawler": "CCBot",
"allowed": true
},
{
"crawler": "Amazonbot",
"allowed": true
}
],
"scope": "Declared robots.txt policy only; not a live bot access test or legal permission.",
"url": "input-1",
"ok": true
}

How to use it

Start a run in Apify Console, by API or from an agent with an input like this one — it is the input Apify runs every day to test this Actor:

{"urls": ["https://docs.apify.com/"]}
FieldTypeMeaning
urlsarrayOne record for each input; only nonpersonal technical metadata is returned.

Events and prices

EventTitleCharged whenFREE / BRONZESILVERGOLD / PLATINUM / DIAMOND
crawler-policy-checkedCrawler policy checkedOne successful input with a readable result written to the dataset.$0.0015$0.00135$0.0012

Platform usage is not passed through. Apify's automatic actor-start event remains $0.00005 per started GB (one GB or less counts once). The synthetic dataset-item event is absent. Charge limits stop further paying work; unprocessed inputs receive uncharged errors. Completed readable pending events are settled on abort.

Worked cost example: ten successful crawler policy checked events cost $0.015 at list, plus actor start. Failures are not included in that count.

Call it from an agent

Through Apify's MCP server (https://mcp.apify.com) use call-actor:

{
"actor": "hermeskd/ai-crawler-access-check",
"input": {
"urls": [
"https://docs.apify.com/"
]
},
"callOptions": {
"maxTotalChargeUsd": 0.01,
"timeout": 600
},
"waitSecs": 30
}

Then call get-dataset-items with the returned defaultDatasetId. Dedicated tool URL: https://mcp.apify.com?tools=hermeskd/ai-crawler-access-check

Output fields

FieldMeaning
urlOne-based input reference (input-1, input-2, ...); never the supplied value.
okTrue for a returned result; a failure is never charged.
robotsStatusHTTP status from robots.txt; 404/410 means no declared policy.
robotsSha256Hash of a valid policy body, or null if absent.
crawlersFixed named crawler tokens and declared allowed booleans.
scopeDeclared robots policy only, not a live bot access test.
errorFailure, always uncharged.

Limits and run time

1–50 public URLs, each at most 2048 characters. Only the origin robots.txt is fetched, at most 64 KiB/512 allow-disallow rules/2048 lines. Six fixed crawler tokens; unavailable/throttled/invalid policy refuses uncharged. Missing 404/410 policy permits by RFC convention. This checks declared policy, not actual bot HTTP access, training rights, page content or legal permission.

The default run timeout is 600 seconds. Local production-image tests at 128 MB and one CPU: three cold typical calls took 7.88–9.37 seconds wall time, peak typical RSS 82.5 MiB; the ten-event benchmark took 13.78 seconds. Apify cold startup, billing and the deploy pricing floor remain unverified.

Inputs are correlated by their one-based list position. Caller strings, URL paths, queries, credentials and exception text are never copied into identities or errors. Duplicate entries retain separate positions.

Errors

CodeMeaning
http_errorThe source answered an unsuccessful HTTP status.
download_failedThe request or connection failed within its bounded deadline.
source_invalidThe source response is malformed or outside the documented supported shape.
not_foundThe requested technical record is unavailable.
robots_disallowedrobots.txt forbids fetching the URL; no request was made to it.
blocked_hostThe host is on the deny-list or resolves to a private or local address; no request was made.
too_largeThe response exceeded the size cap.
timeoutThe input did not finish within the run's time budget.
invalid_inputThe run input passed the input schema but cannot be used; the message names the field.
internal_errorUnexpected internal failure; private exception details are excluded.
charge_limit_reachedThe run reached its maximum total charge; this input was not processed.

No failure record is charged. A run fails only when all input outcomes are Actor-side failures; caller errors and a mixture of caller/Actor failures do not fail the run.

Sources and terms

Only process content you have the right to process. URL fetches obey HermesBot robots-group selection, the shared deny-list, public-address checks on connections and redirects, honest identity, deadlines and rate limits. No caller credentials, cookies, CAPTCHA solving, residential proxies or evasion. Caller-authorized public website robots.txt under the shared fetch policy, based on RFC 9309. The prefill is Apify Apache-2.0 documentation with permissive robots verified on 2026-10-30. No page content, raw rules, sitemap links or contacts returned.

Not affiliated

Not affiliated with or endorsed by the source publishers or Apify.

Changelog

  • 1.0 (2026-10-30) — 2026-10-30: first factory-built version..