By Sagar Shankaran, Founder of CallSphere
Vapi's $0.05/min is a platform fee, not a finished product. Here are the 5 vendors you actually pay — and why CallSphere bundles them.
Key takeaways
Vapi's $0.05/min is a platform orchestration fee, not a complete voice agent. To answer a phone call you must additionally subscribe to Deepgram (or another STT), OpenAI or Anthropic (LLM), ElevenLabs or Cartesia (TTS), and Twilio (telephony). Stack them and your real cost lands at $0.27–$0.33 per minute. CallSphere bundles all five layers into one flat-tier invoice — voice, chat, analytics, dashboards, RBAC included.
Buyers comparing voice AI vendors almost always anchor on the per-minute rate published on the homepage. Vapi's number is $0.05/min. It is among the lowest in the category, and it is real — that is what Vapi charges for its orchestration plane.
The problem isn't the number. The problem is what the number does not include. Vapi is, by design, a developer-first infrastructure product. It assumes you will plug in your own speech recognition, your own LLM, your own voice synthesis, and your own telephony provider. That is the Vapi value proposition — flexibility — and it is also the source of most billing surprises.
This post itemizes every vendor a Vapi customer signs, what each one bills for, and how CallSphere absorbs all of them.
Below is the canonical billing topology of a production Vapi voice agent.
| # | Layer | Common vendors | What they meter |
|---|---|---|---|
| 1 | Orchestration | Vapi | Per minute connected |
| 2 | Speech-to-Text | Deepgram, Whisper | Per audio second |
| 3 | LLM | OpenAI, Anthropic, Google | Per input/output token |
| 4 | Text-to-Speech | ElevenLabs, Cartesia, Azure | Per character spoken |
| 5 | Telephony | Twilio, Telnyx | Per minute + per-number rental |
Each vendor publishes their own price list, their own SLA, their own status page, their own outage history, their own support queue, and their own renewal cycle. Each must be procurement-approved separately. Each generates a separate monthly invoice. Each can change pricing independently.
Take a 10-minute call. Let's walk through what each vendor charges.
Total for one 10-minute call: ~$3.38, or $0.338/min.
That is the all-in real-world cost — about 6.7x the advertised platform fee.
CallSphere does not resell the five vendors. It runs the same kind of stack under the hood, but consolidates pricing, SLA, observability, and accountability into one platform. From a buyer's perspective:
For finance teams, this is often a bigger win than the cost difference. Multi-vendor reconciliation is real overhead.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
graph TD
subgraph Vapi
V1[Vapi invoice]
V2[Deepgram invoice]
V3[OpenAI invoice]
V4[ElevenLabs invoice]
V5[Twilio invoice]
end
subgraph CallSphere
C1[CallSphere invoice]
end
V1 --> R[AP team reconciles]
V2 --> R
V3 --> R
V4 --> R
V5 --> R
C1 --> S[AP team approves]
R --> RES[5 contracts, 5 SLAs, 5 renewals]
S --> SES[1 contract, 1 SLA, 1 renewal]
style Vapi fill:#fee
style CallSphere fill:#efe
Figure 1 — Vapi customers reconcile five recurring invoices. CallSphere customers reconcile one.
The five-vendor stack also requires gluing them together — and keeping them glued. That engineering effort is rarely budgeted explicitly but always shows up:
At a fully-loaded $180k/year senior engineer, 0.25 FTE is $45k/year of carrying cost — often more than the per-minute spend itself for SMB deployments.
Profile: 4 dental clinics, ~6,000 reception minutes per month combined.
| Line | Monthly |
|---|---|
| Vapi platform | $300 |
| Deepgram STT | $46 |
| OpenAI GPT-4o | $840 |
| ElevenLabs | $756 |
| Twilio (4 numbers + traffic) | $124 |
| Direct vendor cost | $2,066 |
| Engineering carrying (0.15 FTE) | $2,250 |
| Effective monthly | ~$4,316 |
Growth tier covers the volume flat. Healthcare product ships HIPAA-ready out of the box with 14 function-calling tools and post-call analytics — none of which the Vapi stack delivers without additional engineering. See /industries/healthcare.
At this profile CallSphere typically lands 40–55% below the Vapi path, with zero variance.
| Surface | Vapi customer | CallSphere customer |
|---|---|---|
| Number of vendor contracts | 5+ | 1 |
| Monthly invoices | 5+ | 1 |
| Status pages to monitor | 5+ | 1 |
| Engineering carrying cost | 0.1–0.25 FTE | ~0 |
| Cost variance month-to-month | High (token + character billing) | Flat |
| Forecastable in a budget | Hard | Easy |
If you're a current Vapi customer and the multi-vendor model is grinding on your finance team:
Because that is genuinely Vapi's price for its layer. They are a platform/orchestration vendor, not a turnkey product. The $0.05 isn't deceptive — it just isn't your final cost.
CallSphere absorbs vendor management by default. Enterprise customers can BYO keys for specific compliance or sovereignty reasons, but the standard model is consolidated billing.
CallSphere prices flat tiers, not per-minute markups. Volume committed across many customers gets passed back as predictable, lower flat pricing.
Flat tiers are sized with realistic LLM headroom. If your agents are unusually verbose (long system prompts, large RAG contexts), the Enterprise tier offers tuned envelopes.
You save the $0.05/min platform fee but inherit all the orchestration work — websocket bus, agent state, function-calling glue, retries, observability. That work is roughly 3–6 months of senior engineering. Most buyers don't actually want to be in the voice infrastructure business.
The flat tiers are listed at /pricing. For volume above Scale, /contact for an Enterprise quote.
Yes — 57+ languages are supported across voice and chat. Multilingual voices and vocabularies are part of the bundled tier; you do not pay separate per-language fees. This contrasts with Vapi-assembled stacks where each language often requires a separate ElevenLabs voice subscription and language-specific Deepgram model selection.
Yes. CallSphere connects via function-calling tools that wrap your CRM, PMS, ticketing system, or custom internal API. Common integrations (HubSpot, Salesforce, athenahealth, Acuity, MindBody, Zendesk, etc.) have prebuilt connectors. Custom integrations are scoped during onboarding.
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
A common Vapi pitch is that the platform's flexibility prevents lock-in: bring your own STT, your own LLM, your own TTS, your own telephony. In theory you can switch any of them without re-architecting.
In practice, this rarely plays out. Once a production voice agent is tuned against a specific Deepgram model, a specific OpenAI model version, a specific ElevenLabs voice, and a specific Twilio routing pattern, swapping any one component is a real engineering project — one that requires re-tuning, re-testing, and re-evaluating end-to-end behavior. The cost of switching components is usually higher than the cost of staying.
The more interesting form of lock-in, though, is the operational kind. Once your team has built workflows around five vendors' dashboards, support queues, and incident channels, the cost of switching the orchestration layer (Vapi itself) is dominated by the cost of re-wiring all those operational rituals.
CallSphere doesn't pretend to eliminate vendor lock-in — every platform is a lock-in to some degree. What CallSphere does is reduce the lock-in surface from five vendors to one. If you ever leave CallSphere, you have one provider to migrate from, not five.
A natural concern with bundled pricing is "what happens when my LLM token usage explodes?" The Vapi argument is that per-meter pricing reflects real cost, while bundled pricing must either build in fat margins or eat losses on heavy users.
CallSphere's answer is that flat-tier envelopes are sized with realistic LLM headroom based on observed traffic across our customer base. The verbose-call problem is real, but at scale (across thousands of agents) the average converges. Heavy verbosity in one tenant is offset by lighter usage in another. CallSphere's volume aggregation means the bundled rate beats the per-meter rate that any single tenant would pay retail.
For tenants with genuinely unusual usage patterns — extremely long conversations, heavy RAG contexts, custom evaluation pipelines — Enterprise tiers are sized explicitly to those envelopes, often with dedicated infra commitments.
Each of the five vendors uses a different unit of measurement, and the conversion between units is non-obvious. This is the source of most billing surprises.
The four different units mean engineering teams must mentally translate between them to forecast costs. Most teams don't, which is why surprises compound. CallSphere flattens all four into one unit: dollars per month, by tier.
graph LR
V[Vapi: per minute] --> X[Forecast unit confusion]
D[Deepgram: per audio second] --> X
O[OpenAI: per token] --> X
E[ElevenLabs: per character] --> X
T[Twilio: per minute + DID rental] --> X
X --> Y[Forecast accuracy ±20%]
C[CallSphere: per month flat] --> Z[Forecast accuracy ±2%]
style X fill:#fcc
style Z fill:#cfc
Figure 3 — Five different billing units vs one. Forecast accuracy follows.
Profile: 6-person clinic offering primary care, dermatology, and physical therapy. 12,000 voice + chat minutes/month combined. HIPAA required.
Plus chat is not handled (would require additional vendor layer with its own LLM, vector store, and frontend SDK).
Healthcare product ships HIPAA-ready, voice + chat unified, 14 function-calling tools, GPT-4o-realtime voice, GPT-4o-mini analytics, 20+ DB tables, post-call sentiment + lead + intent + satisfaction + escalation. See /industries/healthcare.
The clinic gets a working, deployed product on day one — not a prototype to harden. Ops staff grade calls in the dashboard without engineering involvement. Compliance posture is documented.
Growth tier flat: typically lands well below half the Vapi-style all-in, with both voice and chat included, dashboards live, and zero engineering overhead.
Bring your last 90 days of voice AI invoices. We will calculate your true per-minute cost and quote a CallSphere flat tier that beats it — in writing.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
Oilfield-services vendors in Basra field procurement and tender calls at all hours from operators and international partners. CallSphere answers 24/7 in Arabic and English and routes serious tenders to a human.
The Pentagon struck AI deals with 8 Big Tech companies in May 2026, notably excluding Anthropic. The roster, what each contract covers, and what it signals.
Six-domain AI vendor diligence: financial, security, privacy, operational, legal, ethics. Plus 30+ specific questions, SOC 2 / ISO 27001 baselines, and review cadence.
Enterprise AI agent buyers need governance-first evaluation, 30-point scorecards, and quarterly re-verification. The 2026 procurement playbook for CIOs and CTOs.
Reconciling 5+ monthly invoices is a procurement nightmare. Here is the operational cost of multi-vendor voice AI — and the consolidation story.
How CallSphere's 14 healthcare tools are designed: clear naming, idempotency, auth-bound, error contract. Practical patterns for voice AI tool schemas.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI