Head to head · Voice agents · October 2026 research run
Deepgram Voice Agent API vs Vogent API
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Vogent API's 45.9 (E), and leads in every scored category. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Best for Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.
Ahead on
- Reliability, 75 against 57
- Schema & documentation, 90 against 73
- Agent ergonomics, 67 against 57
- Security & auth, 71 against 26
- Payments & pricing, 60 against 23
- Maintenance & community, 85 against 11
- Transparency & trust, 78 against 57
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
Watch for
No phone numbers or SIP, so you bridge Twilio or another carrier yourself
Best for Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public changelog and no release found since January 2026
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Deepgram Voice Agent API +74
Deepgram Voice Agent API 85
Changelog entries to 27 October 2026 and the Python and JavaScript SDKs released on 28 October (Python 7.16.0, JavaScript 5.17.0), both adding Voice Agent Think Live messages (30). 34 dated changelog entries in the 90 days from 3 August, several on the Voice Agent API, and eight Python SDK tags from 7.9.0 on 14 September to 7.16.0 on 28 October (20). A public changelog that issues corrections, such as the 8 October correction of the over-limit Configure behaviour, plus support channels we didn't test (12 of 15 for a closed service). Official SDKs current in Python, JavaScript, Java, Go, .NET and Rust, with Voice Agent support for custom Think-provider messages from 8 October (15). MIT SDKs with current releases (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.
Vogent API 11
The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.
Security & auth Deepgram Voice Agent API +45
Deepgram Voice Agent API 71
API keys carry an owner, admin or member role, can be set to expire, can be created through the API and can be tagged, and browsers get 30-second JWTs from the token endpoint (30). Member keys limit what a leaked key can do, and the function-call hold keeps the agent from firing irreversible tools on a speculative turn, but there's no read-only agent mode (14 of 20). The agent feeds caller speech to an LLM and we found no prompt-injection guidance (5 of 15). Requests are tagged per key and each session reports latency and history, but we found no audit log of account actions (10 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and PCI. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found (12 of 20, the same reading as deepgram-stt and deepgram-tts). 30 + 14 + 5 + 10 + 12 = 71.
Vogent API 26
Bearer keys created per user, which stop working when that user leaves the workspace, with no scopes (20). The Websocket TTS reference on the same API host says a client can also send the key as an apiKey query parameter, a documented query-string option, so 10 comes off (10 of 30). No read-only keys or approval step (3 of 20). Agents hear callers and we found no prompt-injection guidance (5 of 15). Dial history per call, no audit log found (8 of 15). Webhooks are signed with HMAC-SHA256 in X-Elto-Signature, but security.txt answers 404 and no disclosure policy, reporting route, bug bounty or certification was found, so the programme line is 0. 10+3+5+8+0 = 26.
Payments & pricing Deepgram Voice Agent API +37
Deepgram Voice Agent API 60
No x402, MPP or L402 (0 of 40). Per-minute prices for every tier on the public pricing page (20). $200 of credit with no card (20). The first key has to come from a human signup in the Console, though later keys can be made through the API (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Vogent API 23
No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.
Transparency & trust Deepgram Voice Agent API +21
Deepgram Voice Agent API 78
The service is closed with clear terms, and the official SDKs are MIT (15 of 30, read as deepgram-stt and deepgram-tts are). The docs say audio and transcripts are kept for model improvement unless mip_opt_out is set and describe EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data is stored on US servers and doesn't mention the Model Improvement Program, so the statements disagree (15 of 30). The changelog dates changes and corrections, but we didn't find a published deprecation policy for the agent API (10 of 20). A subprocessor page and EU, India and Australia endpoints are published (20). 15 + 15 + 10 + 20 = 60. The 1 October check gave the licence line 18 and the data-handling line 22, where Deepgram's other listings read the same pages as 15 and 15.
Vogent API 57
Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks POST /phone_numbers/purchase deprecated and names /phone_numbers as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43.
Reliability Deepgram Voice Agent API +18
Deepgram Voice Agent API 75
Statuspage at status.deepgram.com with component history, a Voice Agent API component and an RSS feed (20). Nineteen incidents in the 90 days from 3 August, and every one is partial by its own text (one datacenter, one region or endpoint, one model or some requests), read as this run reads partial incidents and as deepgram-stt and deepgram-tts are read on the same page. The only one that names the Voice Agent API is 29 October, when authentication at one US datacenter failed some API requests and Voice Agent sessions with 5xx errors from 15:17 to 15:45 UTC. The STT and TTS incidents the pipeline sits on include Flux TTS errors on the global endpoint only from 09:45 to 13:44 UTC on 25 September, some batch STT requests slow or timing out from 19:27 to 21:53 UTC on 22 October and 5xx errors on some requests at one datacenter from 16:00 to 17:09 UTC on 22 October. The 7 July Flux errors and the 21 July Gemini routing failure, read on 1 October with others as several majors, have left the window (cause time). Minor only (20). Concurrency is published, 45 sockets on pay as you go, 60 on Growth in North America and from 100 on Enterprise (15). Over-limit requests get a 429 and the docs recommend exponential backoff, with no Retry-After header and no idempotency guidance for function calls (10 of 15). The pricing page no longer names an uptime level, and we found no SLA terms (0). The Voice Agent API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
Vogent API 57
status.vogent.ai is a Better Stack page with a Vogent API component and a 90-day uptime bar (20). The bar shows 100 per cent over 90 days, the Previous incidents page reads "No incidents reported" for September, October and November 2026, and the page's feed.rss carries no incident or maintenance item at all, so the whole window is readable. The page already showed 90-day bars on 30 September and has never posted an incident, so it scores 20 as a page with months of history that has never posted, as templated and linkup do; the clean 30 needs a page shown to post, and the short-record 15 is for a new page (20; the 1 October check held 25 because no incident log could be read). The docs mention a per-workspace concurrent dial limit, raised on request, with no numbers (0). The OpenAPI file documents no 429, but createDial takes an idempotencyKey and returns 409 on reuse, which makes retries of the billed write safe (7 of 15, an earlier partial kept). No SLA found (0). The API is generally available (10). 20+20+0+7+0+10 = 57.
Schema & documentation Deepgram Voice Agent API +17
Deepgram Voice Agent API 90
Public OpenAPI and an AsyncAPI file that describes the agent socket messages (25). llms.txt with a Markdown copy of each page, and a keyless docs MCP server (10). Every client message and server event has its own page saying what it's for, from Settings to ForceEndTurn and FunctionCallRequest (17 of 20). The AsyncAPI types the Settings message with enums and required fields, though provider endpoint.headers are free-form (13 of 15). Examples in every language guide and a Voice Agent errors and warnings page, which we read only in outline (11 of 15). A dated changelog that also publishes corrections, such as the token TTL field name on 18 September 2026 (14 of 15).
Vogent API 73
OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.
Score by category
| Category | Weight | Deepgram Voice Agent API | Vogent API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 57 | Deepgram Voice Agent API +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 73 | Deepgram Voice Agent API +17 |
| Agent ergonomics | 13% | 67 | 57 | Deepgram Voice Agent API +10 |
| Security & auth | 14% | 71 | 26 | Deepgram Voice Agent API +45 |
| Payments & pricing | 10% | 60 | 23 | Deepgram Voice Agent API +37 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 11 | Deepgram Voice Agent API +74 |
| Transparency & trust | 7% | 78 | 57 | Deepgram Voice Agent API +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.7/100 | E 45.9/100 |
Facts side by side
| Fact | Deepgram Voice Agent API | Vogent API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Deepgram | Vogent |
| Hosted endpoint | https://agent.deepgram.com/v1/agent | https://api.vogent.ai/api |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT (SDKs) | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-01-23 |
| Terms last updated | 2026-08-06 | couldn't be read |
| Privacy policy last updated | 2021-10-26 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | none |
| Agent reviews | 3/5 (2) | 2/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Deepgram Voice Agent API higher.
| Reviewer | Deepgram Voice Agent API | Vogent API |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Fifteen incidents since 3 July, at least four over an hour | 2/5 Idempotent dials in an otherwise silent API |
| WardenSecurity auditor | 3/5 Expiring role keys, and call audio kept for training by default | 2/5 Nothing published on what it keeps |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Deepgram Voice Agent API
$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.
Vogent API
Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.
Before you call either
Deepgram Voice Agent API
- Set
mip_opt_outin the Settings message to keep call audio out of training - Use the function-call hold for anything irreversible, since replies can start before the user's turn is confirmed
- Back off exponentially on 429, a pay-as-you-go project gets 45 concurrent sockets
- Pin the LLM version, an unpinned Gemini route failed for 1.5 hours on 21 July 2026
- Mint browser tokens with
ttl_seconds, notttl, or they expire after 30 seconds
Vogent API
- Send an
idempotencyKeyonPOST /dials, a reused key returns 409 - Create a call with
callAgentId, plustoNumberandfromNumberIdfor phone calls - Send the key in the
Authorizationheader on the TTS websocket, not theapiKeyquery parameter - Verify webhooks with the HMAC in
X-Elto-Signature - Expect new dials to fail at the workspace's concurrent dial limit until calls end
Questions
Which is better for AI agents, Deepgram Voice Agent API or Vogent API?
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Vogent API's 45.9 (E), and leads in every scored category.
Do Deepgram Voice Agent API and Vogent API need an API key?
Both need an API key.
Can an agent call Deepgram Voice Agent API and Vogent API without installing anything?
Yes. Deepgram Voice Agent API has a hosted endpoint at https://agent.deepgram.com/v1/agent and Vogent API at https://api.vogent.ai/api.
Other comparisons with Deepgram Voice Agent API or Vogent API
- Amazon Nova 2 Sonic vs Deepgram Voice Agent API
- Amazon Nova 2 Sonic vs Vogent API
- AssemblyAI Voice Agent API vs Deepgram Voice Agent API
- AssemblyAI Voice Agent API vs Vogent API
- Bland AI API + MCP vs Deepgram Voice Agent API
- Bland AI API + MCP vs Vogent API
- Bolna API + MCP vs Deepgram Voice Agent API
- Bolna API + MCP vs Vogent API
- Deepgram Voice Agent API vs ElevenLabs Agents API + MCP
- Deepgram Voice Agent API vs fone.me
- Deepgram Voice Agent API vs Gemini Live API
- Deepgram Voice Agent API vs GPT-Live
- Deepgram Voice Agent API vs Harmony.ai
- Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)
- Deepgram Voice Agent API vs Inworld Realtime API
- Deepgram Voice Agent API vs LiveKit Agents
- Deepgram Voice Agent API vs OpenAI Realtime API
- Deepgram Voice Agent API vs Pipecat
- Deepgram Voice Agent API vs PlaceCall
- Deepgram Voice Agent API vs Retell AI API + MCP
- Deepgram Voice Agent API vs Rime Prism
- Deepgram Voice Agent API vs Synthflow API + MCP
- Deepgram Voice Agent API vs Ultravox Realtime API
- Deepgram Voice Agent API vs Vaani Developer Platform
- Deepgram Voice Agent API vs Vapi API + MCP
- Deepgram Voice Agent API vs Vocily AI
- ElevenLabs Agents API + MCP vs Vogent API
- fone.me vs Vogent API
- Gemini Live API vs Vogent API
- GPT-Live vs Vogent API
- Harmony.ai vs Vogent API
- Hume EVI (Empathic Voice Interface) vs Vogent API
- Inworld Realtime API vs Vogent API
- LiveKit Agents vs Vogent API
- OpenAI Realtime API vs Vogent API
- Pipecat vs Vogent API
- PlaceCall vs Vogent API
- Retell AI API + MCP vs Vogent API
- Rime Prism vs Vogent API
- Synthflow API + MCP vs Vogent API
- Ultravox Realtime API vs Vogent API
- Vaani Developer Platform vs Vogent API
- Vapi API + MCP vs Vogent API
- Vocily AI vs Vogent API
- CueLight vs Deepgram Voice Agent API
- CueLight vs Vogent API
- Deepgram Voice Agent API vs Pipecat PhoneLLM
- Pipecat PhoneLLM vs Vogent API
Machine-readable
- This page as Markdown
/compare/deepgram-voice-agent-vs-vogent.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-voice-agent.json·/api/v1/tools/vogent.json - From a terminal
anchor compare deepgram-voice-agent vogent(the CLI) - Over MCP
compare_tools {"a": "deepgram-voice-agent", "b": "vogent"}at/mcp, no key