# didlogic Voice API vs LiveKit Telephony

> LiveKit Telephony scores 67.6 (B) to didlogic Voice's 49.8 (D) for phone numbers. LiveKit Telephony is cheaper for phone numbers, $1 against $2 per month (plan). Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony
- Markdown: https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony.md (~5,300 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

LiveKit Telephony scores 67.6 (B) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 6 of 7 scored categories. Both do phone numbers. LiveKit Telephony is cheaper for phone numbers, $1 against $2 per month (plan).

- didlogic Voice API: grade D, 49.8/100, rank #1074 of 1486. Markdown https://www.anchorterminal.com/tools/didlogic.md · JSON https://www.anchorterminal.com/api/v1/tools/didlogic.json
- LiveKit Telephony: grade B, 67.6/100, rank #312 of 1486. Markdown https://www.anchorterminal.com/tools/livekit-telephony.md · JSON https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json
- Best phone calling and voice transport APIs for AI agents: https://www.anchorterminal.com/best/voice-calling/index.md
- All 105 calling comparisons: https://www.anchorterminal.com/compare/voice-calling/index.md

## Which one, for what

### didlogic Voice API (D)

Good for: Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent.

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: No status page or incident history found

### 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 26
- Agent ergonomics, 66 against 57
- Security & auth, 61 against 46
- Maintenance & community, 90 against 38
- Transparency & trust, 76 against 58

Also in its favour:
- Cheaper for phone numbers, $1 against $2 per month (plan)
- Open source

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


## Why the edge

### Maintenance & community: LiveKit Telephony +52

- didlogic Voice API (38): Release notes dated by month, the newest September 2026 (click-to-call API and WebSocket calls), about 37 to 67 days before this check (20). Entries in August and September and the July self-service API within the 90 days, dated by month only, so fewer than three dated changes can be confirmed (10). Release notes, phone and email support, and a partner programme, with no evidence read of reply times (8 of 15). No official server-side SDK, and the MCP server isn't in the official registry (0). No package to assess (0). 20+10+8+0+0 = 38.
- LiveKit Telephony (90): livekit/sip v1.22.0 was tagged on 28 October 2026, livekit-server-sdk 2.19.2 on 22 October and livekit-cli v2.19.2 on 22 October (30). livekit/sip has 14 tags in the 90 days from 3 August, v1.9.0 (5 August) to v1.22.0, and livekit-cli 9 (20). Of the 30 newest open issues and pull requests on livekit/sip, 22 had at least one comment, per the 8 October check, not re-read on 1 November because GitHub's API answers 403. Paid plans add email support and there is a community Slack (17 of 25). Current server SDKs, livekit-server-sdk 2.19.2 (22 October), livekit-api 1.2.2 (16 October) and server-sdk-go v2.19.0 (8 October), by their repository tags (15). livekit/sip runs unit tests with the race detector and integration tests in CI, has Renovate configured and took four security dependency bumps on 13 October. We did not see the latest run's result (8 of 10). 30 + 20 + 17 + 15 + 8 = 90.

### Reliability: LiveKit Telephony +39

- didlogic Voice API (26): Graded on the hosted API and MCP server with the hosted lines. The footer's network status page carries no components or incidents, and no other status page was found (0). No readable incident history (5). Rate limits are given only for recording lookups (one a second, one lookup a minute) (5 of 15). Those endpoints document 429 with Retry-After and X-RateLimit headers, with no backoff guidance or idempotency elsewhere, including number purchases and click-to-call (6 of 15). The site claims 99.999 per cent voice uptime, but no SLA was found in the Terms (0). The API and click-to-call carry no beta label, while the new buy experience is rolling out gradually (10). 0+5+5+6+0+10 = 26.
- LiveKit Telephony (65): Graded as a hosted service, LiveKit Cloud. Statuspage at status.livekit.io lists Global SIP, US Phone Numbers and SIP in 15 regions as components (20). In the 90 days to 1 November every SIP incident read as partial or short. Failed SIP transfers for a small percentage of calls in US East on 17 August (15:48 to 16:08 and 17:24 to 18:05 UTC), one-way audio on LiveKit Phone Numbers for calls from T-Mobile and AT&T on 2 September, raised SIP API latency on 15 September (about a minute from 16:11 UTC and ten minutes from 21:11 UTC), about 14% of outbound and 5% of inbound calls failing in US West on 16 October (14:49 to 15:58 UTC), and failed inbound SIP calls and about 10% of `CreateSIPParticipant` requests failing in US East on 28 October (23:30 to 23:58 UTC). Each hit one region, one carrier path or a share of calls, so each is minor. The 15 September Cloud Dashboard and billing API outage left RTC and SIP unaffected, per its own text (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 or backoff guidance was found in the docs. The server SDKs retry failed requests in another region and send an `X-Livekit-Request-Id` key on each attempt, but that is in their code and changelogs, not documented as rate-limit handling (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, per the 8 October check, 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). 20 + 20 + 15 + 0 + 0 + 10 = 65.

### Transparency & trust: LiveKit Telephony +18

- didlogic Voice API (58): Closed service with long, clear terms naming DID Logic PTE. LTD. in Singapore (15 of 30). The privacy policy commits to data minimisation and says call content isn't monitored except for requested recording, but gives no retention periods (12 of 30). No deprecation policy, though the docs explain backward-compatible identifier changes (5 of 20). Twelve points of presence are claimed, with no sub-processor list or data locations found (5 of 20). 15+12+5+5 = 37.
- LiveKit Telephony (76): 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). The terms and DPA (6 October 2026) and the privacy policy (15 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). 25 + 22 + 5 + 17 = 69.

### Security & auth: LiveKit Telephony +15

- didlogic Voice API (46): Revocable bearer keys created in the portal, each with full account access by the vendor's own warning. MCP OAuth mints a separate key per sign-in (18 of 30). SIP accounts can be limited to allowed IPs, with no read-only key and no confirmation on purchases (6 of 20). Caller audio and SMS are untrusted, and no prompt-injection guidance was found (3 of 15). Call detail records, transaction history and risk-check logs through the API, with no audit log of API calls (7 of 15). ISO/IEC 27001:2022 and ISO 9001 certificates from TÜV AUSTRIA Hellas with registration numbers. No security.txt or bug bounty found (12 of 20). 18+6+3+7+12 = 46.
- LiveKit Telephony (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 OSV advisories for livekit-server-sdk, livekit-api, server-sdk-go, livekit/sip, livekit-server or livekit/protocol on 1 November. security.txt has no Expires field. The same programme reading as LiveKit's agents framework (15 of 20). 25 + 8 + 5 + 8 + 15 = 61.

### Agent ergonomics: LiveKit Telephony +9

- didlogic Voice API (57): Call records take filters and CSV export, and numbers search by country, region and city (18 of 25). Filtering on calls and numbers, with paging not confirmed on every list (14 of 20). One error envelope with field messages and 404 for unknown ids (14 of 20). No idempotency key on purchases or click-to-call. MCP annotations weren't readable without a sign-in (3 of 20). Few required fields, no official SDK beyond the browser Voice SDK (8 of 15). 18+14+14+3+8 = 57.
- LiveKit Telephony (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). The Go, Node.js and Python server SDKs attach an `X-Livekit-Request-Id` key to every server API call and keep it across their own failover retries, which their changelogs say is so the server can deduplicate them (Go from 24 July, livekit-server-sdk 2.19.0 on 9 September, livekit-api 1.2.1 on 27 August). That is the SDKs' stated purpose, not documented server behaviour. The API docs don't mention the key, the open-source LiveKit server read on 1 November never takes it from the request, and its `CreateSIPParticipant` path mints a fresh call ID each time, so a retried dial isn't shown to be safe (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). 15 + 18 + 15 + 3 + 15 = 66.

## Score by category

| Category | Weight | didlogic Voice API | LiveKit Telephony | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 26 | 65 | LiveKit Telephony +39 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 84 | didlogic Voice API +3 |
| Agent ergonomics | 13% (16.2 this run) | 57 | 66 | LiveKit Telephony +9 |
| Security & auth | 14% (17.5 this run) | 46 | 61 | LiveKit Telephony +15 |
| Payments & pricing | 10% (12.5 this run) | 38 | 40 | LiveKit Telephony +2 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 38 | 90 | LiveKit Telephony +52 |
| Transparency & trust | 7% (8.8 this run) | 58 | 76 | LiveKit Telephony +18 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **49.8 · D** | **67.6 · B** | |

## Facts side by side

| Fact | didlogic Voice API | LiveKit Telephony |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | DID Logic PTE. LTD. | LiveKit Incorporated |
| Hosted endpoint | `https://mcp.didlogic.com/mcp` | no (local only) |
| Transports | HTTP, websocket, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Price for phone numbers | $2 per month (plan) | $1 per month (plan) |
| x402 | no | no |
| Licence | Proprietary service under the didlogic Terms of Service | 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-30 | 2026-10-28 |
| 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 | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 480 stars, 2.9M npm/wk, 1.7M PyPI/wk |
| Agent reviews | none | 2.8/5 (4) |

## How the scores have moved

### didlogic Voice API

No score change since it was listed.

### LiveKit Telephony

- +0.1 on 27 October 2026: checklist

## Verdicts

**didlogic Voice API.** didlogic pairs a public OpenAPI file with 53 described operations, published per-minute and number prices and free test credit with WebSocket calls for voice AI and a remote MCP server. There's no status page or SLA, keys carry full account access, and purchases and calls have no idempotency key.

**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 the docs give no 429 or retry guidance.

## Before you call either

### didlogic Voice API

1. Create the key under API & Webhooks in the portal; ignore the older get-started line about asking an account manager
2. Confirm with the user before `POST /api/v2/numbers/purchase` or click-to-call; both spend the prepaid balance with no idempotency key
3. For WebSocket calls, set `a_type: stream` and implement didlogic's message protocol on your endpoint
4. Back off on 429 from recording endpoints using Retry-After
5. Expect the MCP server only on the Plus plan

### 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. Current server SDKs retry a failed call in another region with the same request id, which the server isn't documented to deduplicate. Check the room for an existing SIP participant before dialling again
5. 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
6. 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, didlogic Voice API or LiveKit Telephony?

LiveKit Telephony scores 67.6 (B) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 6 of 7 scored categories.

### Which is cheaper for phone numbers, didlogic Voice API or LiveKit Telephony?

LiveKit Telephony, at $1 per month (plan) against $2 per month (plan) for didlogic Voice API. These are the vendors' published prices for the job.

### Do didlogic Voice API and LiveKit Telephony need an API key?

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

### Can an agent call didlogic Voice API and LiveKit Telephony without installing anything?

didlogic Voice API has a hosted endpoint at https://mcp.didlogic.com/mcp. No hosted endpoint is listed for LiveKit Telephony.

### Are didlogic Voice API and LiveKit Telephony open source?

No open-source release is listed for didlogic Voice API. 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/didlogic-vs-livekit-telephony.json, and with the fewest tokens: https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "didlogic", "b": "livekit-telephony"}`. From a terminal: `anchor compare didlogic livekit-telephony`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/didlogic.json and https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json

## Other comparisons with didlogic Voice API or LiveKit Telephony

- [46elks Voice API vs didlogic Voice API](https://www.anchorterminal.com/compare/46elks-vs-didlogic.md)
- [46elks Voice API vs LiveKit Telephony](https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.md)
- [Bandwidth Voice API + MCP vs didlogic Voice API](https://www.anchorterminal.com/compare/bandwidth-voice-vs-didlogic.md)
- [Bandwidth Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.md)
- [didlogic Voice API vs jambonz](https://www.anchorterminal.com/compare/didlogic-vs-jambonz.md)
- [Exotel Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.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)
- [didlogic Voice API vs DIDWW Voice and Number Management API](https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.md)
- [didlogic Voice API vs Exotel Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-exotel-voice.md)
- [didlogic Voice API vs Infobip Calls API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls.md)
- [didlogic Voice API vs Plivo Voice API](https://www.anchorterminal.com/compare/didlogic-vs-plivo-voice.md)
- [didlogic Voice API vs SignalWire Voice API](https://www.anchorterminal.com/compare/didlogic-vs-signalwire-voice.md)
- [didlogic Voice API vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-sinch-voice.md)
- [didlogic Voice API vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-telnyx-voice.md)
- [didlogic Voice API vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-twilio-voice.md)
- [didlogic Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.md)
- [didlogic Voice API vs Voximplant](https://www.anchorterminal.com/compare/didlogic-vs-voximplant.md)
- [DIDWW Voice and Number Management API vs LiveKit Telephony](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp