{
 "url": "https://agenticweb.wiki/compare/vercel-agent-readability-vs-agents-md/",
 "title": "Agent Readability Spec vs AGENTS.md",
 "description": "Agent Readability Spec vs AGENTS.md: The map lists them as complementary: sites and agents commonly implement both. Side-by-side step, governance…",
 "markdown_url": "https://agenticweb.wiki/compare/vercel-agent-readability-vs-agents-md/index.md",
 "markdown": "# Agent Readability Spec (ARS) vs AGENTS.md\n\nThe map lists them as complementary: sites and agents commonly implement both.\n\n[4 Read](/category/read/) [Agent Readability Spec](/protocols/vercel-agent-readability/) · [4 Read](/category/read/) [AGENTS.md](/protocols/agents-md/)\n\n|  | [Agent Readability Spec](/protocols/vercel-agent-readability/) ARS | [AGENTS.md](/protocols/agents-md/) |\n| --- | --- | --- |\n| Lifecycle step | 4 Read: Give me the content | 4 Read: Give me the content |\n| Answers | How readable is this site's content for AI agents, and what specifically should be fixed? | What build, test, and convention instructions should a coding agent follow in this repository? |\n| Governed by | Vercel; published in Vercel's own Knowledge Base with no external standards process | Agentic AI Foundation (AAIF), a Linux Foundation project |\n| Status (issuer's words) | A specification and scoring checklist, not a protocol; framed as best practices to implement voluntarily | \"An open format... regardless of which coding agent you use\"; explicitly not proprietary to any one tool |\n| Version | current (last updated 2026-03-23 per a secondary source; no version number or publication date is given on the page itself) (2026-03) | current site guidance (living document) (2026-09) |\n| Form / transport | document format | well-known file |\n| Found at | none | AGENTS.md |\n| Implementation | shipping | multi-implementation — agents.md (site claims over 60,000 AGENTS.md files across open-source GitHub repositories, via a path:AGENTS.md NOT is:fork NOT is:archived code search) |\n| Evidence | 2 reported, 1 verified | 2 reported, 1 verified |\n| Primary use case | Serve readable content to agents | Serve readable content to agents |\n| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |\n| Specification | [https://vercel.com/kb/guide/agent-readability-spec](https://vercel.com/kb/guide/agent-readability-spec) | [https://agents.md](https://agents.md) |\n\n## When to use which\n\n- Choose Agent Readability Spec when your question is “How readable is this site's content for AI agents, and what specifically should be fixed?” and you accept its maturity: status \"A specification and scoring checklist, not a protocol; framed as best practices to implement voluntarily\", implementation shipping.\n- Choose AGENTS.md when your question is “What build, test, and convention instructions should a coding agent follow in this repository?” and you accept its maturity: status \"\"An open format... regardless of which coding agent you use\"; explicitly not proprietary to any one tool\", implementation multi-implementation (agents.md (site claims over 60,000 AGENTS.md files across open-source GitHub repositories, via a path:AGENTS.md NOT is:fork NOT is:archived code search)).\n\nGuidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.\n\n## Read the full articles\n\n- [Agent Readability Spec](/protocols/vercel-agent-readability/): How readable is this site's content for AI agents, and what specifically should be fixed?\n- [AGENTS.md](/protocols/agents-md/): What build, test, and convention instructions should a coding agent follow in this repository?\n\nAsk the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).\n\n[vercel-agent-readability.json](/data/protocols/vercel-agent-readability.json) · [agents-md.json](/data/protocols/agents-md.json) · [Markdown](/compare/vercel-agent-readability-vs-agents-md/index.md)\n"
}