Head to head · Phone calls · October 2026 research run

Infobip Calls API + MCP vs Sinch Voice API + MCP

Sinch Voice API + MCP and Infobip Calls API + MCP score within a point of each other on agent readiness, 68.5 (B) and 67.8 (B). Infobip Calls API + MCP leads on schema & documentation, security & auth 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

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

  • Schema & documentation, 90 against 85
  • Security & auth, 72 against 55
  • Transparency & trust, 82 against 73

Watch for

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

Sinch Voice API + MCP B

Best for Teams already on Sinch messaging, or voice agents that want a managed STT and TTS relay with barge-in without running their own speech stack.

Ahead on

  • Agent ergonomics, 81 against 62
  • Payments & pricing, 53 against 45
  • Maintenance & community, 79 against 60

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

Voice API v2, the listed surface, is labelled preview, and Sinch tells projects that must be generally available to use v1

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.

Agent ergonomics Sinch Voice API + MCP +19

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).

Sinch Voice API + MCP 81

v2 lists take page_size, with no field selection (15 of 25). The v2 call list pages by link and filters by from, to, call type, time range, result and reason (18 of 20). v1 error reference with codes, and v2 errors carry a type and instance per the SDKs (15 of 20). v2 call, batch and service writes take an Idempotency-Key that returns the cached response for repeats within 10 minutes, and the webhook guide says to deduplicate on ce-id and ce-source (18 of 20). Official SDKs in Node, Python, Java and .NET, but a v2 dial is a nested commands document rather than a few fields (15). 15 + 18 + 15 + 18 + 15 = 81.

Maintenance & community Sinch Voice API + MCP +19

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.

Sinch Voice API + MCP 79

Java SDK 2.4.0 (28 October 2026) adds Voice v2 helpers, Node 1.7.0 (15 October) and Python 2.3.0 (14 October) changed Voice v2, and the MCP server's 0.0.1-beta.7 (30 October) moved its voice tools to Voice API v2 (30). In the 90 days, Node 1.6.0 (23 September) and Python 2.2.0 (21 September) added Voice v2, Java 2.3.0 (15 October) did the same, and Java 2.2.0, .NET 1.5.1 (2 September) and the 28 October releases followed (20). v1 voice release notes stop in October 2022 and v2 has an undated what's-new page, while the SDK changelogs are dated (5 of 15). Official SDKs in four languages, with Voice v2 in Node, Python and Java (15). CI on the SDK repositories, with CodeQL and dependency review on Java and an audit job on Node (9 of 10). 30 + 20 + 5 + 15 + 9 = 79.

Security & auth Infobip Calls API + MCP +17

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.

Sinch Voice API + MCP 55

Voice v2 takes a project access key over Basic auth or as an OAuth 2.0 token. v1 uses an application key and secret with signed requests recommended. We found no per-key scopes (25 of 30). No read-only mode or confirmation step. The official MCP server's tool allow-list (--tags, or MCP_TAGS since 0.0.1-beta.7, 30 October) can leave out whole groups, and its released version runs over stdio only, as the Sinch messaging listing reads it (5 of 20). Calls carry untrusted caller speech. Callbacks are signed in v1 and v2, and we found no prompt-injection guidance (5 of 15). Call lookup and call lists by API, no audit log found (10 of 15). The trust centre lists ISO 27001:2022 and SOC 2 Type 2 reports, PCI and HIPAA, and Sinch's security contact for reports. No security.txt (404 on 2 November), no bug bounty and no advisories for @sinch/sdk-core, @sinch/mcp or sinch in OSV (10 of 20, as the Sinch messaging listing). 25 + 5 + 5 + 10 + 10 = 55.

Transparency & trust Infobip Calls API + MCP +9

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.

Sinch Voice API + MCP 73

