Head to head · Phone calls · October 2026 research run

Infobip Calls API + MCP vs SignalWire Voice API

SignalWire Voice API scores 69.4 (B) on agent readiness against Infobip Calls API + MCP's 67.8 (B), and leads in 3 of 7 scored categories. Infobip Calls API + MCP leads on reliability 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

  • Reliability, 62 against 53
  • Transparency & trust, 82 against 74

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

SignalWire Voice API B

Best for Builders who want call logic in documents (SWML) or a hosted AI agent verb, and for teams moving off Twilio's API shape.

Ahead on

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

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

Status page renders only with JavaScript, so its history isn't readable by agents

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 SignalWire Voice API +21

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.

SignalWire Voice API 81

signalwire-python 3.7.5 tagged on 25 October 2026, after 3.6.0 (5 October), 3.7.0 (12 October) and 3.7.1 to 3.7.4, and signalwire-js 4.0.0-rc.5 on 14 October. Changelog entries on 19 and 22 October (30). 13 Python SDK releases from 3.4.0 on 25 August to 3.7.5, plus JS release candidates, and dated changelog entries most weeks (20). Closed service with an active changelog and community support. We didn't sample issue replies (8 of 15). Official Python and Node SDKs current (15). The Python SDK runs test, multi-OS, nightly and docs-audit workflows and Renovate for dependencies. We couldn't see run results (8 of 10). The SDK changelog since 3.5.1 has no removals or breaking changes. 3.7.0 changes how new search indexes embed text and keeps existing indexes working, with an option for the old behaviour. 30 + 20 + 8 + 15 + 8 = 81.

Payments & pricing SignalWire Voice API +15

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.

SignalWire Voice API 60

No x402, MPP or L402 (0). US per-minute rates for calls, SIP, numbers, recording and the AI agent runtime published without a login, re-read on 1 November on signalwire.com/pricing (20). New accounts start in trial mode without a card, limited to 1 number and verified destinations, and a card with at least $5 of credit lifts it, re-read on 1 November. The trial page doesn't state a free credit amount (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): 40 is 60.

Reliability Infobip Calls API + MCP +9

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.

SignalWire Voice API 53

status.signalwire.com redirects to a PagerDuty-hosted page. Re-read on 1 November, its page data names ten services (APIs, SIP Connectivity, WebRTC Connectivity, Video and Conferencing, Website, External Carrier Network, SMS, MMS, AI, Support and Documentation) and says it was created on 23 December 2025, but incidents load only through the page's script and we found no feed, so component history isn't readable (10 of 20). No readable incident history (5). The 1 October note cited a third-party status aggregator for a 14 August degradation; that isn't a first-hand source and isn't used. Trial mode caps queued calls and messages at 10 each, and Space limits are raised on request. The error-codes page, re-read on 1 November, names a rate_limit_exceeded code but no general per-second figures (8 of 15). The error-codes page says to back off and retry on 429, and now also calls every 5xx "Safe to retry with backoff", which for a dial can place a second call. The official Python SDK honours Retry-After with exponential backoff and retries POSTs only on 429 or 503, never on other 5xx, so a dial isn't replayed. No idempotency key (10 of 15). The Service Level Agreement (updated 1 January 2026) commits to 99.95 per cent monthly uptime for SignalWire Cloud APIs on every account, with a 10 per cent credit claimed by ticket within 30 days, per the 2 October read (10). The Calling API is generally available (10). 10 + 5 + 8 + 10 + 10 + 10 = 53.

Transparency & trust Infobip Calls API + MCP +8

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.

SignalWire Voice API 74

Closed service under the SignalWire Cloud Agreement (15). Privacy policy, a Data Processing Addendum and a cloud sub-processor list are published. We didn't find retention periods for call records or recordings (20 of 30). Dated deprecation notice for the token format, old tokens keep working (15 of 20). The sub-processor PDF names five cloud providers with countries (AWS in the US, Bahrain and South Africa, DigitalOcean in seven countries, Google in the US, Microsoft in four, Vultr in Australia), but service-specific sub-processors are listed without purposes or locations and the PDF carries no date (15 of 20).

Agent ergonomics SignalWire Voice API +6

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

SignalWire Voice API 68

A paging guide covers page sizes on list endpoints, with no field selection (15 of 25). Voice logs can be listed and paged. We didn't confirm the full filter set (15 of 20). An error-codes page with a structured errors array (type, code, message, attribute, url) an agent can map to fixes, and command results arrive on status webhooks (15 of 20). No idempotency key. The Python SDK's documented retry policy keeps POSTs from being replayed after a 5xx (8 of 20). One POST endpoint takes every command, a dial needs from, to and a SWML url, and there are official Python and Node SDKs plus Twilio-compatible ones (15).

Score by category

CategoryWeightInfobip Calls API + MCPSignalWire Voice APIEdge
Reliability16%6253Infobip Calls API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9087Infobip Calls API + MCP +3
Agent ergonomics13%6268SignalWire Voice API +6
Security & auth14%7272even
Payments & pricing10%4560SignalWire Voice API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6081SignalWire Voice API +21
Transparency & trust7%8274Infobip Calls API + MCP +8
Negative events≤1500
TotalB 67.8/100B 69.4/100

Facts side by side

FactInfobip Calls API + MCPSignalWire Voice API
KindHTTP APIHTTP API
VendorInfobipSignalWire
Hosted endpointhttps://api.infobip.com/calls/1no (local only)
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceMITMIT
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.infobip/mcpnot listed
Last releasenone2026-10-25
Terms last updatedno date givennot read yet
Privacy policy last updated2026-01-22couldn't be read
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity36 stars, 18k npm/wk8 stars, 1.5k npm/wk, 1.3k PyPI/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate SignalWire Voice API 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.

SignalWire Voice API

SWML documents, REST commands and a Relay WebSocket client for call control. Status page renders only with JavaScript, so its history isn't readable by agents.

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

SignalWire Voice API

  1. Send dial with a url pointing at a SWML document, then use calling.* commands on the returned call ID
  2. Don't retry a dial on a 5xx, whatever the error-codes page says. Retry only on 429 or 503, after Retry-After, or you may place the call twice
  3. Use your own Space subdomain as the host, there is no shared API host
  4. Create a token with only the Voice scope for a calling agent
  5. Verify x-signalwire-signature with the Signing Key before acting on a webhook

Questions

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

SignalWire Voice API scores 69.4 (B) on agent readiness against Infobip Calls API + MCP's 67.8 (B), and leads in 3 of 7 scored categories. Infobip Calls API + MCP leads on reliability and transparency & trust.

Do Infobip Calls API + MCP and SignalWire Voice API need an API key?

Infobip Calls API + MCP takes an API key or an OAuth sign-in. SignalWire Voice API needs an API key.

Can an agent call Infobip Calls API + MCP and SignalWire Voice API without installing anything?

Infobip Calls API + MCP has a hosted endpoint at https://api.infobip.com/calls/1. No hosted endpoint is listed for SignalWire Voice API.

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

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.