AI Agent Readiness Score

Score how easy a domain is for AI agents to discover, understand, access, cite, and interact with — across six weighted, evidence-backed categories: Discoverability, Structured Understanding, API Accessibility, AI Crawler Accessibility, Content Quality, and Trust/Provenance.

What it checks

• robots.txt coverage and AI-crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and others)
• Sitemaps, canonical URLs, and machine-readable discovery signals (llms.txt, JSON-LD, OpenGraph)
• Public API surface discoverability and declared authentication
• Trust and provenance signals: about/contact/privacy/terms pages and structured provenance metadata

The Actor performs a live, deterministic audit through Sentinel Verify — it never requires the domain to already be registered anywhere, and a domain with no prior history still receives a full score.

Pricing

This is a paid, pay-per-event Actor: $0.15 per completed readiness audit.

Exactly one readiness-score event is charged per run, only after a real result exists (success or a useful partial). There is no charge for invalid input, a target blocked by the public-network policy, or a run that fails before a result is produced.

Input

• domain (required): a public domain or HTTPS origin to evaluate, e.g. example.com.
• maxCrawlPages (optional, default 40): upper bound on pages/resources fetched by the underlying collectors.

Example input:

{
  "domain": "example.com",
  "maxCrawlPages": 40
}

Output

The default dataset receives one result envelope per domain; RUN_SUMMARY in the default key-value store records processing, delivery, billing, dependency, and budget totals.

Representative abbreviated output (produced through the Actor's real service path):

{
  "status": "success",
  "target": {"identifier": "example.com"},
  "result": {
    "domain": "example.com",
    "overallScore": 34.38,
    "categories": [
      {"category": "discoverability", "weight": 0.2, "score": 45.0},
      {"category": "structured_understanding", "weight": 0.2, "score": 10.0},
      {"category": "api_accessibility", "weight": 0.2, "score": 0.0},
      {"category": "ai_crawler_accessibility", "weight": 0.15, "score": 100.0},
      {"category": "content_quality", "weight": 0.15, "score": 30.0},
      {"category": "trust_provenance", "weight": 0.1, "score": 0.0}
    ],
    "findingCount": 6
  }
}

restricted means API-IFY rejected the target locally before calling Verify. unreachable means the domain could not be reached. dependency_unavailable means Verify was temporarily unavailable. Failures are isolated per target.

How it works

This Actor is a thin wrapper around Sentinel Verify's POST /v1/audits/readiness endpoint — the same live-probe methodology used by Verify's own trust surfaces. Each domain is checked locally against API-IFY's public-network policy before being sent to Verify. Registry membership, if any, is used only as optional enrichment and never gates the audit.

Limitations

• Public HTTPS domains only; private, loopback, link-local, metadata, reserved, and CGNAT targets are rejected.
• Audit availability depends on Sentinel Verify.

Privacy and security

The target domain is sent to Sentinel Verify for analysis after local public-network validation. Results are stored in the customer's Apify run dataset and summary store. VERIFY_CLIENT_ID/VERIFY_CLIENT_SECRET are operator-managed Actor secrets used to obtain a short-lived Verify access token at runtime; VERIFY_BASE_URL is an operator setting, not an Actor input.

Support

For a reproducible support request, provide the Apify run ID, result itemId, and status. Contact Sentinel Signal Systems through the support link on the Actor page.