#Models and data
Vatio runs the model for you: there is no model to host and no model key in
vatio.yml. Every request to a model goes through
OpenRouter, and only to endpoints with zero data
retention.
#Which models
Every agent uses the same models. Vatio picks them and may change them, and this page always lists the current ones.
| Job | Model |
|---|---|
| Replying to visitors | DeepSeek V4.1 Flash (deepseek/deepseek-v4.1-flash) |
Memory summaries and the question behind chat.rate | The same model as the replies |
| Deciding when to ask for that rating | Jev, by Typesafe (typesafe/jev-1.13) |
| Transcribing voice notes | Voxtral Small, by Mistral (mistralai/voxtral-small-24b-2507) |
| Watching videos and reading PDFs | Gemini 3.8 Flash (google/gemini-3.8-flash) |
| Searching knowledge | OpenAI text-embedding-3-small |
| Judging evals | Gemini 3.8 Flash: a different family than the replies, so it never grades its own kind of answer |
DeepSeek's models are open-weight. OpenRouter serves them from independent inference providers, not from DeepSeek's own API.
How long conversations stay in Vatio, and how to delete them, is in Retention and deletion.
#Zero data retention
Every request, replies and embeddings alike, asks OpenRouter for zero data retention endpoints only. The provider that runs the model keeps neither the prompt nor the answer, and trains on neither. When no such endpoint is available the request fails rather than going to one that keeps data: Vatio retries it, and if it still fails the visitor gets the same message as for any reply that could not be generated.
Vatio keeps the conversation itself, to run the inbox, memory and evals. The privacy policy lists every sub-processor and where it runs.
#Using a different model
Choosing the model for an agent is not available yet. If yours needs a specific one, such as a larger model for harder conversations or one your company already approved, write to support@vatio.ai with the model and what it is for.