Deepgram vs Rime (2026)

Voice Agent function calling lets the customer define custom tools as functions in Settings. Each function runs client side in the customer's application, or server side, where Deepgram calls a web endpoint the customer provides. During a live call, an agent can book appointments, send emails or update records in the customer's CRM, ERP or internal APIs.

SourceDeepgram, developers.deepgram.com (Function Calling)read 2026-09-27

Voice agent stacks call Rime as a text to speech API. It makes no tool calls and takes no action in outside systems. Its integrations with LiveKit, Pipecat, Daily, Vapi, VideoSDK and Twilio plug Rime's voice into those platforms.

SourceRime, docs.rime.ai (llms.txt, integration guides)read 2026-09-27

Each Voice Agent session is a fixed pipeline that Deepgram runs end to end. It chains listen, think and speak, with an ordered LLM fallback chain per request and mid call Update messages for the prompt and providers. The customer configures the pieces, not the control flow. In the multi agent architecture guide, a CallOrchestrator sequences qualifier, advisor and closer agents in a reference repository the customer runs, so that orchestration is the customer's own code.

SourceDeepgram, developers.deepgram.com (LLM Models, Build a Multi-Agent Architecture)read 2026-09-27

Each request turns text into speech, and Rime has no workflow model. In the voice agent tutorials, the listen, think and speak loop runs in the customer's own code or in LiveKit or Pipecat. Orchestration lives in the platform that calls Rime.

SourceRime, docs.rime.ai (Build a voice agent, Streaming TTS)read 2026-09-27

The Voice Agent works on phone calls through inbound and outbound telephony builds for Twilio and Amazon Connect, and in web pages through the Browser Agent SDK and an embeddable widget. Every session starts when a caller dials in, or when the customer's own server opens the socket or places the call. The outbound reference build takes a POST from the customer's CRM or CLI. Deepgram has no event, schedule or webhook of its own that wakes the agent.

SourceDeepgram, developers.deepgram.com (Build an Outbound Telephony Agent, Browser Agent SDK)read 2026-09-27

The customer's application starts every synthesis by sending a request over HTTP or WebSockets, and Rime runs only when called. It owns no phone numbers, channels, schedules or events. Twilio and the voice platforms supply the calls.

SourceRime, docs.rime.ai (Streaming TTS, WebSocket API)read 2026-09-27

The products cover speech to text, text to speech, audio and text intelligence, and the Voice Agent, and none of them ingests, indexes or retrieves the customer's documents. Context reaches the agent through the prompt, loaded history and function results the customer supplies. Keyterm prompting tunes transcription vocabulary.

SourceDeepgram, developers.deepgram.com (llms.txt, Maintaining Context)read 2026-09-27

There is no retrieval over the customer's content. The product covers models, voices, pronunciation, streaming and on premise engines. The pronunciation dictionary shapes how words are spoken.

SourceRime, docs.rime.ai (llms.txt, Pronunciation control)read 2026-09-27

Conversation state lives inside a session. The agent keeps the prompt, turns, injected messages and function results as working memory for the call. History (on by default) lets a new session load prior turns and function calls through agent.context.messages. The customer's application stores and supplies those prior turns. Deepgram names no memory layer of its own that lasts beyond a call.

SourceDeepgram, developers.deepgram.com (Maintaining Context, History)read 2026-09-27

Synthesis is stateless, and each request stands alone. By default Rime collects only character counts and keeps no customer content. It holds no conversation state.

SourceRime, docs.rime.ai (Privacy and compliance)read 2026-09-27

The customer can hold back agent actions, but there is no approval step. Setting defer_until_eot on a function holds any call whose side effect cannot be undone (ending a call, spending money, sending a message) until speech to text confirms the caller has finished the turn. Read only functions still dispatch early. Deepgram advises builders to set it on any irreversible action. No person approves an action inside Deepgram.

SourceDeepgram, developers.deepgram.com (Function Calling: Irreversible Actions and Turn Confirmation)read 2026-09-27

Rime takes no actions, so there is nothing for a person to approve or constrain. Pronunciation control and the spell function govern how text is spoken.

SourceRime, docs.rime.ai (Pronunciation control)read 2026-09-27

Access runs on account permissions plus owner, admin and member project roles, each implying a listed set of scopes. API keys are created per project and scoped to those permissions. Deepgram has SOC 2 Type 1 and Type 2 reports from an independent auditor, with certificates on request. It is a HIPAA business associate and signs a BAA for Enterprise customers. It also states GDPR, CCPA and PCI compliance, reviewed yearly.

SourceDeepgram, developers.deepgram.com (Working With Roles & API Scopes, Data Privacy Compliance) and deepgram.com/pricingread 2026-09-27

Teams have Owner and Member roles, and a permission table sets what each can do. Only owners can invite, edit billing, view all API keys, delete others' keys or remove members. Rime holds SOC 2 Type II, and the audit report is available under NDA. It is HIPAA compliant, with a BAA on Enterprise, and publishes a subprocessor list.

SourceRime, docs.rime.ai (Privacy and compliance, Teams) and rime.ai/securityread 2026-09-27

