{
  "id": "docs-llms-txt",
  "slug": "docs/llms-txt",
  "path": "/docs/llms-txt/",
  "title": "The llms.txt format used here",
  "summary": "What this site's llms.txt and llms-full.txt contain, in what order, and how the build generates them.",
  "type": "doc",
  "tags": [
    "llms-txt",
    "reference"
  ],
  "url": "https://agentsboard.duckdns.org/docs/llms-txt/",
  "md_url": "https://agentsboard.duckdns.org/docs/llms-txt/index.html.md",
  "json_url": "https://agentsboard.duckdns.org/api/v1/pages/docs-llms-txt.json",
  "updated": "2026-11-04T00:00:00Z",
  "anchors": [
    {
      "id": "structure",
      "title": "Structure of llms.txt",
      "level": 2,
      "url": "https://agentsboard.duckdns.org/docs/llms-txt/#structure"
    },
    {
      "id": "example",
      "title": "Example",
      "level": 2,
      "url": "https://agentsboard.duckdns.org/docs/llms-txt/#example"
    },
    {
      "id": "llms-full",
      "title": "llms-full.txt",
      "level": 2,
      "url": "https://agentsboard.duckdns.org/docs/llms-txt/#llms-full"
    },
    {
      "id": "generation",
      "title": "How it is generated",
      "level": 2,
      "url": "https://agentsboard.duckdns.org/docs/llms-txt/#generation"
    }
  ],
  "content_md": "This site publishes [/llms.txt](/llms.txt) following the llmstxt.org proposal, and a companion [/llms-full.txt](/llms-full.txt). For the general convention and why it helps agents, read the guide entry on [the llms.txt file](/guide/llms-txt/).\n\n## Structure of llms.txt {#structure}\n\nThe file is Markdown, served as `text/plain; charset=utf-8`, and is kept under 4 KB. Its parts always come in this order:\n\n1. An `h1` with the site name. This is the only part the spec requires.\n2. A blockquote with a one-sentence summary of the site.\n3. One paragraph explaining the URL conventions: append `index.html.md` for Markdown, and use `/api/v1/pages/{id}.json` for JSON.\n4. `## Docs`: every page in this docs section.\n5. `## Guide`: every guide entry.\n6. `## Machine endpoints`: the JSON index, the three schemas, the feed and the sitemap.\n7. `## Optional`: links an agent can skip when short on context, namely `llms-full.txt` and the about page.\n\nEvery list item has the form `- [Title](absolute URL): summary`. Page links point at the Markdown copy, not the HTML, so an agent gets clean text in one request. There are no headings deeper than `h2`.\n\n## Example {#example}\n\nThe start of the generated file looks like this:\n\n```text\n# Agent-Friendly Web\n\n> A small, fully static guide to web conventions that make sites easy for LLM agents to read, cite and crawl.\n\nAppend `index.html.md` to any page URL for Markdown. ...\n\n## Docs\n\n- [URL and anchor policy](https://agentsboard.duckdns.org/docs/url-policy/index.html.md): The URL scheme, ...\n```\n\n## llms-full.txt {#llms-full}\n\n`/llms-full.txt` contains the Markdown copy of every page in site order, separated by a line containing only `---`. Each copy starts with `# Title`, the summary as a blockquote, and `Canonical:` and `Updated:` lines, so an agent can split the file and still attribute each part. The spec does not define this file; it is a common addition for agents that prefer one large fetch.\n\n## How it is generated {#generation}\n\n`build.py` writes both files from the same page list it uses for HTML, so they cannot drift out of date. Titles and summaries come from each page's front-matter, and every URL is built from `base_url`. `validate.py` then checks the order of the parts, the item format, that every link is absolute and resolves to a built file, that an `## Optional` section exists, and the 4 KB limit.\n"
}
