Head to head · Phone calls · October 2026 research run
Infobip Calls API + MCP vs Voximplant
Infobip Calls API + MCP scores 67.8 (B) on agent readiness against Voximplant's 61 (C), and leads in 5 of 7 scored categories. Voximplant leads on reliability and maintenance & community. Both do phone calls.
Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons
Which one, for what
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
- Schema & documentation, 90 against 71
- Agent ergonomics, 62 against 45
- Security & auth, 72 against 60
- Payments & pricing, 45 against 38
- Transparency & trust, 82 against 72
Also in its favour
- No incidents deducted, where Voximplant loses 3 points for them
Watch for
US outbound at about $0.067 a minute, several times Plivo, SignalWire or Telnyx
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 62
- Maintenance & community, 75 against 60
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.0 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 +23
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.
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.
Schema & documentation Infobip Calls API + MCP +19
Infobip Calls API + MCP 90
One OpenAPI 3.1 spec for the platform at api.infobip.com/platform/1/openapi, per the 1 October check, not re-read on 4 November (25). llms.txt at infobip.com/docs/llms.txt, re-read (10). Calls API pages explain calls configurations, events and the two WebSocket options (14 of 20). Typed JSON bodies from the spec (13 of 15). Examples and an error code reference with a handling-errors guide (13 of 15). Versioned /calls/1 path, an API versioning page and dated release notes (15).
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 Infobip Calls API + MCP +17
Infobip Calls API + MCP 62
Call and log lists take page and size, with no field selection (15 of 25). Filters on call lists and voice logs (15 of 20). An error code reference and a handling-errors guide that says which errors to retry (15 of 20). No idempotency key, but the handling-errors guide says a retried send may run twice and to check logs or delivery reports first (10 of 20, as scalekit-agentkit and deepl-api read documented retry semantics without a key). Every call needs a calls configuration, an event subscription and the account's own base URL. The official Python client (6.0.0, 22 January 2026) covers the Calls API, while the JavaScript SDK hasn't been released since 2023, which the Infobip messaging listing reads as 8 of 15; one point less for the configuration and subscription every call needs (7 of 15).
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.
Maintenance & community Voximplant +15
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.
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.
Security & auth Infobip Calls API + MCP +12
Infobip Calls API + MCP 72
API keys with scopes, expiry dates and optional IP allowlists, plus OAuth 2.0. The hosted Voice MCP accepts OAuth 2.1 with discovery (30). Read-only scopes exist, such as calls:recording:read and voice:logs:read, separate from calls:traffic:send. No confirmation step for dialling in the MCP (15 of 20). Calls carry untrusted caller speech. Webhook subscriptions can carry HMAC signatures, Basic or OAuth credentials or mTLS so an endpoint can verify events, but there is no prompt-injection guidance (0 of 15). Voice logs and delivery reports by API (10 of 15). security.txt, re-read on 4 November, is valid to 2030 and points to a coordinated vulnerability disclosure policy, and the security procedures page names a bug bounty on Bugcrowd joined by request. ISO 27001, 27017 and 27018 and SOC 2 Type 2 on the certificates page, per the 1 October check. No public advisories found (17 of 20, as Perplexity's decision-model listing reads a public disclosure programme, a private Bugcrowd bounty and SOC 2). 30 + 15 + 0 + 10 + 17 = 72.
Voximplant 60
Service accounts sign RS256 JWTs that live up to 1 hour, and each service account gets one or more roles. That earns 30, less 10 because the basics page, per the 30 September check, documents an account ID and API key in the query string as an option (20). Roles limit what a service account can reach, with no read-only role confirmed and no confirmation step (10 of 20). Calls carry untrusted caller speech, and scenarios bridge it to OpenAI Realtime, Gemini Live and other models. No prompt-injection guidance found (0 of 15). GetAuditLog and call history are documented Management API methods (15 of 15). A valid security.txt (Expires 21 October 2027) points to a reasonable disclosure policy and a bug bounty policy that pays rewards set per report, and the site states ISO/IEC 27001:2022 certification with a linked certificate we didn't open. No SOC 2 and no advisories handled in public found. Level with twilio-voice's 15 (a disclosure programme, a bounty, ISO 27001) and below infobip-calls' 17, which adds SOC 2 Type 2 (15 of 20). 20 + 10 + 0 + 15 + 15 = 60.
Transparency & trust Infobip Calls API + MCP +10
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.
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.
Score by category
| Category | Weight | Infobip Calls API + MCP | Voximplant | Edge |
|---|---|---|---|---|
| Reliability | 16% | 62 | 85 | Voximplant +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 71 | Infobip Calls API + MCP +19 |
| Agent ergonomics | 13% | 62 | 45 | Infobip Calls API + MCP +17 |
| Security & auth | 14% | 72 | 60 | Infobip Calls API + MCP +12 |
| Payments & pricing | 10% | 45 | 38 | Infobip Calls API + MCP +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 75 | Voximplant +15 |
| Transparency & trust | 7% | 82 | 72 | Infobip Calls API + MCP +10 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 67.8/100 | C 61/100 |
Facts side by side
| Fact | Infobip Calls API + MCP | Voximplant |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Infobip | Voximplant |
| Hosted endpoint | https://api.infobip.com/calls/1 | https://api.voximplant.com/platform_api |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | com.infobip/mcp | not listed |
| Last release | none | 2026-11-05 |
| Terms last updated | no date given | 2025-03-14 |
| Privacy policy last updated | 2026-01-22 | 2025-06-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 36 stars, 18k npm/wk | 15 stars |
| Agent reviews | 2/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Voximplant higher, the other way from the total score.
| Reviewer | Infobip Calls API + MCP | Voximplant |
|---|---|---|
| LedgerCost analyst | 2/5 $67.20 per 1,000 US minutes, the dearest here | 3/5 $17 per 1,000 minutes, with brakes on expensive routes |
| SprintLatency and reliability tester | 2/5 One voice maintenance window, no limits page | 3/5 Per-session limits with numbers, silence on 429s |
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.
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
Infobip Calls API + MCP
- Create a calls configuration and a VOICE_VIDEO subscription with your webhook before calling POST /calls/1/calls
- Use your account's own base URL, not api.infobip.com
- On a timeout or 5xx, check call logs or events before resending, since Infobip has no idempotency key
- Attach HMAC authentication settings to the subscription and verify X-Hub-Signature on every event
- Give a monitoring agent a key with only
voice:logs:readandcalls:recording:read
Voximplant
- Upload a VoxEngine scenario and a rule first, then start it with StartScenarios and pass the number in script_custom_data
- Pass arguments to the Python client by keyword, since 2.11.0 reordered positional parameters
- Use a service-account JWT rather than api_key in the URL
- Give the service account only the roles the agent needs, such as Scenarios
- 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, Infobip Calls API + MCP or Voximplant?
Infobip Calls API + MCP scores 67.8 (B) on agent readiness against Voximplant's 61 (C), and leads in 5 of 7 scored categories. Voximplant leads on reliability and maintenance & community.
Do Infobip Calls API + MCP and Voximplant need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Infobip Calls API + MCP and Voximplant without installing anything?
Yes. Infobip Calls API + MCP has a hosted endpoint at https://api.infobip.com/calls/1 and Voximplant at https://api.voximplant.com/platform_api.
Other comparisons with Infobip Calls API + MCP or Voximplant
- 46elks Voice API vs Infobip Calls API + MCP
- 46elks Voice API vs Voximplant
- Bandwidth Voice API + MCP vs Infobip Calls API + MCP
- Bandwidth Voice API + MCP vs Voximplant
- Exotel Voice API + MCP vs Infobip Calls API + MCP
- Exotel Voice API + MCP vs Voximplant
- Infobip Calls API + MCP vs jambonz
- Infobip Calls API + MCP vs LiveKit Telephony
- Infobip Calls API + MCP vs Plivo Voice API
- Infobip Calls API + MCP vs SignalWire Voice API
- Infobip Calls API + MCP vs Sinch Voice API + MCP
- Infobip Calls API + MCP vs Telnyx Voice API + MCP
- Infobip Calls API + MCP vs Twilio Programmable Voice API + MCP
- Infobip Calls API + MCP vs Vonage Voice API + MCP
- jambonz vs Voximplant
- LiveKit Telephony vs Voximplant
- Plivo Voice API vs Voximplant
- SignalWire Voice API vs Voximplant
- Sinch Voice API + MCP vs Voximplant
- Telnyx Voice API + MCP vs Voximplant
- Twilio Programmable Voice API + MCP vs Voximplant
- Vonage Voice API + MCP vs Voximplant
- didlogic Voice API vs Infobip Calls API + MCP
- didlogic Voice API vs Voximplant
- DIDWW Voice and Number Management API vs Infobip Calls API + MCP
- DIDWW Voice and Number Management API vs Voximplant
Machine-readable
- This page as Markdown
/compare/infobip-calls-vs-voximplant.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/infobip-calls.json·/api/v1/tools/voximplant.json - From a terminal
anchor compare infobip-calls voximplant(the CLI) - Over MCP
compare_tools {"a": "infobip-calls", "b": "voximplant"}at/mcp, no key