---
title: AI-readable docs
description: Understand the public Markdown, llms.txt, and MCP surfaces Radiant publishes for AI tools.
---

Radiant publishes AI-readable files with every deployed docs site. These files
help external AI assistants, developer tools, crawlers, and code editors read
your docs from stable Markdown and text endpoints instead of scraping rendered
HTML.

No setup is required. If your docs site is public, the AI-readable files are
public too.

<Callout type="warning" title="Published docs are public">
Do not put secrets, private credentials, unreleased plans, or internal-only
notes in published docs source. AI-readable files expose the same public docs
content in formats that tools can read more directly.
</Callout>

## Published files

Each successful deployment can include these public files:

| URL | What it contains |
| --- | --- |
| `/llms.txt` | A compact index of docs pages, page descriptions, Markdown page links, and OpenAPI specs |
| `/llms-full.txt` | A larger combined context file with page content and local OpenAPI specs |
| `/.well-known/llms.txt` | Compatibility alias for `/llms.txt` |
| `/.well-known/llms-full.txt` | Compatibility alias for `/llms-full.txt` |
| `/{page}.md` | Markdown version of an individual docs page |
| `/open-api/{spec}.json` | Published OpenAPI spec used by generated API reference pages |

For example, a page available at `/getting-started/quickstart` is also
available to tools at `/getting-started/quickstart.md`.

## Markdown page versions

Radiant publishes a Markdown version of each routed docs page. For MDX pages,
the Markdown version exposes the source content used to build the page,
including frontmatter and supported Radiant components.

For generated OpenAPI endpoint pages, the Markdown version includes
endpoint-specific content instead of the entire OpenAPI file:

- Method and path.
- Operation description.
- Parameters.
- Request body details.
- Responses.
- A link to the full OpenAPI spec.
- A compact OpenAPI operation block with only the referenced schemas and
  security schemes needed for that endpoint.

## Page descriptions

`/llms.txt` uses each page description to summarize what the page is about.
Radiant resolves descriptions in this order:

1. `description` in the page frontmatter.
2. A generated fallback based on the page title and docs site title.

Use frontmatter descriptions on important pages when you want more specific
summaries.

```mdx
---
title: Deployments
description: Understand deployment triggers, status, and rollout behavior.
---
```

## OpenAPI specs

When your docs include generated API reference pages, Radiant links the full
OpenAPI spec from `/llms.txt` and publishes local specs at their public paths.
Endpoint Markdown pages link back to the full spec and include a focused
operation slice for that endpoint.

Keep your OpenAPI descriptions, parameters, request bodies, responses, examples,
and authentication details accurate. Those fields become part of the
AI-readable output.

## MCP server

Pro docs sites also include a read-only MCP server at `/_mcp/server`.

The MCP server lets compatible AI tools search the published docs and approved
assistant context through a `searchDocs` tool. Users can connect supported
tools from the dropdown menu on any docs page, including Cursor, Claude Code,
and Codex.

The MCP server is read-only. It does not let agents edit docs, access
dashboard data, or perform account actions.

## Custom llms files

Radiant generates `/llms.txt` and `/llms-full.txt` automatically. If you need
full control, add either file at the docs root:

```txt
docs.json
llms.txt
llms-full.txt
getting-started/
  quickstart.mdx
```

When present, the custom file is published instead of the generated version.
Use this only when you need a hand-authored index or context file.

## Common questions

<AccordionGroup>
  <Accordion title="Do I need to configure anything?">
    No. Radiant publishes AI-readable docs files automatically during
    deployment.
  </Accordion>

  <Accordion title="Are these files connected to Knowledge Assistant?">
    No. AI-readable docs are part of the public docs output. Knowledge Assistant is a
    separate Radiant feature.
  </Accordion>

  <Accordion title="Can I turn these files off?">
    Not currently. Treat them as part of the public docs site, like HTML pages,
    images, and OpenAPI specs.
  </Accordion>

  <Accordion title="Why does a page appear in llms.txt without my custom description?">
    Add `description` to the page frontmatter. If no description is set,
    Radiant uses a generated fallback.
  </Accordion>
</AccordionGroup>

## Related pages

<Columns columns={3}>
  <Column>

  <Card title="Deployments" href="/publish-and-manage/deployments" icon="lucide:cloud-upload">
    See what happens during deploy.
  </Card>

  </Column>
  <Column>

  <Card title="Format text" href="/edit-markdown/format-text" icon="lucide:type">
    Add titles and descriptions.
  </Card>

  </Column>
  <Column>

  <Card title="API reference" href="/configure-with-docs-json/api-reference" icon="lucide:file-code-2">
    Publish OpenAPI docs.
  </Card>

  </Column>
</Columns>