Files
agent-protocol/CHANGELOG.md
Bruno Sarlo da9207ded3 v1.0.0-draft: First public draft release
agents.md protocol for AI agent web discovery.

Key features:
- Two formats: Pure Markdown (simple) or YAML frontmatter (structured)
- MCP gateway integration for tool access
- Discovery via /.well-known/agents.md
- Security: origin trust, endpoint validation, auth guidance
- Backward compatible with robots.txt and llms.txt

Design based on 3-iteration process:
1. Gap analysis and planning
2. Multi-model consensus on format decisions
3. Code review for completeness and clarity

Philosophy: robots.txt says what agents CANNOT do,
agents.md says what they CAN do.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-14 09:18:13 -03:00

1.6 KiB

Changelog

All notable changes to the agents.md protocol specification.

[1.0.0-draft] - 2026-01-14

First public draft release.

Added

  • Core specification defining agents.md file format
  • Two format options: Pure Markdown (simple) and YAML frontmatter + Markdown (structured)
  • MCP gateway integration for pointing agents to Model Context Protocol servers
  • Discovery mechanism via /.well-known/agents.md (primary) and /agents.md (fallback)
  • Security section with origin trust, endpoint validation, and authentication guidance
  • Backward compatibility guidance for robots.txt and llms.txt coexistence
  • Caching recommendations for both servers and agents
  • Examples covering minimal sites, MCP-enabled APIs, and OAuth-protected e-commerce

Design Decisions

Based on multi-model consensus:

  1. Hybrid format - Optional YAML frontmatter for machine-readable config, Markdown body for human context
  2. Simple naming - Keep Can/Cannot section names for intuitiveness
  3. MCP as pointer - Reference MCP endpoints, don't embed tool schemas
  4. Websites first - Focus on web use case, extensible for future

Philosophy

Standard Purpose
robots.txt What agents cannot access
llms.txt What content is important
agents.md What agents can do

[0.2.0] - 2026-01-14

Internal revision with MCP integration.

Changed

  • Simplified format from API-centric to text-centric
  • Added MCP gateway pointer concept
  • Removed JSON Schema tool definitions

[0.1.0] - 2026-01-14

Initial internal draft.

Added

  • Basic protocol concept
  • API tool definitions (later removed)