# Amazon Nova 2 Sonic vs Deepgram Voice Agent API (slim)

> Deepgram Voice Agent scores 72.2 (BB) to Amazon Nova 2 Sonic's 67.6 (B) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent.md (~5,400 tokens) · this version ~2,680 tokens · JSON https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent.json · canonical https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Deepgram Voice Agent API scores 72.2 (BB) on agent readiness against Amazon Nova 2 Sonic's 67.6 (B), and leads in 4 of 7 scored categories. Amazon Nova 2 Sonic leads on reliability and security & auth. Both do voice agents.

- Amazon Nova 2 Sonic: B 67.6, rank #314 of 1486 · https://www.anchorterminal.com/tools/amazon-nova-sonic.min.md
- Deepgram Voice Agent API: BB 72.2, rank #135 of 1486 · https://www.anchorterminal.com/tools/deepgram-voice-agent.min.md
- Amazon Nova 2 Sonic, good for Voice agents on AWS, call centres on Amazon Connect, teams that want IAM and in-account data handling. Ahead on Reliability, 95 against 75; Security & auth, 77 against 71.
- Deepgram Voice Agent API, good for Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM. Ahead on Schema & documentation, 90 against 75; Payments & pricing, 40 against 10; Maintenance & community, 85 against 50. Also Agent-ready, a grade of BB or better; A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.

| Category | Amazon Nova 2 Sonic | Deepgram Voice Agent API |
| --- | --- | --- |
| Reliability (16%) | 95 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 90 |
| Agent ergonomics (13%) | 64 | 67 |
| Security & auth (14%) | 77 | 71 |
| Payments & pricing (10%) | 10 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 50 | 85 |
| Transparency & trust (7%) | 79 | 78 |

| Fact (where they differ) | Amazon Nova 2 Sonic | Deepgram Voice Agent API |
| --- | --- | --- |
| Vendor | Amazon Web Services | Deepgram |
| Hosted endpoint | no (local only) | `https://agent.deepgram.com/v1/agent` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio, SSE (legacy) |
| Licence | none | MIT (SDKs) |
| Tools exposed | 0 | none |
| Last release | 2026-05-28 | 2026-10-28 |
| Terms last updated | 2026-10-01 | 2026-08-06 |
| Privacy policy last updated | 2026-05-18 | 2021-10-26 |
| Terms restrict automated access | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 468 stars, 1.1M npm/wk, 805k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Maintenance & community, Deepgram Voice Agent API +35: Amazon Nova 2 Sonic 50 (Read as a model. The newest dated change is the May 2026 refresh, completed on 28 May, 162 days before this check (10). No Sonic release note or document history entry in the 90 days from 8 August. The pre-alpha Python SDK shipped 0.9.0, 0.10.0, 0.11.0 and 0.12.0 in the window, counted half (10 of 20). Release notes, document history, re:Post and AWS Support (10 of 15). The JavaScript Bedrock runtime client is current at 3.1163.0, while the Python route is pre-alpha (10 of 15). The SDKs ship on AWS's release train; CI not read (10). Total 50.); 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.)
- Payments & pricing, Deepgram Voice Agent API +30: Amazon Nova 2 Sonic 10 (No x402, MPP or L402 (0). The Nova and Bedrock pricing pages carry a speech-to-speech table drawn by script, so the per-token prices weren't read and this line scores absent, which is our reader's limit and not the vendor's (0). New accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says most new customers need no payment method, read as half on the other AWS listings (10). A person signs up for an AWS account in a browser (0). Total 10.); Deepgram Voice Agent API 40 (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).)
- Reliability, Amazon Nova 2 Sonic +20: Amazon Nova 2 Sonic 95 (Hosted reading. AWS Health Dashboard with per-service, per-Region history (20). The dashboard history file (newest event 30 October 2026) lists no Bedrock event in the 90 days from 8 August, and the 3 September us-west-2 event names STS, Connect and IAM Identity Center, not Bedrock. The public dashboard records broad events only, so 25 of 30, as amazon-nova-embeddings was read. Quotas published, 20 concurrent requests per Region, not adjustable (15). The stream API lists `ThrottlingException` (429), `ServiceUnavailableException` (503), `ModelTimeoutException` (408) and `ModelStreamErrorException` (424), Bedrock's troubleshooting guide advises backoff with jitter, and the 8-minute connection limit comes with a session-continuation sample (15). Bedrock's SLA of 99.9 per cent a month per Region for model APIs, as read for amazon-nova-embeddings on 1 November (10). Generally available since 2 December 2025 (10). 20 + 25 + 15 + 15 + 10 + 10 = 95.); 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.)
- Schema & documentation, Deepgram Voice Agent API +15: Amazon Nova 2 Sonic 75 (The Bedrock service model types `InvokeModelWithBidirectionalStream`, but the Sonic events inside it (session, prompt, content, tool and usage events) are JSON payloads documented only in the guide, with no schema file (12 of 25). llms.txt and Markdown copies of the Nova 2 guide (10). Guides on the event lifecycle, barge-in, turn-taking, async tools and chat history say when and how to use each (16 of 20). Event fields are documented as JSON examples and tables, not typed schemas (10 of 15). Sample repositories in several languages and the API's exceptions with HTTP codes (12 of 15). Release notes and document history, with in-place model refreshes and a versioned model ID (15). Total 75.); 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).)
- Security & auth, Amazon Nova 2 Sonic +6: Amazon Nova 2 Sonic 77 (SigV4 with IAM roles and temporary credentials scoped per model ARN, as the Sonic quickstart signs (30). Tools run in the client, so side effects are the developer's to approve, and IAM can restrict which models a role invokes, with no approval step in the API (12 of 20). The model listens to callers and acts on tool results, and no prompt-injection guidance was found in the Sonic guide (5 of 15). CloudTrail logs Bedrock API calls, read as amazon-nova-embeddings was (12 of 15). VDP on HackerOne, Bedrock in SOC scope and a valid security.txt on aws.amazon.com, with no paid bounty, as on the other AWS listings (18 of 20). Total 77.); 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.)