agenticweb.wiki

facilitator.live.nevermined.app agentic web readiness

B Score 30 (coverage 20 + breadth 0 + conformance 10). 2 standards observed across 2 of 9 steps; 2 manifests present, 1 error, 0 warnings. Checked 2026-10-19 01:53:13 UTC. This grades the agent-facing files published at facilitator.live.nevermined.app, not the organisation's products.

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

Coverage by step

01 DiscoverAI Catalog well-known file02 Identifynothing observed03 PermitOAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readnothing observed05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
errors HTTP 200
  • body is not valid JSON
AI Catalog well-known file
/.well-known/ai-catalog.json
valid HTTP 200
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
absent HTTP 404
AGENTS.md
/AGENTS.md
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
absent HTTP 404
security.txt (RFC 9116)
/.well-known/security.txt
absent HTTP 404
auth.md
/auth.md
absent HTTP 404

What an agent can call

Standards observed

Cheapest next steps

  1. llms.txt: one Markdown index file; the most widely read agent-facing file
  2. AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve
  3. AGENTS.md: instructions for coding agents working on or with the site

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). A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. 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