Utilities & AI

AI Search Visibility API API

The GEO Intelligence API audits a page's AI-search readiness as clean JSON.

6 actionsLive JSON1,000 free creditsMCP-ready
Get a free keyOpen in playground

🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.

The primary check endpoint returns a score (grade, breakdown, recommendations), AI-crawler access, llms.txt status and schema, and you can pull crawlers, llms_txt, schema, score and batch. It is built for SEO/GEO tools and site audits that need an AI-visibility signal for a URL. One ReefAPI key, one shared credit pool, the standard envelope.

Live example

Real request and response JSON

Captured from the indexed primary action, check, on .

Captured request
{
  "method": "POST",
  "url": "https://api.reefapi.com/geo-intel/v1/check",
  "headers": {
    "x-api-key": "$REEF_KEY",
    "content-type": "application/json"
  },
  "body": {
    "url": "https://docs.anthropic.com"
  }
}
Captured response
{
  "ok": true,
  "meta": {
    "api": "geo-intel",
    "endpoint": "check",
    "mode": "live",
    "latency_ms": 14218.3,
    "record_count": 1,
    "bytes": 928401,
    "cache_hit": false,
    "method": "fetch_target_site_bare_dc_curl_cffi",
    "ssrf_guarded": true,
    "final_url": "https://platform.claude.com/docs/en/home",
    "score": 80.5,
    "grade": "B",
    "critical_blocked": 0
  },
  "data": {
    "url": "https://docs.anthropic.com",
    "final_url": "https://platform.claude.com/docs/en/home",
    "http_status": 200,
    "score": {
      "score": 80.5,
      "grade": "B",
      "breakdown": {
        "crawler_access": {
          "score": 40,
          "max": 40
        },
        "structured_data": {
          "score": 6,
          "max": 25
        },
        "llms_txt": {
          "score": 15,
          "max": 15
        },
        "meta_signals": {
          "score": 11.5,
          "max": 12
        },
        "crawlability": {
          "score": 8,
          "max": 8
        }
      },
      "recommendations": [
        {
          "priority": "high",
          "pillar": "structured_data",
          "points_recoverable": 19,
          "fix": "only microdata/RDFa found — JSON-LD is the AI-preferred format; add it"
        }
      ]
    },
    "ai_crawlers": {
      "bots": [
        {
          "token": "[redacted-secret]",
          "operator": "OpenAI",
          "engine": "ChatGPT Search",
          "category": "search",
          "cites": true,
          "critical": true,
          "allowed": true,
          "matched_rule": null,
          "via_ua": "*",
          "crawl_delay": null,
          "reason": "allowed (no matching disallow)"
        },
        {
          "token": "[redacted-secret]",
          "operator": "OpenAI",
          "engine": "ChatGPT (user-fetch)",
          "category": "agent",
          "cites": true,
          "critical": true,
          "allowed": true,
          "matched_rule": null,
          "via_ua": "*",
          "crawl_delay": null,
          "reason": "allowed (no matching disallow)"
        },
        {
          "token": "[redacted-secret]",
          "operator": "OpenAI",
          "engine": "ChatGPT (training)",
          "category": "training",
          "cites": false,
          "critical": false,
          "allowed": true,
          "matched_rule": null,
          "via_ua": "*",
          "crawl_delay": null,
          "reason": "allowed (no matching disallow)"
        }
      ],
      "summary": {
        "total": 73,
        "allowed": 73,
        "blocked": 0,
        "critical_blocked": [],
        "citation_bots_blocked": []
      },
      "blanket_block_all": false,
      "robots_present": true
    },
    "llms_txt": {
      "present": true,
      "valid": true,
      "status": 206,
      "content_type": "text/plain; charset=UTF-8",
      "looks_like_html": false,
      "bytes": 204609,
      "title": "Anthropic Developer Documentation",
      "h1_count": 1,
      "section_count": 3,
      "sections": [
        "Root URL",
        "Available Languages on Website",
        "English"
      ],
      "link_count": 1895,
      "links_sample": [
        {
          "text": "Overview",
          "url": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview.md"
        },
        {
          "text": "Features overview",
          "url": "https://platform.claude.com/docs/en/build-with-claude/overview.md"
        },
        {
          "text": "Quickstart",
          "url": "https://platform.claude.com/docs/en/agents-and-tools/agent-skills/quickstart.md"
        }
      ],
      "findings": [],
      "head": "# Anthropic Developer Documentation\n\nThis file provides an overview of the Anthropic API documentation and developer resources.\n\n## Root URL\n\nClaude Developer Platform Console (Requires login)\n\nhttps://platform.claude.com\n\n## Available Languages on Website\n\nThe full documentation is available in the following languages on https://platform.claude.com/docs:\n\n- English (en) - 1894 pages - /docs - Con",
      "url": "https://docs.anthropic.com/llms.txt"
    },
    "llms_full_txt": {
      "present": true,
      "status": 200,
      "content_length_header": null,
      "url": "https://docs.anthropic.com/llms-full.txt"
    },
    "structured_data": {
      "jsonld_blocks": 0,
      "jsonld_parsed": 0,
      "jsonld_unparseable": 0,
      "types": [],
      "type_counts": {},
      "citable_types": [],
      "high_value_types": [],
      "has_organization": false,
      "has_article": false,
      "has_faq": false,
      "has_breadcrumb": false,
      "has_speakable": false,
      "has_microdata": false,
      "has_rdfa": true,
      "has_structured_data": true
    },
    "meta": {
      "title": "Documentation - Claude Platform Docs",
      "meta_description": "Claude API Documentation",
      "canonical": "https://platform.claude.com/docs/en/home",
      "robots_meta": null,
      "noindex": false,
      "nosnippet": false,
      "noai_meta": false,
      "ai_meta_directives": null,
      "has_opengraph": true,
      "og_title": "Documentation",
      "og_description": "Claude API Documentation",
      "og_type": "article",
      "og_site_name": "Claude Platform Docs",
      "twitter_card": "summary_large_image",
      "has_twitter_card": true,
      "html_lang": "en-US",
      "hreflang": null,
      "feeds": null,
      "favicon": "https://platform.claude.com/favicon.ico",
      "has_viewport": true
    },
    "extractability": {
      "text_ratio": 0.0048,
      "visible_text_chars": 3387,
      "script_count": 159,
      "script_heavy": true,
      "likely_js_app": false
    },
    "sitemaps": [
      "https://platform.claude.com/sitemap.xml"
    ],
    "sitemap_xml_present": true
  }
}
Actions

