aitp.dev agentic web readiness

F Manifest validity: 0 manifests published (0 errors, 0 warnings) · Surface score 0 (coverage 0 + breadth 0 + conformance 0). 0 standards observed across 0 of 9 steps; 0 manifests present, 0 errors, 0 warnings. Checked 2026-10-24 14:09:44 UTC. This grades the agent-facing files published at aitp.dev, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/aitp.dev.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

Standards observed

None of the ~30 probed paths answered as a known standard.

Cheapest next steps

1. llms.txt: one Markdown index file; the most widely read agent-facing file
   Generate starter /llms.txt for aitp.dev

   # Aitp
   
   > Aitp and what it offers to agents
   
   Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.
   
   ## Docs
   - [Getting started](https://aitp.dev/docs/getting-started): the first page to read
   - [API reference](https://aitp.dev/openapi.json): OpenAPI description
   
   ## Optional
   - [Changelog](https://aitp.dev/changelog): what changed, newest first
   

2. AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve
   Generate starter /robots.txt for aitp.dev

   # search and answer-engine crawlers
   User-agent: Googlebot
   User-agent: bingbot
   User-agent: OAI-SearchBot
   User-agent: Claude-SearchBot
   User-agent: PerplexityBot
   User-agent: ExaSearchBot
   User-agent: TavilyBot
   Allow: /
   
   # model-training crawlers: choose Allow or Disallow and keep it explicit
   User-agent: GPTBot
   User-agent: ClaudeBot
   User-agent: Google-Extended
   User-agent: Applebot-Extended
   User-agent: CCBot
   User-agent: meta-externalagent
   User-agent: Bytespider
   Disallow: /
   
   # user-triggered fetchers (a person asked for this page)
   User-agent: ChatGPT-User
   User-agent: Claude-User
   User-agent: Perplexity-User
   Allow: /
   
   User-agent: *
   Allow: /
   Disallow: /account/
   
   Sitemap: https://aitp.dev/sitemap.xml
   Agentmap: https://aitp.dev/.well-known/ard.json
   Content-Signal: ai-train=no, search=yes, ai-input=yes
   

3. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "aitp.dev"}))

Agent pre-flight & practical readiness

Preferred mode: exa_or_http_fetch. No structured agent endpoint was found. The page has readable text, so fetch it directly or through a search index.

Fetch: GET https://aitp.dev/ No structured agent endpoint was found. Fetch the public page or use a search index.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, tables 2 (14 rows), first content at byte 13855.

AI crawler posture: unspecified · Assistant access: OpenAI unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.

Readiness subscores: reach 0/20, readability 20/30, capabilities 0/35, conformance 0/15, total 20/100, grade D.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules