trunk.io agentic web readiness

A Manifest validity: 67% (2/3 valid, 1 error, 1 warning) · Surface score 49 (coverage 30 + breadth 9 + conformance 10). 5 standards observed across 3 of 9 steps; 3 manifests present, 1 error, 1 warning. Checked 2026-10-25 23:11:13 UTC. This grades the agent-facing files published at trunk.io, not the organisation's products.

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

Coverage by step

Manifests

{
  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
  "skills": [
    {
      "name": "trunk",
      "type": "skill-md",
      "description": "Trunk and what it offers to agents",
      "url": "https://trunk.io/.well-known/agent-skills/trunk/SKILL.md",
      "digest": "sha256:0000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}

What an agent can call

• llms.txt: Trunk, 136 links, llms-full.txt present
• robots.txt AI policy: allows GPTBot, ChatGPT-User, ClaudeBot, Google-Extended, PerplexityBot, Applebot-Extended, cohere-ai; unlisted crawlers allowed

Standards observed

• llms.txt https://trunk.io/llms.txt
• Content Signals Policy https://trunk.io/robots.txt
• AI Crawler User-Agent Tokens in robots.txt https://trunk.io/robots.txt
• Agent Skills https://trunk.io/.well-known/agent-skills/index.json
• Markdown for Agents https://trunk.io/

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": "trunk.io"}))
2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for trunk.io

   # Trunk for agents
   
   Trunk and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://trunk.io/llms.txt
   - API description: https://trunk.io/openapi.json
   - Discovery catalog: https://trunk.io/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://trunk.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@trunk.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": "trunk.io"}))

Agent pre-flight & practical readiness

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

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

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.

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

Readiness subscores: reach 20/20, readability 30/30, capabilities 6/35, conformance 10/15, total 66/100, grade A.

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