Get an audit

Head to head · Voice calls · October 2026 research run

jambonz vs LiveKit Telephony

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

jambonzFirstFive8, Inc. · HTTP API D49.2/100#711 of 841 LiveKit TelephonyLiveKit Incorporated · HTTP API B67.5/100#234 of 841

Which one, for what

jambonz D

Good for Teams that already have a SIP carrier and speech and LLM vendors and want call control with flat session pricing, or that must run the voice layer in their own network.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No status page, uptime SLA, security.txt, SECURITY.md or published advisory was found for jambonz.cloud or the repositories

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 36
  • Schema & documentation, 84 against 78
  • Agent ergonomics, 66 against 54
  • Security & auth, 61 against 42
  • Maintenance & community, 90 against 78
  • Transparency & trust, 75 against 50

Also in its favour

  • No incidents deducted, where jambonz loses 3 points for them

Watch for

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

Score by category

CategoryWeight this runjambonzLiveKit TelephonyEdge
Reliability16%203665LiveKit Telephony +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27884LiveKit Telephony +6
Agent ergonomics13%16.25466LiveKit Telephony +12
Security & auth14%17.54261LiveKit Telephony +19
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87890LiveKit Telephony +12
Transparency & trust7%8.85075LiveKit Telephony +25
Negative events≤15-30
Total49.2 · D67.5 · B

Facts side by side

FactjambonzLiveKit Telephony
KindHTTP APIHTTP API
VendorFirstFive8, Inc.LiveKit Incorporated
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
LicenceProprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MITProprietary 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 documentednono
llms.txtyesyes
Last release2026-10-042026-10-08
Terms last updated2021-05-04no date given
Privacy policy last updated2021-05-04no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot 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
Popularity103 stars, 1.4k npm/wk, 420 PyPI/wk480 stars, 2.9M npm/wk, 1.7M PyPI/wk

Verdicts

jambonz

OpenAPI 3.1 and AsyncAPI documents, an llms.txt and Markdown pages cover the REST and WebSocket APIs, and session prices are public. No status page, security.txt or advisory was found, API keys carry no scopes, and the 2021 privacy policy says audio is never stored while the October 2026 release notes say support keeps call audio for a few days.

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

jambonz

  1. Send Authorization: Bearer <token> to https://api.jambonz.cloud/v1, the server in the OpenAPI files. The REST introduction page gives https://jambonz.cloud/api instead, so confirm the base URL with the operator
  2. Create a call with from, to and either application_sid or call_hook. Do not retry a timed-out create without checking GET /Accounts/{AccountSid}/Calls first
  3. Read ratelimit-remaining and ratelimit-reset on every response and stop when a 429 arrives
  4. Append #rc=3&rp=5xx,ct to an application URL to turn on webhook retries. HTTP webhooks are not retried by default
  5. Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services

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, jambonz or LiveKit Telephony?

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

Do jambonz and LiveKit Telephony need an API key?

Both need an API key.

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

No hosted endpoint is listed for jambonz. No hosted endpoint is listed for LiveKit Telephony.

Are jambonz and LiveKit Telephony open source?

Yes. jambonz is open source (Proprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MIT). 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 jambonz 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