# didlogic Voice API vs DIDWW Voice and Number Management API (slim)

> DIDWW Voice and Number Management scores 64.7 (B) to didlogic Voice's 49.8 (D) for phone numbers. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.md (~5,650 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.json · canonical https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

DIDWW Voice and Number Management API scores 64.7 (B) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 5 of 7 scored categories. didlogic Voice API leads on payments & pricing. Both do phone numbers.

- didlogic Voice API: D 49.8, rank #1074 of 1486 · https://www.anchorterminal.com/tools/didlogic.min.md
- DIDWW Voice and Number Management API: B 64.7, rank #456 of 1486 · https://www.anchorterminal.com/tools/didww-voice-and-number-management.min.md
- didlogic Voice API, good for Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent. Ahead on Payments & pricing, 38 against 27. Also Free to start without a card; No incidents deducted, where DIDWW Voice and Number Management API loses 3 points for them.
- DIDWW Voice and Number Management API, 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, 71 against 26; Agent ergonomics, 77 against 57; Security & auth, 57 against 46; Maintenance & community, 83 against 38; Transparency & trust, 71 against 58.

| Category | didlogic Voice API | DIDWW Voice and Number Management API |
| --- | --- | --- |
| Reliability (16%) | 26 | 71 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 87 |
| Agent ergonomics (13%) | 57 | 77 |
| Security & auth (14%) | 46 | 57 |
| Payments & pricing (10%) | 38 | 27 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 38 | 83 |
| Transparency & trust (7%) | 58 | 71 |

