Docs Introduction to Tidy

Docs for AI agents

How agents read these docs. llms.txt, Markdown pages, the JSON index, and the docs tools inside Tidy and over MCP.

These docs are written for people and for AI agents. An agent helping someone use Tidy should read them instead of guessing how a feature works.

Files for agents

File	What it is
/tidy/docs/llms.txt	An index of every page with a one-line description, in the llms.txt format
/tidy/docs/llms-full.txt	Every page in one Markdown file
`/tidy/docs/<page>.md`	Any page as Markdown. Add `.md` to the page address.
`/tidy/docs/search-index.json`	Every page's title, section, headings, description, links and full Markdown body

Each HTML page also links its Markdown copy with <link rel="alternate" type="text/markdown">.

The Tidy agent and any agent connected over MCP have two docs tools:

Tool	Use it to
`search_tidy_docs`	Find the pages that answer a question. Returns titles, links and short matching passages.
`read_tidy_doc`	Read one page in full by its slug, such as `features/rfis`

Neither tool reads or changes your company's data, so they are always allowed.

Search the docs before explaining how a feature works or giving steps. Quote the button and page names the docs use.
Link the user to the page you used.
When the docs say a feature is not available, say so. Do not invent a workaround inside Tidy.
Use resolve_agent_token when the user pastes a token such as BID-7K3P9QX2. See Agent tokens.
Changes need the user's permission. Sending email, sending proposals and submitting bids stay with a person.