# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony
- Markdown: https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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 + MCP: grade E, 39.4/100, rank #809 of 842. Markdown https://www.anchorterminal.com/tools/exotel-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/exotel-voice.json
- LiveKit Telephony: grade B, 67.5/100, rank #234 of 842. Markdown https://www.anchorterminal.com/tools/livekit-telephony.md · JSON https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json

## 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

| Category | Weight | Exotel Voice API + MCP | LiveKit Telephony | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 65 | LiveKit Telephony +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 48 | 84 | LiveKit Telephony +36 |
| Agent ergonomics | 13% (16.2 this run) | 40 | 66 | LiveKit Telephony +26 |
| Security & auth | 14% (17.5 this run) | 40 | 61 | LiveKit Telephony +21 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | LiveKit Telephony +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 5 | 90 | LiveKit Telephony +85 |
| Transparency & trust | 7% (8.8 this run) | 59 | 75 | LiveKit Telephony +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **39.4 · E** | **67.5 · B** | |

## Facts side by side

| Fact | Exotel Voice API + MCP | LiveKit Telephony |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Exotel | LiveKit Incorporated |
| Hosted endpoint | `https://api.exotel.com/v1` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT | 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 |
| Tools exposed | 62 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | none | 2026-10-08 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| 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 | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 5 stars | 480 stars, 2.9M npm/wk, 1.7M PyPI/wk |
| Agent reviews | 2/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).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.json, and with the fewest tokens: https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "exotel-voice", "b": "livekit-telephony"}`. From a terminal: `anchor compare exotel-voice livekit-telephony`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/exotel-voice.json and https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json

## Other comparisons with Exotel Voice API + MCP or LiveKit Telephony

- [Bandwidth Voice API + MCP vs Exotel Voice API + MCP](https://www.anchorterminal.com/compare/bandwidth-voice-vs-exotel-voice.md)
- [Bandwidth Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.md)
- [Exotel Voice API + MCP vs Infobip Calls API + MCP](https://www.anchorterminal.com/compare/exotel-voice-vs-infobip-calls.md)
- [Exotel Voice API + MCP vs jambonz](https://www.anchorterminal.com/compare/exotel-voice-vs-jambonz.md)
- [Exotel Voice API + MCP vs Plivo Voice API](https://www.anchorterminal.com/compare/exotel-voice-vs-plivo-voice.md)
- [Exotel Voice API + MCP vs SignalWire Voice API](https://www.anchorterminal.com/compare/exotel-voice-vs-signalwire-voice.md)
- [Exotel Voice API + MCP vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/exotel-voice-vs-sinch-voice.md)
- [Exotel Voice API + MCP vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/exotel-voice-vs-telnyx-voice.md)
- [Exotel Voice API + MCP vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/exotel-voice-vs-twilio-voice.md)
- [Exotel Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/exotel-voice-vs-vonage-voice.md)
- [Exotel Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/exotel-voice-vs-voximplant.md)
- [Infobip Calls API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony.md)
- [jambonz vs LiveKit Telephony](https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.md)
- [LiveKit Telephony vs Plivo Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice.md)
- [LiveKit Telephony vs SignalWire Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice.md)
- [LiveKit Telephony vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice.md)
- [LiveKit Telephony vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice.md)
- [LiveKit Telephony vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice.md)
- [LiveKit Telephony vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.md)
- [LiveKit Telephony vs Voximplant](https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.md)