agenticweb.wiki

cncf.io agentic web readiness

B Manifest validity: 100% (2/2 valid, 0 errors, 2 warnings) · Surface score 38 (coverage 20 + breadth 3 + conformance 15). 3 standards observed across 2 of 9 steps; 2 manifests present, 0 errors, 2 warnings. Checked 2026-10-25 03:10:16 UTC via www.cncf.io. This grades the agent-facing files published at cncf.io, not the organisation's products.

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

Coverage by step

01 Discovernothing observed02 Identifynothing observed03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt04 Readllms.txt05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json
absent HTTP 404
MCP Server Cards (SEP-2127)
/mcp/server-card
absent HTTP 404
Agent2Agent Protocol
/.well-known/agent-card.json
absent HTTP 404
llms.txt
/llms.txt
valid
AGENTS.md
/AGENTS.md
absent HTTP 404
Agent Skills
/.well-known/agent-skills/index.json
absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog
absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt
/robots.txt
valid
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116)
/.well-known/security.txt
absent HTTP 404
auth.md
/auth.md
absent HTTP 404
Open Knowledge Format
/okf/index.md
absent HTTP 404

What an agent can call

Standards observed

Cheapest next steps

  1. 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": "cncf.io"}))
  2. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for cncf.io
    # Cncf for agents
    
    Cncf and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://cncf.io/llms.txt
    - API description: https://cncf.io/openapi.json
    - Discovery catalog: https://cncf.io/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://cncf.io/mcp
    - Rate limits and authentication: describe them here
    
    ## Conventions
    - How to cite or attribute content
    - What not to do (no scraping of /account/, no automated sign-ups, etc.)
    
    Contact: security@cncf.io
    
  3. api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "cncf.io"}))

Agent pre-flight & practical readiness

Preferred mode: llms_txt. GET /llms.txt and follow the links it names. That index is the page list an agent should read.

Fetch: GET https://cncf.io/llms.txt GET /llms.txt and follow its links.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 112750 (~110 KB of head/script markup before main text), HTML-to-llms.txt token ratio 19.689×, JSON-LD WebSite, SearchAction, EntryPoint, WebPage, BreadcrumbList, ListItem, ReadAction, Organization, ImageObject.

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

Readiness subscores: reach 20/20, readability 22/30, capabilities 4/35, conformance 15/15, total 61/100, grade B.

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