Docs for AI assistants
These docs are written to be read by people and by AI assistants alike. Give an assistant the whole text, and it can answer questions about Evocal from it.
The files
| Address | What it holds |
|---|---|
| evocal.app/llms.txt | A short index of the site and the docs, with a link and one line for each page. |
| evocal.app/llms-full.txt | Every doc in one Markdown file, in reading order, with the plans and the languages as tables. |
| evocal.app/llms-full.txt?lang=pt | The same file in another language of the site: use its two-letter code, such as pt, es or ja. |
Every doc page also has Copy as Markdown at the top, which copies that page alone, ready to paste into a chat.
Using them with an assistant
- Give it the docsPaste the address of the full file, or the file itself, into the assistant, or copy only the page you need.
- Ask about your caseFor example: “How many credits does a 12-minute video into two languages use?” or “What does this alert in the editor mean?”
- Check what mattersPrices, limits and your own balance are always current in the app and on the pricing page. The docs say when each page was last updated.
Good to know
- The files are plain text, with no account needed, and change when the docs change.
- They describe the product, not your account: an assistant cannot see your projects or credits through them.
- The docs are written in English and translated; where a translation and the English differ, the English is the reference.
Read next
API and MCP (coming soon)What the Evocal API and MCP server will do, the plans that include them, how keys and voice confirmation will work, and the rules that apply to every call.Evocal docsHow to use Evocal, from the first upload to the files you publish: languages, voices, the editor, downloads, credits, plans, your account and the API.QuestionsHow dubbing, the editor, credits, files and voices work today.