# Amazon Nova 2 Sonic vs Bolna API + MCP (slim)

> Amazon Nova 2 Sonic scores 67.6 (B) to Bolna's 44.7 (E) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bolna.md (~5,600 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bolna.json · canonical https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bolna
- 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)

Amazon Nova 2 Sonic scores 67.6 (B) on agent readiness against Bolna API + MCP's 44.7 (E), and leads in 5 of 7 scored categories. Bolna API + MCP leads on payments & pricing and maintenance & community. 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
- Bolna API + MCP: E 44.7, rank #1193 of 1486 · https://www.anchorterminal.com/tools/bolna.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 40; Schema & documentation, 75 against 63; Agent ergonomics, 64 against 52; Security & auth, 77 against 44; Transparency & trust, 79 against 67. Also No incidents deducted, where Bolna API + MCP loses 6 points for them.
- Bolna API + MCP, good for Indian-language phone agents and campaigns that need local carriers and India data residency, and for teams that want to self-host the MIT core. Ahead on Payments & pricing, 30 against 10; Maintenance & community, 76 against 50. Also A hosted endpoint, with nothing to install; Open source.

| Category | Amazon Nova 2 Sonic | Bolna API + MCP |
| --- | --- | --- |
| Reliability (16%) | 95 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 63 |
| Agent ergonomics (13%) | 64 | 52 |
| Security & auth (14%) | 77 | 44 |
| Payments & pricing (10%) | 10 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 50 | 76 |
| Transparency & trust (7%) | 79 | 67 |

| Fact (where they differ) | Amazon Nova 2 Sonic | Bolna API + MCP |
| --- | --- | --- |
| Vendor | Amazon Web Services | Bolna |
| Hosted endpoint | no (local only) | `https://api.bolna.ai` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Licence | none | MIT |
| Tools exposed | 0 | 117 |
| Last release | 2026-05-28 | 2026-11-04 |
| Terms last updated | 2026-10-01 | 2026-08-13 |
| Privacy policy last updated | 2026-05-18 | 2025-03-28 |
| 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 |
| Popularity | none | 779 stars, 579 npm/wk, 2.6k PyPI/wk |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Reliability, Amazon Nova 2 Sonic +55: 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.); Bolna API + MCP 40 (A status page sits at status.bolna.ai, linked from the site footer, but its robots.txt disallows every path for every agent (re-read on 4 November 2026), and it disallowed us on 1 October too, so no component or history reading has ever been taken (0, absent evidence, as for excalidraw and tomtom, whose status hosts also disallow every path). No readable incident history (5). Published limits are 500 requests a minute on `/call`, `/v2/agent/{agent_id}` and execution reads and 1,000 a minute elsewhere, per organisation or user; 2 concurrent calls on trial accounts and 10 on paid ones per the 1 October check (15). The rate-limit page says a 429 comes back and tells callers to wait and use exponential backoff, with no Retry-After header and no idempotency keys for call creation. Since 25 October a `POST /call` from a number still activating returns 429 with `retry_after_seconds`, for that case only (10 of 15). No SLA found for any tier (0). The API is generally available (10). 0+5+15+10+0+10 = 40.)
- Security & auth, Amazon Nova 2 Sonic +33: 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.); Bolna API + MCP 44 (Bearer keys shown once and stored hashed, revocable from the dashboard, with separate `sa-` keys for enterprise sub-accounts (25). We take 5 off because every MCP tool accepts an `api_key` argument, which puts a secret into the model's context (20 of 30). Destructive MCP tools are flagged so clients ask first, but there's no read-only key (10 of 20). Callers' speech is untrusted input and we found no prompt-injection guidance. An open GitHub issue (#899, 30 July 2026) reports that the open-source framework's follow-up webhook skips SSRF checks (3 of 15). Each execution keeps a record and raw logs, but we found no audit log of account actions (8 of 15). No security.txt, no bug bounty, and no SOC 2 or ISO 27001 claim. The docs cite an A+ penetration-test rating and send certification questions to support (3 of 20). Webhooks and tool calls carry no signature, only three fixed source IPs. On 4 November the security page is unchanged, www.bolna.ai serves no security.txt (404), and osv.dev lists no advisory for `bolna`. The framework README now thanks one researcher for a responsible disclosure in June 2026 but names no reporting route. 20+10+3+8+3 = 44.)
- Maintenance & community, Bolna API + MCP +26: 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.); Bolna API + MCP 76 (Framework release 0.11.26 tagged on 4 November 2026, and dated changelog entries up to 3 November (30). 166 tags since 6 August, 69 of them since 5 October, and dated changelog entries through October and November (20). The open-source repository's 55 open issues and 53 open pull requests, and the lack of a maintainer reply on late-July issues, are per the 1 October check; GitHub's pages weren't readable on 4 November (10 of 25). Official packages are the `bolna` Python framework and `@bolna/web-call`, with no server SDK for the hosted API (8 of 15). Python 3.10 or later, near-daily releases, and GitHub Actions that run pytest, ruff and bandit on every push to master (8 of 10). 30+20+10+8+8 = 76.)
- Payments & pricing, Bolna API + MCP +20: 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.); Bolna API + MCP 30 (No x402, MPP or L402 (0 of 40). The $0.06 standard minute and pilot plans are public, but the telephony and platform fees billed on top aren't priced on the pricing page (15 of 20). $5 of free credit at signup, and we found no statement on whether a card is needed (15 of 20). Access starts with a human signup in the dashboard (0). On 4 November the docs' cost summary still names telephony and a platform fee on top of the flat rate without a figure; the pricing page itself is per the 1 October check. 0+15+15+0 = 30.)
- Schema & documentation, Amazon Nova 2 Sonic +12: 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.); Bolna API + MCP 63 (llms.txt links an OpenAPI file at `/docs/api-reference/openapi.yml`, but the link returned 404 on 2026-10-01 and again on 2026-11-04. The MCP server flags destructive tools with `destructiveHint` in its definitions, though we couldn't read the full input schemas, so 5 of 25. llms.txt plus Markdown copies of every page (10). Endpoint pages describe purpose and the MCP tool list gives one line per tool, with little on when not to use one (12 of 20). Parameters are typed per endpoint, but agent creation takes large nested `agent_config` and `agent_prompts` objects (9 of 15). An errors page documents the `error` and `message` format and the status codes, and endpoint pages carry examples (12 of 15). v2 endpoints, a dated changelog and retirement notices (15).)
- Agent ergonomics, Amazon Nova 2 Sonic +12: 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.); Bolna API + MCP 52 (The hosted MCP server loads 117 tools (84 on 1 October), grouped by area but with no way to load only some. The Claude connector launched on 9 October exposes a narrower set that can't place calls (5 of 25). Execution and batch lists page and filter (14 of 20). Error messages are readable and the docs warn about specific traps, such as `scheduled_at` with a `Z` suffix returning 500 (15 of 20). 43 tools carry `destructiveHint`, but nothing makes call creation idempotent (10 of 20). A call needs only `agent_id` and `recipient_phone_number`. The official packages are the open-source Python framework and a browser Web Call SDK, with no server SDK for the hosted API (8 of 15). 5+14+15+10+8 = 52.)