Closed service with general terms. The contracting Sinch entity is named only in the order form (15). Privacy notice, a DPA addendum, a sub-processor list and deletion on request. Sinch says it updates the sub-processor page at least 30 days before engaging a new one and emails subscribers. Recordings go to your own S3, Google Cloud Storage or Azure bucket. No retention periods found (22 of 30). No deprecation policy or dated notice for v1 found (0). The sub-processor list, re-read on 2 November, gives hosting locations by service, Voice API and In-App Calling in Australia, Brazil, Germany, Singapore and the USA, Microsoft Azure (USA, EU) for Voice API text to speech, MongoDB for Voice API v2 since 31 July 2026, and TransUnion for Elastic SIP STIR/SHAKEN, as the Sinch messaging listing's list is read (20). 15 + 22 + 0 + 20 = 57.

Payments & pricing Sinch 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.

Sinch Voice API + MCP 53

No x402, MPP or L402 (0). The voice pricing page, re-read on 2 November, gives domestic outbound from $0.01 a minute with a downloadable Voice API price list, and only illustrative inbound, SIP, recording and number prices (15 of 20). Test credits and a test number on signup, with a payment method needed only to upgrade (20). A person signs up in a browser (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Schema & documentation Infobip Calls API + MCP +5

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).

Sinch Voice API + MCP 85

The v2 reference links an OpenAPI 3.1.1 file (version 2.0.59), read on 2 November with 11 paths and 17 operations (25). llms.txt with Markdown pages for v1 and v2 (10). Reference pages describe each SVAML action or v2 command, with a migration page on why to move to v2 (12 of 20). Typed fields with enums for call type, result and reason, and bounded integers such as maxCps and ttlSeconds (13 of 15). A v1 error and troubleshooting reference, request examples, and problem-details error answers (400, 401, 403, 404, 429, 500) documented on the v2 operations (15). Two API generations, v1 release notes last updated 2022-10-06 and an undated v2 what's-new page (10 of 15). 25 + 10 + 12 + 13 + 15 + 10 = 85.

Score by category

CategoryWeightInfobip Calls API + MCPSinch Voice API + MCPEdge
Reliability16%6260Infobip Calls API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9085Infobip Calls API + MCP +5
Agent ergonomics13%6281Sinch Voice API + MCP +19
Security & auth14%7255Infobip Calls API + MCP +17
Payments & pricing10%4553Sinch Voice API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6079Sinch Voice API + MCP +19
Transparency & trust7%8273Infobip Calls API + MCP +9
Negative events≤1500
TotalB 67.8/100B 68.5/100

Facts side by side

FactInfobip Calls API + MCPSinch Voice API + MCP
KindHTTP APIHTTP API
VendorInfobipSinch
Hosted endpointhttps://api.infobip.com/calls/1https://voice.api.sinch.com/v2
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITApache-2.0
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.infobip/mcpnot listed
Last releasenone2026-10-28
Terms last updatedno date given2026-06-01
Privacy policy last updated2026-01-222025-12-12
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity36 stars, 18k npm/wk1 stars, 16k npm/wk, 11k PyPI/wk
Agent reviews2/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Sinch Voice API + MCP higher.

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.

Sinch Voice API + MCP

Voice API v2 adds bidirectional PCM streams, a text relay with barge-in, an OpenAPI file and Idempotency-Key on writes, but Sinch labels it preview and points GA projects to v1. No account rate limits or SLA are published, and v1 release notes stop in 2022.

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

Sinch Voice API + MCP

  1. Start new work on Voice API v2 at voice.api.sinch.com, and check the preview label before relying on it in production
  2. Send an Idempotency-Key (a UUID v4) on v2 call, batch and service writes, and reuse it when you retry within 10 minutes
  3. On a 429, wait for the Retry-After seconds before retrying
  4. Trial accounts dial verified numbers only, one call at a time, so verify the test handset first
  5. Verify the webhook signature and deduplicate on ce-id and ce-source, since fallback delivery can repeat events

Questions

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

Sinch Voice API + MCP and Infobip Calls API + MCP score within a point of each other on agent readiness, 68.5 (B) and 67.8 (B). Infobip Calls API + MCP leads on schema & documentation, security & auth and transparency & trust.

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

Yes. Infobip Calls API + MCP has a hosted endpoint at https://api.infobip.com/calls/1 and Sinch Voice API + MCP at https://voice.api.sinch.com/v2.

Other comparisons with Infobip Calls API + MCP or Sinch 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.