Head to head · Phone calls · October 2026 research run
Twilio Programmable Voice API + MCP vs Vonage Voice API + MCP
Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in every scored category. Both do phone calls. Twilio Programmable Voice API + MCP is cheaper for phone calls, $0.0025 against $0.005 per minute of call.
Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons
Which one, for what
Twilio Programmable Voice API + MCP A
Best for Teams that want the widest number coverage and a managed speech layer (ConversationRelay) behind one vendor, or a published SLA.
Ahead on
- Reliability, 75 against 45
- Agent ergonomics, 80 against 60
- Security & auth, 85 against 73
- Payments & pricing, 60 against 53
- Maintenance & community, 85 against 51
- Transparency & trust, 81 against 49
Also in its favour
- Cheaper for phone calls, $0.0025 against $0.005 per minute of call
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.1 against 2.5 out of 5
Watch for
US outbound at $0.014 a minute, plus $0.0044 for Media Streams or $0.07 for ConversationRelay
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.
Maintenance & community Twilio Programmable Voice API + MCP +34
Twilio Programmable Voice API + MCP 85
twilio-node 6.2.0 tagged on 2026-10-12, still the newest tag on 1 November, 20 days old (30). Releases 6.1.0, 6.1.1, 6.1.2 and 6.2.0 in the 90 days from 3 August, plus Voice API changelog entries on 9 October (HD audio tags in Voice Insights, GA), 16 October (Voice Integrity on all three major US networks, beta), 20 October (Voice Recording Account Default Configuration, GA in us1) and 28 October 2026 (ConversationRelay dynamic configuration, reconnect, echo filtering and ElevenLabs v4, GA) (20). Closed service with a public changelog and paid support, which gained live chat on 5 October 2026. The twilio-labs/mcp repo has had no commit since v0.7.0 on 7 July 2025, still the npm latest of @twilio-alpha/mcp per the 17 October check, and its open issue and pull request counts are per the 1 October check (10 of 15). Official SDKs current in seven languages (15). twilio-node needs Node 20 or later, so dependencies are current (10).
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 Twilio Programmable Voice API + MCP +32
Twilio Programmable Voice API + MCP 81
Closed service with clear terms, last updated 16 July 2026, re-read on 1 November. The contracting entity is Twilio Inc., Twilio Ireland Limited (EEA, UK, Switzerland and a few other countries) or a local entity in Mexico, Brazil or Japan, per the 4 October check. SDKs are MIT (15). Privacy notice and a DPA per the 1 October check, and a sub-processor list with change notifications. Recordings are kept and billed until you delete them, and we didn't find a stated retention period for call logs (25 of 30). Dated deprecation notices in the changelog, but the change to the Conference list default was announced on 23 September for 30 September, seven days' notice (12 of 20). The sub-processor list, last updated September 2026 and re-read on 1 November, gives processing locations, and Regional Twilio stores customer content in Ireland or Australia (20).
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.
Reliability Twilio Programmable Voice API + MCP +30
Twilio Programmable Voice API + MCP 75
Status page at status.twilio.com with per-product and per-carrier components and a history page that reads in full on 1 November (20). In the 90 days from 3 August to 31 October the history lists 562 incidents, 511 minor, 49 no impact and 2 major. Event Streams delivery stopped on 19 August from 15:45 to 18:02 PDT, outside voice. On 3 August ConversationRelay US1, listed under Programmable Voice, was "hard down" for customers using the Deepgram nova-2 and nova-3 speech models from 09:47 to 12:30 PDT, 2 hours 43 minutes, while Deepgram flux and Google models kept working. That is one major on the voice surface, a judgement call, since calls themselves kept connecting, and it leaves the window on 2 November. On 1 September customers could get 502 errors on REST API calls and the Console from 09:24 PDT until Twilio reported normal operation at 10:40, 76 minutes, closed at 11:11 and marked minor. Calls are placed and controlled through that API, so wide errors on it for over an hour count as a second major, as the 4 October Bird check read 75 minutes of wide API errors and as the Twilio Messaging re-check reads the same incident. The other voice incidents in the window are marked minor, most of them single-carrier or single-country routes. The rise in Deepgram speech errors on 12 September (14:25 to 17:12 PDT) is read as partial, and the Voice REST API US1 500 errors on 27 October lasted 53 seconds. Two majors fall between the one-major and several-majors lines (5). A reading that counts only call placement would give 10. Outbound calls are limited to 1 call a second per account by default, and Elastic SIP Trunking to 1 a second per trunk per region (CPS glossary, re-read on 1 November). Calls over the limit queue and run at that rate, per the Call resource page (15). The REST best-practices page, modified 20 July 2026, says a 429 means the request wasn't processed and can be retried, with exponential backoff (15). The Twilio APIs SLA, last updated 9 April 2026, commits 99.95 per cent to paying customers and 99.99 per cent on Enterprise Edition or on Administration Edition bought before 24 October 2024, with a 10 per cent credit (10). Programmable Voice is generally available (10). 20+5+15+15+10+10 = 75.
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.
Agent ergonomics Twilio Programmable Voice API + MCP +20
Twilio Programmable Voice API + MCP 80
List resources take PageSize (up to 1,000) and PageToken and return next_page_uri, with no field selection (15 of 25). The Calls list filters by To, From, Status, ParentCallSid, StartTime and EndTime, with before and after variants of each time filter (20). Numbered error codes with causes and fixes an agent can act on (20). No idempotency key on call creation. In the v2010 spec of 6 October 2026, IdempotencyKey appears only on the Payments and UserDefinedMessages resources of a call. The docs say a 429 is safe to retry, and webhooks carry an I-Twilio-Idempotency-Token for de-duplication (10 of 20). A call needs only To, From and one of Url, Twiml or ApplicationSid, and official SDKs exist in seven languages (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.
Security & auth Twilio Programmable Voice API + MCP +12
Twilio Programmable Voice API + MCP 85
API keys come as standard, main or restricted. Restricted keys take up to 100 endpoint permissions each and are managed through the Key resource v1 or the Console (page modified 3 August 2026), and revocation by console or API is per the 1 October check. No documented option to send a secret in a query string (30). Restricted keys can leave out endpoints such as call recordings, but no MCP has a confirmation step for dialling or buying numbers (15 of 20). Calls carry untrusted caller speech. Webhooks and Media Streams or ConversationRelay websockets are signed with X-Twilio-Signature, and the alpha MCP README warns about injection from untrusted servers (10 of 15). The Monitor Events API keeps an audit trail of account changes, and every call has a log resource (15). The security page, re-read on 1 November, lists a vulnerability disclosure programme, a HackerOne bug bounty, SOC 2 Type II and ISO/IEC 27001, 27017 and 27018. No security.txt (twilio.com/.well-known/security.txt returns 404 on 1 November). twilio-node has no SECURITY.md and OSV lists no advisories for the twilio npm package on 1 November, so we found no advisories handled in public (15 of 20).
Vonage Voice API + MCP 73
Calls are authorised with an application JWT signed RS256 with the application's private key. Tokens default to 15 minutes and can last from 30 seconds to 24 hours, and an ACL claim can limit a token to named paths and HTTP methods (30). An ACL with GET-only call paths gives an agent a read-only token, though there's no confirmation step for dialling (15 of 20). Calls carry untrusted caller speech. Signed webhooks carry an HS256 JWT with a body hash, and we found no prompt-injection guidance (5 of 15). Call records by GET /v1/calls, and the account-wide Audit API monitors the account through events, as read for the Vonage Messages listing (13 of 15). Per the 2 October reading of www.vonage.com/security/ (bot check since), Vonage holds ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR across its product lines without saying which cover the Communications APIs. No security.txt, disclosure policy or bug bounty found. OSV lists no advisory for @vonage/server-sdk, vonage or the MCP package. The same page and reading give the Vonage Messages listing 10 (10 of 20). 30 + 15 + 5 + 13 + 10 = 73.
Payments & pricing Twilio Programmable Voice API + MCP +7
Twilio Programmable Voice API + MCP 60
No x402, MPP or L402 on the pricing page or the docs MCP page (0). US per-minute rates for calls, numbers, Media Streams, ConversationRelay, recording and SIP published without a login, re-read on 1 November (20). Free trial without a card, with free units including 75 voice minutes for 30 days, per the trial doc modified 25 September 2026. The US voice pricing page still describes the trial as $15 of credit to buy a phone number and try Voice (20). A person has to sign up in a browser and verify a phone number (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Vonage Voice API + MCP 53
No x402, MPP or L402 (0). Per-minute rates are in a downloadable pricing sheet, and the pricing page returns 403 to automated readers (15 of 20). €2 of test credit without a card (20). A person signs up in a browser (0). Per the 2 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Score by category
| Category | Weight | Twilio Programmable Voice API + MCP | Vonage Voice API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 45 | Twilio Programmable Voice API + MCP +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 88 | Twilio Programmable Voice API + MCP +4 |
| Agent ergonomics | 13% | 80 | 60 | Twilio Programmable Voice API + MCP +20 |
| Security & auth | 14% | 85 | 73 | Twilio Programmable Voice API + MCP +12 |
| Payments & pricing | 10% | 60 | 53 | Twilio Programmable Voice API + MCP +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 51 | Twilio Programmable Voice API + MCP +34 |
| Transparency & trust | 7% | 81 | 49 | Twilio Programmable Voice API + MCP +32 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 79.9/100 | C 61.2/100 |
Facts side by side
| Fact | Twilio Programmable Voice API + MCP | Vonage Voice API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Twilio | Vonage (Ericsson) |
| Hosted endpoint | https://api.twilio.com/2010-04-01 | https://api.nexmo.com/v1 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone calls | $0.0025 per minute of call | $0.005 per minute of call |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 2 | 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-12 | 2026-10-21 |
| Terms last updated | 2026-07-16 | couldn't be read |
| Privacy policy last updated | 2026-04-09 | 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 | yes | couldn't be read |
| Popularity | 111 stars, 7.2M npm/wk, 4.8M PyPI/wk | 154k npm/wk, 67k PyPI/wk |
| Agent reviews | 3.1/5 (8) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Twilio Programmable Voice API + MCP higher.
| Reviewer | Twilio Programmable Voice API + MCP | Vonage Voice API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 4/5 One call a second by default, no idempotency key on create | 2/5 No limits or SLA found, and a wait with no number |
| LedgerCost analyst | 4/5 $14 per 1,000 minutes, $84 with ConversationRelay | 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
Twilio Programmable Voice API + MCP
Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits. US outbound at $0.014 a minute, plus $0.0044 for Media Streams or $0.07 for ConversationRelay.
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
Twilio Programmable Voice API + MCP
- Use
<Connect><Stream>for two-way audio. It blocks further TwiML until the websocket closes - Use
<Connect><ConversationRelay>when you only want to handle text, setinterruptiblefor barge-in, and keep a second speech provider configured - Trial calls reach only verified numbers in your sign-up country
- Retry a 429 with backoff, but check the Calls list before retrying a create that timed out, since there's no idempotency key
- Validate
X-Twilio-Signatureon every webhook and websocket upgrade
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, Twilio Programmable Voice API + MCP or Vonage Voice API + MCP?
Twilio Programmable Voice API + MCP scores 79.9 (A) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in every scored category.
Which is cheaper for phone calls, Twilio Programmable Voice API + MCP or Vonage Voice API + MCP?
Twilio Programmable Voice API + MCP, at $0.0025 per minute of call against $0.005 per minute of call for Vonage Voice API + MCP. These are the vendors' published prices for the job.
Do Twilio Programmable Voice API + MCP and Vonage Voice API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Twilio Programmable Voice API + MCP and Vonage Voice API + MCP without installing anything?
Yes. Twilio Programmable Voice API + MCP has a hosted endpoint at https://api.twilio.com/2010-04-01 and Vonage Voice API + MCP at https://api.nexmo.com/v1.
Other comparisons with Twilio Programmable Voice API + MCP or Vonage Voice API + MCP
- 46elks Voice API vs Twilio Programmable Voice API + MCP
- 46elks Voice API vs Vonage Voice API + MCP
- Bandwidth Voice API + MCP vs Twilio Programmable Voice API + MCP
- Bandwidth Voice API + MCP vs Vonage Voice API + MCP
- Exotel Voice API + MCP vs Twilio Programmable Voice API + MCP
- Exotel Voice API + MCP vs Vonage Voice API + MCP
- Infobip Calls API + MCP vs Twilio Programmable Voice API + MCP
- Infobip Calls API + MCP vs Vonage Voice API + MCP
- jambonz vs Twilio Programmable Voice API + MCP
- jambonz vs Vonage Voice API + MCP
- LiveKit Telephony vs Twilio Programmable Voice API + MCP
- LiveKit Telephony vs Vonage Voice API + MCP
- Plivo Voice API vs Twilio Programmable Voice API + MCP
- Plivo Voice API vs Vonage Voice API + MCP
- SignalWire Voice API vs Twilio Programmable Voice API + MCP
- SignalWire Voice API vs Vonage Voice API + MCP
- Sinch Voice API + MCP vs Twilio Programmable Voice API + MCP
- Sinch Voice API + MCP vs Vonage Voice API + MCP
- Telnyx Voice API + MCP vs Twilio Programmable Voice API + MCP
- Telnyx Voice API + MCP vs Vonage Voice API + MCP
- Twilio Programmable Voice API + MCP vs Voximplant
- Vonage Voice API + MCP vs Voximplant
- didlogic Voice API vs Twilio Programmable Voice API + MCP
- didlogic Voice API vs Vonage Voice API + MCP
- DIDWW Voice and Number Management API vs Twilio Programmable Voice API + MCP
- DIDWW Voice and Number Management API vs Vonage Voice API + MCP
Machine-readable
- This page as Markdown
/compare/twilio-voice-vs-vonage-voice.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/twilio-voice.json·/api/v1/tools/vonage-voice.json - From a terminal
anchor compare twilio-voice vonage-voice(the CLI) - Over MCP
compare_tools {"a": "twilio-voice", "b": "vonage-voice"}at/mcp, no key