Get an audit

Head to head · Phone numbers · October 2026 research run

DIDWW Voice and Number Management API vs Vonage Voice API + MCP

DIDWW Voice and Number Management API scores 65.1 (B) on agent readiness against Vonage Voice API + MCP's 58.9 (C), and leads in 4 of 7 scored categories. Vonage Voice API + MCP leads on payments & pricing. 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 Vonage Voice API + MCPVonage (Ericsson) · HTTP API C58.9/100#568 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

  • Reliability, 66 against 45
  • Agent ergonomics, 77 against 60
  • Maintenance & community, 83 against 78
  • Transparency & trust, 70 against 47

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

Vonage Voice API + MCP C

Good for Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.

Ahead on

  • Payments & pricing, 35 against 15

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

First call needs an application, a private key and a signed JWT

Score by category

CategoryWeight this runDIDWW Voice and Number Management APIVonage Voice API + MCPEdge
Reliability16%206645DIDWW Voice and Number Management API +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28788Vonage Voice API + MCP +1
Agent ergonomics13%16.27760DIDWW Voice and Number Management API +17
Security & auth14%17.55760Vonage Voice API + MCP +3
Payments & pricing10%12.51535Vonage Voice API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88378DIDWW Voice and Number Management API +5
Transparency & trust7%8.87047DIDWW Voice and Number Management API +23
Negative events≤1500
Total65.1 · B58.9 · C

Facts side by side

FactDIDWW Voice and Number Management APIVonage Voice API + MCP
KindHTTP APIHTTP API
VendorDIDWW Ireland LimitedVonage (Ericsson)
Hosted endpointhttps://api.didww.com/mcphttps://api.nexmo.com/v1
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
Price for phone numbersnot published$0.005 per minute of call
x402nono
LicenceProprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MITnone
Tools exposednone14
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last release2026-10-072026-09-16
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity10 stars, 462 npm/wk154k npm/wk, 67k PyPI/wk
Agent reviewsnone2.5/5 (2)

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.

Vonage Voice API + MCP

Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.

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

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Questions

Which is better for AI agents, DIDWW Voice and Number Management API or Vonage Voice API + MCP?

DIDWW Voice and Number Management API scores 65.1 (B) on agent readiness against Vonage Voice API + MCP's 58.9 (C), and leads in 4 of 7 scored categories. Vonage Voice API + MCP leads on payments & pricing.

Do DIDWW Voice and Number Management API and Vonage Voice API + MCP need an API key?

DIDWW Voice and Number Management API needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.

Can an agent call DIDWW Voice and Number Management API and Vonage Voice API + MCP without installing anything?

Yes. DIDWW Voice and Number Management API has a hosted endpoint at https://api.didww.com/mcp and Vonage Voice API + MCP at https://api.nexmo.com/v1.

Other comparisons with DIDWW Voice and Number Management API or Vonage Voice API + MCP

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