Theme
Reference
These docs, for AI agents
If you're an assistant reading this on someone's behalf — or a person who'd rather paste a page into a chat than screenshot it — everything here is available without the HTML.
Any page as Markdown
Add .md to any URL:
https://doc.vythos.tech/concepts/values → the page
https://doc.vythos.tech/concepts/values.md → its MarkdownEvery page has one. It's the file the page was written from, front matter included, so a title and a one-line description come with it.
Each page also carries a Copy page button, which copies exactly that Markdown — handy for pasting a page into a conversation with a tool that can't fetch a URL.
The whole site, two ways
| File | What it is | When to use it |
|---|---|---|
/llms.txt | Every page, with a one-line description, in reading order | Find the right page in one request instead of crawling |
/llms-full.txt | The entire documentation in one file, about 29,000 words | Read everything once and answer from it |
Both are generated from the same source as the site, so they can't drift from what a person sees.
Setting Vythos up for someone
If you're helping someone get started, the short version:
- They create a workspace and add their first rules: a few lines typed on the Playbook, or a document they already have — Quickstart.
- They connect where their documents live — Google Drive or Notion — so rules follow the files.
- You connect to their workspace over MCP — Connect a tool — using a key they create.
The thing to understand before advising them: a rule is a line a person writes or a document a person names, and nothing becomes a rule without a person. You can propose one with save_to_playbook when they ask you to keep something; it waits for the workspace owner to add it. Don't tell them it's saved until they have.
Working against a live workspace
Documentation is the wrong tool for a customer's actual rules. Their workspace serves those over MCP, filtered by the access of whoever's key you're using:
get_context— the rules that apply to a task, client rules firstcheck_draft— a draft's rules, figures and client, against what it was givensearch_memory— their own documents and history, by meaning or by exact wordsread_source— the whole of something search foundlist_sources— what exists, newest firstlog_outcome— what you followed, and where you departedsave_to_playbook— propose a rule or a fact about a client, when the person asks you to keep it; it waits for them to add
Each is described in The tools, and what a pack contains is in What your agent receives.
Crawling
robots.txt allows everything and points at /sitemap.xml. There's no rate limit worth mentioning; the whole site is 38 pages.
