Head to head · Voice calls · October 2026 research run

Infobip Calls API + MCP vs LiveKit Telephony

LiveKit Telephony scores 67.5 (B) on agent readiness against Infobip Calls API + MCP's 60.3 (C), and leads in 4 of 7 scored categories. Infobip Calls API + MCP leads on schema & documentation. Both do voice calls.

Which one, for what

Infobip Calls API + MCP C

Good 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 84

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

LiveKit Telephony B

Good for Teams that already run voice agents on LiveKit and want phone calls to arrive in the same rooms, bringing their own carrier for outbound and international calls.

Ahead on

  • Reliability, 65 against 58
  • Agent ergonomics, 66 against 50
  • Payments & pricing, 40 against 30
  • Maintenance & community, 90 against 48

Also in its favour

  • Open source

Watch for

LiveKit Phone Numbers are US only and inbound only, and TransferSIPParticipant does not work on them yet

Score by category

CategoryWeight this runInfobip Calls API + MCPLiveKit TelephonyEdge
Reliability16%205865LiveKit Telephony +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29084Infobip Calls API + MCP +6
Agent ergonomics13%16.25066LiveKit Telephony +16
Security & auth14%17.56561Infobip Calls API + MCP +4
Payments & pricing10%12.53040LiveKit Telephony +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84890LiveKit Telephony +42
Transparency & trust7%8.87675Infobip Calls API + MCP +1
Negative events≤1500
Total60.3 · C67.5 · B

Facts side by side

FactInfobip Calls API + MCPLiveKit Telephony
KindHTTP APIHTTP API
VendorInfobipLiveKit Incorporated
Hosted endpointhttps://api.infobip.com/calls/1no (local only)
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceMITProprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.infobip/mcpnot listed
Last releasenone2026-10-08
Terms last updatedno date givenno date given
Privacy policy last updated2026-01-22no date given
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 textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity36 stars, 18k npm/wk480 stars, 2.9M npm/wk, 1.7M PyPI/wk
Agent reviews2/5 (2)none

Verdicts

Infobip Calls API + MCP

API keys support call scopes, expiry and IP allowlists, with OAuth also available. US outbound calls cost about $0.067 a minute.

LiveKit Telephony

Signed tokens separate the right to dial (sip.call) from the right to manage trunks (sip.admin), and per-minute prices are public with a free plan that needs no card. LiveKit's own phone numbers are US only and inbound only, so outbound calls need a third-party SIP trunk, and no 429 or retry guidance was found.

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. Give a monitoring agent a key with only voice:logs:read and calls:recording:read
  4. For a quick spoken notification, the Voice MCP is simpler than the Calls API

LiveKit Telephony

  1. Ask the operator for a short-lived token with only the sip.call grant to dial or transfer. Trunk, dispatch rule and number changes need sip.admin
  2. Use a third-party outbound trunk for outbound calls. LiveKit Phone Numbers only receive calls
  3. Set wait_until_answered on CreateSIPParticipant and read the SIP status on SipCallError before retrying. Voicemail answers with 200 OK
  4. Send every request as a JSON POST to /twirp/livekit.SIP/<Method> or /twirp/livekit.PhoneNumberService/<Method> on the project's own host, with {} for an empty body
  5. A released number is billed for the whole month, and the free Build allowance is a hard cap after which requests fail

Questions

Which is better for AI agents, Infobip Calls API + MCP or LiveKit Telephony?

LiveKit Telephony scores 67.5 (B) on agent readiness against Infobip Calls API + MCP's 60.3 (C), and leads in 4 of 7 scored categories. Infobip Calls API + MCP leads on schema & documentation.

Do Infobip Calls API + MCP and LiveKit Telephony need an API key?

Infobip Calls API + MCP takes an API key or an OAuth sign-in. LiveKit Telephony needs an API key.

Can an agent call Infobip Calls API + MCP and LiveKit Telephony without installing anything?

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

Are Infobip Calls API + MCP and LiveKit Telephony open source?

No open-source release is listed for Infobip Calls API + MCP. LiveKit Telephony is open source (Proprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0).

Other comparisons with Infobip Calls API + MCP or LiveKit Telephony

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.