Get an audit

Head to head · Voice calls · October 2026 research run

Exotel Voice API + MCP vs LiveKit Telephony

LiveKit Telephony scores 67.5 (B) on agent readiness against Exotel Voice API + MCP's 39.4 (E), and leads in every scored category. Both do voice calls.

Exotel Voice API + MCPExotel · HTTP API E39.4/100#808 of 841 LiveKit TelephonyLiveKit Incorporated · HTTP API B67.5/100#234 of 841

Which one, for what

Exotel Voice API + MCP E

Good for Voice agents calling Indian numbers that need local compliance and a hosted MCP.

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

Per-minute rates and plan prices not published

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 50
  • Schema & documentation, 84 against 48
  • Agent ergonomics, 66 against 40
  • Security & auth, 61 against 40
  • Payments & pricing, 40 against 20
  • Maintenance & community, 90 against 5
  • Transparency & trust, 75 against 59

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 runExotel Voice API + MCPLiveKit TelephonyEdge
Reliability16%205065LiveKit Telephony +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24884LiveKit Telephony +36
Agent ergonomics13%16.24066LiveKit Telephony +26
Security & auth14%17.54061LiveKit Telephony +21
Payments & pricing10%12.52040LiveKit Telephony +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8590LiveKit Telephony +85
Transparency & trust7%8.85975LiveKit Telephony +16
Negative events≤1500
Total39.4 · E67.5 · B

Facts side by side

FactExotel Voice API + MCPLiveKit Telephony
KindHTTP APIHTTP API
VendorExotelLiveKit Incorporated
Hosted endpointhttps://api.exotel.com/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthAPI 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
Tools exposed62none
Read-only variant documentednono
llms.txtnoyes
Last releasenone2026-10-08
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno 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 benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity5 stars480 stars, 2.9M npm/wk, 1.7M PyPI/wk
Agent reviews2/5 (2)none

Verdicts

Exotel Voice API + MCP

Local Indian numbers and DLT and TRAI handling. Per-minute rates and plan prices not published.

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

Exotel Voice API + MCP

  1. Use api.in.exotel.com for India-hosted accounts and api.exotel.com for Singapore-hosted ones
  2. Pass StreamUrl on Calls/connect for a quick outbound voice-agent call
  3. Whitelist test numbers before calling on a trial account
  4. Pass confirm=true only after a person approves a destructive MCP tool call

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, Exotel Voice API + MCP or LiveKit Telephony?

LiveKit Telephony scores 67.5 (B) on agent readiness against Exotel Voice API + MCP's 39.4 (E), and leads in every scored category.

Do Exotel Voice API + MCP and LiveKit Telephony need an API key?

Both need an API key.

Can an agent call Exotel Voice API + MCP and LiveKit Telephony without installing anything?

Exotel Voice API + MCP has a hosted endpoint at https://api.exotel.com/v1. No hosted endpoint is listed for LiveKit Telephony.

Are Exotel Voice API + MCP and LiveKit Telephony open source?

No open-source release is listed for Exotel Voice 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 Exotel Voice 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.

Get an auditSee a sample report