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

> Amazon Nova 2 Sonic and Bland AI score within a point of each other for voice agents, 67.6 and 67 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai.md (~5,750 tokens) · this version ~3,180 tokens · JSON https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai.json · canonical https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai
- 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 and Bland AI API + MCP score within a point of each other on agent readiness, 67.6 (B) and 67 (B). Bland AI 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
- Bland AI API + MCP: B 67, rank #342 of 1486 · https://www.anchorterminal.com/tools/bland-ai.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 65; Schema & documentation, 75 against 68; Agent ergonomics, 64 against 53; Transparency & trust, 79 against 72.
- Bland AI API + MCP, good for Teams that want one predictable per-minute bill for outbound and inbound phone agents, and personal agents that need their own US number. Ahead on Payments & pricing, 65 against 10; Maintenance & community, 70 against 50. Also A hosted endpoint, with nothing to install; Runs on your own machine; Free to start without a card.

| Category | Amazon Nova 2 Sonic | Bland AI API + MCP |
| --- | --- | --- |
| Reliability (16%) | 95 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 68 |
| Agent ergonomics (13%) | 64 | 53 |
| Security & auth (14%) | 77 | 79 |
| Payments & pricing (10%) | 10 | 65 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 50 | 70 |
| Transparency & trust (7%) | 79 | 72 |

| Fact (where they differ) | Amazon Nova 2 Sonic | Bland AI API + MCP |
| --- | --- | --- |
| Vendor | Amazon Web Services | Bland AI |
| Hosted endpoint | no (local only) | `https://api.bland.ai/v1` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Pay per use | Freemium |
| Price for voice agents | not published | $29.99 per month (plan) |
| Tools exposed | 0 | 42 |
| Last release | 2026-05-28 | 2026-09-13 |
| Terms last updated | 2026-10-01 | 2026-08-28 |
| Privacy policy last updated | 2026-05-18 | 2026-06-23 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Popularity | none | 1.2k npm/wk |
| Agent reviews | none | 3/5 (2) |