What the AI Search Visibility API API does

ActionDescriptionConcrete use caseKey params
checkFull AI-readiness report for a URL: AI-crawler access map + llms.txt + schema + meta + 0-100 score + ranked fix recommendations. One call, everything.Ops teams call check to get full AI-readiness report for a URL.url, path, bots, follow_redirects
crawlersAI-crawler access map from robots.txt: per-bot allow/block (Google longest-match), operator, AI engine, purpose (search/training/agent), crawl-delay, sitemaps.Developer tools call crawlers to get aI-crawler access map from robots.txt.url, path, bots
llms_txtDetect + parse + validate /llms.txt (and /llms-full.txt) — the emerging AI-context standard. Content-type sniffed so an HTML 404 can't masquerade as a real file.Validation workflows call llms_txt to detect + parse + validate /llms.txt (and /llms-full.txt).url
schemaExtract and classify schema.org structured data ( and @graph) for AI citability signals: Organization, Article, FAQ, BreadcrumbList, Product, Speakable — plus microdata and RDFa presence.Data-quality teams call schema to extract and classify schema.org structured data ( and @graph) for AI citability signals.url, follow_redirects
scoreComposite AI-readiness score (0-100) + transparent per-pillar breakdown (crawler_access 40 / structured_data 25 / llms_txt 15 / meta 12 / crawlability 8) + ranked recommendations.Ops teams call score to get composite AI-readiness score (0-100) + transparent per-pillar breakdown (crawler_access 40 /….url, path, follow_redirects
batchScore up to 20 sites concurrently in one call (each independently SSRF-guarded). Returns a compact score+grade per URL.Developer tools call batch to get score up to 20 sites concurrently in one call (each independently SSRF-guarded).urls
Code samples

Call check from your stack

curl -X POST https://api.reefapi.com/geo-intel/v1/check \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://docs.anthropic.com"}'
MCP one-liner
Ask your MCP-connected assistant: call reefapi.geo-intel.check with {"url":"https://docs.anthropic.com"}.
Use cases

Who uses this API and why

  • SEO/GEO tools call check to grade a page's readiness for AI search.
  • Agencies use the recommendations to prioritize fixes for a client.
  • Monitors use batch to audit a whole site's pages.
FAQ

Questions developers ask before integrating

What is the AI Search Visibility API API?

AI Search Visibility API API is a ReefAPI endpoint group for ai search visibility api It returns live JSON through POST requests under /geo-intel/v1.

Is the AI Search Visibility API API free to try?

Yes. ReefAPI starts with 1,000 free credits, no card required. AI Search Visibility API calls use the same shared credit balance as every other ReefAPI engine.

Do I need a AI Search Visibility API login or account?

No login to AI Search Visibility API is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the AI Search Visibility API data?

The page example is captured from a live check call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the AI Search Visibility API API use?

AI Search Visibility API actions currently cost 1 credit per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Can I call AI Search Visibility API from an AI assistant or MCP client?

Yes. Connect ReefAPI once through MCP and your assistant can call geo-intel actions with the same key, credit pool and JSON envelope used by normal REST requests.

Is the AI Search Visibility API API a AI Search Visibility API scraper?

It is the managed alternative to a DIY AI Search Visibility API scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same ai search visibility api back as clean JSON.

Why does my AI Search Visibility API scraper keep getting blocked?

Most AI Search Visibility API scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked or failed calls are free.

docs / geo-intel

AI Search Visibility API

AI Search Visibility API

base /geo-intel/v16 endpoints
post/geo-intel/v1/check1 credit

Full AI-readiness report for a URL: AI-crawler access map + llms.txt + schema + meta + 0-100 score + ranked fix recommendations. One call, everything.

ParameterAllowed / rangeDescription
urlrequiredThe site to analyse. Accepts a full URL (https://example.com/page) or a bare domain (example.com → https:// assumed). Only http/https; private/internal/metadata targets are SSRF-blocked. Alias: domain.
path = /optionalThe path to evaluate robots.txt access against (default '/'). Use a real content path (e.g. /blog/post) to test whether AI bots may fetch THAT page.
botsoptionalOptional subset of AI-bot tokens to report (comma-separated or array). Omit for the full 50+ bot map. Unknown tokens are still checked against robots.txt verbatim.
follow_redirects = trueoptionalFollow redirects (e.g. http→https, apex→www) before analysing the final URL (default true). Each hop is independently SSRF-validated.
Try in playground →
post/geo-intel/v1/crawlers1 credit

AI-crawler access map from robots.txt: per-bot allow/block (Google longest-match), operator, AI engine, purpose (search/training/agent), crawl-delay, sitemaps.

ParameterAllowed / rangeDescription
urlrequiredThe site to analyse. Accepts a full URL (https://example.com/page) or a bare domain (example.com → https:// assumed). Only http/https; private/internal/metadata targets are SSRF-blocked. Alias: domain.
path = /optionalThe path to evaluate robots.txt access against (default '/'). Use a real content path (e.g. /blog/post) to test whether AI bots may fetch THAT page.
botsoptionalOptional subset of AI-bot tokens to report (comma-separated or array). Omit for the full 50+ bot map. Unknown tokens are still checked against robots.txt verbatim.
Try in playground →
post/geo-intel/v1/llms_txt1 credit

Detect + parse + validate /llms.txt (and /llms-full.txt) — the emerging AI-context standard. Content-type sniffed so an HTML 404 can't masquerade as a real file.

ParameterAllowed / rangeDescription
urlrequiredThe site to analyse. Accepts a full URL (https://example.com/page) or a bare domain (example.com → https:// assumed). Only http/https; private/internal/metadata targets are SSRF-blocked. Alias: domain.
Try in playground →
post/geo-intel/v1/schema1 credit

Extract and classify schema.org structured data ( and @graph) for AI citability signals: Organization, Article, FAQ, BreadcrumbList, Product, Speakable — plus microdata and RDFa presence.

ParameterAllowed / rangeDescription
urlrequiredThe site to analyse. Accepts a full URL (https://example.com/page) or a bare domain (example.com → https:// assumed). Only http/https; private/internal/metadata targets are SSRF-blocked. Alias: domain.
follow_redirects = trueoptionalFollow redirects (e.g. http→https, apex→www) before analysing the final URL (default true). Each hop is independently SSRF-validated.
Try in playground →
post/geo-intel/v1/score1 credit

Composite AI-readiness score (0-100) + transparent per-pillar breakdown (crawler_access 40 / structured_data 25 / llms_txt 15 / meta 12 / crawlability 8) + ranked recommendations.

ParameterAllowed / rangeDescription
urlrequiredThe site to analyse. Accepts a full URL (https://example.com/page) or a bare domain (example.com → https:// assumed). Only http/https; private/internal/metadata targets are SSRF-blocked. Alias: domain.
path = /optionalThe path to evaluate robots.txt access against (default '/'). Use a real content path (e.g. /blog/post) to test whether AI bots may fetch THAT page.
follow_redirects = trueoptionalFollow redirects (e.g. http→https, apex→www) before analysing the final URL (default true). Each hop is independently SSRF-validated.
Try in playground →
post/geo-intel/v1/batch1 credit

Score up to 20 sites concurrently in one call (each independently SSRF-guarded). Returns a compact score+grade per URL.

ParameterAllowed / rangeDescription
urlsrequiredList of sites to score in one call (max 20); each is independently SSRF-guarded and fetched concurrently.
Try in playground →