docs.augmentcode.com agentic web readiness

B Score 41 (coverage 30 + breadth 6 + conformance 5). 4 standards observed across 3 of 9 steps; 4 manifests present, 4 errors, 7 warnings. Checked 2026-10-18 23:42:14 UTC. This grades the agent-facing files published at docs.augmentcode.com, not the organisation's products.

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

Coverage by step

01 Discovernothing observed 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt 05 Actnothing observed 06 CoordinateA2A 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
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.json`	errors HTTP 200	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) name missing description missing 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 no ETag
Agent2Agent Protocol `/.well-known/agent-card.json`	errors HTTP 200	description missing (required in A2A 1.0)
llms.txt `/llms.txt`	valid HTTP 200	no blockquote summary under the title
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`	valid HTTP 200	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

What an agent can call

MCP endpoint https://augment-mtje7p526w.main-kill-isr.mintlify.me/mcp (http) — from /.well-known/mcp.json
A2A agent Augment at https://docs.augmentcode.com/, skills: augment
llms.txt: Augment, 212 links
robots.txt AI policy: unlisted crawlers partial

Standards observed

Agent2Agent Protocol https://docs.augmentcode.com/.well-known/agent-card.json
llms.txt https://docs.augmentcode.com/llms.txt
Content Signals Policy https://docs.augmentcode.com/robots.txt
AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
AGENTS.md: instructions for coding agents working on or with the site
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description

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