agenticweb.wiki

docs.devin.ai agentic web readiness

A+ Manifest validity: 60% (3/5 valid, 3 errors, 10 warnings) · Surface score 60 (coverage 40 + breadth 15 + conformance 5). 8 standards observed across 4 of 9 steps; 5 manifests present (+ robots.txt), 3 errors, 10 warnings. Checked 2026-10-25 23:11:05 UTC. This grades the agent-facing files published at docs.devin.ai, not the organisation's products.

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

Coverage by step

01 DiscoverRFC 972702 Identifynothing observed03 PermitContent Signals Policy04 Readllms.txt, AGENTS.md, Markdown for Agents05 ActAgent Skills06 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)
/.well-known/mcp/server-card.json
errors
  • $schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json)
  • name must be reverse-DNS with exactly one slash, e.g. com.example/weather
  • Content-Type is application/json; SEP-2127 says serve application/mcp-server-card+json
  • pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[]
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key)
  • no ETag
  • legacy /.well-known/mcp.json is still live and may shadow /.well-known/mcp/server-card.json in older scanners
View valid /mcp/server-card template for docs.devin.ai
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "ai.devin.docs/docs",
  "title": "Docs",
  "version": "1.0.0",
  "description": "Docs and what it offers to agents",
  "websiteUrl": "https://docs.devin.ai/",
  "icons": [
    {
      "src": "https://docs.devin.ai/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://docs.devin.ai/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json
errors
  • description missing (required in A2A 1.0)
  • protocolVersion is "0.3" (pre-1.0 legacy shape; A2A 1.0 uses protocolVersion "1.0" and supportedInterfaces[])
  • declared A2A endpoint https://docs.devin.ai/ is not a callable agent endpoint (agent card url points to the HTML homepage rather than a callable A2A endpoint)
View valid /.well-known/agent-card.json template for docs.devin.ai
{
  "name": "Docs",
  "description": "Docs and what it offers to agents",
  "version": "1.0.0",
  "provider": {
    "organization": "Docs",
    "url": "https://docs.devin.ai/"
  },
  "documentationUrl": "https://docs.devin.ai/AGENTS.md",
  "supportedInterfaces": [
    {
      "url": "https://docs.devin.ai/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    }
  ],
  "url": "https://docs.devin.ai/a2a",
  "protocolVersion": "1.0",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "defaultInputModes": [
    "text/plain"
  ],
  "defaultOutputModes": [
    "text/plain"
  ],
  "skills": [
    {
      "id": "answer",
      "name": "Answer questions",
      "description": "Answer questions about Docs.",
      "tags": [
        "qa"
      ],
      "examples": [
        "What does Docs do?"
      ]
    }
  ],
  "securitySchemes": {},
  "securityRequirements": []
}
llms.txt
/llms.txt
valid
AGENTS.md
/AGENTS.md
valid
Agent Skills
/.well-known/agent-skills/index.json
valid
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
no AI tokens
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial)
  • 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": "docs.devin.ai"}))
  2. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
    Generate starter /.well-known/security.txt for docs.devin.ai
    Contact: mailto:security@docs.devin.ai
    Expires: 2027-09-20T23:11:05Z
    Canonical: https://docs.devin.ai/.well-known/security.txt
    Preferred-Languages: en
    Policy: https://docs.devin.ai/security-policy
    

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback agent_skills). Call the MCP endpoint at https://docs.devin.ai/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://docs.devin.ai/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

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 28/30, capabilities 23/35, conformance 5/15, total 76/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