Agent Metadata Endpoints
The site exposes machine-readable metadata endpoints that describe crawl policy, content discovery, and agent behavior.
Endpoints
/robots.txt- Crawl permissions and sitemap discovery for legacy crawlers./sitemap.xml- XML sitemap for search engine indexing./sitemap.md- Human and LLM-friendly markdown sitemap grouped by content type./llms.txt- LLM usage guidance, markdown access notes, and discovery pointers./agents.md- Guidance for autonomous agents on how to interact with the site./.well-known/mcp- MCP discovery document (endpoint,transport)./index.md- Homepage markdown (also served when/is requested withAccept: text/markdown)./api/openapi.json- OpenAPI 3.1 specification for the public JSON API (source of truth)./api/content- Cross-type list/search endpoint./api/blogpostsand/api/blogposts/{slug}- Blogpost list and detail endpoints./api/guidesand/api/guides/{slug_path}- Guide list and detail endpoints./api/livestreamsand/api/livestreams/{slug_path}- Livestream list and detail endpoints./api/kickstartsand/api/kickstarts/{slug_path}- Kickstart list and detail endpoints./api/pagesand/api/pages/{slug_path}- Page list and detail endpoints./api/personsand/api/persons/{name}- Person list and detail endpoints./api/search/typeahead?q={query}- Search suggestion endpoint used by on-site search UX.
Behavior Notes
- All endpoints are served as static routes with hourly revalidation.
agents.mdincludes a dynamically generated content index and access guidance.- The MCP server at
/api/mcpprovidescontent_search,content_get,people_get_profile, andpeople_list(Streamable HTTP JSON responses). - WebMCP (browser-native):
document.modelContextis installed via a small polyfill when the native Chrome 146+ API is missing, then tools are registered by WebMcpShell. content_getsupports blog posts, guides (including chapter sub-pages), livestreams, kickstarts, and person pages.- The public JSON API provides list/detail endpoints for blog posts, guides, livestreams, kickstarts, pages, and persons.
- Unknown HTML paths return HTTP 404. The page title/description and body tell agents to recover via
/search,/sitemap.xml,/llms.txt, or/agents.mdand not invent a replacement URL. - Unknown
.mdURLs return HTTP 404 astext/markdownwith the same recovery links.