Voice agent cost
A voice agent is four paid services stacked on a phone call: listen (STT) → think (LLM) → speak (TTS) → the line itself (telephony). The LLM is often less than half the bill.
The formula
Defaults reflect mainstream hosted APIs as of : Whisper-class STT, mid-tier neural TTS (~450 chars/min), typical US inbound voice-API rate. Token prices update daily from OpenRouter's API. Barge-in (interrupted speech) typically cuts billed minutes 10–20% — not modeled; treat the result as the conservative case.
What actually drives the per-minute number
Four meters run at once on every call, and they do not move together. Knowing which one your workload stresses is the difference between a $0.04/min agent and a $0.30/min one.
| Meter | Typical rate | Scales with |
|---|---|---|
| Speech-to-text | $0.004–0.006 / min | Call duration, not turns |
| LLM turns | $0.005–0.060 / min | Turns × context size × model tier |
| Text-to-speech | $0.010–0.030 / min | Call duration; premium voices cost 3–10× mid-tier |
| Telephony | $0.007–0.020 / min | Call duration; inbound US is the cheapest case |
Two consequences follow. First, three of the four meters bill on minutes, not on intelligence — so making the model cheaper buys you less than you expect. Second, the model is the only meter you can move by editing code, which is precisely why teams over-optimise it and under-budget the rest.
Why the transcript, not the model, is the real turn meter
Every turn re-sends the running transcript. Turn one might carry 300 tokens; turn eight carries the entire preceding exchange plus the system prompt. On a six-turn call the input side is therefore not 6 × 600 — it is closer to the triangular sum of a transcript that keeps growing, which is why the context-per-turn default here describes a mid-call turn rather than the first one.
The practical effect is counter-intuitive: cutting a bloated system prompt from 1,200 tokens to 400 often saves more than switching the answering model from a frontier tier down to a mini, and it costs you nothing in answer quality on the short transactional intents that make up most call volume.
Where teams get this wrong
- Quoting the token bill as "the cost of the agent". It is usually under half. A vendor page that shows only per-token pricing is showing you the smallest of the four meters.
- Assuming every call completes. Calls that hang up mid-turn, reach voicemail, or loop through a retry still bill speech and telephony. A 10–20% non-productive call rate is normal and belongs in the model.
- Forgetting barge-in. When callers interrupt, synthesised audio stops early, so billed TTS minutes run below call minutes. This calculator does not model that, which makes its output the conservative case — real bills tend to land 10–20% under it.
- Ignoring concurrency. Per-minute rates price the marginal call; platform or per-concurrent-session fees price the peak. An agent taking 100 calls a day and an agent holding 20 simultaneous calls are two different pricing conversations.
- Benchmarking on short calls. A 90-second demo costs a fraction of a seven-minute production call, and the production distribution looks nothing like the demo.
Cutting the bill without hurting the call
- Route by intent, not by default. Send "what are your opening hours" to a small model and reserve the expensive tier for genuine escalations. Most voice traffic is transactional.
- Cap transcript growth. Summarise every N turns instead of re-sending everything. This is the single largest lever on the LLM meter and the one most teams leave untouched.
- Audit the system prompt quarterly. Voice prompts accumulate policy text nobody has read in months.
- Check your TTS tier. Over phone-band audio, mid-tier neural voices are hard to distinguish from premium ones for most transactional use cases.
- Measure abandonment, not just cost. The cheapest agent that callers hang up on is the most expensive one you can build.
Concurrency: the cost that never appears on a per-minute rate card
Everything on this page is priced per minute, which describes the marginal call and says nothing about the busiest one. Production voice platforms charge for capacity somewhere — a per-concurrent-session fee, a tiered package, or a committed minimum. An agent answering 100 calls spread across a day needs very little capacity; the same 100 calls arriving inside a two-hour window needs an order of magnitude more.
Before committing to infrastructure, take the per-call figure this calculator produces and multiply it by your expected peak calls per minute rather than the daily average. The two numbers differ by far more than teams expect, and it is the second one that gets priced.
The same distinction applies to the model. A per-token rate is a marginal price; rate limits and provisioned throughput tiers are capacity prices. An agent that performs perfectly in testing and fails at nine o'clock on a Monday morning is not experiencing a model problem — it is experiencing a capacity problem, and capacity is where voice projects most often discover a cost they never modelled.