> ## Documentation Index
> Fetch the complete documentation index at: https://docs.creatoraudit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Docs as agent context

> Feed the CreatorAudit docs to an agent via llms.txt, per-page Markdown, the docs MCP, and the OpenAPI spec.

These docs are published in formats an agent can consume directly. Use them to ground an assistant in how CreatorAudit works — what the endpoints do, how auth and pagination behave, and which workflows to follow — without scraping HTML.

<Note>
  The URLs below use `docs.creatoraudit.com` as a placeholder for this documentation
  site's domain. Replace it with the real docs domain.
</Note>

## The four sources

<CardGroup cols={2}>
  <Card title="llms.txt" icon="list">
    `https://docs.creatoraudit.com/llms.txt`

    A curated, structured map of the docs — page titles and links. Small enough to drop into a prompt so the agent knows what exists.
  </Card>

  <Card title="llms-full.txt" icon="file-lines">
    `https://docs.creatoraudit.com/llms-full.txt`

    The full text of the docs in one file. Use it when you want to load the entire documentation as context.
  </Card>

  <Card title="Per-page Markdown" icon="markdown">
    Append `.md` to any page URL, e.g. `https://docs.creatoraudit.com/agents/recipes.md`

    A clean Markdown version of a single page — ideal when you need just one topic.
  </Card>

  <Card title="OpenAPI spec" icon="code">
    `https://api.creatoraudit.com/v2/openapi.json`

    The machine-readable API contract. Turn it into tool/function definitions for the API itself.
  </Card>
</CardGroup>

<Tip>
  `llms.txt` and `llms-full.txt` are also served under `/.well-known/`
  (`/.well-known/llms.txt`). The docs site sends an HTTP `Link` header with
  `rel="llms-txt"` so agents can discover them automatically.
</Tip>

## Search the docs live over MCP

For an always-current source, point your agent at the docs MCP server at `https://docs.creatoraudit.com/mcp`. It exposes search and content-retrieval tools, so the agent queries the docs on demand instead of carrying a snapshot. See [Connect via MCP](/agents/mcp) for connection commands for Claude Code, Cursor, and VS Code.

## When to use which

<Steps>
  <Step title="Quick orientation → llms.txt">
    Give the agent the map so it knows which topics exist, then let it fetch the specific page it needs as Markdown.
  </Step>

  <Step title="Full grounding → llms-full.txt">
    Load the whole corpus when you want the agent to answer broadly about CreatorAudit
    without round-tripping for each page. Best for large-context models.
  </Step>

  <Step title="Live lookups → docs MCP (/mcp)">
    Use MCP search when you want the freshest answer and don't want to manage a copy of
    the docs yourself.
  </Step>

  <Step title="Calling the API → OpenAPI spec">
    To generate tools that hit the CreatorAudit API, use the OpenAPI document — not the docs MCP. The docs MCP searches documentation; it does not call the API. See [Use the API as agent tools](/agents/tool-use).
  </Step>
</Steps>

<Warning>
  Keep the two MCP roles distinct: the **docs MCP** (`/mcp`) searches these docs.
  **Calling the API** is done with the OpenAPI-as-tools approach or a [custom API MCP
  server](/agents/mcp#build-a-creatoraudit-api-mcp-server). Only the API path needs
  `YOUR_API_KEY`.
</Warning>

## Next

* Generate tools from the contract — [Use the API as agent tools](/agents/tool-use).
* Wrap the API as MCP tools — [Connect via MCP](/agents/mcp).
* Start from the top — [CreatorAudit for AI agents](/agents/overview).