# DIDWW Voice and Number Management API vs LiveKit Telephony

> LiveKit Telephony scores 67.5 (B) to DIDWW Voice and Number Management's 65.1 (B) for phone numbers. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony
- Markdown: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.md (~3,150 tokens)
- Slim: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-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

LiveKit Telephony scores 67.5 (B) on agent readiness against DIDWW Voice and Number Management API's 65.1 (B), and leads in 4 of 7 scored categories. DIDWW Voice and Number Management API leads on agent ergonomics. Both do phone numbers.

- DIDWW Voice and Number Management API: grade B, 65.1/100, rank #330 of 950. Markdown https://www.anchorterminal.com/tools/didww-voice-and-number-management.md · JSON https://www.anchorterminal.com/api/v1/tools/didww-voice-and-number-management.json
- LiveKit Telephony: grade B, 67.5/100, rank #253 of 950. 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 78 calling comparisons: https://www.anchorterminal.com/compare/voice-calling/index.md

## Which one, for what

### DIDWW Voice and Number Management API (B)

Good for: Teams that run their own SIP system, or a voice agent platform that accepts SIP trunks, and need numbers in many countries with compliance records handled through an API.

Ahead on:
- Agent ergonomics, 77 against 66

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: No per-number or per-minute price is published. Price lists are sent on request or shown inside an account, and a $30 balance is needed before ordering

### 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:
- Payments & pricing, 40 against 15
- Maintenance & community, 90 against 83
- Transparency & trust, 75 against 70

Also in its favour:
- Open source

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


## Score by category

| Category | Weight | DIDWW Voice and Number Management API | LiveKit Telephony | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 66 | 65 | DIDWW Voice and Number Management API +1 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 84 | DIDWW Voice and Number Management API +3 |
| Agent ergonomics | 13% (16.2 this run) | 77 | 66 | DIDWW Voice and Number Management API +11 |
| Security & auth | 14% (17.5 this run) | 57 | 61 | LiveKit Telephony +4 |
| Payments & pricing | 10% (12.5 this run) | 15 | 40 | LiveKit Telephony +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 90 | LiveKit Telephony +7 |
| Transparency & trust | 7% (8.8 this run) | 70 | 75 | LiveKit Telephony +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **65.1 · B** | **67.5 · B** | |

## Facts side by side

| Fact | DIDWW Voice and Number Management API | LiveKit Telephony |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | DIDWW Ireland Limited | LiveKit Incorporated |
| Hosted endpoint | `https://api.didww.com/mcp` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| Price for phone numbers | not published | $1 per month (plan) |
| x402 | no | no |
| Licence | Proprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-07 | 2026-10-08 |
| 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 | not found in the text | yes |
| Popularity | 10 stars, 462 npm/wk | 480 stars, 2.9M npm/wk, 1.7M PyPI/wk |

## Verdicts

**DIDWW Voice and Number Management API.** An OpenAPI 3.0.3 document with 107 operations, Markdown docs, a free sandbox and SDKs in seven languages cover number ordering and SIP trunk set-up. No per-number or per-minute price is public, API keys carry no scopes, orders have no idempotency key, and outbound calling needs an approved application. Calls travel over SIP only.

**LiveKit Telephony.** Signed tokens separate the right to dial (`sip.call`) from the right to manage trunks (`sip.admin`), and per-minute prices are public with a free plan that needs no card. LiveKit's own phone numbers are US only and inbound only, so outbound calls need a third-party SIP trunk, and no 429 or retry guidance was found.

## Before you call either

### DIDWW Voice and Number Management API

1. Send `Api-Key: <key>` with no `Bearer` prefix, plus `Accept: application/vnd.api+json`, and `Content-Type: application/vnd.api+json` on every request with a body
2. Set `X-DIDWW-API-Version: 2026-04-16` on each request and read `meta.api_version` in the reply. A header older than the account's version is ignored
3. Before retrying a timed-out `POST /orders`, list `GET /orders` first. The order is charged to the balance at once and no idempotency key exists
4. Stay under 20 requests a second per key. On `429` wait before retrying, since no `Retry-After` header is documented
5. Use `fields[...]`, `filter[...]`, `include` and `page[size]` (default 50, maximum 100) to keep JSON:API replies small
6. Check `GET /address_requirements` before buying a number. Many countries need a verified identity and address, and the sandbox cannot run identity verification
7. Create and enable a callback secret in the User Panel before relying on callbacks. Without one nothing is sent, and receivers must verify `X-DIDWW-Signature`

### LiveKit Telephony

1. Ask the operator for a short-lived token with only the `sip.call` grant to dial or transfer. Trunk, dispatch rule and number changes need `sip.admin`
2. Use a third-party outbound trunk for outbound calls. LiveKit Phone Numbers only receive calls
3. Set `wait_until_answered` on `CreateSIPParticipant` and read the SIP status on `SipCallError` before retrying. Voicemail answers with 200 OK
4. Send every request as a JSON POST to `/twirp/livekit.SIP/<Method>` or `/twirp/livekit.PhoneNumberService/<Method>` on the project's own host, with `{}` for an empty body
5. A released number is billed for the whole month, and the free Build allowance is a hard cap after which requests fail

## Questions

### Which is better for AI agents, DIDWW Voice and Number Management API or LiveKit Telephony?

LiveKit Telephony scores 67.5 (B) on agent readiness against DIDWW Voice and Number Management API's 65.1 (B), and leads in 4 of 7 scored categories. DIDWW Voice and Number Management API leads on agent ergonomics.

### Do DIDWW Voice and Number Management API and LiveKit Telephony need an API key?

Both need an API key.

### Can an agent call DIDWW Voice and Number Management API and LiveKit Telephony without installing anything?

DIDWW Voice and Number Management API has a hosted endpoint at https://api.didww.com/mcp. No hosted endpoint is listed for LiveKit Telephony.

### Are DIDWW Voice and Number Management API and LiveKit Telephony open source?

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

## Other comparisons with DIDWW Voice and Number Management API or LiveKit Telephony

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