Head to head · Phone calls · October 2026 research run

Infobip Calls API + MCP vs Vonage Voice API + MCP

Infobip Calls API + MCP scores 67.8 (B) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. Vonage Voice API + MCP leads on payments & pricing. Both do phone calls.

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

Which one, for what

Infobip Calls API + MCP B

Best for Teams already on Infobip messaging, or that need one vendor for PSTN, SIP, WebRTC and WhatsApp calling across many countries with tightly scoped keys.

Ahead on

  • Reliability, 62 against 45
  • Maintenance & community, 60 against 51
  • Transparency & trust, 82 against 49

Watch for

US outbound at about $0.067 a minute, several times Plivo, SignalWire or Telnyx

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

  • Payments & pricing, 53 against 45

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

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.

Transparency & trust Infobip Calls API + MCP +33

Infobip Calls API + MCP 82

Closed service with clear service terms (15). Privacy notice, a data retention notice, a data transfer agreement, information security terms and a sub-processor page. We didn't check the retention notice against the voice docs (25 of 30). A deprecation policy, re-read on 4 November, says deprecated endpoints keep working until a sunset date, are flagged in the OpenAPI file and in Deprecation, Sunset and Link response headers, and trigger email to active users, but sets no fixed notice period, and no dated Calls API notice was found (10 of 20). The sub-processor page says where customer data is stored and accessed, has a separate list for the EU region-locked data centre, and has email alerts on changes (15 of 20). 15 + 25 + 10 + 15 = 65.

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 Infobip Calls API + MCP +17

Infobip Calls API + MCP 62

Statuspage at status.infobip.com with components and history (20). Its history pages, re-read on 4 November, list every incident touching voice since 6 August as partial. Multi-channel delays in several data centres on 26 August (21:02 to 22:12 UTC), intermittent HTTP API access in Global (Europe) on 26 August, a 15 August Global (Europe) degradation, 7 October SaaS and CPaaS degradation, a seven-minute Voice disruption in Colombia on 16 October and an EU Region-locked degradation naming Voice on 19 October. Each names one region, one country or delays, so minor only (20). The 26 and 27 September US numbers and SIP trunk work was an emergency maintenance. The 1 October third-party incident count (IsDown) is struck, a barred status mirror. The rate-limits page says each endpoint's reference lists its limits, but no Calls API numbers were read (0). The rate-limits and handling-errors pages give exponential backoff with a retry cap for 429, and say a retried send may run twice, there is no public idempotency key, and to check logs or delivery reports before retrying (12, safe-retry guidance without a key). No SLA found (0). Calls API is generally available (10). 20 + 20 + 0 + 12 + 0 + 10 = 62.

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 Infobip Calls API + MCP +9

Infobip Calls API + MCP 60

The Jasper release notes of 14 October 2026 include Subscriptions sending the same event to multiple webhooks, the route Calls API events take (30). Two dated release entries in the 90 days from 6 August (Ink on 9 September, Jasper on 14 October) and one dated MCP repository change adding a non-voice server (12 September), read as the Infobip messaging listing reads its launches (10 of 20). Closed service with release notes and support (8 of 15). The official Python client 6.0.0 (22 January 2026) covers the Voice and Calls APIs, while the JavaScript SDK's last release was in 2023, the reading the Infobip messaging listing takes (10 of 15). The JavaScript SDK's dependencies are stale (2 of 10). 30 + 10 + 8 + 10 + 2 = 60.

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.

Payments & pricing Vonage Voice API + MCP +8

Infobip Calls API + MCP 45

No x402, MPP or L402 (0). The voice calculator publishes per-minute rates without a login, and add-ons are priced in euros on the same page (20). A 60-day free trial exists, limited to the number verified at signup. The trial page doesn't say whether a card is needed and says nothing about voice allowances (10 of 20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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

CategoryWeightInfobip Calls API + MCPVonage Voice API + MCPEdge
Reliability16%6245Infobip Calls API + MCP +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9088Infobip Calls API + MCP +2
Agent ergonomics13%6260Infobip Calls API + MCP +2
Security & auth14%7273Vonage Voice API + MCP +1
Payments & pricing10%4553Vonage Voice API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6051Infobip Calls API + MCP +9
Transparency & trust7%8249Infobip Calls API + MCP +33
Negative events≤1500
TotalB 67.8/100C 61.2/100

Facts side by side

FactInfobip Calls API + MCPVonage Voice API + MCP
KindHTTP APIHTTP API
VendorInfobipVonage (Ericsson)
Hosted endpointhttps://api.infobip.com/calls/1https://api.nexmo.com/v1
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for phone callsnot published$0.005 per minute of call
x402nono
LicenceMITnone
Tools exposednone14
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.infobip/mcpio.github.Vonage/vonage-documentation-mcp
Last releasenone2026-10-21
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-01-22couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity36 stars, 18k npm/wk154k npm/wk, 67k PyPI/wk
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Vonage Voice API + MCP 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

Infobip Calls API + MCP

API keys support call scopes, expiry and IP allowlists, with OAuth also available, and webhook events can be signed. Retry guidance warns that a resent request may run twice, with no idempotency key. US outbound calls cost about $0.067 a minute, and no Calls API rate limits or SLA were found.

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

Infobip Calls API + MCP

  1. Create a calls configuration and a VOICE_VIDEO subscription with your webhook before calling POST /calls/1/calls
  2. Use your account's own base URL, not api.infobip.com
  3. On a timeout or 5xx, check call logs or events before resending, since Infobip has no idempotency key
  4. Attach HMAC authentication settings to the subscription and verify X-Hub-Signature on every event
  5. Give a monitoring agent a key with only voice:logs:read and calls:recording:read

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

Questions

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

Infobip Calls API + MCP scores 67.8 (B) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. Vonage Voice API + MCP leads on payments & pricing.

Do Infobip Calls 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 Infobip Calls API + MCP and Vonage Voice API + MCP without installing anything?

Yes. Infobip Calls API + MCP has a hosted endpoint at https://api.infobip.com/calls/1 and Vonage Voice API + MCP at https://api.nexmo.com/v1.

Other comparisons with Infobip Calls API + MCP or Vonage Voice API + MCP

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.