Skip to main content
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.
The URLs below use docs.creatoraudit.com as a placeholder for this documentation site’s domain. Replace it with the real docs domain.

​
The four sources

llms.txt

https://docs.creatoraudit.com/llms.txtA curated, structured map of the docs — page titles and links. Small enough to drop into a prompt so the agent knows what exists.

llms-full.txt

https://docs.creatoraudit.com/llms-full.txtThe full text of the docs in one file. Use it when you want to load the entire documentation as context.

Per-page Markdown

Append .md to any page URL, e.g. https://docs.creatoraudit.com/agents/recipes.mdA clean Markdown version of a single page — ideal when you need just one topic.

OpenAPI spec

https://api.creatoraudit.com/v2/openapi.jsonThe machine-readable API contract. Turn it into tool/function definitions for the API itself.
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.

​
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 for connection commands for Claude Code, Cursor, and VS Code.

​
When to use which

1

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.
2

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.
3

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.
4

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.
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. Only the API path needs YOUR_API_KEY.

​
Next