Skip to main content
The AI Access API lets you probe a public domain and find out whether the major AI answer engines (ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, DeepSeek, Rufus) can actually reach it. Useful when triaging why a brand isn’t being cited, or when filing a host or CDN ticket because a specific bot is being blocked.

What you get back

Every check returns three pieces:
  • result — the per-model verdict. Two parallel maps under http and robots (see AIAccessUIBotAccess) plus an overall status (accessible, partial, or blocked).
  • diagnostics — the request fingerprint for every probe: HTTP status code, CDN headers (cf-ray, x-vercel-id, x-amz-cf-id, x-fastly-request-id, x-akamai-request-id, server, via, x-served-by, x-cache), error codes, duration, and UTC timestamp. Pasted into a host or CDN ticket, this is enough for support to correlate the request on their side.
  • log — a plain-text rendering of result + diagnostics shaped for a host/CDN ticket. Identical to the string the AthenaHQ web app’s “Copy log” button produces.

Quickstart

Status values

The status field reflects live HTTP behaviour, not robots.txt. A permissive robots.txt paired with a CDN that blocks GPTBot returns blocked for ChatGPT, because robots.txt is a policy hint and not all crawlers honour it.

Rate limits

The endpoint is rate-limited to 30 requests per minute per organization. Exceeding the limit returns 429 with Retry-After.

Authentication

Standard AthenaHQ API key authentication. See Authentication.

Endpoint reference

See POST /api/v1/ai-access/check for the full request and response schema.