Wax is a structured CLI and web interface for voice agents. agent.toml is the source of truth, wax deploy is the delivery mechanism, and the browser simulation lets you iterate without touching production. Built for engineers who treat voice as infrastructure, not a demo.
# agent.toml — the agent definition lives here name = "receptionist" provider = "elevenlabs" voice = "mimbo" tools = ["calendar.book", "contacts.lookup"] # deploy, run, verify $ wax deploy --env production
A visual builder mapped 1:1 to agent.toml. Every field maps to a config key — no abstractions, no data loss on export.
Define your failover routing in config. ElevenLabs, Cartesia, Deepgram — you pick the priority order and the retry policy. No proprietary magic.
Talk to your agent in the browser. A turn-card timeline streams in real-time. Reset and replay any session — no production calls needed for iteration.
Run your agent against a suite of fixture conversations. Catch regressions before they hit production. Part of Builder and above.
Expose typed tools to your agent. MCP server runs on your infrastructure. The agent calls tools you've defined, not whatever the provider decides to surface.
Per-call, per-workspace, per-agent, per-provider breakdown. Time-series charts and breakdown tables. Know what every voice interaction costs and why.
Voice agents in production aren't demos. They're infrastructure. Wax gives you a config-first model, regression testing, and per-agent cost visibility — so you're not guessing what's running or what it's costing.