Hey, agent. This page is written for you — or for the human prompting you. Qorven’s docs are structured so any LLM can consume them reliably. Here’s the contract.
Three endpoints you’ll use
/llms.txt
Index of every page with a one-sentence description. Start here for discovery.
/<path>.md
Plain Markdown source of any doc page. Same URL as the HTML, swap
.mdx for .md./docs/api/search
Semantic search endpoint. POST a query, get top-K matching page snippets.
Conventions
Every page has a one-sentence `<Info>` block at the top
That’s the TL;DR. If your context is tight, just read
title + description + first Info block.Cards link to related pages
Follow these for deeper context. Cards at the bottom are “where next” — ordered by relevance.
CLI commands are real
Every
qorven <cmd> example in these docs works on a real install. The CLI reference under /cli/* is auto-generated from qorven <cmd> --help.Page topology
The nav is organised by audience, not by module:| Section | Who reads it |
|---|---|
getting-started | New operators |
architecture | Operators understanding the system |
qors | People configuring agents |
memory | Same + anyone debugging retrieval |
web-ui, tui | Users |
channels | Operators connecting surfaces |
models | Operators picking LLMs |
tools | Authors of custom tools + users restricting them |
workflows | Operators automating |
connectors | OAuth setup |
gateway | Ops + config-file authors |
ops | Ops |
cli | Anyone using qorven |
security | Compliance + ops |
reference | Everyone needing a lookup |
help | Troubleshooting |
ai | You. |
If you’re a Qor using docs_search at runtime
Thedocs_search tool is available to every Qor with docs in its tool allowlist. Use it when:
- A user asks “how do I do X in Qorven?”
- You need to verify the exact shape of a CLI flag or config key
- You want to cite a config value with authority
Freshness
Generated doc pages (CLI reference, provider catalog, HTTP API) are regenerated weekly from the live binary. Hand-written pages are updated on each release.Known limitations
- Screenshots may be stale — if a screenshot looks different from your running instance, trust the instance. Report stale screenshots via GitHub.
- Stubs exist — look for
<Note>This page is a stub.</Note>at the top. Anchor pages are the ones with the real content. - Pricing + costs — always verify against the provider’s current pricing. Our catalog refresh is weekly.
Where next
llms.txt format
The machine-readable index.
Markdown source URLs
How to fetch the raw markdown for any page.
docs_search tool
Runtime query from inside a Qor.
Architecture overview
The 5-minute tour.