Head to head · Phone calls · October 2026 research run

Vonage Voice API + MCP vs Voximplant

Vonage Voice API + MCP and Voximplant score within a point of each other on agent readiness, 61.2 (C) and 61 (C). Voximplant leads on reliability, maintenance & community and transparency & trust. Both do phone calls.

Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons

Which one, for what

Vonage Voice API + MCP C

Best for Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.

Ahead on

  • Schema & documentation, 88 against 71
  • Agent ergonomics, 60 against 45
  • Security & auth, 73 against 60
  • Payments & pricing, 53 against 38

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Voximplant loses 3 points for them

Watch for

First call needs an application, a private key and a signed JWT

Voximplant C

Best for Teams that want speech-to-speech models on the phone without running a media server, and are happy to write call logic in VoxEngine JavaScript.

Ahead on

  • Reliability, 85 against 45
  • Maintenance & community, 75 against 51
  • Transparency & trust, 72 against 49

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks)

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 Voximplant +40

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.

Voximplant 85

Statuspage at status.voximplant.com with components and history (20). The history feed, read on 11 November, runs from 20 October. Every Platform incident in it is scoped to one region or carrier (Russia PSTN on 20 and 29 October and 5 and 9 November, US SIP for 43 minutes on 21 October, Kazakhstan PSTN on 22 October, Europe PSTN and SIP on 29 October), and Kit, website and announced maintenance entries are left out. The 13 August to 19 October part of the window wasn't re-read, so the line keeps its recorded minor-only award (20). Per the 30 September check, not re-read on 11 November, limits published with numbers, 50 call attempts, 10 unanswered calls and 3 active HTTP requests per session, 1,000 users per account (15). The StartScenarios method page says the method returns 429 Too Many Requests past 200 concurrent HTTP requests until the number of active requests is reduced, and the Management API error catalogue lists RATE_LIMIT_EXCEED (340) and RETRY_LATER (416, "Repeat after N seconds", a stated wait). No idempotency keys or safe-retry guidance found (10, the value backoff or a stated wait takes). A Service Level Agreement, effective 15 September 2023, sets 99.95% uptime with service credits (10). The platform is generally available (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Maintenance & community Voximplant +24

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.

Voximplant 75

The Node.js client 5.2.0 and the Python client 2.13.0 were released on 5 November 2026, 6 days before 11 November (30). Since 13 August the Node.js client released 4.11.0 (26 August), 5.0.0 (7 October), 5.1.0 (26 October) and 5.2.0, and the Python client 2.10.0 (26 August), 2.11.0 (22 October), 2.12.0 (26 October) and 2.13.0, five release dates in all (20). No public changelog, and support exists (5 of 15). Official clients for the Management API in six languages, the Node.js and Python ones current (15). Package health not checked beyond the release tags (5 of 10, the earlier partial kept). 30 + 20 + 5 + 15 + 5 = 75.

Transparency & trust Voximplant +23

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.

Voximplant 72

Closed service under a Master Subscription Agreement updated 14 March 2025 that names Voximplant, Inc. The API clients are Apache-2.0 (15). Per the 1 October check, not re-read on 11 November, the privacy policy states retention (closed accounts deleted within 12 months, billing data kept 7 years), and cloud recordings are kept 3 months or sent to your own S3. The site footer now links a data processing addendum, which we didn't open (25 of 30). No deprecation policy or dated notices found (0). A sub-processor list names AWS, Google Cloud Platform, Servers.com, LiquidWeb, Google, Voxbone, PostHog and Shufti Pro with their purposes but no locations, and the privacy policy, per 1 October, says data may be processed in the US, Europe or elsewhere with an option to keep it in the EU (15 of 20). 15 + 25 + 0 + 15 = 55.

Schema & documentation Vonage Voice API + MCP +17

Vonage Voice API + MCP 88

OpenAPI spec for the Voice API on developer.vonage.com, version 1.10.0 (25). llms.txt that tells agents to keep the api.nexmo.com and rest.nexmo.com hostnames (10). The NCCO reference explains each action, talk, input, record, connect, transfer, with notes on which to choose (14 of 20). Typed fields from the spec (12 of 15). Examples per action, a webhook reference and a shared API error catalogue in RFC 7807 form at developer.vonage.com/en/api-errors, though the Voice spec documents only a 201 for POST /v1/calls (12 of 15). Versioned /v1 path and a public changelog index (15). Per the 2 October check, not re-read on 4 November.

