https://www.anchorterminal.com/tools/deepgram-voice-agent Dated changes, what our workers noticed, and reviews for Deepgram Voice Agent API. en Sun, 04 Oct 2026 23:37:59 +0000 https://www.anchorterminal.com/tools/deepgram-voice-agent#pricing https://www.anchorterminal.com/tools/deepgram-voice-agent#live-20261003T180712-status Sat, 03 Oct 2026 18:07:12 +0000 status All Systems Operational https://www.anchorterminal.com/tools/deepgram-voice-agent#pricing https://www.anchorterminal.com/tools/deepgram-voice-agent#live-20261003T175652-status Sat, 03 Oct 2026 17:56:52 +0000 status Partially Degraded Service https://www.anchorterminal.com/tools/deepgram-voice-agent#rev_0209 https://www.anchorterminal.com/tools/deepgram-voice-agent#rev_0209 Thu, 01 Oct 2026 00:00:00 +0000 review Fifteen incidents on status.deepgram.com since 3 July, at least four of an hour or more on parts the agent socket depends on. Flux STT errors for about 2.5 hours on 7 July. Failed Voice Agent responses on unpinned Gemini models for about 1.5 hours on 21 July. STT degraded for about 3.5 hours on 4 August. Flux TTS errors on the global endpoint for about 4 hours on 25 September. Deepgram posts short incidents most vendors wouldn't, so the count is partly a sign of candour. Concurrency is published, 45 sockets on pay as you go and 60 on Growth. Over-limit gets a 429 with backoff advice and no Retry-After. Errors and warnings are typed events. Sessions close at 2 hours with a 5-minute warning, a failure mode announced in advance. Self-serve plans say Standard Uptime with no figure. Three, because the record is busy even with docs this clear. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/deepgram-voice-agent#rev_0210 https://www.anchorterminal.com/tools/deepgram-voice-agent#rev_0210 Thu, 01 Oct 2026 00:00:00 +0000 review Keys carry an owner, admin or member role, can expire on a date or after a duration, and can be tagged, and browsers get 30-second JWTs from `/v1/auth/grant` so the real key stays on the server. Member keys narrow what a stolen key does, but there's no read-only agent mode. The function-call hold waits for a confirmed user turn before irreversible tools run, and without it calls can fire on a speculative reply. Your own LLM and TTS keys travel in `endpoint.headers` of the Settings message, so Deepgram holds them in flight. The default worries me most. Audio and transcripts are kept for model improvement unless `mip_opt_out` is set. No prompt-injection guidance, no audit log of account actions, no security.txt (carried over from last week's check) and no bug bounty. SOC 2, HIPAA and PCI DSS are vendor-stated. Three, for good keys and a bad default. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/deepgram-voice-agent https://www.anchorterminal.com/tools/deepgram-voice-agent#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing One WebSocket that runs Deepgram STT (Flux or Nova-3), a managed or bring-your-own LLM and Deepgram or third-party TTS, with turn-taking, barge-in and function calling.