Docs for AI Agents
Every page on this site is also published as plain markdown. Use these formats when you are supplying context to an assistant, building a retrieval index, or pointing a coding agent at Aurora's APIs.
Copy a single page
Each page has a Copy page button in its upper right corner. The button copies that page as markdown, ready to paste into a conversation. The adjacent menu adds three further actions:
- View page source — open this page's markdown in a new tab
- Copy entire documentation — every page in a single file
- Copy documentation index — page titles and links only
Fetch a page as markdown
Append .md to any documentation URL to retrieve the same content
programmatically:
# The page you are reading
curl https://docs.aur.lu/docs/ai-agents.md
# Any other page
curl https://docs.aur.lu/docs/s3/getting-started.md
Responses contain the page content only—no navigation, no HTML. Interactive elements are resolved to their default state, so code samples arrive with a working endpoint already substituted rather than a placeholder.
Each HTML page declares its markdown equivalent, so tooling can discover it without constructing URLs:
<link rel="alternate" type="text/markdown" href="https://docs.aur.lu/docs/ai-agents.md" />
Site-wide bundles
Two files cover the entire documentation set, following the llmstxt.org convention:
| File | Contents | Use it for |
|---|---|---|
/llms.txt | Title, description, and markdown link for every page | Letting an agent choose which pages to fetch |
/llms-full.txt | Every page concatenated into a single document | Loading the complete documentation into one context window |
curl https://docs.aur.lu/llms.txt
curl https://docs.aur.lu/llms-full.txt
The header of /llms.txt states the current size of the full bundle.
Both files are also available from the Copy page menu on any page.
Portal API
API reference pages are published as markdown like every other page, with each endpoint's method, path, authentication, parameters, request body, and responses rendered as text.
Client generation should use the OpenAPI Specification page for the authoritative Swagger 2.0 documentation.
Markdown output is regenerated on every deployment to maintain consistency with the rendered documentation.