Get an audit

Head to head · Phone numbers · October 2026 research run

DIDWW Voice and Number Management API vs 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. Both do phone numbers.

Best phone calling and voice transport APIs for AI agents · All 78 calling comparisons

DIDWW Voice and Number Management APIDIDWW Ireland Limited · HTTP API B65.1/100#330 of 950 LiveKit TelephonyLiveKit Incorporated · HTTP API B67.5/100#253 of 950

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

CategoryWeight this runDIDWW Voice and Number Management APILiveKit TelephonyEdge
Reliability16%206665DIDWW Voice and Number Management API +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28784DIDWW Voice and Number Management API +3
Agent ergonomics13%16.27766DIDWW Voice and Number Management API +11
Security & auth14%17.55761LiveKit Telephony +4
Payments & pricing10%12.51540LiveKit Telephony +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88390LiveKit Telephony +7
Transparency & trust7%8.87075LiveKit Telephony +5
Negative events≤1500
Total65.1 · B67.5 · B

Facts side by side

FactDIDWW Voice and Number Management APILiveKit Telephony
KindHTTP APIHTTP API
VendorDIDWW Ireland LimitedLiveKit Incorporated
Hosted endpointhttps://api.didww.com/mcpno (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per useFreemium
Price for phone numbersnot published$1 per month (plan)
x402nono
LicenceProprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MITProprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-10-08
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity10 stars, 462 npm/wk480 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).

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

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report