Full observability for your Vapi voice agents
Connect your Vapi assistant to Tuner with no code, paste your API key and every call's transcript, latency, and outcome flows in automatically. Works with both permanent and transient agents, so even inline per-call assistants stay grouped and analyzable.
Setup
Integrate in under two minutes
Paste your Vapi key, point Tuner at your assistant, and Tuner configures the webhook for you.
01
Get your Vapi credentials
Copy your Private API key and Assistant ID from the Vapi dashboard.
02
Add your key in Tuner
Paste your Vapi Private key under Workspace Settings → API Keys & Integrations and save, before you create the agent.
03
Create your agent
Add a new agent in Tuner with Provider: vapi and your Assistant ID as the Agent Remote ID.
04
Tuner wires the webhook
Tuner configures the Vapi webhook automatically. Already using a webhook? The webhook proxy forwards every call to your existing n8n or Zapier flow too.
Setup
Works with both Permanent and Transient agents
However you build on Vapi, Tuner captures every call — including the inline, per-call agents that normally vanish.
Permanent agents
Stored in Vapi, referenced by Assistant
Your assistant lives in the Vapi dashboard and every call points at its Assistant ID. Connect it to Tuner once and all of that agent's calls are captured, scored, and alerted on automatically.
Transient agents
Built inline, per call, and they scatter
You hand Vapi the whole agent inline on every call, so nothing is stored and calls aren't tied to an Assistant ID. Tuner pulls those scattered calls back into one view, grouped by customer, use case, or prompt version — so multi-business and per-caller agents stay fully analyzable.
Why Tuner
See what's happening in production
Voice agents fail quietly, and at a scale no team can review by hand. Tuner turns every production call into structured data you can search, debug, evaluate, alert on, and test against.
Comparison
Tuner vs Vapi Monitoring
Vapi's monitoring, alerting, and evals are good. The problem is that Vapi is scoring the same agent it built, and it only reports per turn. One turn can hide several nodes, so you get a number without knowing which step broke. Tuner stays independent and goes node by node, pointing to the exact STT, LLM, or TTS step behind a failure or delay. It also tracks quality across versions and runs SIP simulations with AI agents before you ship.
Capability
Tuner
Vendor-independent observability, eliminating the conflict of a platform evaluating its own output
Evals pricing built for scale: tuner price per call, no per minute surcharge
Built-in flags (hallucination, dead air, early hangup)
Root-cause diagnosis with a specific fix, not just metrics
30+ voice quality metrics & red flags out of the box
Drift & regression alerts over time
SIP call simulations with AI agents, using your live evals
Turn-by-turn transcripts & latency traces
FAQ
Frequently asked questions
Common questions about connecting Tuner to your Vapi agents.
Read the docs
Do I need to write code to connect Vapi to Tuner?
Will connecting Tuner break my existing Vapi webhook?
Does Tuner work with transient (inline) Vapi agents?
What gets captured?
Can I test my agent before going live?
How long does setup take?
Does Tuner support alerts and monitoring?
Can I define my own evaluations and metrics?
How is Tuner priced?
Is my call data private and secure?
