# Amazon Nova 2 Sonic vs LiveKit Agents (slim)

> LiveKit Agents scores 72.7 (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-livekit-agents.md (~6,400 tokens) · this version ~3,680 tokens · JSON https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-livekit-agents.json · canonical https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-livekit-agents
- 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)

LiveKit Agents scores 72.7 (BB) on agent readiness against Amazon Nova 2 Sonic's 67.6 (B), and leads in 5 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
- LiveKit Agents: BB 72.7, rank #119 of 1486 · https://www.anchorterminal.com/tools/livekit-agents.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 67; Security & auth, 77 against 62.
- LiveKit Agents, good for Teams writing their own voice agents in Python or Node.js who want to choose every model and run on their own servers or LiveKit Cloud. Ahead on Schema & documentation, 81 against 75; Agent ergonomics, 80 against 64; Payments & pricing, 60 against 10; Maintenance & community, 87 against 50. Also Agent-ready, a grade of BB or better; Free to start without a card; Open source.

| Category | Amazon Nova 2 Sonic | LiveKit Agents |
| --- | --- | --- |
| Reliability (16%) | 95 | 67 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 81 |
| Agent ergonomics (13%) | 64 | 80 |
| Security & auth (14%) | 77 | 62 |
| Payments & pricing (10%) | 10 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 50 | 87 |
| Transparency & trust (7%) | 79 | 82 |