| Fact (where they differ) | didlogic Voice API | DIDWW Voice and Number Management API |
| --- | --- | --- |
| Vendor | DID Logic PTE. LTD. | DIDWW Ireland Limited |
| Hosted endpoint | `https://mcp.didlogic.com/mcp` | `https://api.didww.com/mcp` |
| Transports | HTTP, websocket, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Price for phone numbers | $2 per month (plan) | not published |
| Licence | Proprietary service under the didlogic Terms of Service | Proprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MIT |
| Last release | 2026-09-30 | 2026-10-07 |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 10 stars, 462 npm/wk |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Reliability, DIDWW Voice and Number Management API +45: didlogic Voice API 26 (Graded on the hosted API and MCP server with the hosted lines. The footer's network status page carries no components or incidents, and no other status page was found (0). No readable incident history (5). Rate limits are given only for recording lookups (one a second, one lookup a minute) (5 of 15). Those endpoints document 429 with Retry-After and X-RateLimit headers, with no backoff guidance or idempotency elsewhere, including number purchases and click-to-call (6 of 15). The site claims 99.999 per cent voice uptime, but no SLA was found in the Terms (0). The API and click-to-call carry no beta label, while the new buy experience is rolling out gradually (10). 0+5+5+6+0+10 = 26.); DIDWW Voice and Number Management API 71 (Graded as a hosted service on the REST API v3. A public status page on Instatus lists eight components, among them DIDWW API, Inbound Voice and Outbound Voice (20). Its history feed, re-read on 2 November, shows no incident on the API component in the 90 days from 4 August. Every incident in the window is limited to one country or one product. They are Inbound Voice for Mexico numbers on 3 October (3 hours 56 minutes) and 29 October (4 hours 31 minutes), Inbound Voice for Guatemala numbers on 4 October (13 hours 9 minutes) and 25 October (22 hours 5 minutes), Inbound and Outbound Voice for Greece on 19 October (26 minutes) and Nigeria on 29 October (1 hour 50 minutes), Inbound SMS for Sweden on 21 October and phone.systems on 5 October. Partial incidents read as minor, whatever their length, so minor incidents only (20, was 15, a value off the checklist). Rate limits are published as 20 requests a second per API key (15). `429` is documented with advice to wait before retrying. No `Retry-After` header and no idempotency key were found for the REST API. Callbacks are retried nine times at a widening interval (6 of 15). No SLA was found, and the terms give no warranty of continuous service (0). API v3 is generally available with a sandbox. Outbound trunks need an approved application (10). 20+20+15+6+0+10 = 71.)
- Maintenance & community, DIDWW Voice and Number Management API +45: didlogic Voice API 38 (Release notes dated by month, the newest September 2026 (click-to-call API and WebSocket calls), about 37 to 67 days before this check (20). Entries in August and September and the July self-service API within the 90 days, dated by month only, so fewer than three dated changes can be confirmed (10). Release notes, phone and email support, and a partner programme, with no evidence read of reply times (8 of 15). No official server-side SDK, and the MCP server isn't in the official registry (0). No package to assess (0). 20+10+8+0+0 = 38.); DIDWW Voice and Number Management API 83 (The public OpenAPI document was regenerated on 8 and 22 October 2026 (the 22 October revision corrects the `include` pattern and price examples, with the API itself unchanged), and the TypeScript SDK v3.1.1 and Python SDK v3.2.0 were tagged on 7 October 2026 (30). The OpenAPI repository has dated revisions of the 2026-04-16 document on 20, 25 and 31 August, 14 and 16 September and 6, 8 and 22 October 2026 (20). As a closed service, responsiveness is read from the public changelog, a support address with a stated 24 hour service, and GitHub, where a pull request from a fork of the TypeScript SDK was merged on 3 September 2026, a day after its commit, per the 9 October check (11 of 15). Official SDKs for seven languages follow API version 2026-04-16 (15). The SDK repositories carry CI workflows, tests and lock files. We did not see the latest run results (7 of 10). 30+20+11+15+7 = 83.)
- Agent ergonomics, DIDWW Voice and Number Management API +20: didlogic Voice API 57 (Call records take filters and CSV export, and numbers search by country, region and city (18 of 25). Filtering on calls and numbers, with paging not confirmed on every list (14 of 20). One error envelope with field messages and 404 for unknown ids (14 of 20). No idempotency key on purchases or click-to-call. MCP annotations weren't readable without a sign-in (3 of 20). Few required fields, no official SDK beyond the browser Voice SDK (8 of 15). 18+14+14+3+8 = 57.); DIDWW Voice and Number Management API 77 (Sparse fieldsets with `fields[...]`, `include` for related resources and `page[size]` let a caller size replies. JSON:API envelopes add some weight (22 of 25). Pagination defaults to 50 and allows 100 a page, with documented filters and sorting on each collection (20). Errors are JSON:API objects with `title`, `detail`, `code` and `source.pointer`, and an insufficient balance error returns the order cost and the available balance (17 of 20). No idempotency key was found on `POST /orders`, which charges the balance at once, so a retried request can buy twice. Reservations and order polling help a caller check first, and MCP confirmations work once (5 of 20). Every request needs an `Accept` header and writes need a JSON:API body. Official SDKs exist for TypeScript, Python, PHP, Java, Go, .NET and Ruby (13 of 15). 22+20+17+5+13 = 77.)
- Transparency & trust, DIDWW Voice and Number Management API +13: didlogic Voice API 58 (Closed service with long, clear terms naming DID Logic PTE. LTD. in Singapore (15 of 30). The privacy policy commits to data minimisation and says call content isn't monitored except for requested recording, but gives no retention periods (12 of 30). No deprecation policy, though the docs explain backward-compatible identifier changes (5 of 20). Twelve points of presence are claimed, with no sub-processor list or data locations found (5 of 20). 15+12+5+5 = 37.); DIDWW Voice and Number Management API 71 (The service is closed, under the DIDWW Terms and Agreements, Rev 3.1, with a named Irish legal entity. The OpenAPI document and SDKs are MIT (17 of 30). The Privacy Notice, Rev 2.1, lists the data collected and the legal basis for each kind, and says data may be processed in the USA, Singapore and Germany among other countries. It gives no retention periods, and no data processing agreement was found. The MCP data handling page says what an MCP client receives and what DIDWW logs (14 of 30). A published policy says released dated API versions are not retired, and deprecated fields are marked in the schema. The callback change of 6 October 2026 altered a released version without an entry on its changelog page (16 of 20). Points of presence are listed with street addresses. No sub-processor list was found, and payment processors are not named in the notice (8 of 20). 17+14+16+8 = 55.)
- Security & auth, DIDWW Voice and Number Management API +11: didlogic Voice API 46 (Revocable bearer keys created in the portal, each with full account access by the vendor's own warning. MCP OAuth mints a separate key per sign-in (18 of 30). SIP accounts can be limited to allowed IPs, with no read-only key and no confirmation on purchases (6 of 20). Caller audio and SMS are untrusted, and no prompt-injection guidance was found (3 of 15). Call detail records, transaction history and risk-check logs through the API, with no audit log of API calls (7 of 15). ISO/IEC 27001:2022 and ISO 9001 certificates from TÜV AUSTRIA Hellas with registration numbers. No security.txt or bug bounty found (12 of 20). 18+6+3+7+12 = 46.); DIDWW Voice and Number Management API 57 (REST API keys are named, revocable and can be limited to source IP addresses. Several keys can exist. They reach the whole account, with no scopes (22 of 30). No read-only key was found and an order placed through the API is charged with no confirmation step. The sandbox is separate, panel users have six roles, and the MCP server applies those roles and a server-side preview and confirmation before purchases and deletions (9 of 20). API replies are mostly the account's own records. Free-text descriptions, caller numbers in call records and inbound SMS routed to the customer are untrusted, and the MCP docs warn that clients can make mistakes. No prompt-injection guidance was found (9 of 15). DID history records the method of each change, such as `api3` or `user_panel`, for 90 days, and connected MCP clients are listed with recent activity and IP address. No log of API requests was found (8 of 15). The docs say DIDWW holds ISO/IEC 27001:2022 certification from Bureau Veritas. The certificate was not seen. No security.txt (404 on 2 November), disclosure policy, bug bounty or published advisory was found. Callbacks are signed with HMAC SHA-1 (9 of 20). 22+9+9+8+9 = 57.)
- Payments & pricing, didlogic Voice API +11: didlogic Voice API 38 (No x402, MPP or L402 (0). Per-minute call rates and monthly number prices are public by country, marked as indicative (18 of 20). Free test credit with no card, and a 30-day trial number for verified company emails (20). Signup and key creation happen in the portal (0). 0+18+20+0 = 38.); DIDWW Voice and Number Management API 27 (No x402, MPP or L402 found (0). Since the 9 October check the public pricing page (pricing.md, prices generated on 30 October 2026) lists the monthly price, setup price and inbound per-minute rate for every number prefix DIDWW sells, by country, for example United States local numbers from $1.20 a month and $0.010 a minute inbound. Its by-country table also gives the starting per-minute outbound rate for calls to each country (United States from $0.004 a minute), but exact outbound rates by destination and flat-rate channel prices are still in price lists sent on request or shown inside an account, so 17 of 20 (was 5), as vonage with one channel's prices unpublished. The sandbox is free with no real card, and production needs a $30 prepaid balance before any order (10 of 20). An account is created by a person in a browser with email confirmation, keys are created in the User Panel, and MCP access needs a browser sign-in (0). 0+17+10+0 = 27.)