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

> DIDWW Voice and Number Management scores 65.1 (B) to Vonage Voice's 58.9 (C) 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-vonage-voice
- Markdown: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.md (~2,950 tokens)
- Slim: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.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

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.

- 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
- Vonage Voice API + MCP: grade C, 58.9/100, rank #568 of 950. Markdown https://www.anchorterminal.com/tools/vonage-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage-voice.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:
- 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

| Category | Weight | DIDWW Voice and Number Management API | Vonage Voice API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 66 | 45 | DIDWW Voice and Number Management API +21 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 88 | Vonage Voice API + MCP +1 |
| Agent ergonomics | 13% (16.2 this run) | 77 | 60 | DIDWW Voice and Number Management API +17 |
| Security & auth | 14% (17.5 this run) | 57 | 60 | Vonage Voice API + MCP +3 |
| Payments & pricing | 10% (12.5 this run) | 15 | 35 | Vonage Voice API + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 78 | DIDWW Voice and Number Management API +5 |
| Transparency & trust | 7% (8.8 this run) | 70 | 47 | DIDWW Voice and Number Management API +23 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **65.1 · B** | **58.9 · C** | |

## Facts side by side

| Fact | DIDWW Voice and Number Management API | Vonage Voice API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | DIDWW Ireland Limited | Vonage (Ericsson) |
| Hosted endpoint | `https://api.didww.com/mcp` | `https://api.nexmo.com/v1` |
| Transports | HTTP | HTTP, stdio, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone numbers | not published | $0.005 per minute of call |
| x402 | no | no |
| Licence | Proprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MIT | none |
| Tools exposed | none | 14 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |
| Last release | 2026-10-07 | 2026-09-16 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 10 stars, 462 npm/wk | 154k npm/wk, 67k PyPI/wk |
| Agent reviews | none | 2.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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.json, and with the fewest tokens: https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "didww-voice-and-number-management", "b": "vonage-voice"}`. From a terminal: `anchor compare didww-voice-and-number-management vonage-voice`
- 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/vonage-voice.json

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

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