agenticweb.wiki

goplausible.com agentic web readiness

C Manifest validity: 100% (1/1 valid, 0 errors, 2 warnings) · Surface score 20 (coverage 10 + breadth 0 + conformance 10). 1 standard observed across 1 of 9 steps; 1 manifest present, 0 errors, 2 warnings. Checked 2026-10-23 18:38:11 UTC. This grades the agent-facing files published at goplausible.com, not the organisation's products.

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

Coverage by step

01 Discovernothing observed02 Identifynothing observed03 PermitAI Crawler User-Agent Tokens in robots.txt04 Readnothing observed05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
AI Catalog well-known file
/.well-known/ai-catalog.json		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
MCP Server Cards (SEP-2127)
/mcp/server-card		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
Agent2Agent Protocol
/.well-known/agent-card.json		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
llms.txt
/llms.txt		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
AGENTS.md
/AGENTS.md		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
Agent Skills
/.well-known/agent-skills/index.json		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
AI Crawler User-Agent Tokens in robots.txt
/robots.txt		valid
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
  • no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116)
/.well-known/security.txt		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
auth.md
/auth.md		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
Open Knowledge Format
/okf/index.md		soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent

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. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
  3. AGENTS.md: instructions for coding agents working on or with the site

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://goplausible.com/ 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, JSON-LD Organization, WebSite.

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 0/35, conformance 10/15, total 52/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