# LiveKit Telephony

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

- Canonical: https://www.anchorterminal.com/tools/livekit-telephony
- Markdown: https://www.anchorterminal.com/tools/livekit-telephony.md (~8,200 tokens)
- Slim: https://www.anchorterminal.com/tools/livekit-telephony.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/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

## Overview

**Grade B · 67.5/100 · rank #234 of 842 · #3 in Phone calling & voice transport · not agent-ready · confidence medium**


## Assessment

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.

## Facts

| Field | Value |
| --- | --- |
| Vendor | LiveKit Incorporated (https://livekit.com) |
| Kind | HTTP API |
| Category | Phone calling & voice transport (https://www.anchorterminal.com/categories/voice-calling) |
| Transport | HTTP |
| Auth | API key · A project API key and secret, created in the LiveKit Cloud dashboard, sign a JWT sent as `Authorization: Bearer <token>`. 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 ($1 / mo) · 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). |
| x402 | No · No x402, MPP or L402 in the telephony docs, the SIP and Phone Numbers API references or the pricing page (checked 2026-10-08). |
| Licence | 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 |
| Packages | npm: `livekit-server-sdk`; pypi: `livekit-api`; go: `github.com/livekit/server-sdk-go/v2` |
| Source | https://github.com/livekit/sip |
| Docs | https://docs.livekit.io/telephony/ |
| llms.txt | https://docs.livekit.io/telephony/llms.txt |
| Last release | 2026-10-08 |
| GitHub stars | 480 (as of 2026-10-08) |
| npm downloads / week | 2,938,925 |
| PyPI downloads / week | 1,673,299 |
| Countries with numbers | United States only for LiveKit Phone Numbers (local and toll-free, inbound only). Other countries through a third-party SIP trunk |
| SIP | Inbound and outbound trunks over UDP, TCP or TLS with SRTP. No SIP REGISTER, SIPREC or video. Tested with Twilio, Telnyx, Exotel, Plivo, Wavix, Sinch and didlogic |
| Media streams | Call audio joins a LiveKit room as a participant track over WebRTC. Connectors bridge Twilio calls over websockets and WhatsApp Business voice calls |
| Voice AI layer | LiveKit Agents joins the same room. Agent session minutes on LiveKit Cloud are $0.01 a minute past the plan allowance, with models billed separately |
| Recording | Through the separate Egress service, written to the customer's own S3, GCS or Azure bucket. Audio-only transcode from $0.005 a minute past the allowance on Ship |
| Transfer | `TransferSIPParticipant` sends SIP REFER for a cold transfer. Agent-assisted warm transfer runs through an Agents task marked beta, in Python only |
| Free tier | Build plan, $0, no card. 1 US local number, 50 inbound minutes and 1,000 third-party SIP minutes a month, as a hard cap |
| Rate limits | 1,000 Server API requests a minute per project. 100 local numbers on Ship and 300 on Scale. Outbound ringing timeout capped at 80 seconds |
| SLA | 99.99% uptime listed for every plan as an objective. The terms give no credits outside a written Enterprise agreement |
| Data retention | Telemetry up to 60 days by default. Call detail records kept as long as law or carrier rules require, with no fixed period stated |
| Regions | Global SIP endpoint by default. Region-pinned endpoints for aus, eu, india, japan, sa, uk and us. The pricing page lists region pinning for Scale and Enterprise |
| MCP server | Docs only, at https://docs.livekit.io/mcp. No MCP server for call control was found |
| 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 |
| JSON | https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json |

## Score breakdown (methodology v0.4, October 2026 research run)

Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 65 | 13.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 84 | 13.7 |
| Agent ergonomics | 13% | 16.2 | 66 | 10.7 |
| Security & auth | 14% | 17.5 | 61 | 10.7 |
| Payments & pricing | 10% | 12.5 | 40 | 5.0 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 90 | 7.9 |
| Transparency & trust (editorial 69, provenance 81) | 7% | 8.8 | 75 | 6.6 |
| Negative events | up to −15 | up to −15 | none recorded | 0 |
| **Total** | | | | **67.5 → B** |

### Why each score

- Reliability 65: Graded as a hosted service, LiveKit Cloud. Statuspage at status.livekit.io with SIP per region, Global SIP and US Phone Numbers as components (20). In the 90 days to 8 October the SIP incidents were all marked minor or none. Failed SIP transfers in US East ran about 72 minutes on 17 August, one-way audio on LiveKit Phone Numbers about 42 minutes on 2 September, and raised API latency on SIP twice on 15 September for about 70 minutes each. The two incidents marked major (2 and 15 September) hit the dashboard, analytics and billing API, not calls (20). The Server API limit is 1,000 requests a minute per project, with number limits of 100 on Ship and 300 on Scale (15). No 429, Retry-After, backoff or idempotency guidance was found for the SIP API (0). The pricing page lists 99.99% uptime for every plan, and section 2.5 of the terms calls such figures objectives with no credits outside a written Enterprise agreement, so no SLA is counted (0). The SIP API carries no beta label, though the warm transfer task in the Agents framework is marked beta, in Python only (10).
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 84: The contract is protobuf in livekit/protocol (17 SIP RPCs, 6 phone number RPCs), called as JSON over Twirp. No OpenAPI document was found, and we counted the protobuf files as the similar spec (25). llms.txt per docs section and every page as Markdown (10). Reference tables give each parameter's purpose, and the guides say when to use an inline trunk or a stored one (15 of 20). Typed fields with enums for transport, encryption and number status and required fields marked, with metadata as a free string (13 of 15). Examples in six languages and the CLI, a call outcome table and a troubleshooting guide by SIP code. No full list of Twirp errors was found, and the reference still shows `TransferSIPParticipant` returning an empty message where the protocol changelog says it now returns a response object (11 of 15). The Twirp path has no version. Changes are dated in livekit/sip release tags and the protocol `CHANGELOG.md`, with no cloud changelog page found (10 of 15).
- Agent ergonomics 66: List calls take a limit and ID, number or status filters, with no field selection (15 of 25). A `Pagination` type with `after_id` and `limit` on the SIP list calls (18 of 20). `wait_until_answered` returns a `SipCallError` with the carrier's SIP status code, and the docs map codes to outcomes. Twirp errors are named only in passing (15 of 20). No idempotency key was found, so a retried `CreateSIPParticipant` can place a second call (3 of 20). A call needs a trunk, a number and a room name, and SIP clients ship in Go, JavaScript, Python, Ruby, Kotlin and Rust plus the `lk` CLI (15).
- Security & auth 61: A project key and secret sign JWTs whose `sip` grant is `admin` or `call`, with a lifetime the signer sets. Keys rotate in the dashboard. The key pair itself can mint any grant, so scoping depends on the operator handing an agent a token and not the secret (25 of 30). `call` without `admin` is a least-privilege mode for dialling, inbound trunks can be limited by number, IP range or credentials, and no read-only grant or confirmation step for dialling or renting numbers was found (8 of 20). Calls carry untrusted caller speech, and no prompt-injection guidance was found in the telephony docs (5 of 15). The security overview says project configuration changes are logged, with export to a SIEM still on the roadmap, and the dashboard shows call logs (8 of 15). security.txt with a disclosure policy and safe harbour, a Hall of Fame with no cash bounty stated, SOC 2 Type II, six-monthly penetration tests, ISO 27001 in progress, and no published advisories on livekit/sip, livekit/livekit or livekit/livekit-cli (15 of 20).
- Payments & pricing 40: No x402, MPP or L402 found (0). Per-minute and per-number prices are public without a login, also as Markdown (20). The Build plan is free with no card and includes a US local number, 50 inbound minutes and 1,000 third-party SIP minutes a month (20). An account is created in a browser and `lk cloud auth` opens one, and no programmatic sign-up or key API was found (0).
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 90: livekit-cli v2.19.0 was tagged on 8 October 2026 and livekit/sip v1.18.0 on 5 October (30). livekit/sip has 12 tags from v1.7.0 on 10 July to v1.18.0 (20). Of the 30 newest open issues and pull requests on livekit/sip, 22 have at least one comment. We read the counts and not who replied. Paid plans add email support and there is a community Slack (17 of 25). Current server SDKs, with livekit-server-sdk 2.19.1 on npm and livekit-api 1.2.1 on PyPI from 27 August 2026 (15). livekit/sip runs unit tests with the race detector and integration tests in CI and has Renovate configured. We did not see the latest run's result (8 of 10).
- Transparency & trust 75: The SIP service, protocol, CLI and SDKs are Apache 2.0, and the security page says the same code runs on LiveKit Cloud. The cloud control plane and LiveKit Phone Numbers are closed, under clear terms (25 of 30). Terms, privacy policy and DPA all dated 6 October 2026 agree. The DPA lists retention by data category, user content is deleted after delivery unless recording is on, telemetry is kept up to 60 days and backups up to 30. Call detail records have no fixed period, and the sub-processor list names no telephony carrier for LiveKit Phone Numbers (22 of 30). No deprecation policy was found. Deprecated fields are flagged in the reference without dates, and the terms give 30 days' notice of changes to the agreement (5 of 20). The sub-processor list gives each entity, its activity and its country, all in the United States, with a way to subscribe to changes, and the docs list the SIP regions (17 of 20).

Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/livekit-telephony.md (JSON https://www.anchorterminal.com/fixes/livekit-telephony.json)

### What we couldn't check

- The lead gave livekit.io as the vendor's site. It now redirects to livekit.com, and the listing uses livekit.com
- Which carrier supplies LiveKit Phone Numbers. The sub-processor list of 10 September 2026 names none
- Whether unanswered or failed outbound attempts count as billed SIP minutes
- How long call detail records are kept. The terms say as long as law or carrier rules require
- Whether the SIP API returns 429 with a Retry-After header at the 1,000 requests a minute limit. No call was made to the API
- unchecked: trust.livekit.io, where the SOC 2 report and penetration test summaries sit behind an NDA request
- unchecked: the Enterprise agreement and its support and uptime SLA, which are not published
- unchecked: who answered the open issues on livekit/sip, and whether the latest CI run on its default branch passed
- unchecked: the Egress docs for recording a SIP call, so `voice.recording` is left out of the capabilities
- The npm and PyPI download counts are for the whole server SDKs, not for SIP use

### Sources

- telephony docs index: <https://docs.livekit.io/telephony/llms.txt> (seen 2026-10-08)
- telephony introduction and SIP support table: <https://docs.livekit.io/telephony.md> (seen 2026-10-08)
- LiveKit Phone Numbers, limits and CLI: <https://docs.livekit.io/telephony/start/phone-numbers.md> (seen 2026-10-08)
- SIP API reference: <https://docs.livekit.io/reference/telephony/sip-api.md> (seen 2026-10-08)
- Phone Numbers API reference: <https://docs.livekit.io/reference/telephony/phone-numbers-api.md> (seen 2026-10-08)
- outbound calls, call outcomes and SipCallError: <https://docs.livekit.io/telephony/making-calls/outbound-calls.md> (seen 2026-10-08)
- cold transfer by SIP REFER: <https://docs.livekit.io/telephony/features/transfers/cold.md> (seen 2026-10-08)
- agent-assisted transfer (beta workflow): <https://docs.livekit.io/telephony/features/transfers/warm.md> (seen 2026-10-08)
- answering machine detection: <https://docs.livekit.io/telephony/features/answering-machine-detection.md> (seen 2026-10-08)
- SIP region pinning: <https://docs.livekit.io/telephony/features/region-pinning.md> (seen 2026-10-08)
- Connectors API: <https://docs.livekit.io/reference/telephony/connectors-api.md> (seen 2026-10-08)
- SIP troubleshooting guide: <https://docs.livekit.io/reference/telephony/troubleshooting.md> (seen 2026-10-08)
- quotas, rate limits and metered resources: <https://docs.livekit.io/deploy/admin/quotas-and-limits.md> (seen 2026-10-08)
- access tokens and the SIP grant: <https://docs.livekit.io/frontends/authentication/tokens.md> (seen 2026-10-08)
- webhooks, signing and retries: <https://docs.livekit.io/intro/basics/rooms-participants-tracks/webhooks-events.md> (seen 2026-10-08)
- CLI install and project linking: <https://docs.livekit.io/reference/developer-tools/livekit-cli.md> (seen 2026-10-08)
- docs MCP server: <https://docs.livekit.io/reference/developer-tools/docs-mcp.md> (seen 2026-10-08)
- pricing as Markdown: <https://livekit.com/pricing.md> (seen 2026-10-08)
- terms of service, 6 October 2026: <https://livekit.com/legal/terms-of-service> (seen 2026-10-08)
- privacy policy, 6 October 2026: <https://livekit.com/legal/privacy-policy> (seen 2026-10-08)
- data processing addendum: <https://livekit.com/legal/data-processing-addendum> (seen 2026-10-08)
- sub-processor list, 10 September 2026: <https://livekit.com/legal/sub-processors> (seen 2026-10-08)
- security page and compliance: <https://livekit.com/security> (seen 2026-10-08)
- security overview: <https://livekit.com/security/overview> (seen 2026-10-08)
- vulnerability disclosure policy: <https://livekit.com/security/policy> (seen 2026-10-08)
- security.txt: <https://livekit.com/.well-known/security.txt> (seen 2026-10-08)
- robots.txt, no Content-Signal line: <https://livekit.com/robots.txt> (seen 2026-10-08)
- status incidents feed: <https://status.livekit.io/api/v2/incidents.json> (seen 2026-10-08)
- status components: <https://status.livekit.io/api/v2/components.json> (seen 2026-10-08)
- livekit/sip repository, tags and CI (shallow clone): <https://github.com/livekit/sip> (seen 2026-10-08)
- livekit/sip stars, licence and open issues: <https://api.github.com/repos/livekit/sip> (seen 2026-10-08)
- livekit-cli tags (shallow clone): <https://github.com/livekit/livekit-cli> (seen 2026-10-08)
- protocol definitions and changelog (shallow clone): <https://github.com/livekit/protocol> (seen 2026-10-08)
- livekit/sip advisories, none published: <https://api.github.com/repos/livekit/sip/security-advisories> (seen 2026-10-08)
- npm weekly downloads, livekit-server-sdk: <https://api.npmjs.org/downloads/point/last-week/livekit-server-sdk> (seen 2026-10-08)
- PyPI recent downloads, livekit-api: <https://pypistats.org/api/packages/livekit-api/recent> (seen 2026-10-08)
- RDAP for livekit.com: <https://rdap.org/domain/livekit.com> (seen 2026-10-08)

## Who's behind it (provenance 81/100, checked 2026-10-08)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | LiveKit Incorporated | 20/20 |
| Domain age | livekit.com, registered 2000-02-24 (26 years) | 15/15 |
| Endpoint on the vendor's domain |  is not on livekit.com | 0/15 |
| Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 |
| Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 |
| Status page | status.livekit.io | 10/10 |
| Changelog | published | 10/10 |
| security.txt | valid | 10/10 |

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 <subdomain>.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.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://livekit.com/legal/terms-of-service), read 2026-10-08, gives no date, states 6 of the 7 things a reader expects.

- To know. Restricts benchmarking or competitive use (costs points). "to build a competing product or service, or benchmark for competitive purposes, without LiveKit's"
- To know. Says access can be ended without notice or for any reason. "LiveKit may terminate the Services under the Build subscription plan at any time."
- To know. Requires arbitration or waives class actions. "Any dispute arising out of or relating to this Agreement will be resolved by final and binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules before one arbitrator in Santa Clara County, California, in English."
- Not found in the text. Gives the date it was last updated.
- Names the governing law or courts. The law of the State of California.
- States a limit on its liability. Capped at the greater of $1,000 and the fees paid in the 12 months before the claim.
- Says how changes to the terms are announced. Gives 10 days of notice before a change.
- Also in the text (2026-10-08). Use of the Services for a use case classed as high-risk under the EU AI Act needs LiveKit's prior written consent. "as high-risk under the AI Act, Customer must first obtain LiveKit's prior written consent and"
- Also in the text (2026-10-08). Third-party providers reached through the Services may train on data under their own terms, except providers used through LiveKit Inference. "Provider through the Services. Third-Party Service Providers may train on data as set forth in their"
- Also in the text (2026-10-08). The customer must export its data before termination, and LiveKit is not responsible for storing customer data afterwards. "After termination, LiveKit is not responsible for storing any Customer Data."

**Privacy policy** (https://livekit.com/legal/privacy-policy), read 2026-10-08, gives no date, states 6 of the 8 things a reader expects.

- Not found in the text. Gives the date it was last updated.
- Says how long data is kept. Names a period of twelve months.
- Not found in the text. Says whether personal data is sold or shared for advertising.
- Gives a privacy contact. privacy@livekit.io.
- Says where data is transferred or stored. Relies on the Data Privacy Framework.
- Also in the text (2026-10-08). The policy covers LiveKit's website and does not apply where LiveKit processes data as a processor for customers, such as through cloud.livekit.io. "This Privacy Policy does not apply to the extent we process information in the role of a processor or service provider on behalf of our customers"

## Live (updated 2026-10-09 10:41 UTC)

- Vendor status page: none, All Systems Operational
- Always current: https://www.anchorterminal.com/api/v1/live/livekit-telephony.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Prices

| Item | Price | Unit | Note |
| --- | --- | --- | --- |
| Third-party SIP minutes, Ship plan | $0.004 | per minute of call | past 5,000 included minutes, carrier charges extra |
| Third-party SIP minutes, Scale plan | $0.003 | per minute of call | past 50,000 included minutes, carrier charges extra |
| US local inbound minutes | $0.01 | per minute of call | LiveKit Phone Numbers, past 100 (Ship) or 1,000 (Scale) included minutes |
| US toll-free inbound minutes | $0.02 | per minute of call | Ship and Scale only |
| US local number | $1 | per month (plan) | first number free on every plan |
| US toll-free number | $2 | per month (plan) | Ship and Scale only |
| Ship plan | $50 | per month (plan) | starting price |
| Scale plan | $500 | per month (plan) | starting price |

Across all listings: https://www.anchorterminal.com/prices/index.md

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

## Before you call it (notes for agents)

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

## Connect

Install:

```bash
brew install livekit-cli
```

First request:

```bash
curl -X POST https://<your LiveKit URL domain>/twirp/livekit.SIP/ListSIPInboundTrunk \
	-H "Authorization: Bearer <token-with-sip-admin>" \
	-H 'Content-Type: application/json' \
	-d '{}'
```

Through letme (picks today, calling later): https://letme.dev/livekit-telephony. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Twilio Programmable Voice API + MCP | A | 80.4 | 9 | voice.calls, voice.numbers, voice.streaming, voice.sip, voice.transfer | no | https://www.anchorterminal.com/tools/twilio-voice.md |
| Telnyx Voice API + MCP | BB | 74.2 | 73 | voice.calls, voice.numbers, voice.streaming, voice.sip, voice.transfer | no | https://www.anchorterminal.com/tools/telnyx-voice.md |
| SignalWire Voice API | B | 67.1 | 242 | voice.calls, voice.numbers, voice.streaming, voice.sip, voice.transfer | no | https://www.anchorterminal.com/tools/signalwire-voice.md |
| Bandwidth Voice API + MCP | B | 63.7 | 338 | voice.calls, voice.numbers, voice.streaming, voice.sip, voice.transfer | no | https://www.anchorterminal.com/tools/bandwidth-voice.md |
| Sinch Voice API + MCP | B | 62.7 | 381 | voice.calls, voice.numbers, voice.streaming, voice.sip, voice.transfer | no | https://www.anchorterminal.com/tools/sinch-voice.md |
| Plivo Voice API | C | 60.4 | 466 | voice.calls, voice.numbers, voice.streaming, voice.sip, voice.transfer | no | https://www.anchorterminal.com/tools/plivo-voice.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- LiveKit Phone Numbers are US only and inbound only, and forwarding with `TransferSIPParticipant` is not yet supported on them (source: <https://docs.livekit.io/telephony/start/phone-numbers.md>)
- The SIP API has 17 RPCs and the Phone Numbers API 6, defined as protobuf in livekit/protocol and called as JSON over Twirp (source: <https://github.com/livekit/protocol/blob/main/protobufs/livekit_sip.proto>)
- Outbound trunk settings can be stored or passed inline on each `CreateSIPParticipant` call (source: <https://docs.livekit.io/telephony/making-calls/outbound-calls.md>)
- Answering machine detection classifies an outbound call as human, IVR, voicemail, unavailable or uncertain inside the Agents framework (source: <https://docs.livekit.io/telephony/features/answering-machine-detection.md>)
- The terms forbid emergency calls (911, 112) and benchmarking for competitive purposes without written consent (source: <https://livekit.com/legal/terms-of-service>)
- The server SDK download counts cover every LiveKit server API, of which SIP is one part
- LiveKit Agents, the framework that usually answers these calls, is a separate product and is not graded here

## Compare

- [Bandwidth Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.md): B 63.7 vs B 67.5
- [Exotel Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.md): E 39.4 vs B 67.5
- [Infobip Calls API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony.md): C 60.3 vs B 67.5
- [jambonz vs LiveKit Telephony](https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.md): D 49.2 vs B 67.5
- [LiveKit Telephony vs Plivo Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice.md): B 67.5 vs C 60.4
- [LiveKit Telephony vs SignalWire Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice.md): B 67.5 vs B 67.1
- [LiveKit Telephony vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice.md): B 67.5 vs B 62.7
- [LiveKit Telephony vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice.md): B 67.5 vs BB 74.2
- [LiveKit Telephony vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice.md): B 67.5 vs A 80.4
- [LiveKit Telephony vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.md): B 67.5 vs C 58.9
- [LiveKit Telephony vs Voximplant](https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.md): B 67.5 vs D 51.7

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on livekit.com or one of its subdomains, or the README of github.com/livekit/sip. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "livekit-telephony", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/livekit-telephony"><img src="https://www.anchorterminal.com/badges/livekit-telephony.svg" alt="LiveKit Telephony on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![LiveKit Telephony on Anchor Terminal](https://www.anchorterminal.com/badges/livekit-telephony.svg)](https://www.anchorterminal.com/tools/livekit-telephony)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/livekit-telephony">LiveKit Telephony on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say LiveKit Telephony is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/livekit-telephony-dark.png
- Light: https://www.anchorterminal.com/assets/share/livekit-telephony-light.png