The Console shows usage and up to 90 days of request logs, and a Usage API exports them to tools such as Grafana or Datadog. For the Voice Agent, the dashboard gives no per session, turn by turn observability, and there is no separate logging API. The customer taps the WebSocket and stores the transcript, function call, latency and error events it emits. The per session trace is the customer's to keep.

SourceDeepgram, developers.deepgram.com (Session Observability, Logs & Usage Data)read 2026-09-27

Character usage shows in the dashboard and the CLI, and the CLI measures time to first byte per endpoint. On premise containers expose health and OpenTelemetry metrics for Prometheus. Reporting is aggregate, with no trace of each run. Rime keeps no request content by default, so there is nothing per request to inspect.

SourceRime, docs.rime.ai (Monitoring and usage, on-prem Metrics)read 2026-09-27

Regional endpoints at api.eu.deepgram.com (EU, never routed outside it) and api.au.deepgram.com (Australian infrastructure for storage and inference) serve speech to text, text to speech and the Voice Agent with the same keys. Premium customers can self host in cloud instances they requisition, such as AWS or GCP, or in their own data center. A third party LLM in the think step runs on that provider's infrastructure.

SourceDeepgram, developers.deepgram.com (Regional Endpoints, Deployment Options, Data Privacy Compliance)read 2026-09-27

Enterprise customers can run a licensed Coda or Mist v3 engine on their own NVIDIA hosts with Docker Compose or Kubernetes. This on premise option is generally available. Synthesis text and audio stay in the deployment, and only aggregate usage counts go to Rime. Plans offer cloud, on premise or VPC deployment. The cloud API has US West and US East endpoints.

SourceRime, docs.rime.ai (On-prem quickstart, Regional endpoints) and rime.ai/pricingread 2026-09-27

There are no packaged agents for customers to adopt. The Voice Agent template apps are one starter ported to twelve languages and frameworks on GitHub, offered as sample code. Reusable Agent Configurations store the customer's own agent blocks. Nova-3 Medical and Pharma are industry tuned speech models, not agents.

SourceDeepgram, developers.deepgram.com (Template Apps, Reusable Agent Configurations)read 2026-09-27

There are no packaged agents. The voice catalog holds 287 Coda voices plus Mist voices, which set how the model sounds. Voice agent tutorials for Next.js, Vite, Express, Node and FastAPI give developers sample code to build from, as does an MCP tool that generates Pipecat or LiveKit code.

SourceRime, docs.rime.ai (Build a voice agent, Voices)read 2026-09-27

Each Voice Agent's Settings name the think provider and model. The customer picks from OpenAI, Anthropic, Google and NVIDIA models Deepgram manages, or points to its own endpoint for Groq, Amazon Bedrock or any OpenAI compatible API. An ordered array of providers acts as a per request fallback chain that can mix providers. Listen and speak models are chosen the same way, including BYO TTS.

SourceDeepgram, developers.deepgram.com (LLM Models)read 2026-09-27

The customer picks among Rime's own speech models. Coda is the default, Mist v3 gives the lowest latency and Mist v2 offers inline pronunciation. Rime is the only provider, and it names no other provider or way to bring your own model.

SourceRime, docs.rime.ai (Models)read 2026-09-27

REST and WebSocket APIs cover speech to text, text to speech, text intelligence and the Voice Agent. A management API handles projects, keys and usage, and an Agent Configuration API sits beside it. Python, JavaScript, Go and .NET SDKs come with a feature matrix, alongside a Browser Agent SDK and the dg CLI, whose built in MCP server proxies the developer API's tools.

SourceDeepgram, developers.deepgram.com (llms.txt, Reusable Agent Configurations, MCP Server)read 2026-09-27

The API covers HTTP, SSE and WebSocket synthesis and a dictionary coverage endpoint, with quickstarts in cURL, Python, JavaScript and TypeScript. A Rime CLI sits beside it, along with a hosted MCP server whose authenticated tools list voices, check the dictionary, normalize text and synthesize speech. On premise engines take HTTP, gRPC or WebSocket.

SourceRime, docs.rime.ai (API reference, MCP Quickstart, Engine protocols)read 2026-09-27

There is no evaluation harness, scored test cases or quality gate for voice agents. Testing tools cover integrations, such as a streaming starter kit and a SageMaker endpoint check. Reusable Agent Configurations list A/B testing of voices or prompts as a use case, but the customer measures conversion or CSAT on its own. Custom model training improves transcription.

SourceDeepgram, developers.deepgram.com (llms.txt, Reusable Agent Configurations)read 2026-09-27

The coverage endpoint and its MCP tool report which words in the customer's script are missing from Rime's pronunciation dictionary. The check runs on input text. Rime's latency benchmarks are measurements of its own models. Customers get no way to evaluate agent behavior.

SourceRime, docs.rime.ai (Coverage, Latency)read 2026-09-27

The Browser Agent SDK embeds a voice agent in a web page, so the product runs in a browser without operating one. Telephony is a voice channel. Deepgram names no browser, desktop or computer control for its agents.

SourceDeepgram, developers.deepgram.com (llms.txt, Browser Agent SDK)read 2026-09-27

As a speech synthesis API, Rime has no browser, desktop or computer control.

SourceRime, docs.rime.ai (llms.txt)read 2026-09-27