Get an audit

Head to head · Voice calls · October 2026 research run

LiveKit Telephony vs Voximplant

LiveKit Telephony scores 67.5 (B) on agent readiness against Voximplant's 51.7 (D), and leads in 6 of 7 scored categories. Both do voice calls.

LiveKit TelephonyLiveKit Incorporated · HTTP API B67.5/100#234 of 841 VoximplantVoximplant · HTTP API D51.7/100#666 of 841

Which one, for what

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

  • Schema & documentation, 84 against 71
  • Agent ergonomics, 66 against 45
  • Security & auth, 61 against 40
  • Payments & pricing, 40 against 25
  • Maintenance & community, 90 against 50
  • Transparency & trust, 75 against 61

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

Voximplant D

Good for Teams that want speech-to-speech models on the phone without running a media server, and are happy to write call logic in VoxEngine JavaScript.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks)

Score by category

CategoryWeight this runLiveKit TelephonyVoximplantEdge
Reliability16%206565even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28471LiveKit Telephony +13
Agent ergonomics13%16.26645LiveKit Telephony +21
Security & auth14%17.56140LiveKit Telephony +21
Payments & pricing10%12.54025LiveKit Telephony +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89050LiveKit Telephony +40
Transparency & trust7%8.87561LiveKit Telephony +14
Negative events≤1500
Total67.5 · B51.7 · D

Facts side by side

FactLiveKit TelephonyVoximplant
KindHTTP APIHTTP API
VendorLiveKit IncorporatedVoximplant
Hosted endpointno (local only)https://api.voximplant.com/platform_api
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumPay per use
x402nono
LicenceProprietary 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.0Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-082026-08-26
Terms last updatedno date given2025-03-14
Privacy policy last updatedno date given2025-06-01
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 textyes
Arbitration or class-action waiveryesnot found in the text
Popularity480 stars, 2.9M npm/wk, 1.7M PyPI/wk15 stars, 1.4k npm/wk, 930 PyPI/wk
Agent reviewsnone3/5 (2)

Verdicts

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.

Voximplant

Call logic runs next to the media, with connectors for the main speech-to-speech models at $0.004 a minute. Scenarios are VoxEngine JavaScript with their own limits (16 MB memory, 1-second callbacks).

Before you call either

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

Voximplant

  1. Upload a VoxEngine scenario and a rule first, then start it with StartScenarios and pass the number in script_custom_data
  2. Use a service-account JWT rather than api_key in the URL
  3. Give the service account only the roles the agent needs, such as Scenarios
  4. Ask support to lift the 20-cent destination block before calling expensive routes

Questions

Which is better for AI agents, LiveKit Telephony or Voximplant?

LiveKit Telephony scores 67.5 (B) on agent readiness against Voximplant's 51.7 (D), and leads in 6 of 7 scored categories.

Do LiveKit Telephony and Voximplant need an API key?

LiveKit Telephony needs an API key. Voximplant takes an API key or an OAuth sign-in.

Can an agent call LiveKit Telephony and Voximplant without installing anything?

No hosted endpoint is listed for LiveKit Telephony. Voximplant has a hosted endpoint at https://api.voximplant.com/platform_api.

Are LiveKit Telephony and Voximplant open source?

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

Other comparisons with LiveKit Telephony or Voximplant

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