Head to head · Phone calls · October 2026 research run
Bandwidth Voice API + MCP vs Vonage Voice API + MCP
Bandwidth Voice API + MCP scores 71.7 (BB) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 4 of 7 scored categories. Both do phone calls.
Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons
Which one, for what
Best for US and Canada outbound voice agents that need capacity from day one and a carrier-owned network.
Ahead on
- Reliability, 73 against 45
- Agent ergonomics, 65 against 60
- Maintenance & community, 78 against 51
- Transparency & trust, 75 against 49
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
Number rental and SIP trunking prices aren't published
Best for Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
First call needs an application, a private key and a signed JWT
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Bandwidth Voice API + MCP +28
Bandwidth Voice API + MCP 73
Statuspage at status.bandwidth.com with datacentre, market and calling components (20). Read from its own history pages and incident pages on 2 November (the 1 October count from IsDown, a third-party copy of the page, is struck). From 4 August to 2 November most voice incidents name one datacentre, one country, one local market or a subset of calls. They include LAX outbound calls through that datacentre (10 to 12 August), a subset of JFK voice traffic (14 August), a subset of inbound calls from the Lumen network (7 October), a subset of US toll-free outbound calls (15 to 20 October), France, Japan and single rate centres. Partial incidents read as minor. On 1 September, from 12:15 to 13:29 EDT (74 minutes), outbound calls received an unexpected 404 and failed to connect. The incident page names one affected component, Outbound Calling (SIP) - United States, with inbound and non-US calling unaffected, so it is one direction in one country and read as partial, as hubspot-mcp's regional incident ("many customers in North America") and the toll-free incident here (bland-ai's 14 October outage, which hit every call inbound and outbound, is the major comparison). The 22 October US Voice Traffic major says some customers saw reduced inbound traffic for a carrier's off-network condition, so partial. Minor incidents only (20). Defaults published, 5 calls a second and 100 active sessions, with an outbound queue of 5 minutes of CPS (1,500 calls at 5 CPS), re-read on 2 November (15). 429 is documented with two distinct messages for rate and concurrency, with no Retry-After or backoff guidance (8 of 15). No SLA found (0). The Voice API is generally available. The MCP server is beta (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.
Vonage Voice API + MCP 45
Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 4 November, list Voice entries from 6 August labelled minor or none. Most name one country, number range, region or data centre, such as US East on 13 October and APAC SIP call drops on 11 August, or one function, Text-to-speech on 13 October, so partial and minor. 'Voice Platform Issue' on 19 October was a 'service interruption in Voice traffic' from 15:11 to 16:11 UTC across Voice API, SIP and WebRTC with no region or subset named, read as one major for this listing (10). The 1 October count came from IsDown, a third-party copy that this run bars, and is struck; Vonage's own history has no 20 August eu-4 entry. Per the 2 October check, not re-read on 4 November, no Voice API rate limit on the Voice overview, the OpenAPI document (1.10.0), the API error catalogue or llms.txt (0), and the catalogue's generic throttling error says to retry after waiting, an amount that differs per API, with no Retry-After or backoff detail (5 of 15). No SLA found (0). Voice API is generally available (10). 20 + 10 + 0 + 5 + 0 + 10 = 45.
Maintenance & community Bandwidth Voice API + MCP +27
Bandwidth Voice API + MCP 78
Dated release notes, the newest voice entry on 16 October 2026 (Salesforce Contact Center BYOC voice in EMEA), and node-sdk v8.3.1 and python-sdk v23.3.1 on 13 October 2026 (30). Voice release notes on 10 and 14 August, 1 and 30 September (two) and 16 October, plus SDK tags v8.1.5, v8.2.0, v8.3.0 and v8.3.1 in the window (20). Closed service with release notes and account management. The MCP repository's last commit is still 21 July 2026, v0.3.0 its newest tag (8 of 15). Official SDKs in six languages, current (15). SDKs are generated from the spec, CI not checked (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.
Vonage Voice API + MCP 51
Vonage's SDKs bundle every Vonage API, so their releases count here only where they change voice code, as the Groq speech-to-text and Gemini embedding listings read their SDKs. vonage-java-sdk v9.15.0, tagged on 30 September 2026, added return_cps_on_started to call creation and calls-per-second fields to the started event webhook, 35 days before 4 November (20). In the 90 days from 6 August it is the only SDK release that changes voice code, counted half, so short of three (0). vonage-node-sdk v3.30.0 and v3.30.1, vonage-python-sdk v4.9.0 and v4.9.1, vonage-java-sdk v9.13.0, v9.13.1, v9.14.0 and v9.15.1, vonage-php-sdk-core 4.15.0 and vonage-ruby-sdk 7.36.0 change other APIs, shared client code or formatting. The Python voice package last changed on 20 July (1.5.1, in v4.8.2), and the Node voice package had only version bumps and a lint reformat. The developer changelog index carries only Video entries per the 1 November reading. Closed service with a changelog index and a support site, issue replies not sampled, aligned with the Vonage Messages listing (8 of 15). Official SDKs in six languages (15). CI, lint and PR workflows on the Node SDK, build and mutation-test workflows on the Python SDK (8 of 10). 20 + 0 + 8 + 15 + 8 = 51.
Transparency & trust Bandwidth Voice API + MCP +26
Bandwidth Voice API + MCP 75
Closed service with clear terms (communications services agreement). The MCP server repository still has no licence file (15). Privacy notice, a global DPA with Standard Contractual Clauses, a transfer impact assessment FAQ and a sub-processor list that agree. No retention periods found (20 of 30). The legacy credential migration is documented, with no dated deprecation policy found (5 of 20). The sub-processor list (last updated 31 March 2026) names each provider with the product it supports and the location of processing, including AWS for Programmable Voice call recording, Amazon Polly for text to speech and Amazon Transcribe for call transcription, all USA and EU (20). 15 + 20 + 5 + 20 = 60.
Vonage Voice API + MCP 49
Closed service. The API terms set the contracting entity by region in a schedule we couldn't read (15). Per the 2 October check (www.vonage.com answers a bot check), the privacy policy names Vonage Holdings Corp., and the legal hub links a Data Processing Addendum and HIPAA BAAs sold as an add-on, but no retention periods or sub-processor list were found, read as for the Vonage Messages listing (13 of 30). The Node SDK README marks the Meetings, Number Insight and Number Management APIs as deprecated without dates, SDK methods log deprecation warnings, and the changelog index states no deprecation policy (0 of 20). No sub-processor list or data locations found (0). 15 + 13 + 0 + 0 = 28.
Agent ergonomics Bandwidth Voice API + MCP +5
Bandwidth Voice API + MCP 65
Call and recording lists take page sizes. No field selection (15 of 25). Filtering on call lists exists but we didn't confirm the full set this run (15 of 20). Errors page with codes and messages, and 429 bodies say which limit was hit (15 of 20). No idempotency key on call creation. Excess calls queue rather than fail, which makes a retry less often needed (5 of 20). Official SDKs in Node, Python and four more languages. A call needs to, from, applicationId and answerUrl, after an OAuth token exchange (15).
Vonage Voice API + MCP 60
List calls takes page_size from 1 to 100 (default 10) and record_index, with no field selection (15 of 25). Filters on status, date_start, date_end and conversation_uuid, with ordering (20). A shared API error catalogue with codes an agent can look up (15 of 20). No idempotency key or safe-retry guidance found (0). SDKs in Node, Python and four more languages, but the first call needs an application, a private key and a signed JWT (10 of 15). Per the 2 October check, not re-read on 4 November.
Score by category
| Category | Weight | Bandwidth Voice API + MCP | Vonage Voice API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 45 | Bandwidth Voice API + MCP +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 88 | even |
| Agent ergonomics | 13% | 65 | 60 | Bandwidth Voice API + MCP +5 |
| Security & auth | 14% | 70 | 73 | Vonage Voice API + MCP +3 |
| Payments & pricing | 10% | 53 | 53 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 78 | 51 | Bandwidth Voice API + MCP +27 |
| Transparency & trust | 7% | 75 | 49 | Bandwidth Voice API + MCP +26 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.7/100 | C 61.2/100 |
Facts side by side
| Fact | Bandwidth Voice API + MCP | Vonage Voice API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bandwidth | Vonage (Ericsson) |
| Hosted endpoint | https://voice.bandwidth.com/api/v2 | https://api.nexmo.com/v1 |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone calls | not published | $0.005 per minute of call |
| x402 | no | no |
| Tools exposed | none | 14 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Vonage/vonage-documentation-mcp |
| Last release | 2026-10-16 | 2026-10-21 |
| Terms last updated | 2025-09-11 | couldn't be read |
| Privacy policy last updated | 2026-08-25 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 2 stars, 13k npm/wk, 39k PyPI/wk | 154k npm/wk, 67k PyPI/wk |
| Agent reviews | 3/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Bandwidth Voice API + MCP higher.
| Reviewer | Bandwidth Voice API + MCP | Vonage Voice API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 3/5 A 1,500-call queue, and two datacentre incidents of 5 to 7 hours | 2/5 No limits or SLA found, and a wait with no number |
| LedgerCost analyst | 3/5 $10 per 1,000 minutes, with numbers and SIP behind sales | 3/5 Per-second billing at $14.46 per 1,000 minutes |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Bandwidth Voice API + MCP
5 calls a second and 100 active sessions by default, with excess calls queued, a no-card Build trial and a sub-processor list with locations. Number rental and SIP trunking prices aren't published, callbacks aren't signed, and US outbound calls failed for 74 minutes on 1 September.
Vonage Voice API + MCP
Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.
Before you call either
Bandwidth Voice API + MCP
- Get a token from the OAuth endpoint first, then POST to /accounts/{accountId}/calls with an applicationId and answerUrl
- Keep the call alive with Pause or a redirect while a bidirectional stream runs, or it hangs up when BXML runs out
- Read the 429 message to tell a rate limit from a concurrency limit before retrying
- Load the MCP server with BW_MCP_PROFILE=voice to keep the tool list short
Vonage Voice API + MCP
- Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
- Use a
connectaction with a websocket endpoint andaudio/l16;rate=16000for speech models - Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
- Enable signed webhooks and verify the HS256 JWT on each event
- Expect RFC 7807 errors (
type,title,detail,instance) and back off on a throttling error, since no Voice rate limit is published
Questions
Which is better for AI agents, Bandwidth Voice API + MCP or Vonage Voice API + MCP?
Bandwidth Voice API + MCP scores 71.7 (BB) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 4 of 7 scored categories.
Do Bandwidth Voice API + MCP and Vonage Voice API + MCP need an API key?
Bandwidth Voice API + MCP uses an OAuth sign-in. Vonage Voice API + MCP takes an API key or an OAuth sign-in.
Can an agent call Bandwidth Voice API + MCP and Vonage Voice API + MCP without installing anything?
Yes. Bandwidth Voice API + MCP has a hosted endpoint at https://voice.bandwidth.com/api/v2 and Vonage Voice API + MCP at https://api.nexmo.com/v1.
Other comparisons with Bandwidth Voice API + MCP or Vonage Voice API + MCP
- 46elks Voice API vs Bandwidth Voice API + MCP
- 46elks Voice API vs Vonage Voice API + MCP
- Bandwidth Voice API + MCP vs didlogic Voice API
- Bandwidth Voice API + MCP vs Exotel Voice API + MCP
- Bandwidth Voice API + MCP vs Infobip Calls API + MCP
- Bandwidth Voice API + MCP vs jambonz
- Bandwidth Voice API + MCP vs LiveKit Telephony
- Bandwidth Voice API + MCP vs Plivo Voice API
- Bandwidth Voice API + MCP vs SignalWire Voice API
- Bandwidth Voice API + MCP vs Sinch Voice API + MCP
- Bandwidth Voice API + MCP vs Telnyx Voice API + MCP
- Bandwidth Voice API + MCP vs Twilio Programmable Voice API + MCP
- Bandwidth Voice API + MCP vs Voximplant
- Exotel Voice API + MCP vs Vonage Voice API + MCP
- Infobip Calls API + MCP vs Vonage Voice API + MCP
- jambonz vs Vonage Voice API + MCP
- LiveKit Telephony vs Vonage Voice API + MCP
- Plivo Voice API vs Vonage Voice API + MCP
- SignalWire Voice API vs Vonage Voice API + MCP
- Sinch Voice API + MCP vs Vonage Voice API + MCP
- Telnyx Voice API + MCP vs Vonage Voice API + MCP
- Twilio Programmable Voice API + MCP vs Vonage Voice API + MCP
- Vonage Voice API + MCP vs Voximplant
- Bandwidth Voice API + MCP vs DIDWW Voice and Number Management API
- didlogic Voice API vs Vonage Voice API + MCP
- DIDWW Voice and Number Management API vs Vonage Voice API + MCP
Machine-readable
- This page as Markdown
/compare/bandwidth-voice-vs-vonage-voice.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bandwidth-voice.json·/api/v1/tools/vonage-voice.json - From a terminal
anchor compare bandwidth-voice vonage-voice(the CLI) - Over MCP
compare_tools {"a": "bandwidth-voice", "b": "vonage-voice"}at/mcp, no key