Point your AI assistant at Maventa documentation

Maventa’s documentation now publishes an LLM-friendly markdown copy of every page alongside the HTML. If you use an AI coding assistant when working on Maventa integrations (Claude, Cursor, GitHub Copilot, ChatGPT, or anything else that can fetch a URL), you can point it at the docs directly and get answers grounded in the current source rather than the assistant’s training data.

What is available

Three things, all on documentation.maventa.com:

• /llms.txt: a hierarchical index of every public page, following the llms.txt convention. Most AI tools recognise this URL pattern automatically.
• /llms-full.txt: every documentation page concatenated into one file, around 830 KB of plain markdown. Useful when you want to load all the docs into context in one go.
• <url>.md for every page: for example, the Getting Started guide is also available as plain markdown. Useful for fetching one specific page on demand.

A typical workflow: add /llms.txt to your assistant’s documentation sources or paste it at the start of a session, then ask integration questions as normal. The assistant fetches the relevant pages on demand and can quote them back.

What is not included

Changelog entries are kept out of the bundled /llms-full.txt. Individual changelog posts are historical records, and an entry from a year ago may describe a flow that has since changed. Concatenated alongside current docs, that context is easy to lose. Each entry remains fetchable individually as <url>.md under /changelogs/.

A handful of pages depend on interactive components (the country reach map and the Peppol participant lookup tool) and appear as plain markup in their .md form. The HTML versions on the live site remain the primary way to use those features.