Web chat + WhatsApp · one file, one command
Your coding agent can ship your customer agent.
The runtime for AI agents that talk to real customers, on web chat and on WhatsApp. An agent is one YAML file — so your agent can write it.
Hand it to Claude Code, Cursor or Codex — anything that can run a shell.
- A free shared WhatsApp number. No Meta account.
- Preview, live, and a one-command rollback.
- Safeguards you can't switch off.
Zero to live
Six commands. There is no step seven.
No dashboard wizard, no infrastructure YAML, no container to build. Push to preview, talk to it, publish when it reads right.
vatio pushis idempotent — no link or create step.vatio chatnever reaches a real customer.- Every deploy is a snapshot.
vatio rollbackundoes it.
workspace: acme business: name: Estudio Acme widget: accent_color: "#3355FF" agent: name: Sofía instructions: >- Answer questions about Estudio Acme: classes, schedule, prices and memberships. Check real availability before promising a spot. If you do not know something, say so. personality: Warm, brief, Chilean Spanish. tools: - search_knowledge - check_availability - identify_contact
One agent, every channel
Write the file. Push it. Text it.
One agent per workspace — the agent block of vatio.yml —
answering every conversation on every channel. No handoffs, no phases, no routing graph.
The same file powers the widget, the web chat page and WhatsApp — in whatever language the visitor writes in.
The platform
Everything a real conversation needs.
The channel nobody wants to integrate, the safeguards nobody wants to write, and the boring 80% underneath both.
A shared preview number every workspace can message from day one — no Meta Business account, no template approvals. Bring your own number when you go live.
How the preview worksSafeguards
Prompt-injection resistance, no invented links, no empty replies. A layer that runs on every turn and takes precedence over your manifest — you can't switch it off.
What runs on every turnFeatures
Knowledge base and crawling, JavaScript and declarative tools, a CRM that fills itself, silent auth, evals, the widget, secrets and diagnostics.
The boring 80%Built for the agent building it
One page. The entire contract.
Quick start, concepts, features, CLI and API on a single static page — because the thing most likely to read it is a language model with one shot at context. Your agent fetches the whole platform in one request, then writes a manifest that validates.
Give your agent the keys.
Copy the prompt, paste it into your agent, answer what it asks about your business.
# Vatio bootstrap prompt · docs: https://vatio.ai/docs Install the Vatio CLI and ship me a production agent. 1. Install: curl -fsSL https://vatio.ai/install.sh | bash 2. Run vatio docs --save and read vatio-docs.md first — one page, the whole contract. Don't guess the manifest format. 3. vatio login, then vatio init <slug> in a folder next to the code the agent will call. 4. Ask me what the business does and what the agent must never say, then write vatio.yml — workspace, business, widget and agent, all in that one file. 5. vatio push, then vatio chat "hi" and iterate with vatio chat debug --last 30. 6. Show me the WhatsApp preview link, then vatio publish.
curl, tar and Ruby ≥ 2.6.