Product teams usually need predictable APIs, embedded controls, identity, analytics, and a reliable path from prototype to production. Price the runtime and the engineering around it together.
Questions to ask
Can the experience fit our product and auth model?
Programmable Voice component that connects a TwiML ConversationRelay session to an application WebSocket for STT/TTS, language settings, DTMF, and call events.
Telephony voice-agent runtime
Scope and signals
Best fit: Developers building their own voice-agent logic while keeping telephony, media handling, and call control in Twilio.
Voice stack: Cascaded speech interface with developer-supplied LLM
Regular monthly: Free 15 min; Starter $6/75, Creator $22/275, Pro $99/1,238, Scale $299/3,738, Business $990/12,375 min. Extra minutes $0.08; concurrency burst $0.16. LLM and external carrier charges are separate.
Google's Gemini Live API streams multimodal sessions over WebSockets; its stable native voice-agent models are Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking.
Native realtime multimodal model API
Scope and signals
Best fit: Developers building low-latency conversational agents that need native audio, multimodal input, and function calling in a persistent WebSocket session.
Voice stack: Native audio agents: Gemini 3.8 Live (gemini-3.8-live) and Gemini 3.8 Live Extended Thinking (gemini-3.8-live-extended-thinking)., Separate TTS models: gemini-3.8-flash-tts and gemini-3.8-flash-lite-tts generate speech; neither is a Live agent., Separate transcription endpoints: gemini-3.5-transcribe handles audio files; gemini-3.5-transcribe-live is a Live API speech-to-text mode, not a conversational agent., Separate translation mode: gemini-3.5-live-translate-preview is a Live API interpreter for 70+ languages, not a conversational agent; it is preview.
Standard paid rates are $0.005/min equivalent for input audio and $0.018/min equivalent for output audio, billed separately plus text tokens; Google also lists a free API tier.
Revenue and contact-center platform with a no-code voice-agent builder, unified customer profiles, event-triggered journeys, IVR/routing, and cross-channel outreach.
Revenue and contact-center voice agent platform
Scope and signals
Best fit: Revenue or service teams coordinating inbound and outbound voice with customer-signal-driven journeys.
Hosted voice and chat agent platform built around either node-based conversation flows or single prompts, with telephony, tools, knowledge base, and analytics.
Voice agent platform
Scope and signals
Best fit: Teams comparing a managed agent builder with both visual flow design and API/SDK control.
Voice stack: Configurable STT-LLM-TTS pipeline with custom LLM option
No-code voice-agent builder with configurable voice engines, imported or cloned voices, and an enterprise fallback voice model.
No-code voice agent builder
Scope and signals
Best fit: Teams wanting visual call-flow construction and voice-provider controls with deployment pricing scoped by usage, telephony, integrations, and support.
Unified Voice Agent API that combines Deepgram speech recognition, LLM orchestration, and voice synthesis with function calling and mid-session controls.
Voice agent API and speech infrastructure
Scope and signals
Best fit: Developers who want one managed voice API instead of assembling separate STT, orchestration, and TTS services.
Voice stack: Cascaded STT-LLM-TTS managed full stack
Product teams need to know which layer becomes part of their application. Specify the browser or phone entry point, session state, authenticated tools, failure behavior and event data your product must retain.
Prototype the hardest integration before polishing a demo. Estimate the work to release changes, reproduce failed sessions and monitor cost per completed user task. Use the platform category for provider selection and the build-versus-buy guide for ownership decisions.
Evaluate language support in real calls
Test recognition, speech quality, interruptions, language switching, tool use, and human transfer with your own calls in the required language. Availability can vary by model, plan, and phone route.
DocsBot documents multilingual voice workflows and Japanese support. Verify the exact voice, phone path, and transfer behavior in your pilot. Review DocsBot language information ↗
Other providers’ language claims reflect cited vendor material; confirm Japanese and other required languages directly with each provider.
Listing does not imply endorsement or a performance guarantee. This directory is published by DocsBot. Editorial policy
Your business. Your shortlist.
Find your best-fit AI voice system.
Start with your website. Answer a few focused questions, then get a personalized PDF with fit, trade-offs, alternatives and a pilot plan for your call flow.