Voximplant 71

The docs' llms.txt, read on 11 November, links the Management API's OpenAPI 3.1 file at docs.voximplant.ai/openapi.json and openapi.yaml under "OpenAPI Specification". The file itself is per the 1 October reading, not re-read on 11 November (25). llms.txt with Markdown copies of every page (10). Reference pages describe each Management API method and VoxEngine class, with little on when not to use one (12 of 20). Method pages give each parameter's type, whether it's required, and example values (12 of 15). An error catalogue with every code the API returns, and request examples in several languages on each method page (12 of 15). No public changelog found and no version in the API path (0 of 15). 25 + 10 + 12 + 12 + 12 + 0 = 71.

Agent ergonomics Vonage Voice API + MCP +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.

Voximplant 45

List methods such as call history take count and offset, and we didn't confirm field controls (10 of 25). Filters not confirmed (10 of 20). The error catalogue names every code with a message, though errors arrive with HTTP 200 and an error object (15 of 20). No idempotency key or safe-retry guidance found (0). Official clients in Node.js, Python, PHP, Java, Go and .NET, but a first call needs an uploaded VoxEngine scenario and a rule before StartScenarios (10 of 15). 10 + 10 + 15 + 0 + 10 = 45.

Payments & pricing Vonage Voice API + MCP +15

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.

Voximplant 38

Per the 1 October check, not re-read on 11 November. No x402, MPP or L402 (0). Per-country per-minute rates, number fees, streaming and connector prices published without a login (20). Signup for a developer account is free, but the pricing page states no trial credit or card policy (5 of 20). A person signs up in a browser (0). 0 + 20 + 5 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Score by category

CategoryWeightVonage Voice API + MCPVoximplantEdge
Reliability16%4585Voximplant +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8871Vonage Voice API + MCP +17
Agent ergonomics13%6045Vonage Voice API + MCP +15
Security & auth14%7360Vonage Voice API + MCP +13
Payments & pricing10%5338Vonage Voice API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5175Voximplant +24
Transparency & trust7%4972Voximplant +23
Negative events≤150-3
TotalC 61.2/100C 61/100

Facts side by side

FactVonage Voice API + MCPVoximplant
KindHTTP APIHTTP API
VendorVonage (Ericsson)Voximplant
Hosted endpointhttps://api.nexmo.com/v1https://api.voximplant.com/platform_api
TransportsHTTP, stdio, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for phone calls$0.005 per minute of callnot published
x402nono
LicencenoneApache-2.0
Tools exposed14none
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.Vonage/vonage-documentation-mcpnot listed
Last release2026-10-212026-11-05
Terms last updatedcouldn't be read2025-03-14
Privacy policy last updatedcouldn't be read2025-06-01
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity154k npm/wk, 67k PyPI/wk15 stars
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Voximplant higher, the other way from the total score.

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

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.

Voximplant

Voximplant runs call logic in VoxEngine JavaScript next to the media, with connectors for the main speech-to-speech models at $0.004 a minute and a published 99.95% uptime SLA. The Management API documents query-string keys as an option, there's no public changelog, and the Python client's 2.11.0 minor release reordered positional parameters without notice.

Before you call either

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Voximplant

  1. Upload a VoxEngine scenario and a rule first, then start it with StartScenarios and pass the number in script_custom_data
  2. Pass arguments to the Python client by keyword, since 2.11.0 reordered positional parameters
  3. Use a service-account JWT rather than api_key in the URL
  4. Give the service account only the roles the agent needs, such as Scenarios
  5. Check the error object in every HTTP 200 response, since Management API errors don't use HTTP status codes

Questions

Which is better for AI agents, Vonage Voice API + MCP or Voximplant?

Vonage Voice API + MCP and Voximplant score within a point of each other on agent readiness, 61.2 (C) and 61 (C). Voximplant leads on reliability, maintenance & community and transparency & trust.

Do Vonage Voice API + MCP and Voximplant need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Vonage Voice API + MCP and Voximplant without installing anything?

Yes. Vonage Voice API + MCP has a hosted endpoint at https://api.nexmo.com/v1 and Voximplant at https://api.voximplant.com/platform_api.

Other comparisons with Vonage Voice API + MCP or Voximplant

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.