Head to head · SIP trunking · October 2026 research run

DIDWW Voice and Number Management API vs jambonz

DIDWW Voice and Number Management API scores 65.1 (B) on agent readiness against jambonz's 49.2 (D), and leads in 6 of 7 scored categories. jambonz leads on payments & pricing. Both do sip trunking.

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

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

  • Reliability, 66 against 36
  • Schema & documentation, 87 against 78
  • Agent ergonomics, 77 against 54
  • Security & auth, 57 against 42
  • Maintenance & community, 83 against 78
  • Transparency & trust, 70 against 50

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where jambonz loses 3 points for them

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

jambonz D

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

Ahead on

  • Payments & pricing, 40 against 15

Also in its favour

  • Open source

Watch for

No status page, uptime SLA, security.txt, SECURITY.md or published advisory was found for jambonz.cloud or the repositories

Score by category

CategoryWeight this runDIDWW Voice and Number Management APIjambonzEdge
Reliability16%206636DIDWW Voice and Number Management API +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28778DIDWW Voice and Number Management API +9
Agent ergonomics13%16.27754DIDWW Voice and Number Management API +23
Security & auth14%17.55742DIDWW Voice and Number Management API +15
Payments & pricing10%12.51540jambonz +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88378DIDWW Voice and Number Management API +5
Transparency & trust7%8.87050DIDWW Voice and Number Management API +20
Negative events≤150-3
Total65.1 · B49.2 · D

Facts side by side

FactDIDWW Voice and Number Management APIjambonz
KindHTTP APIHTTP API
VendorDIDWW Ireland LimitedFirstFive8, Inc.
Hosted endpointhttps://api.didww.com/mcpno (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePaid
x402nono
LicenceProprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MITProprietary. 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
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-10-04
Terms last updatedno date given2021-05-04
Privacy policy last updatedno date given2021-05-04
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity10 stars, 462 npm/wk103 stars, 1.4k npm/wk, 420 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.

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.

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

jambonz

  1. Send Authorization: Bearer <token> 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
  2. 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
  3. Read ratelimit-remaining and ratelimit-reset on every response and stop when a 429 arrives
  4. Append #rc=3&rp=5xx,ct to an application URL to turn on webhook retries. HTTP webhooks are not retried by default
  5. Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services

Questions

Which is better for AI agents, DIDWW Voice and Number Management API or jambonz?

DIDWW Voice and Number Management API scores 65.1 (B) on agent readiness against jambonz's 49.2 (D), and leads in 6 of 7 scored categories. jambonz leads on payments & pricing.

Do DIDWW Voice and Number Management API and jambonz need an API key?

Both need an API key.

Can an agent call DIDWW Voice and Number Management API and jambonz 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 jambonz.

Are DIDWW Voice and Number Management API and jambonz open source?

No open-source release is listed for DIDWW Voice and Number Management API. 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).

Other comparisons with DIDWW Voice and Number Management API or jambonz

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.