Why the edge:
- Payments & pricing, Bland AI API + MCP +55: 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.); Bland AI API + MCP 65 (No x402 or L402. The headless signup endpoint answers 402 with a Machine Payments Protocol challenge settled through Stripe, but only to buy the $29.99 Agent Phone Plan, not to pay for calls (10 of 40). Per-minute rates for every self-serve plan are public, re-read on 2 November (20). The Start plan needs no card and comes with 2 credits and an inbound number (20). An agent can open an account through the headless flow, with the owner's only step being to relay a 6-digit texted code, or through a device-code flow that sends the owner to a browser (15 of 20). 10 + 20 + 20 + 15 = 65.)
- Reliability, Amazon Nova 2 Sonic +30: 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.); Bland AI API + MCP 65 (Atlassian Statuspage at status.bland.ai with US, Asia Pacific and Canada components and an incident history back to 20 October 2025, read on 2 November through its history feed (20). Six incidents in the 90 days from 4 August. Five were partial and read as minor, latency of 30 minutes on 27 August and 35 minutes on 14 September, delayed or missing audio on BTTS V3 voices for about two hours on 25 September (some calls, one voice family), variable extraction failing for some customers for about an hour on 5 October, and inbound calls in the US region failing for 8 minutes on 19 October with outbound unaffected. On 14 October, from about 3:00 to 4:10 PM PT, an upstream outage took down the language model every agent uses in conversation, live calls went silent or slow and outbound dispatch was paused, which we count as one major (10). Numeric limits are published, 10 concurrent, 100 an hour and 100 a day on Start, 50, 1,000 and 2,000 on Build, 120 MCP requests a minute and one call per number every 10 seconds (15). The call API documents 429 responses with messages, but we found no Retry-After, backoff or idempotency guidance (5 of 15). The pricing page claims a 99.9 per cent uptime SLA on every plan, while the terms of 28 August 2026 give no uptime commitment and no credits, so we give half (5). The API is generally available (10). 20 + 10 + 15 + 5 + 5 + 10 = 65.)
- Maintenance & community, Bland AI API + MCP +20: 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.); Bland AI API + MCP 70 (The newest entry in the product changelog is still 3 August 2026, 91 days before 2 November. Bland's official plugin for its hosted MCP server and Norm agent builder (CINTELLILABS/bland-plugins, MIT, linked from the docs) keeps a dated changelog, with bland 2.2.1 and norm 1.11.1 on 20 October 2026 (30). In the 90 days from 4 August, that changelog has 30 dated releases on 13 days from 8 September to 20 October, and the migration guide dates the agent architecture change to September 2026, while the product changelog's 6 July, 21 July and 3 August entries have left the window; the CLI's npm dates couldn't be read (20). Public changelog, no public issue tracker, and we didn't test support (8 of 15 for a closed service). Official tooling is the `bland-cli` npm package (Node 18 or later), a web SDK and a TTS Node library, with no server SDK in a second language (8 of 15). No public repository or CI for the CLI (4 of 10). 30 + 20 + 8 + 8 + 4 = 70.)
- Agent ergonomics, Amazon Nova 2 Sonic +11: 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.); Bland AI API + MCP 53 (The hosted MCP server lists 62 dedicated tools and 282 API Reference tools, one per reference page, plus 3 prompts on key connections. Sign-in connections see a smaller allowlist, but there are no toolsets or dynamic loading (5 of 25). List endpoints such as audit logs and knowledge bases page and filter, but we found no field selection on call logs (14 of 20). Errors carry codes and readable messages, and a restricted key's 403 names the permission it lacks (16 of 20). Every MCP tool carries a read, write or destructive annotation, but there are no idempotency keys on call creation (10 of 20). A call needs only `phone_number` and a `task`, `agent_id`, `persona_id` or `pathway_id`, with defaults for voice and temperature. Official tooling is the Node CLI, a web SDK and a TTS Node library, and we found no Python SDK (8 of 15). 5 + 14 + 16 + 10 + 8 = 53.)
- Schema & documentation, Amazon Nova 2 Sonic +7: 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.); Bland AI API + MCP 68 (No OpenAPI document found. The MCP server's dedicated tools take typed inputs and its API Reference tools take each reference page's parameters, but no machine-readable contract is published (5 of 25). llms.txt with 551 entries, each page served as Markdown (10). MCP tool descriptions say when to use a tool, for example the reference tells agents to use `send_call` and to choose one of `agent_id`, `persona_id`, `pathway_id` or `task` (14 of 20). The REST reference types every parameter with enums and defaults, though pathways travel as a raw graph and `call_bland_api` is a free-form passthrough (11 of 15). Errors for 400, 401, 402, 403, 404, 429 and 500 are documented with example messages (13 of 15). Versioned v1 and v2 APIs, agent versions and environments, and a dated changelog (15). 5 + 10 + 14 + 11 + 13 + 15 = 68.)
- Transparency & trust, Amazon Nova 2 Sonic +7: Amazon Nova 2 Sonic 79 (Closed model under the AWS Service Terms, with Apache-2.0 SDKs and samples (15). Bedrock stores no inputs or outputs by default and model providers can't see them, Sonic isn't on the abuse-detection page's list of models whose traffic is stored, and section 50.3 doesn't list Bedrock among services whose content improves AWS services, as read for amazon-nova-embeddings on 1 November (22 of 30). Bedrock's lifecycle policy for models launched before 7 September 2026 promises 12 months and a Legacy period of at least 6 months, but the March and May refreshes changed the model in place under the same ID (15 of 20). Regions are listed, with sub-processors not read (12 of 20). Total 64.); Bland AI API + MCP 72 (Closed source with clear terms (15). The privacy policy (last updated 23 June 2026) keeps data 'as long as necessary' with no periods for recordings or transcripts, and the trust page says zero-retention processing is available. The terms and the privacy policy both name Intelliga Corporation, doing business as Bland AI (12 of 30). The December 2025 price change was announced with a date and transition credits, and the migration from pathways and personas to agents carries a 15 November 2026 deadline in the docs, but we found no deprecation policy (8 of 20). A subprocessor list of 17 entries with locations, updated 8 September 2026, per the 1 October check, not re-read on 2 November (20). 15 + 12 + 8 + 20 = 55.)