{ "data": { "a": { "slug": "jambonz", "name": "jambonz", "vendor": "FirstFive8, Inc.", "vendorUrl": "https://jambonz.org", "kind": "http-api", "category": "voice-calling", "summary": "jambonz is a programmable voice platform from FirstFive8 for calls over a customer's own SIP carriers. Applications control calls through a REST API, webhooks or a WebSocket API, on the hosted jambonz.cloud or a self-hosted cluster under a commercial licence.", "url": "https://www.anchorterminal.com/tools/jambonz", "markdownUrl": "https://www.anchorterminal.com/tools/jambonz.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/jambonz.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/jambonz.json", "repo": "https://github.com/jambonz/jambonz-feature-server", "license": "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", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@jambonz/sdk" }, { "registry": "pypi", "name": "jambonz-python-sdk" }, { "registry": "npm", "name": "@jambonz/mcp-schema-server" } ], "auth": "api-key", "authNotes": "A bearer token sent as `Authorization: Bearer \u003ctoken\u003e`, created in the jambonz.cloud portal or with `POST /ApiKeys` by an existing token. A token belongs to one account or one service provider and reaches everything that owner can. No scopes or read-only keys were found. Access is self-serve after a browser sign-up with email, Google or GitHub. Webhooks to the application are signed with a `Jambonz-Signature` header on the hosted platform, or protected with HTTP basic authentication.", "pricing": "paid", "pricingNotes": "jambonz.cloud costs $8 a concurrent session a month for 5 to 249 sessions, $6 for 250 to 499 and $5 for 500 or more, with no per-minute charge. A three-week trial comes first, and the terms describe choosing a subscription at its end. Self-hosted licences cost $7 a session a month or $2,000 a month for unlimited sessions on one cluster, after a 30-day trial of 10 sessions. Carrier minutes, phone numbers, speech and LLM usage are bought from other vendors. Air-gapped, OEM and Enterprise support prices are by quote (https://jambonz.org/pricing, checked 2026-10-08).", "priceSummary": "$8 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the three OpenAPI files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 103, "npmWeekly": 1368, "pypiWeekly": 420, "asOf": "2026-10-08" }, "docsUrl": "https://docs.jambonz.org", "llmsTxt": "https://docs.jambonz.org/llms.txt", "openapi": "https://docs.jambonz.org/openapi/rest-call-control.json", "capabilities": [ "voice.calls", "voice.sip", "voice.streaming", "voice.recording", "voice.agent" ], "tags": [ "hosted", "self-hosted", "sip", "webrtc", "open-source", "openapi", "llms-txt", "typescript", "python", "webhooks", "websocket", "free-trial" ], "lastRelease": "2026-10-04", "graded": true, "anchor": { "graded": true, "score": 49.2, "grade": "D", "agentReady": false, "rank": 712, "ranked": true, "rankOf": 842, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 78, "payments": 40, "reliability": 36, "schema": 78, "security": 42, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -3, "negativeNotes": [ "24 September 2026, fixed and documented. The 11.1.5 release notes list API server flaws found in a security review, among them privilege escalation in user management, accounts able to write operator-only fields and limits, and a call-logs route that could read arbitrary CloudWatch log groups. The 11.0.0 notes of 8 July 2026 also mention cross-account authorisation hardening. No advisory or CVE was published. 3 points, reduced because the fixes shipped and were disclosed (https://docs.jambonz.org/changelog/2026/9/24)" ], "verdict": "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.", "bestFor": "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.", "strengths": [ "Three OpenAPI 3.1 documents (10, 116 and 4 operations) and an AsyncAPI 2.6.0 document for the WebSocket channels are public", "The docs publish an llms.txt, every page as Markdown and a docs MCP server at `https://docs.jambonz.org/_mcp/server`", "Prices are per concurrent session a month ($8, $6 or $5 on the cloud), with no per-minute charge and recording and streaming included", "Six dated release notes from 14 August to 4 October 2026, each with a component version table and self-hosted upgrade notes", "The API server, feature server and both SDKs are public under MIT, and the same platform can run in the customer's own network" ], "weaknesses": [ "No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories", "The privacy policy of 4 May 2021 says audio is never stored. The 4 October 2026 release notes say support keeps SIP and RTP from calls for a few days", "API keys are bearer tokens for a whole account or service provider, with no scopes, no read-only key and no delete operation in the published reference", "The rate limit page gives 600 requests per 5 minutes per IP address. The 4 October release notes give 4,000 call creations a minute per account", "No idempotency key was found on `POST /Accounts/{AccountSid}/Calls`, so a retried request can place a second call", "jambonz sells no phone numbers or minutes. Every call needs a SIP trunk from another carrier and the customer's own speech vendor keys" ], "agentNotes": [ "Send `Authorization: Bearer \u003ctoken\u003e` 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", "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", "Read `ratelimit-remaining` and `ratelimit-reset` on every response and stop when a `429` arrives", "Append `#rc=3\u0026rp=5xx,ct` to an application URL to turn on webhook retries. HTTP webhooks are not retried by default", "Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.2 } ], "editorialScores": { "ergonomics": 54, "maintenance": 78, "payments": 40, "reliability": 36, "schema": 78, "security": 42, "transparency": 43 }, "provenanceScore": 57 }, "connect": { "install": "npm install @jambonz/sdk", "http": "POST https://api.jambonz.cloud/v1/Accounts/{AccountSid}/Calls\nAuthorization: Bearer \u003ctoken\u003e\nContent-Type: application/json" }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/jambonz" }, "area": "voice", "unitPrices": [ { "item": "Cloud, concurrent session (5 to 249 sessions)", "unit": "month", "usd": 8, "note": "monthly subscription, no per-minute charge" }, { "item": "Cloud, concurrent session (250 to 499 sessions)", "unit": "month", "usd": 6, "note": "monthly subscription" }, { "item": "Cloud, concurrent session (500 or more sessions)", "unit": "month", "usd": 5, "note": "monthly subscription" }, { "item": "Self-hosted licence, concurrent session", "unit": "month", "usd": 7, "note": "one cluster, keyed to its domain" }, { "item": "Self-hosted licence, unlimited sessions", "unit": "month", "usd": 2000, "note": "one cluster, keyed to its domain" }, { "item": "Installation support package", "unit": "tx", "usd": 1000, "note": "one-time fee for one month of installation support" } ], "provenance": { "legalEntity": "FirstFive8, Inc.", "domain": "jambonz.org", "domainRegistered": "2019-08-13", "endpointOnVendorDomain": false, "terms": "https://jambonz.org/terms", "privacy": "https://jambonz.org/privacy", "statusPage": "", "changelog": "https://docs.jambonz.org/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms link is the jambonz Terms of Use, labelled Terms of Service (Cloud) in the site footer, last updated 4 May 2021, between the user and FirstFive8, Inc of Charlestown, Massachusetts. Self-hosted and OEM customers have separate terms at https://jambonz.org/legal-terms-selfhosted and https://jambonz.org/legal-terms-oem.", "The privacy policy was last updated 4 May 2021. It says it is intended for residents of the United States. No data processing addendum or sub-processor list was found.", "The hosted API answers on jambonz.cloud (`https://api.jambonz.cloud/v1` in the OpenAPI files, `https://jambonz.cloud/api` in the REST introduction), a second domain of the vendor's. The schema MCP server is on jambonz.app.", "No status page is linked from jambonz.org, the docs or the jambonz.cloud landing page.", "https://jambonz.org/.well-known/security.txt returned 404. No `SECURITY.md` was found in jambonz-api-server, jambonz-feature-server, node-sdk or python-sdk.", "RDAP for jambonz.org gives a registration date of 2019-08-13.", "The cloud terms forbid crawling, indexing or storing pages of the Service in a non-transitory manner. robots.txt on jambonz.org, docs.jambonz.org and jambonz.cloud allows every path we read. The pages were read once and the copies deleted.", "docs.jambonz.org/llms.txt opens with a block headed Instructions for AI Agents (append `.md` for Markdown, connect to the docs MCP server). We recorded it and did not act on it." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jambonz.json" }, "answer": "LiveKit Telephony scores 67.5 (B) on agent readiness against jambonz's 49.2 (D), and leads in 6 of 7 scored categories.", "b": { "slug": "livekit-telephony", "name": "LiveKit Telephony", "vendor": "LiveKit Incorporated", "vendorUrl": "https://livekit.com", "kind": "http-api", "category": "voice-calling", "summary": "LiveKit Telephony connects phone calls to LiveKit rooms as SIP participants. On LiveKit Cloud it covers SIP trunks to outside carriers, US inbound phone numbers, dispatch rules and transfers, managed through a Twirp API, server SDKs and the `lk` CLI.", "url": "https://www.anchorterminal.com/tools/livekit-telephony", "markdownUrl": "https://www.anchorterminal.com/tools/livekit-telephony.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/livekit-telephony.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json", "repo": "https://github.com/livekit/sip", "license": "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", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "livekit-server-sdk" }, { "registry": "pypi", "name": "livekit-api" }, { "registry": "go", "name": "github.com/livekit/server-sdk-go/v2" } ], "auth": "api-key", "authNotes": "A project API key and secret, created in the LiveKit Cloud dashboard, sign a JWT sent as `Authorization: Bearer \u003ctoken\u003e`. The token's `sip` grant carries `admin` (trunks, dispatch rules, phone numbers) or `call` (`CreateSIPParticipant` and `TransferSIPParticipant`), and its lifetime is set by whoever signs it. Keys can be rotated in the dashboard and the secret is shown once. Access is self-serve after a browser sign-up. The CLI links a project with `lk cloud auth`, which opens a browser.", "pricing": "freemium", "pricingNotes": "Free Build plan with no card. It includes 1 US local number, 50 US local inbound minutes and 1,000 third-party SIP minutes a month as a hard cap. Ship starts at $50 a month and Scale at $500, with third-party SIP minutes at $0.004 and $0.003 past the allowance, US local inbound at $0.01 a minute, toll-free inbound at $0.02, local numbers $1 a month and toll-free $2. A third-party carrier bills its own trunk and number charges. A number released mid-month is billed for the full month. Enterprise is priced by sales (https://livekit.com/pricing.md, checked 2026-10-08).", "priceSummary": "$1 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the telephony docs, the SIP and Phone Numbers API references or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 480, "npmWeekly": 2938925, "pypiWeekly": 1673299, "asOf": "2026-10-08" }, "docsUrl": "https://docs.livekit.io/telephony/", "llmsTxt": "https://docs.livekit.io/telephony/llms.txt", "capabilities": [ "voice.calls", "voice.sip", "voice.numbers", "voice.transfer", "voice.streaming" ], "tags": [ "hosted", "sip", "open-source", "llms-txt", "cli", "typescript", "python", "go", "webhooks", "free-tier", "status-page", "soc2" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 67.5, "grade": "B", "agentReady": false, "rank": 234, "ranked": true, "rankOf": 842, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 90, "payments": 40, "reliability": 65, "schema": 84, "security": 61, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Token grants separate `sip.call` (dial and transfer) from `sip.admin` (trunks, dispatch rules, numbers), with a lifetime the issuer sets", "Free Build plan with no card has one US local number, 50 inbound minutes and 1,000 third-party SIP minutes a month", "Per-minute and per-number prices are public, also as Markdown at livekit.com/pricing.md", "The SIP service is open source under Apache 2.0, with 12 tagged releases from 10 July to 5 October 2026", "Status page lists SIP per region and US Phone Numbers as separate components" ], "weaknesses": [ "LiveKit Phone Numbers are US only and inbound only, and `TransferSIPParticipant` does not work on them yet", "Outbound calls need a trunk from another carrier, billed by that carrier on top of LiveKit's SIP minutes", "No 429, Retry-After or idempotency guidance was found for the SIP API, so a retried `CreateSIPParticipant` may dial twice", "The 99.99% uptime on the pricing page is an objective only, with no credits outside a written Enterprise agreement", "Sign-up and `lk cloud auth` need a person in a browser, and no machine payment protocol was found", "The terms bar benchmarking for competitive purposes without written consent" ], "agentNotes": [ "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`", "Use a third-party outbound trunk for outbound calls. LiveKit Phone Numbers only receive calls", "Set `wait_until_answered` on `CreateSIPParticipant` and read the SIP status on `SipCallError` before retrying. Voicemail answers with 200 OK", "Send every request as a JSON POST to `/twirp/livekit.SIP/\u003cMethod\u003e` or `/twirp/livekit.PhoneNumberService/\u003cMethod\u003e` on the project's own host, with `{}` for an empty body", "A released number is billed for the whole month, and the free Build allowance is a hard cap after which requests fail" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.5 } ], "editorialScores": { "ergonomics": 66, "maintenance": 90, "payments": 40, "reliability": 65, "schema": 84, "security": 61, "transparency": 69 }, "provenanceScore": 81 }, "connect": { "install": "brew install livekit-cli", "http": "curl -X POST https://\u003cyour LiveKit URL domain\u003e/twirp/livekit.SIP/ListSIPInboundTrunk \\\n\t-H \"Authorization: Bearer \u003ctoken-with-sip-admin\u003e\" \\\n\t-H 'Content-Type: application/json' \\\n\t-d '{}'" }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/livekit-telephony" }, "area": "voice", "unitPrices": [ { "item": "Third-party SIP minutes, Ship plan", "unit": "call-minute", "usd": 0.004, "note": "past 5,000 included minutes, carrier charges extra" }, { "item": "Third-party SIP minutes, Scale plan", "unit": "call-minute", "usd": 0.003, "note": "past 50,000 included minutes, carrier charges extra" }, { "item": "US local inbound minutes", "unit": "call-minute", "usd": 0.01, "note": "LiveKit Phone Numbers, past 100 (Ship) or 1,000 (Scale) included minutes" }, { "item": "US toll-free inbound minutes", "unit": "call-minute", "usd": 0.02, "note": "Ship and Scale only" }, { "item": "US local number", "unit": "month", "usd": 1, "note": "first number free on every plan" }, { "item": "US toll-free number", "unit": "month", "usd": 2, "note": "Ship and Scale only" }, { "item": "Ship plan", "unit": "month", "usd": 50, "note": "starting price" }, { "item": "Scale plan", "unit": "month", "usd": 500, "note": "starting price" } ], "provenance": { "legalEntity": "LiveKit Incorporated", "domain": "livekit.com", "domainRegistered": "2000-02-24", "endpointOnVendorDomain": false, "terms": "https://livekit.com/legal/terms-of-service", "privacy": "https://livekit.com/legal/privacy-policy", "statusPage": "https://status.livekit.io", "changelog": "https://github.com/livekit/sip/releases", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "livekit.io answers 308 to livekit.com. Docs stay at docs.livekit.io, the dashboard at cloud.livekit.io and the status page at status.livekit.io.", "The terms link is the Terms of Service Agreement for the Build, Ship and Scale plans of LiveKit Cloud, last updated 6 October 2026, between the customer and LiveKit Incorporated of San Francisco. Enterprise customers sign a separate agreement we did not see.", "The privacy policy was last updated 6 October 2026. A Data Processing Addendum of the same date is at https://livekit.com/legal/data-processing-addendum and the sub-processor list (10 September 2026) at https://livekit.com/legal/sub-processors.", "Each project's API answers on its own host under livekit.cloud and SIP at \u003csubdomain\u003e.sip.livekit.cloud, a second domain. LiveKit's disclosure policy lists *.livekit.cloud among its own systems.", "livekit.com/.well-known/security.txt gives security@livekit.io, a PGP key and the policy at https://livekit.com/security/policy. It has no Expires field. livekit.com/security.txt returns 404.", "No changelog page for LiveKit Cloud was found (livekit.com/changelog returns 404). Dated changes are in the livekit/sip release tags and `CHANGELOG.md` in livekit/protocol.", "RDAP for livekit.com gives a registration date of 2000-02-24, long before the company existed. RDAP for livekit.io returned no events.", "livekit/sip tagged v1.18.0 on 5 October 2026 and livekit-cli tagged v2.19.0 on 8 October 2026." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/livekit-telephony.json", "live": { "slug": "livekit-telephony", "vendorStatus": { "page": "https://status.livekit.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:41:47.741400325Z" }, "updatedAt": "2026-10-09T10:41:47.741400325Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "FirstFive8, Inc.", "b": "LiveKit Incorporated", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "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", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-04", "b": "2026-10-08", "name": "Last release" }, { "a": "2021-05-04", "b": "no date given", "name": "Terms last updated" }, { "a": "2021-05-04", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "103 stars, 1.4k npm/wk, 420 PyPI/wk", "b": "480 stars, 2.9M npm/wk, 1.7M PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "LiveKit Telephony scores 67.5 (B) on agent readiness against jambonz's 49.2 (D), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, jambonz or LiveKit Telephony?" }, { "answer": "Both need an API key.", "question": "Do jambonz and LiveKit Telephony need an API key?" }, { "answer": "No hosted endpoint is listed for jambonz. No hosted endpoint is listed for LiveKit Telephony.", "question": "Can an agent call jambonz and LiveKit Telephony without installing anything?" }, { "answer": "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).", "question": "Are jambonz and LiveKit Telephony open source?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "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.", "slug": "jambonz", "watchFor": "No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories" }, { "aheadOn": [ "Reliability, 65 against 36", "Schema \u0026 documentation, 84 against 78", "Agent ergonomics, 66 against 54", "Security \u0026 auth, 61 against 42", "Maintenance \u0026 community, 90 against 78", "Transparency \u0026 trust, 75 against 50" ], "also": [ "No incidents deducted, where jambonz loses 3 points for them" ], "goodFor": "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.", "slug": "livekit-telephony", "watchFor": "LiveKit Phone Numbers are US only and inbound only, and `TransferSIPParticipant` does not work on them yet" } ], "job": { "capability": "voice.calls", "name": "Voice calls" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz.json", "title": "Bandwidth Voice API + MCP vs jambonz", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.json", "title": "Bandwidth Voice API + MCP vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/exotel-voice-vs-jambonz.json", "title": "Exotel Voice API + MCP vs jambonz", "url": "https://www.anchorterminal.com/compare/exotel-voice-vs-jambonz" }, { "json": "https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.json", "title": "Exotel Voice API + MCP vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/infobip-calls-vs-jambonz.json", "title": "Infobip Calls API + MCP vs jambonz", "url": "https://www.anchorterminal.com/compare/infobip-calls-vs-jambonz" }, { "json": "https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony.json", "title": "Infobip Calls API + MCP vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice.json", "title": "jambonz vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice.json", "title": "jambonz vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice.json", "title": "jambonz vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice.json", "title": "jambonz vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice.json", "title": "jambonz vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.json", "title": "jambonz vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-voximplant.json", "title": "jambonz vs Voximplant", "url": "https://www.anchorterminal.com/compare/jambonz-vs-voximplant" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice.json", "title": "LiveKit Telephony vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice.json", "title": "LiveKit Telephony vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice.json", "title": "LiveKit Telephony vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice.json", "title": "LiveKit Telephony vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice.json", "title": "LiveKit Telephony vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.json", "title": "LiveKit Telephony vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.json", "title": "LiveKit Telephony vs Voximplant", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant" } ], "scores": [ { "by": 29, "edge": "livekit-telephony", "jambonz": 36, "key": "reliability", "livekit-telephony": 65, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "edge": "livekit-telephony", "jambonz": 78, "key": "schema", "livekit-telephony": 84, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 12, "edge": "livekit-telephony", "jambonz": 54, "key": "ergonomics", "livekit-telephony": 66, "name": "Agent ergonomics", "weight": 13 }, { "by": 19, "edge": "livekit-telephony", "jambonz": 42, "key": "security", "livekit-telephony": 61, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edge": "", "jambonz": 40, "key": "payments", "livekit-telephony": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "livekit-telephony", "jambonz": 78, "key": "maintenance", "livekit-telephony": 90, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 25, "edge": "livekit-telephony", "jambonz": 50, "key": "transparency", "livekit-telephony": 75, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony", "json": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.md", "slim": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.min.md" }, "markdown": "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.\n\n- jambonz: grade D, 49.2/100, rank #712 of 842. Markdown https://www.anchorterminal.com/tools/jambonz.md · JSON https://www.anchorterminal.com/api/v1/tools/jambonz.json\n- 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\n\n## Which one, for what\n\n### jambonz (D)\n\nGood 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.\n\nWatch for: No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories\n\n### LiveKit Telephony (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 65 against 36\n- Schema \u0026 documentation, 84 against 78\n- Agent ergonomics, 66 against 54\n- Security \u0026 auth, 61 against 42\n- Maintenance \u0026 community, 90 against 78\n- Transparency \u0026 trust, 75 against 50\n\nAlso in its favour:\n- No incidents deducted, where jambonz loses 3 points for them\n\nWatch for: LiveKit Phone Numbers are US only and inbound only, and `TransferSIPParticipant` does not work on them yet\n\n\n## Score by category\n\n| Category | Weight | jambonz | LiveKit Telephony | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 36 | 65 | LiveKit Telephony +29 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 84 | LiveKit Telephony +6 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 66 | LiveKit Telephony +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 61 | LiveKit Telephony +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 90 | LiveKit Telephony +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 50 | 75 | LiveKit Telephony +25 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **49.2 · D** | **67.5 · B** | |\n\n## Facts side by side\n\n| Fact | jambonz | LiveKit Telephony |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FirstFive8, Inc. | LiveKit Incorporated |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | 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 | 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-04 | 2026-10-08 |\n| Terms last updated | 2021-05-04 | no date given |\n| Privacy policy last updated | 2021-05-04 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 103 stars, 1.4k npm/wk, 420 PyPI/wk | 480 stars, 2.9M npm/wk, 1.7M PyPI/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### jambonz\n\n1. Send `Authorization: Bearer \u003ctoken\u003e` 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\n2. 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\n3. Read `ratelimit-remaining` and `ratelimit-reset` on every response and stop when a `429` arrives\n4. Append `#rc=3\u0026rp=5xx,ct` to an application URL to turn on webhook retries. HTTP webhooks are not retried by default\n5. Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services\n\n### LiveKit Telephony\n\n1. 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`\n2. Use a third-party outbound trunk for outbound calls. LiveKit Phone Numbers only receive calls\n3. Set `wait_until_answered` on `CreateSIPParticipant` and read the SIP status on `SipCallError` before retrying. Voicemail answers with 200 OK\n4. Send every request as a JSON POST to `/twirp/livekit.SIP/\u003cMethod\u003e` or `/twirp/livekit.PhoneNumberService/\u003cMethod\u003e` on the project's own host, with `{}` for an empty body\n5. A released number is billed for the whole month, and the free Build allowance is a hard cap after which requests fail\n\n## Questions\n\n### Which is better for AI agents, jambonz or LiveKit Telephony?\n\nLiveKit Telephony scores 67.5 (B) on agent readiness against jambonz's 49.2 (D), and leads in 6 of 7 scored categories.\n\n### Do jambonz and LiveKit Telephony need an API key?\n\nBoth need an API key.\n\n### Can an agent call jambonz and LiveKit Telephony without installing anything?\n\nNo hosted endpoint is listed for jambonz. No hosted endpoint is listed for LiveKit Telephony.\n\n### Are jambonz and LiveKit Telephony open source?\n\nYes. 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).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.json, and with the fewest tokens: https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"jambonz\", \"b\": \"livekit-telephony\"}`. From a terminal: `anchor compare jambonz livekit-telephony`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/jambonz.json and https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json\n\n## Other comparisons with jambonz or LiveKit Telephony\n\n- [Bandwidth Voice API + MCP vs jambonz](https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz.md)\n- [Bandwidth Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.md)\n- [Exotel Voice API + MCP vs jambonz](https://www.anchorterminal.com/compare/exotel-voice-vs-jambonz.md)\n- [Exotel Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.md)\n- [Infobip Calls API + MCP vs jambonz](https://www.anchorterminal.com/compare/infobip-calls-vs-jambonz.md)\n- [Infobip Calls API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony.md)\n- [jambonz vs Plivo Voice API](https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice.md)\n- [jambonz vs SignalWire Voice API](https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice.md)\n- [jambonz vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice.md)\n- [jambonz vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice.md)\n- [jambonz vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice.md)\n- [jambonz vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.md)\n- [jambonz vs Voximplant](https://www.anchorterminal.com/compare/jambonz-vs-voximplant.md)\n- [LiveKit Telephony vs Plivo Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice.md)\n- [LiveKit Telephony vs SignalWire Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice.md)\n- [LiveKit Telephony vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice.md)\n- [LiveKit Telephony vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice.md)\n- [LiveKit Telephony vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice.md)\n- [LiveKit Telephony vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.md)\n- [LiveKit Telephony vs Voximplant](https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "jambonz vs LiveKit Telephony", "url": "" } ], "description": "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. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "jambonz D 49.2", "LiveKit Telephony B 67.5", "scores" ], "h1": "jambonz vs LiveKit Telephony", "image": "https://www.anchorterminal.com/assets/og/compare-jambonz-vs-livekit-telephony.png", "path": "/compare/jambonz-vs-livekit-telephony", "published": "2026-10-01", "section": "tools", "title": "jambonz vs LiveKit Telephony for AI agents, D 49.2 vs B 67.5", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony" }, "tokens": { "markdown": 2650, "slim": 730 }, "version": 1 }