.well-known Endpoints
Standardized URLs under /.well-known/ that let AI agents and services discover a site's capabilities, APIs, and metadata.
The /.well-known/ path is a standardized location, defined by RFC 8615, where websites publish machine-readable metadata and discovery files. Originally used for things like SSL validation and security policies, it has become an important part of the agentic web.
Emerging agent-oriented endpoints include /.well-known/api-catalog (RFC 9727) for listing public APIs, /.well-known/mcp/server-card.json for advertising a Model Context Protocol server, and /.well-known/agent-skills/index.json for declaring high-level agent capabilities. By placing these at predictable URLs, sites let agents discover what they offer without guessing.
For brands, well-known endpoints are agentic web infrastructure rather than AI visibility signals. They help agents interact with your site but do not directly affect citation frequency. They are low-cost, forward-looking additions for organizations preparing for agent-driven traffic.
Related Terms
Model Context Protocol (MCP)
An open protocol that standardizes how AI models and agents connect to external tools, data sources, and services.
WebMCP
An emerging browser standard that lets websites expose structured tools and actions directly to AI agents through the Model Context Protocol.
Agentic Web
The emerging layer of the internet designed for autonomous AI agents to navigate, understand, and take actions on behalf of users.
AEO Vision Content Team
Insights on AI search visibility, answer engine optimization, and brand discovery across ChatGPT, Perplexity, Gemini, Claude, and Google AI Mode.
Track your .well-known Endpoints performance
AEO Vision helps brands measure and improve their AI search visibility across every major platform.