| Fact (where they differ) | Amazon Nova 2 Sonic | LiveKit Agents |
| --- | --- | --- |
| Kind | HTTP API | Agent framework |
| Vendor | Amazon Web Services | LiveKit Incorporated |
| Transports | HTTP |  |
| Pricing | Pay per use | Free |
| Price for voice agents | not published | $0.005 per minute of audio |
| Licence | none | Apache-2.0 for the framework and plugins. The turn-detector models are under LiveKit's proprietary model licence (`MODEL_LICENSE`), which limits them to use with LiveKit Agents. LiveKit Cloud and LiveKit Inference are closed services under LiveKit's terms |
| Tools exposed | 0 | none |
| Last release | 2026-05-28 | 2026-10-28 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 820k npm/wk, 1.1M PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Payments & pricing, LiveKit Agents +50: 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.); LiveKit Agents 60 (No x402, MPP or L402 (0 of 40). Read with the rule for open-source software that has a paid hosted option. LiveKit Cloud publishes per-minute prices for agent sessions and recordings and per-unit prices for every LiveKit Inference model without a login (20). The Apache-2.0 packages install with no card, and LiveKit Cloud's Build plan is $0 with no card (20). The framework and a LiveKit server can both run self-hosted with no account or sign-up (20).)
- Maintenance & community, LiveKit Agents +37: 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.); LiveKit Agents 87 (`livekit-agents` 1.8.10 tagged on 28 October 2026, after 1.8.9 on 23 October (30). 18 tagged releases in the 90 days to 1 November, from 1.6.8 on 3 August to 1.8.10, counted from the repository's tags since PyPI didn't answer from our shell on 1 November, and `@livekit/agents` 1.9.4 (24 October) and 1.9.5 (28 October) in livekit/agents-js (20). Issue and pull request reply times weren't read, because GitHub's pages answer 403, and the earlier figures, taken from a third-party copy of GitHub data, are struck. In the clone, 147 of the 200 newest commits (11 to 31 October) came from about 80 authors with addresses outside livekit.io, bots aside, and every one of the 200 landed as a numbered pull request. CODEOWNERS sends every change to the agent-devs team, a workflow requests that team's review on pull requests from the repository's own branches, and the issue form points questions to LiveKit's community forum, with a Slack linked from the README (15 of 25). Python 1.8.10 and Node.js 1.9.5 were both tagged on 28 October (15). Renovate, a uv lockfile that holds new dependencies back seven days, security bumps of aiohttp (22 October) and nltk (27 October), pinned actions and CI on every push, with the pass state unconfirmed (7 of 10). 30 + 20 + 15 + 15 + 7 = 87.)
- Reliability, Amazon Nova 2 Sonic +28: 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.); LiveKit Agents 67 (Graded as a framework with the local-software lines, since LiveKit Cloud is optional and not graded. Official packages on PyPI (Python 3.10 to 3.14 declared) and npm (Node.js 20 or later per the docs) (20). Public workflows run on every push to main and on pull requests. Unit tests on Linux with Python 3.12 over 310 test files on 1 November, ruff, and mypy on Python 3.10 and 3.13, with a small blockguard suite on Linux, macOS and Windows. GitHub's pages and API weren't readable from our session, so a passing main is not confirmed (15 of 25). Open issues and reply times weren't read, because GitHub's pages answer 403, and the earlier issue figures, taken from a third-party copy of GitHub data, are struck. In a clone of main, the 200 newest commits run from 11 to 31 October 2026 and 104 of them are fixes, among them an Inference STT socket that hung when silently dropped (#8023) and an avatar plugin's error handler that crashed (#7498). None names the issue it closes and there is no changelog, so whether reported crashes and regressions get handled can't be seen (10 of 25). No CHANGELOG file. Release notes are on GitHub, which we couldn't read, and the repository's release-notes script asks for Breaking changes and Security sections. Migration guides exist for 0.x to 1.0, AGENTS.md makes patch bumps the default, and 2.0.0b1 was tagged on 12 October and the docs' migration guides still stop at Python 0.x to 1.0 and Node.js 1.x to 1.5 on 1 November (7 of 15). 1.8.10, stable since 1.0 (15).)
- Agent ergonomics, LiveKit Agents +16: Amazon Nova 2 Sonic 64 (Scored as an API. Responses carry transcripts of both sides and usage events, chat history is capped at 200 KB and can be injected once per session (15 of 25). Output controls are voice, turn-taking sensitivity and text or audio input (12 of 20). Typed exceptions with HTTP codes, while errors inside the event stream are less documented (15 of 20). Asynchronous tool calls let the model keep talking, and AWS samples show how to resume after the 8-minute limit, with nothing on repeating tool side effects after a reconnect (12 of 20). A session needs a sequence of start events before audio. The JavaScript SDK is current, but the Python SDK the quickstart uses is pre-alpha and needs Python 3.12 (10 of 15). Total 64.); LiveKit Agents 80 (Framework reading. An MCP server is about ten lines with `mcp.MCPToolset`, with `allowed_tools`, `filter_tools()` and a `tool_result_resolver` to trim results before they reach the model, but Python only (20 of 25). Tools can be added, removed or replaced per agent and per state, flags such as `IGNORE_ON_ENTER` hide a tool at the greeting, and handoffs swap the active toolset (16 of 20). `ToolError` returns a message the model can act on, invalid arguments come back as a `ToolError` naming the tool, and by default a session closes only after more than three unrecoverable STT, LLM or TTS errors of one kind (17 of 20). Interrupted tools finish in the background and keep their result in history, `disallow_interruptions()` protects tools that write, and `on_duplicate` can reject, replace or confirm a second call. Duplicates are matched by tool name only, and there are no idempotency keys (14 of 20). `AgentSession` supplies VAD and a turn detector by default and LiveKit Inference takes model strings with one key, in Python and Node.js, but every agent needs a LiveKit server and three environment variables (13 of 15).)
- Security & auth, Amazon Nova 2 Sonic +15: 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.); LiveKit Agents 62 (Framework reading. Agents authenticate to a LiveKit server with an API key and secret that sign JWT access tokens with room grants and a lifetime. No analytics calls were found in the source. Uploads to LiveKit Cloud happen only when the agent connects to LiveKit Cloud media servers and the project enables Agent Observability, which the terms call a capability the customer elects to enable. `record` then defaults to the project setting, and since 23 October (1.8.9) the recording header also carries a session summary without chat history or events, with `record=False` or per-category opt-outs, 30-day retention and PII redaction that is off by default. The default turn detector streams user audio to LiveKit Inference when deployed to LiveKit Cloud or in `dev` mode with credentials, which the docs state (20 of 30). No built-in approval step or read-only mode. `disallow_interruptions()`, `on_duplicate="confirm"`, MCP `allowed_tools`, prebuilt tasks with `require_confirmation` and the docs' advice to gate critical actions in code. Hosted agents run in sandboxed per-instance environments per the security page (10 of 20). Callers' speech and MCP results reach the model, and a search of llms-full.txt found no prompt-injection guidance (3 of 15). OpenTelemetry traces and metrics per session, session reports, and Agent Insights on LiveKit Cloud (14 of 15). security.txt with a contact and PGP key but no Expires field, a disclosure policy with safe harbour and a hall of fame, a SOC 2 Type II report for LiveKit Cloud under NDA, and no OSV advisories for livekit-agents or @livekit/agents on 1 November. No SECURITY.md in the repository and no paid bug bounty found. CI pins its actions by commit (15 of 20).)
- Schema & documentation, LiveKit Agents +6: 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.); LiveKit Agents 81 (Library reading. A typed Python package (`py.typed`, mypy in CI) with a Python and Node.js API reference on docs.livekit.io. The reference llms.txt link to the Python reference's Markdown still returns 404 on 1 November (22 of 25). llms.txt with section indexes, `.md` on every page, llms-full.txt and a docs MCP server (10). Pages say when to use a realtime model or a pipeline, when to choose `v1` or `v1-mini`, when to disallow interruptions and how to gate critical actions, and mark MCP as Python only (16 of 20). Function tools take their schema from typed signatures and docstrings, raw JSON Schema is accepted, and argument validation failures go back to the model as `ToolError` (13 of 15). 15 example folders in the repository after provider-specific examples were removed on 27 October, 39 recipes, and an events and error-handling reference (13 of 15). No changelog in the repository or docs, release notes only on GitHub, and the quickstart's `agent.py` still ends with `agents.cli.run_app(server)`, which the framework marks as deprecated, still so on 1 November (7 of 15).)