{ "data": { "similar": [ { "grade": "A", "json": "https://www.anchorterminal.com/tools/twilio-voice.json", "name": "Twilio Programmable Voice API + MCP", "score": 80.4, "shared": [ "voice.numbers", "voice.sip" ], "slug": "twilio-voice" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/telnyx-voice.json", "name": "Telnyx Voice API + MCP", "score": 74.2, "shared": [ "voice.numbers", "voice.sip" ], "slug": "telnyx-voice" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/livekit-telephony.json", "name": "LiveKit Telephony", "score": 67.5, "shared": [ "voice.sip", "voice.numbers" ], "slug": "livekit-telephony" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/signalwire-voice.json", "name": "SignalWire Voice API", "score": 67.1, "shared": [ "voice.numbers", "voice.sip" ], "slug": "signalwire-voice" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/bandwidth-voice.json", "name": "Bandwidth Voice API + MCP", "score": 63.7, "shared": [ "voice.numbers", "voice.sip" ], "slug": "bandwidth-voice" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/sinch-voice.json", "name": "Sinch Voice API + MCP", "score": 62.7, "shared": [ "voice.numbers", "voice.sip" ], "slug": "sinch-voice" } ], "tool": { "slug": "didww-voice-and-number-management", "name": "DIDWW Voice and Number Management API", "vendor": "DIDWW Ireland Limited", "vendorUrl": "https://www.didww.com", "kind": "http-api", "category": "voice-calling", "summary": "DIDWW is a telecoms carrier selling phone numbers in more than 90 countries with inbound and outbound SIP trunking. Its REST API v3 orders numbers and configures trunks and capacity, and a remote MCP server covers the same account tasks.", "url": "https://www.anchorterminal.com/tools/didww-voice-and-number-management", "markdownUrl": "https://www.anchorterminal.com/tools/didww-voice-and-number-management.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/didww-voice-and-number-management.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/didww-voice-and-number-management.json", "repo": "https://github.com/didww/didww-api-3-openapi", "license": "Proprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MIT", "transports": [ "http" ], "remoteUrl": "https://api.didww.com/mcp", "packages": [ { "registry": "npm", "name": "@didww/sdk" }, { "registry": "pypi", "name": "didww" } ], "auth": "api-key", "authNotes": "REST API v3 takes an API key in the `Api-Key` header with no `Bearer` prefix. Keys are created by a signed-in person in the User Panel under APIs, DIDWW API 3, with a friendly name and an optional source IP allow list. No scopes or read-only keys were found. Production and sandbox keys are separate. Access is self-serve after a browser sign-up with email confirmation. Outbound trunks need an approved application. The MCP server at `https://api.didww.com/mcp` uses OAuth 2.0 with PKCE and dynamic client registration, a browser sign-in and the user's panel roles, with tokens lasting two hours.", "pricing": "usage", "pricingNotes": "No per-number or per-minute price is public. Price lists are requested through a form or read inside an account or through the API. Accounts are free and prepaid in US dollars, with a $30 minimum balance before ordering and a $100 minimum for wire transfers. A number costs a one-time fee equal to one month's charge, waived for API orders, plus a monthly charge. Inbound capacity is flat-rate per channel or per minute, and outbound termination is per minute. The sandbox is free and takes Stripe test cards (https://www.didww.com/pricing.md, checked 2026-10-09).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI document, the docs indexes, the authentication guide or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10, "npmWeekly": 462, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://doc.didww.com/api3/2026-04-16/index.html", "llmsTxt": "https://doc.didww.com/llms.txt", "openapi": "https://doc.didww.com/openapi/2026-04-16/v3_api.json", "capabilities": [ "voice.numbers", "voice.sip" ], "tags": [ "hosted", "sip", "phone-numbers", "openapi", "llms-txt", "mcp", "oauth", "sandbox", "typescript", "python", "webhooks", "prepaid" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 65.1, "grade": "B", "agentReady": false, "rank": 330, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 83, "payments": 15, "reliability": 66, "schema": 87, "security": 57, "transparency": 70 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 66, "points": 13.2, "reason": "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 90 day history shows no incident on the API component, a 13 hour 9 minute Inbound Voice incident for Guatemala numbers on 4 October 2026, one of 3 hours 56 minutes for Mexico numbers on 3 October, a 47 minute phone.systems incident on 5 October and one planned maintenance. Both voice incidents were limited to one country's numbers, so we read them between minor and major (15 of 30). 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)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 87, "points": 14.14, "reason": "A public OpenAPI 3.0.3 document for version 2026-04-16 describes 107 operations on 67 paths with 242 schemas, in JSON and YAML, with a discovery manifest at `/.well-known/openapi.json` (25). Both sites publish llms.txt indexes and a Markdown twin of each page (10). 105 of 107 operations carry a description, and those read say what the call does, what it charges and what to do next, such as polling an order until it leaves `pending` (16 of 20). The document has 325 enums, required fields and patterns, within JSON:API envelopes that need nested `data`, `attributes` and `relationships` objects (13 of 15). 52 of 107 operations have examples. Responses 400, 401, 403, 404, 406, 415 and 422 are documented and an error object page explains codes. `429` is in the prose docs and not in the OpenAPI responses (12 of 15). Versions are dated and selected by header, with a changelog page per version. Entries are not dated, and the callback secret change of 6 October 2026 is not on the 2026-04-16 changelog page (11 of 15)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 77, "points": 12.51, "reason": "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)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 57, "points": 9.98, "reason": "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, disclosure policy, bug bounty or published advisory was found. Callbacks are signed with HMAC SHA-1 (9 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 15, "points": 1.88, "reason": "No x402, MPP or L402 found (0). The pricing page explains the charging models, the $30 minimum balance and the waived activation fee for API orders, and gives no price for a number or a minute. Price lists are sent on request or shown inside an account, so we gave 5 of 20 for the public model. 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)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 83, "points": 7.26, "reason": "The public OpenAPI document was last revised on 6 October 2026 and the Ruby, Python and TypeScript SDKs were tagged on 7 October 2026 (30). The OpenAPI repository has six dated revisions of the 2026-04-16 document from 20 August to 6 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 the three repositories checked have no open issues and a pull request from a fork of the TypeScript SDK was merged on 3 September 2026, a day after its commit (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)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 70, "points": 6.13, "note": "editorial 55, provenance 85", "reason": "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)." } ], "assessment": { "date": "2026-10-09", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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).", "maintenance": "The public OpenAPI document was last revised on 6 October 2026 and the Ruby, Python and TypeScript SDKs were tagged on 7 October 2026 (30). The OpenAPI repository has six dated revisions of the 2026-04-16 document from 20 August to 6 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 the three repositories checked have no open issues and a pull request from a fork of the TypeScript SDK was merged on 3 September 2026, a day after its commit (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).", "payments": "No x402, MPP or L402 found (0). The pricing page explains the charging models, the $30 minimum balance and the waived activation fee for API orders, and gives no price for a number or a minute. Price lists are sent on request or shown inside an account, so we gave 5 of 20 for the public model. 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).", "reliability": "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 90 day history shows no incident on the API component, a 13 hour 9 minute Inbound Voice incident for Guatemala numbers on 4 October 2026, one of 3 hours 56 minutes for Mexico numbers on 3 October, a 47 minute phone.systems incident on 5 October and one planned maintenance. Both voice incidents were limited to one country's numbers, so we read them between minor and major (15 of 30). 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).", "schema": "A public OpenAPI 3.0.3 document for version 2026-04-16 describes 107 operations on 67 paths with 242 schemas, in JSON and YAML, with a discovery manifest at `/.well-known/openapi.json` (25). Both sites publish llms.txt indexes and a Markdown twin of each page (10). 105 of 107 operations carry a description, and those read say what the call does, what it charges and what to do next, such as polling an order until it leaves `pending` (16 of 20). The document has 325 enums, required fields and patterns, within JSON:API envelopes that need nested `data`, `attributes` and `relationships` objects (13 of 15). 52 of 107 operations have examples. Responses 400, 401, 403, 404, 406, 415 and 422 are documented and an error object page explains codes. `429` is in the prose docs and not in the OpenAPI responses (12 of 15). Versions are dated and selected by header, with a changelog page per version. Entries are not dated, and the callback secret change of 6 October 2026 is not on the 2026-04-16 changelog page (11 of 15).", "security": "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, disclosure policy, bug bounty or published advisory was found. Callbacks are signed with HMAC SHA-1 (9 of 20).", "transparency": "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)." }, "sources": [ { "what": "website llms.txt and agent view", "url": "https://www.didww.com/llms.txt", "seen": "2026-10-09" }, { "what": "agent mode view", "url": "https://www.didww.com/?mode=agent", "seen": "2026-10-09" }, { "what": "pricing overview", "url": "https://www.didww.com/pricing.md", "seen": "2026-10-09" }, { "what": "DID number pricing", "url": "https://www.didww.com/coverage-and-prices/did-pricing", "seen": "2026-10-09" }, { "what": "SIP trunking pricing", "url": "https://www.didww.com/coverage-and-prices/sip-trunking-pricing", "seen": "2026-10-09" }, { "what": "authentication guide", "url": "https://www.didww.com/auth.md", "seen": "2026-10-09" }, { "what": "OpenAPI discovery manifest", "url": "https://www.didww.com/.well-known/openapi.json", "seen": "2026-10-09" }, { "what": "MCP server card", "url": "https://www.didww.com/.well-known/mcp/server-card.json", "seen": "2026-10-09" }, { "what": "Terms and Agreements, Rev 3.1", "url": "https://www.didww.com/DIDWW-Terms-and-Agreements", "seen": "2026-10-09" }, { "what": "Service Appendix", "url": "https://www.didww.com/DIDWW-Service-Appendix", "seen": "2026-10-09" }, { "what": "Privacy Notice, Rev 2.1", "url": "https://www.didww.com/privacy-notice", "seen": "2026-10-09" }, { "what": "security.txt, 404", "url": "https://www.didww.com/.well-known/security.txt", "seen": "2026-10-09" }, { "what": "docs llms.txt and full index", "url": "https://doc.didww.com/llms.txt", "seen": "2026-10-09" }, { "what": "OpenAPI document for 2026-04-16, read as the description file and not the rendered reference", "url": "https://doc.didww.com/openapi/2026-04-16/v3_api.json", "seen": "2026-10-09" }, { "what": "API versioning and deprecation policy", "url": "https://doc.didww.com/api3/api-versioning.html", "seen": "2026-10-09" }, { "what": "API authentication and rate limit", "url": "https://doc.didww.com/api3/2026-04-16/authentication.html", "seen": "2026-10-09" }, { "what": "API changelog for 2026-04-16", "url": "https://doc.didww.com/api3/2026-04-16/changelog.html", "seen": "2026-10-09" }, { "what": "callback details", "url": "https://doc.didww.com/api3/2026-04-16/callbacks-details.html", "seen": "2026-10-09" }, { "what": "sandbox guide", "url": "https://doc.didww.com/api3/sandbox.html", "seen": "2026-10-09" }, { "what": "getting started and API keys", "url": "https://doc.didww.com/api3/configuration.html", "seen": "2026-10-09" }, { "what": "pagination", "url": "https://doc.didww.com/api3/specification/pagination.html", "seen": "2026-10-09" }, { "what": "error objects", "url": "https://doc.didww.com/api3/specification/errors/index.html", "seen": "2026-10-09" }, { "what": "SDKs and tools", "url": "https://doc.didww.com/api3/sdks-and-tools.html", "seen": "2026-10-09" }, { "what": "MCP overview", "url": "https://doc.didww.com/mcp/overview.html", "seen": "2026-10-09" }, { "what": "MCP available tools", "url": "https://doc.didww.com/mcp/available-tools.html", "seen": "2026-10-09" }, { "what": "MCP connection details", "url": "https://doc.didww.com/mcp/connection-details.html", "seen": "2026-10-09" }, { "what": "MCP privacy and data handling", "url": "https://doc.didww.com/mcp/privacy-and-data-handling.html", "seen": "2026-10-09" }, { "what": "call events", "url": "https://doc.didww.com/call-events/index.html", "seen": "2026-10-09" }, { "what": "outbound trunk access", "url": "https://doc.didww.com/voice/outbound-trunks/get-access.html", "seen": "2026-10-09" }, { "what": "inbound trunks", "url": "https://doc.didww.com/voice/inbound-trunks/index.html", "seen": "2026-10-09" }, { "what": "network and points of presence", "url": "https://doc.didww.com/presence/index.html", "seen": "2026-10-09" }, { "what": "billing and pricing", "url": "https://doc.didww.com/billing/billing-and-prices/index.html", "seen": "2026-10-09" }, { "what": "certifications", "url": "https://doc.didww.com/certifications-and-memberships.html", "seen": "2026-10-09" }, { "what": "status page", "url": "https://status.didww.com/", "seen": "2026-10-09" }, { "what": "status history feed", "url": "https://status.didww.com/history.rss", "seen": "2026-10-09" }, { "what": "OpenAPI repository, commit history and RELEASING.md (shallow clone)", "url": "https://github.com/didww/didww-api-3-openapi", "seen": "2026-10-09" }, { "what": "TypeScript SDK, tags and CI (shallow clone)", "url": "https://github.com/didww/didww-api-3-typescript-sdk", "seen": "2026-10-09" }, { "what": "Python SDK, tags (shallow clone)", "url": "https://github.com/didww/didww-api-3-python-sdk", "seen": "2026-10-09" }, { "what": "Ruby client, tags and changelog (shallow clone)", "url": "https://github.com/didww/didww-v3-ruby", "seen": "2026-10-09" }, { "what": "npm latest version of @didww/sdk", "url": "https://registry.npmjs.org/@didww%2Fsdk/latest", "seen": "2026-10-09" }, { "what": "npm weekly downloads", "url": "https://api.npmjs.org/downloads/point/last-week/@didww/sdk", "seen": "2026-10-09" }, { "what": "MCP registry search, no result", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=didww", "seen": "2026-10-09" }, { "what": "RDAP for didww.com", "url": "https://rdap.verisign.com/com/v1/domain/didww.com", "seen": "2026-10-09" } ], "openQuestions": [ "The lead named the REST API and SIP transport and did not mention the remote MCP server at `https://api.didww.com/mcp`. The legal entity is DIDWW Ireland Limited", "Category fit. DIDWW sells numbers and SIP trunks and has no API for placing, streaming, transferring or recording a call, so only `voice.numbers` and `voice.sip` are listed and `voice.calls` is left out", "Whether the callback secret change of 6 October 2026 stopped callbacks for accounts that had signed them with an API key, and whether customers were told in advance", "Whether the MCP server has 81 or 82 tools, and whether its tools carry `readOnlyHint` and `destructiveHint` annotations. The server card lists names and descriptions only", "What a number, a channel and a minute cost. No price list was read, and `unitPrices` is empty", "Whether a `Retry-After` header comes with `429` on the REST API", "The terms forbid auto-dialling, telemarketing and continuous or extensive call forwarding. This matters before any probe places calls", "unchecked: the OAuth metadata and every other path on api.didww.com, because its robots.txt answered 403 and no further request was sent to that host", "unchecked: the ISO/IEC 27001 certificate, the User Panel and the sign-up form, including whether sign-up asks for a card", "unchecked: the per-endpoint reference pages, the outbound trunk security page in full, the Postman workspace and news.didww.com", "unchecked: weekly downloads of the `didww` Python package, and the result of the latest CI runs on the SDK repositories", "On 6 October 2026 the API description for released version 2026-04-16 moved callback signing from an API key to a separate callback secret, with no entry on that version's changelog page. Whether existing integrations stopped receiving callbacks, or customers were told, was not established, so no deduction was taken (https://github.com/didww/didww-api-3-openapi/commit/9ee36774515e26b433cf84c742ce7d30f8beed89)." ] }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "A public OpenAPI 3.0.3 document describes 107 operations on 67 paths, and 105 of them carry a description of purpose and behaviour", "Every docs page has a Markdown twin, with llms.txt indexes on both sites, an OpenAPI discovery manifest and an MCP server card", "A sandbox at `https://sandbox-api.didww.com/v3` is free, separate from production, and funded with Stripe test cards", "The versioning policy says released dated API versions are never retired, and an account stays on its version until a person upgrades it", "The MCP server shows a server-side preview and waits for confirmation before purchases, deletions and PSTN rate acceptance, and a confirmation works once", "Official SDKs for TypeScript, Python, PHP, Java, Go, .NET and Ruby are public under MIT, with Ruby, Python and TypeScript tagged on 7 October 2026" ], "weaknesses": [ "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", "REST API keys reach the whole account. An optional source IP allow list is the only restriction, with no scopes and no read-only key", "No idempotency key was found on `POST /orders`, which charges the prepaid balance at once, so a retried request can buy twice", "The API cannot place, answer, record or stream a call. Calls run over the customer's own SIP system, and Call Events webhooks are switched on by support", "Outbound trunks need an approved application from a business account with a company name and VAT or tax ID", "Callback signing moved from an API key to a separate callback secret on 6 October 2026, and the 2026-04-16 changelog page does not record it", "No security.txt, disclosure policy, bug bounty, uptime SLA, data processing agreement or sub-processor list was found", "The terms forbid auto-dialling, telemarketing and continuous or extensive call forwarding, which matters before an agent places outbound calls" ], "agentNotes": [ "Send `Api-Key: \u003ckey\u003e` with no `Bearer` prefix, plus `Accept: application/vnd.api+json`, and `Content-Type: application/vnd.api+json` on every request with a body", "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", "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", "Stay under 20 requests a second per key. On `429` wait before retrying, since no `Retry-After` header is documented", "Use `fields[...]`, `filter[...]`, `include` and `page[size]` (default 50, maximum 100) to keep JSON:API replies small", "Check `GET /address_requirements` before buying a number. Many countries need a verified identity and address, and the sandbox cannot run identity verification", "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`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.1 } ], "editorialScores": { "ergonomics": 77, "maintenance": 83, "payments": 15, "reliability": 66, "schema": 87, "security": 57, "transparency": 55 }, "provenanceScore": 85 }, "connect": { "install": "npm install @didww/sdk", "http": "GET https://api.didww.com/v3/countries\nApi-Key: YOUR_API_KEY\nX-DIDWW-API-Version: 2026-04-16\nAccept: application/vnd.api+json" }, "letme": { "capability": "https://letme.dev/voice.numbers", "tool": "https://letme.dev/didww-voice-and-number-management" }, "notable": [ "The OpenAPI document for version 2026-04-16 is OpenAPI 3.0.3 with 107 operations on 67 paths and 242 schemas, built from the services' own test suites per the repository's `RELEASING.md` (https://github.com/didww/didww-api-3-openapi)", "The versioning policy says released dated versions of API v3 are not retired and have no retirement deadline. Dated versions are 2021-04-19, 2021-12-15, 2022-05-10 and 2026-04-16 (https://doc.didww.com/api3/api-versioning.html)", "The MCP docs page lists 82 tools and the server card and website llms.txt say 81. The card omits `update_did_description` (https://doc.didww.com/mcp/available-tools.html, https://www.didww.com/.well-known/mcp/server-card.json)", "Of the 82 documented MCP tools, 35 are read-only and 14 always need a server-side confirmation, among them both purchase tools and all nine destructive tools", "The 6 October 2026 revision of the 2026-04-16 OpenAPI document changed callback signing from an API key with callbacks enabled to a separate callback secret created in the User Panel", "The status page lists a 13 hour 9 minute Inbound Voice incident for Guatemala numbers on 4 October 2026 and one of 3 hours 56 minutes for Mexico numbers on 3 October 2026 (https://status.didww.com/history.rss)", "The docs say DIDWW holds ISO/IEC 27001:2022 certification from Bureau Veritas, first announced in June 2023. The certificate itself was not seen (https://doc.didww.com/certifications-and-memberships.html)", "Both llms.txt files carry instructions addressed to AI models, such as preferring Markdown pages and not mixing phone.systems guidance into DIDWW answers. We recorded them and did not act on them", "The GitHub star count is for didww-api-3-openapi. didww-v3-ruby has 18 and didww-api-3-typescript-sdk 13. The npm count is for `@didww/sdk`, 1 to 7 October 2026" ], "area": "voice", "details": [ { "label": "Countries with numbers", "value": "More than 90 countries by the vendor's count (one llms.txt line says more than 100). Local, national, mobile, toll-free, shared-cost and UIFN numbers. Many countries need a verified identity and address first" }, { "label": "SIP", "value": "Inbound SIP trunks with trunk groups for failover and load balancing, PSTN forwarding trunks, and outbound trunks over UDP, TCP or TLS with optional encrypted media. Points of presence in New York, Los Angeles, Miami, Frankfurt, Amsterdam, Singapore and Hong Kong" }, { "label": "Call control", "value": "None in the API. Calls are placed by a SIP INVITE from the customer's system and received on the customer's SIP endpoint. The API orders numbers and configures trunks, capacity and compliance records" }, { "label": "Media streams", "value": "None found. No websocket or media fork is documented for API v3" }, { "label": "Recording", "value": "None found for API v3. Recording belongs to phone.systems, a separate cloud PBX product" }, { "label": "Call events", "value": "Webhooks for inbound and outbound call start, connect and end, and CDR streaming. Enabled by Technical Support on request, then configured in the User Panel" }, { "label": "Outbound calling", "value": "Not enabled at sign-up. An application form is reviewed, and it needs a business account with a company name and VAT or tax ID. Local termination needs a number in the account" }, { "label": "Free tier", "value": "Sandbox with its own account and keys, no real provisioning or billing, funded by Stripe test cards. Production needs a $30 prepaid balance" }, { "label": "Rate limits", "value": "20 requests a second per API key, with `429` over the limit. MCP requests are counted per connected client and a refusal gives the seconds to wait" }, { "label": "SLA", "value": "None found. The terms give no warranty that the service is continuous or free from faults" }, { "label": "Data retention", "value": "No retention periods in the Privacy Notice. DID history covers 90 days and finished export files are kept one month. The notice names the USA, Singapore and Germany among processing countries" }, { "label": "MCP server", "value": "`https://api.didww.com/mcp`, Streamable HTTP with OAuth, 82 tools in the docs. Guides for Claude, ChatGPT and Perplexity. The vendor says it is for account tasks and does not replace the API for software integrations" } ], "provenance": { "legalEntity": "DIDWW Ireland Limited", "domain": "didww.com", "domainRegistered": "2006-01-16", "endpointOnVendorDomain": true, "terms": "https://www.didww.com/DIDWW-Terms-and-Agreements", "privacy": "https://www.didww.com/privacy-notice", "statusPage": "https://status.didww.com", "changelog": "https://doc.didww.com/api3/2026-04-16/changelog.html", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The terms link is the DIDWW Terms and Agreements, Rev 3.1, copyright 2026, between the customer and DIDWW Ireland Limited of 25 North Wall Quay, Dublin 1. It covers all DIDWW services and refers to a Service Appendix.", "The Privacy Notice is Rev 2.1, copyright 2025. It gives the company number as 473521 and names gdpr@didww.com for requests. No data processing agreement or sub-processor list was found.", "The REST API and the MCP server answer on api.didww.com and the sandbox on sandbox-api.didww.com.", "The status page runs on Instatus with eight components, among them DIDWW API, Inbound Voice and Outbound Voice.", "https://www.didww.com/.well-known/security.txt returned 404.", "RDAP for didww.com gives a registration date of 2006-01-16.", "The changelog link is the page for API version 2026-04-16. Its entries are not dated. Dated revisions are in the commit history of github.com/didww/didww-api-3-openapi.", "No clause on automated access, scraping or benchmarking was found in the Terms and Agreements. robots.txt on www.didww.com and doc.didww.com allows the pages read.", "https://api.didww.com/robots.txt answered 403, so no request was sent to that host and the OAuth metadata was not read." ], "score": 85, "checks": [ { "check": "Legal entity named", "value": "DIDWW Ireland Limited", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "didww.com, registered 2006-01-16 (20 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "api.didww.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 4 of the 7 things a reader expects", "points": 7.4, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 5 of the 8 things a reader expects", "points": 7.8, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.didww.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ], "policies": [ { "kind": "terms", "url": "https://www.didww.com/DIDWW-Terms-and-Agreements", "state": "read", "readAt": "2026-10-09", "words": 5063, "points": 7.4, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "This Agreement shall be governed by Irish law and the Customer consents to the exclusive jurisdiction of the Irish courts in all matters regarding it." }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "DIDWW shall not be liable for any indirect, incidental, special or consequential damages or for interrupted communications, lost data, or loss of profit, or economic loss arising out of or in connection with this Agreement and in particular shall not be liable for any delay in rectification of any such problem.", "says": "Rules out indirect and consequential losses, with no cap named in this sentence" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "If Customer’s prepaid balance is insufficient Services may be automatically suspended until further credit is applied." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "Jurisdiction Restrictions: if the Customer is residing in a jurisdiction where it is forbidden by law to offer or use internet telephony, the Customer may not enter into this Agreement." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "notes": [ { "date": "2026-10-08", "text": "Price increases for services with a variable charge take effect immediately when the price list in the customer's account is updated.", "quote": "8.3.2. DIDWW may increase prices: 8.3.2.1. For Services based on a variable charge, changes are effective immediately and are updated in the pricelist associated with Customers’ account on the DIDWW website." }, { "date": "2026-10-08", "text": "DIDWW may suspend the service for maintenance, upgrade works or back-ups without prior warning to the customer or its consent.", "quote": "9.1. DIDWW may without liability, prior warning or consent of the Customer, suspend the service, in the event that it wishes to carry out maintenance, upgrade works, or back-ups." }, { "date": "2026-10-08", "text": "Direct damages are limited to the lower of 5,000 US dollars and the amount invoiced and received for the previous month.", "quote": "Direct damages caused as a result of DIDWW’s breaches of this Agreement shall in any event be limited to the lower of: 5,000 U.S. Dollars; and, the amount invoiced to the customer and received by DIDWW for the month prior to, for any one event or series of events." } ] }, { "kind": "privacy", "url": "https://www.didww.com/privacy-notice", "state": "read", "readAt": "2026-10-09", "words": 3513, "points": 7.8, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": false }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "It sets out the conditions under which we may process any information that we collect from you, or that you provide to us." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "Except as otherwise mentioned in this privacy notice, we keep your personal information only for as long as required by us:", "says": "For as long as needed, with no period named" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "- Except as set out below, we do not share, sell, or disclose to a third party, any information collected through our website." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": false }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "description: \"DIDWW Privacy Notice complies with Ireland law accordingly implemented, including that required by the EU General Data Protection Regulation (GDPR).\"" }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": false }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "The provision of our services requires the transfer of data outside of the European Economic Area (the “EEA”)." } ] } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/didww-voice-and-number-management.json", "live": { "slug": "didww-voice-and-number-management", "probe": { "target": "https://api.didww.com/mcp", "method": "get", "lastAt": "2026-10-10T03:53:25.677851947Z", "lastOk": true, "lastStatus": 401, "lastMs": 386, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 394, "p95ms24h": 524, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.didww.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:25.908796867Z" }, "versions": [ { "registry": "npm", "name": "@didww/sdk", "version": "3.1.1", "seenAt": "2026-10-09T16:49:43.396621514Z" }, { "registry": "pypi", "name": "didww", "version": "3.2.0", "released": "2026-10-08", "seenAt": "2026-10-09T16:49:44.365849676Z" } ], "githubStars": 10, "npmWeekly": 462, "pypiWeekly": 915, "pages": [ { "url": "https://doc.didww.com/api3/2026-04-16/changelog.html", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:36:22.294016104Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7d9c86f4f536" }, { "url": "https://www.didww.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:49:33.776952203Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "60eebb22a63e" }, { "url": "https://www.didww.com/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:49:35.769637352Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a193b3f64bb0" }, { "url": "https://www.didww.com/DIDWW-Terms-and-Agreements", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:49:31.750868001Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2568f2c611f6" } ], "updatedAt": "2026-10-10T03:53:25.677851947Z" } }, "verify": { "accepts": "a page on didww.com or one of its subdomains, or the README of github.com/didww/didww-api-3-openapi", "badgeUrl": "https://www.anchorterminal.com/badges/didww-voice-and-number-management.svg", "body": { "slug": "didww-voice-and-number-management", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/didww-voice-and-number-management", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/didww-voice-and-number-management\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/didww-voice-and-number-management.svg\" alt=\"DIDWW Voice and Number Management API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![DIDWW Voice and Number Management API on Anchor Terminal](https://www.anchorterminal.com/badges/didww-voice-and-number-management.svg)](https://www.anchorterminal.com/tools/didww-voice-and-number-management)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/didww-voice-and-number-management\"\u003eDIDWW Voice and Number Management API on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/didww-voice-and-number-management", "json": "https://www.anchorterminal.com/tools/didww-voice-and-number-management.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/didww-voice-and-number-management.md", "slim": "https://www.anchorterminal.com/tools/didww-voice-and-number-management.min.md" }, "markdown": "## Overview\n\n**Grade B · 65.1/100 · rank #330 of 950 · #5 in Phone calling \u0026 voice transport · not agent-ready · confidence medium**\n\n\n## Assessment\n\nAn 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.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | DIDWW Ireland Limited (https://www.didww.com) |\n| Kind | HTTP API |\n| Category | Phone calling \u0026 voice transport (https://www.anchorterminal.com/categories/voice-calling) |\n| Transport | HTTP |\n| Endpoint | `https://api.didww.com/mcp` |\n| Auth | API key · REST API v3 takes an API key in the `Api-Key` header with no `Bearer` prefix. Keys are created by a signed-in person in the User Panel under APIs, DIDWW API 3, with a friendly name and an optional source IP allow list. No scopes or read-only keys were found. Production and sandbox keys are separate. Access is self-serve after a browser sign-up with email confirmation. Outbound trunks need an approved application. The MCP server at `https://api.didww.com/mcp` uses OAuth 2.0 with PKCE and dynamic client registration, a browser sign-in and the user's panel roles, with tokens lasting two hours. |\n| Pricing | Pay per use (Pay per use) · No per-number or per-minute price is public. Price lists are requested through a form or read inside an account or through the API. Accounts are free and prepaid in US dollars, with a $30 minimum balance before ordering and a $100 minimum for wire transfers. A number costs a one-time fee equal to one month's charge, waived for API orders, plus a monthly charge. Inbound capacity is flat-rate per channel or per minute, and outbound termination is per minute. The sandbox is free and takes Stripe test cards (https://www.didww.com/pricing.md, checked 2026-10-09). |\n| x402 | No · No x402, MPP or L402 in the OpenAPI document, the docs indexes, the authentication guide or the pricing page (checked 2026-10-09). |\n| Licence | Proprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MIT |\n| Packages | npm: `@didww/sdk`; pypi: `didww` |\n| Source | https://github.com/didww/didww-api-3-openapi |\n| Docs | https://doc.didww.com/api3/2026-04-16/index.html |\n| llms.txt | https://doc.didww.com/llms.txt |\n| Last release | 2026-10-07 |\n| GitHub stars | 10 (as of 2026-10-09) |\n| npm downloads / week | 462 |\n| Countries with numbers | More than 90 countries by the vendor's count (one llms.txt line says more than 100). Local, national, mobile, toll-free, shared-cost and UIFN numbers. Many countries need a verified identity and address first |\n| SIP | Inbound SIP trunks with trunk groups for failover and load balancing, PSTN forwarding trunks, and outbound trunks over UDP, TCP or TLS with optional encrypted media. Points of presence in New York, Los Angeles, Miami, Frankfurt, Amsterdam, Singapore and Hong Kong |\n| Call control | None in the API. Calls are placed by a SIP INVITE from the customer's system and received on the customer's SIP endpoint. The API orders numbers and configures trunks, capacity and compliance records |\n| Media streams | None found. No websocket or media fork is documented for API v3 |\n| Recording | None found for API v3. Recording belongs to phone.systems, a separate cloud PBX product |\n| Call events | Webhooks for inbound and outbound call start, connect and end, and CDR streaming. Enabled by Technical Support on request, then configured in the User Panel |\n| Outbound calling | Not enabled at sign-up. An application form is reviewed, and it needs a business account with a company name and VAT or tax ID. Local termination needs a number in the account |\n| Free tier | Sandbox with its own account and keys, no real provisioning or billing, funded by Stripe test cards. Production needs a $30 prepaid balance |\n| Rate limits | 20 requests a second per API key, with `429` over the limit. MCP requests are counted per connected client and a refusal gives the seconds to wait |\n| SLA | None found. The terms give no warranty that the service is continuous or free from faults |\n| Data retention | No retention periods in the Privacy Notice. DID history covers 90 days and finished export files are kept one month. The notice names the USA, Singapore and Germany among processing countries |\n| MCP server | `https://api.didww.com/mcp`, Streamable HTTP with OAuth, 82 tools in the docs. Guides for Claude, ChatGPT and Perplexity. The vendor says it is for account tasks and does not replace the API for software integrations |\n| Capabilities | voice.numbers, voice.sip |\n| Tags | hosted, sip, phone-numbers, openapi, llms-txt, mcp, oauth, sandbox, typescript, python, webhooks, prepaid |\n| JSON | https://www.anchorterminal.com/api/v1/tools/didww-voice-and-number-management.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 66 | 13.2 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 87 | 14.1 |\n| Agent ergonomics | 13% | 16.2 | 77 | 12.5 |\n| Security \u0026 auth | 14% | 17.5 | 57 | 10.0 |\n| Payments \u0026 pricing | 10% | 12.5 | 15 | 1.9 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 83 | 7.3 |\n| Transparency \u0026 trust (editorial 55, provenance 85) | 7% | 8.8 | 70 | 6.1 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **65.1 → B** |\n\n### Why each score\n\n- Reliability 66: 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 90 day history shows no incident on the API component, a 13 hour 9 minute Inbound Voice incident for Guatemala numbers on 4 October 2026, one of 3 hours 56 minutes for Mexico numbers on 3 October, a 47 minute phone.systems incident on 5 October and one planned maintenance. Both voice incidents were limited to one country's numbers, so we read them between minor and major (15 of 30). 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).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 87: A public OpenAPI 3.0.3 document for version 2026-04-16 describes 107 operations on 67 paths with 242 schemas, in JSON and YAML, with a discovery manifest at `/.well-known/openapi.json` (25). Both sites publish llms.txt indexes and a Markdown twin of each page (10). 105 of 107 operations carry a description, and those read say what the call does, what it charges and what to do next, such as polling an order until it leaves `pending` (16 of 20). The document has 325 enums, required fields and patterns, within JSON:API envelopes that need nested `data`, `attributes` and `relationships` objects (13 of 15). 52 of 107 operations have examples. Responses 400, 401, 403, 404, 406, 415 and 422 are documented and an error object page explains codes. `429` is in the prose docs and not in the OpenAPI responses (12 of 15). Versions are dated and selected by header, with a changelog page per version. Entries are not dated, and the callback secret change of 6 October 2026 is not on the 2026-04-16 changelog page (11 of 15).\n- Agent ergonomics 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).\n- Security \u0026 auth 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, disclosure policy, bug bounty or published advisory was found. Callbacks are signed with HMAC SHA-1 (9 of 20).\n- Payments \u0026 pricing 15: No x402, MPP or L402 found (0). The pricing page explains the charging models, the $30 minimum balance and the waived activation fee for API orders, and gives no price for a number or a minute. Price lists are sent on request or shown inside an account, so we gave 5 of 20 for the public model. 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).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 83: The public OpenAPI document was last revised on 6 October 2026 and the Ruby, Python and TypeScript SDKs were tagged on 7 October 2026 (30). The OpenAPI repository has six dated revisions of the 2026-04-16 document from 20 August to 6 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 the three repositories checked have no open issues and a pull request from a fork of the TypeScript SDK was merged on 3 September 2026, a day after its commit (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).\n- Transparency \u0026 trust 70: 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).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/didww-voice-and-number-management.md (JSON https://www.anchorterminal.com/fixes/didww-voice-and-number-management.json)\n\n### What we couldn't check\n\n- The lead named the REST API and SIP transport and did not mention the remote MCP server at `https://api.didww.com/mcp`. The legal entity is DIDWW Ireland Limited\n- Category fit. DIDWW sells numbers and SIP trunks and has no API for placing, streaming, transferring or recording a call, so only `voice.numbers` and `voice.sip` are listed and `voice.calls` is left out\n- Whether the callback secret change of 6 October 2026 stopped callbacks for accounts that had signed them with an API key, and whether customers were told in advance\n- Whether the MCP server has 81 or 82 tools, and whether its tools carry `readOnlyHint` and `destructiveHint` annotations. The server card lists names and descriptions only\n- What a number, a channel and a minute cost. No price list was read, and `unitPrices` is empty\n- Whether a `Retry-After` header comes with `429` on the REST API\n- The terms forbid auto-dialling, telemarketing and continuous or extensive call forwarding. This matters before any probe places calls\n- unchecked: the OAuth metadata and every other path on api.didww.com, because its robots.txt answered 403 and no further request was sent to that host\n- unchecked: the ISO/IEC 27001 certificate, the User Panel and the sign-up form, including whether sign-up asks for a card\n- unchecked: the per-endpoint reference pages, the outbound trunk security page in full, the Postman workspace and news.didww.com\n- unchecked: weekly downloads of the `didww` Python package, and the result of the latest CI runs on the SDK repositories\n- On 6 October 2026 the API description for released version 2026-04-16 moved callback signing from an API key to a separate callback secret, with no entry on that version's changelog page. Whether existing integrations stopped receiving callbacks, or customers were told, was not established, so no deduction was taken (https://github.com/didww/didww-api-3-openapi/commit/9ee36774515e26b433cf84c742ce7d30f8beed89).\n\n### Sources\n\n- website llms.txt and agent view: \u003chttps://www.didww.com/llms.txt\u003e (seen 2026-10-09)\n- agent mode view: \u003chttps://www.didww.com/?mode=agent\u003e (seen 2026-10-09)\n- pricing overview: \u003chttps://www.didww.com/pricing.md\u003e (seen 2026-10-09)\n- DID number pricing: \u003chttps://www.didww.com/coverage-and-prices/did-pricing\u003e (seen 2026-10-09)\n- SIP trunking pricing: \u003chttps://www.didww.com/coverage-and-prices/sip-trunking-pricing\u003e (seen 2026-10-09)\n- authentication guide: \u003chttps://www.didww.com/auth.md\u003e (seen 2026-10-09)\n- OpenAPI discovery manifest: \u003chttps://www.didww.com/.well-known/openapi.json\u003e (seen 2026-10-09)\n- MCP server card: \u003chttps://www.didww.com/.well-known/mcp/server-card.json\u003e (seen 2026-10-09)\n- Terms and Agreements, Rev 3.1: \u003chttps://www.didww.com/DIDWW-Terms-and-Agreements\u003e (seen 2026-10-09)\n- Service Appendix: \u003chttps://www.didww.com/DIDWW-Service-Appendix\u003e (seen 2026-10-09)\n- Privacy Notice, Rev 2.1: \u003chttps://www.didww.com/privacy-notice\u003e (seen 2026-10-09)\n- security.txt, 404: \u003chttps://www.didww.com/.well-known/security.txt\u003e (seen 2026-10-09)\n- docs llms.txt and full index: \u003chttps://doc.didww.com/llms.txt\u003e (seen 2026-10-09)\n- OpenAPI document for 2026-04-16, read as the description file and not the rendered reference: \u003chttps://doc.didww.com/openapi/2026-04-16/v3_api.json\u003e (seen 2026-10-09)\n- API versioning and deprecation policy: \u003chttps://doc.didww.com/api3/api-versioning.html\u003e (seen 2026-10-09)\n- API authentication and rate limit: \u003chttps://doc.didww.com/api3/2026-04-16/authentication.html\u003e (seen 2026-10-09)\n- API changelog for 2026-04-16: \u003chttps://doc.didww.com/api3/2026-04-16/changelog.html\u003e (seen 2026-10-09)\n- callback details: \u003chttps://doc.didww.com/api3/2026-04-16/callbacks-details.html\u003e (seen 2026-10-09)\n- sandbox guide: \u003chttps://doc.didww.com/api3/sandbox.html\u003e (seen 2026-10-09)\n- getting started and API keys: \u003chttps://doc.didww.com/api3/configuration.html\u003e (seen 2026-10-09)\n- pagination: \u003chttps://doc.didww.com/api3/specification/pagination.html\u003e (seen 2026-10-09)\n- error objects: \u003chttps://doc.didww.com/api3/specification/errors/index.html\u003e (seen 2026-10-09)\n- SDKs and tools: \u003chttps://doc.didww.com/api3/sdks-and-tools.html\u003e (seen 2026-10-09)\n- MCP overview: \u003chttps://doc.didww.com/mcp/overview.html\u003e (seen 2026-10-09)\n- MCP available tools: \u003chttps://doc.didww.com/mcp/available-tools.html\u003e (seen 2026-10-09)\n- MCP connection details: \u003chttps://doc.didww.com/mcp/connection-details.html\u003e (seen 2026-10-09)\n- MCP privacy and data handling: \u003chttps://doc.didww.com/mcp/privacy-and-data-handling.html\u003e (seen 2026-10-09)\n- call events: \u003chttps://doc.didww.com/call-events/index.html\u003e (seen 2026-10-09)\n- outbound trunk access: \u003chttps://doc.didww.com/voice/outbound-trunks/get-access.html\u003e (seen 2026-10-09)\n- inbound trunks: \u003chttps://doc.didww.com/voice/inbound-trunks/index.html\u003e (seen 2026-10-09)\n- network and points of presence: \u003chttps://doc.didww.com/presence/index.html\u003e (seen 2026-10-09)\n- billing and pricing: \u003chttps://doc.didww.com/billing/billing-and-prices/index.html\u003e (seen 2026-10-09)\n- certifications: \u003chttps://doc.didww.com/certifications-and-memberships.html\u003e (seen 2026-10-09)\n- status page: \u003chttps://status.didww.com/\u003e (seen 2026-10-09)\n- status history feed: \u003chttps://status.didww.com/history.rss\u003e (seen 2026-10-09)\n- OpenAPI repository, commit history and RELEASING.md (shallow clone): \u003chttps://github.com/didww/didww-api-3-openapi\u003e (seen 2026-10-09)\n- TypeScript SDK, tags and CI (shallow clone): \u003chttps://github.com/didww/didww-api-3-typescript-sdk\u003e (seen 2026-10-09)\n- Python SDK, tags (shallow clone): \u003chttps://github.com/didww/didww-api-3-python-sdk\u003e (seen 2026-10-09)\n- Ruby client, tags and changelog (shallow clone): \u003chttps://github.com/didww/didww-v3-ruby\u003e (seen 2026-10-09)\n- npm latest version of @didww/sdk: \u003chttps://registry.npmjs.org/@didww%2Fsdk/latest\u003e (seen 2026-10-09)\n- npm weekly downloads: \u003chttps://api.npmjs.org/downloads/point/last-week/@didww/sdk\u003e (seen 2026-10-09)\n- MCP registry search, no result: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=didww\u003e (seen 2026-10-09)\n- RDAP for didww.com: \u003chttps://rdap.verisign.com/com/v1/domain/didww.com\u003e (seen 2026-10-09)\n\n## Who's behind it (provenance 85/100, checked 2026-10-09)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | DIDWW Ireland Limited | 20/20 |\n| Domain age | didww.com, registered 2006-01-16 (20 years) | 15/15 |\n| Endpoint on the vendor's domain | api.didww.com | 15/15 |\n| Terms of service | read, states 4 of the 7 things a reader expects | 7.4/10 |\n| Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 |\n| Status page | status.didww.com | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n\nThe terms link is the DIDWW Terms and Agreements, Rev 3.1, copyright 2026, between the customer and DIDWW Ireland Limited of 25 North Wall Quay, Dublin 1. It covers all DIDWW services and refers to a Service Appendix.\n\nThe Privacy Notice is Rev 2.1, copyright 2025. It gives the company number as 473521 and names gdpr@didww.com for requests. No data processing agreement or sub-processor list was found.\n\nThe REST API and the MCP server answer on api.didww.com and the sandbox on sandbox-api.didww.com.\n\nThe status page runs on Instatus with eight components, among them DIDWW API, Inbound Voice and Outbound Voice.\n\nhttps://www.didww.com/.well-known/security.txt returned 404.\n\nRDAP for didww.com gives a registration date of 2006-01-16.\n\nThe changelog link is the page for API version 2026-04-16. Its entries are not dated. Dated revisions are in the commit history of github.com/didww/didww-api-3-openapi.\n\nNo clause on automated access, scraping or benchmarking was found in the Terms and Agreements. robots.txt on www.didww.com and doc.didww.com allows the pages read.\n\nhttps://api.didww.com/robots.txt answered 403, so no request was sent to that host and the OAuth metadata was not read.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.didww.com/DIDWW-Terms-and-Agreements), read 2026-10-09, gives no date, states 4 of the 7 things a reader expects.\n\n- Not found in the text. Gives the date it was last updated.\n- States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence.\n- Not found in the text. Says how changes to the terms are announced.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-10-08). Price increases for services with a variable charge take effect immediately when the price list in the customer's account is updated. \"8.3.2. DIDWW may increase prices: 8.3.2.1. For Services based on a variable charge, changes are effective immediately and are updated in the pricelist associated with Customers’ account on the DIDWW website.\"\n- Also in the text (2026-10-08). DIDWW may suspend the service for maintenance, upgrade works or back-ups without prior warning to the customer or its consent. \"9.1. DIDWW may without liability, prior warning or consent of the Customer, suspend the service, in the event that it wishes to carry out maintenance, upgrade works, or back-ups.\"\n- Also in the text (2026-10-08). Direct damages are limited to the lower of 5,000 US dollars and the amount invoiced and received for the previous month. \"Direct damages caused as a result of DIDWW’s breaches of this Agreement shall in any event be limited to the lower of: 5,000 U.S. Dollars; and, the amount invoiced to the customer and received by DIDWW for the month prior to, for any one event or series of events.\"\n\n**Privacy policy** (https://www.didww.com/privacy-notice), read 2026-10-09, gives no date, states 5 of the 8 things a reader expects.\n\n- Not found in the text. Gives the date it was last updated.\n- Says how long data is kept. For as long as needed, with no period named.\n- Not found in the text. Says whether personal data is sold or shared for advertising.\n- Not found in the text. Gives a privacy contact.\n\n## Live (updated 2026-10-10 03:53 UTC)\n\n- Right now: up, HTTP 401, 386 ms, checked 2026-10-10 03:53 UTC (get on `https://api.didww.com/mcp`, asks for auth)\n- Uptime 24h 100.0% (125 probes) · 30 days 100.0% (125 probes) · p50 394 ms · p95 524 ms\n- Vendor status page: unknown, no machine-readable status found\n- npm `@didww/sdk` 3.1.1\n- pypi `didww` 3.2.0, released 2026-10-08\n- Watching changelog \u003chttps://doc.didww.com/api3/2026-04-16/changelog.html\u003e\n- Watching pricing \u003chttps://www.didww.com/pricing.md\u003e\n- Watching privacy \u003chttps://www.didww.com/privacy-notice\u003e\n- Watching terms \u003chttps://www.didww.com/DIDWW-Terms-and-Agreements\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/didww-voice-and-number-management.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- A public OpenAPI 3.0.3 document describes 107 operations on 67 paths, and 105 of them carry a description of purpose and behaviour\n- Every docs page has a Markdown twin, with llms.txt indexes on both sites, an OpenAPI discovery manifest and an MCP server card\n- A sandbox at `https://sandbox-api.didww.com/v3` is free, separate from production, and funded with Stripe test cards\n- The versioning policy says released dated API versions are never retired, and an account stays on its version until a person upgrades it\n- The MCP server shows a server-side preview and waits for confirmation before purchases, deletions and PSTN rate acceptance, and a confirmation works once\n- Official SDKs for TypeScript, Python, PHP, Java, Go, .NET and Ruby are public under MIT, with Ruby, Python and TypeScript tagged on 7 October 2026\n\n## Weaknesses\n\n- 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\n- REST API keys reach the whole account. An optional source IP allow list is the only restriction, with no scopes and no read-only key\n- No idempotency key was found on `POST /orders`, which charges the prepaid balance at once, so a retried request can buy twice\n- The API cannot place, answer, record or stream a call. Calls run over the customer's own SIP system, and Call Events webhooks are switched on by support\n- Outbound trunks need an approved application from a business account with a company name and VAT or tax ID\n- Callback signing moved from an API key to a separate callback secret on 6 October 2026, and the 2026-04-16 changelog page does not record it\n- No security.txt, disclosure policy, bug bounty, uptime SLA, data processing agreement or sub-processor list was found\n- The terms forbid auto-dialling, telemarketing and continuous or extensive call forwarding, which matters before an agent places outbound calls\n\n## Before you call it (notes for agents)\n\n1. Send `Api-Key: \u003ckey\u003e` with no `Bearer` prefix, plus `Accept: application/vnd.api+json`, and `Content-Type: application/vnd.api+json` on every request with a body\n2. 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\n3. 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\n4. Stay under 20 requests a second per key. On `429` wait before retrying, since no `Retry-After` header is documented\n5. Use `fields[...]`, `filter[...]`, `include` and `page[size]` (default 50, maximum 100) to keep JSON:API replies small\n6. Check `GET /address_requirements` before buying a number. Many countries need a verified identity and address, and the sandbox cannot run identity verification\n7. 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`\n\n## Connect\n\nInstall:\n\n```bash\nnpm install @didww/sdk\n```\n\nFirst request:\n\n```bash\nGET https://api.didww.com/v3/countries\nApi-Key: YOUR_API_KEY\nX-DIDWW-API-Version: 2026-04-16\nAccept: application/vnd.api+json\n```\n\nThrough letme (picks today, calling later): https://letme.dev/didww-voice-and-number-management. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Twilio Programmable Voice API + MCP | A | 80.4 | 9 | voice.numbers, voice.sip | no | https://www.anchorterminal.com/tools/twilio-voice.md |\n| Telnyx Voice API + MCP | BB | 74.2 | 74 | voice.numbers, voice.sip | no | https://www.anchorterminal.com/tools/telnyx-voice.md |\n| LiveKit Telephony | B | 67.5 | 253 | voice.sip, voice.numbers | no | https://www.anchorterminal.com/tools/livekit-telephony.md |\n| SignalWire Voice API | B | 67.1 | 261 | voice.numbers, voice.sip | no | https://www.anchorterminal.com/tools/signalwire-voice.md |\n| Bandwidth Voice API + MCP | B | 63.7 | 374 | voice.numbers, voice.sip | no | https://www.anchorterminal.com/tools/bandwidth-voice.md |\n| Sinch Voice API + MCP | B | 62.7 | 422 | voice.numbers, voice.sip | no | https://www.anchorterminal.com/tools/sinch-voice.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The OpenAPI document for version 2026-04-16 is OpenAPI 3.0.3 with 107 operations on 67 paths and 242 schemas, built from the services' own test suites per the repository's `RELEASING.md` (source: \u003chttps://github.com/didww/didww-api-3-openapi\u003e)\n- The versioning policy says released dated versions of API v3 are not retired and have no retirement deadline. Dated versions are 2021-04-19, 2021-12-15, 2022-05-10 and 2026-04-16 (source: \u003chttps://doc.didww.com/api3/api-versioning.html\u003e)\n- The MCP docs page lists 82 tools and the server card and website llms.txt say 81. The card omits `update_did_description` (source: \u003chttps://doc.didww.com/mcp/available-tools.html, https://www.didww.com/.well-known/mcp/server-card.json\u003e)\n- Of the 82 documented MCP tools, 35 are read-only and 14 always need a server-side confirmation, among them both purchase tools and all nine destructive tools\n- The 6 October 2026 revision of the 2026-04-16 OpenAPI document changed callback signing from an API key with callbacks enabled to a separate callback secret created in the User Panel\n- The status page lists a 13 hour 9 minute Inbound Voice incident for Guatemala numbers on 4 October 2026 and one of 3 hours 56 minutes for Mexico numbers on 3 October 2026 (source: \u003chttps://status.didww.com/history.rss\u003e)\n- The docs say DIDWW holds ISO/IEC 27001:2022 certification from Bureau Veritas, first announced in June 2023. The certificate itself was not seen (source: \u003chttps://doc.didww.com/certifications-and-memberships.html\u003e)\n- Both llms.txt files carry instructions addressed to AI models, such as preferring Markdown pages and not mixing phone.systems guidance into DIDWW answers. We recorded them and did not act on them\n- The GitHub star count is for didww-api-3-openapi. didww-v3-ruby has 18 and didww-api-3-typescript-sdk 13. The npm count is for `@didww/sdk`, 1 to 7 October 2026\n\n- #5 of 13 in Best phone calling and voice transport APIs for AI agents: https://www.anchorterminal.com/best/voice-calling/index.md\n- All 78 calling comparisons: https://www.anchorterminal.com/compare/voice-calling/index.md\n\n## Compare\n\n- [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): B 63.7 vs B 65.1\n- [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): B 65.1 vs E 39.4\n- [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): B 65.1 vs C 60.3\n- [DIDWW Voice and Number Management API vs LiveKit Telephony](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.md): B 65.1 vs B 67.5\n- [DIDWW Voice and Number Management API vs Plivo Voice API](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-plivo-voice.md): B 65.1 vs C 60.4\n- [DIDWW Voice and Number Management API vs SignalWire Voice API](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-signalwire-voice.md): B 65.1 vs B 67.1\n- [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): B 65.1 vs B 62.7\n- [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): B 65.1 vs BB 74.2\n- [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): B 65.1 vs A 80.4\n- [DIDWW Voice and Number Management API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.md): B 65.1 vs C 58.9\n- [DIDWW Voice and Number Management API vs Voximplant](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-voximplant.md): B 65.1 vs D 51.7\n- [DIDWW Voice and Number Management API vs jambonz](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-jambonz.md): B 65.1 vs D 49.2\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on didww.com or one of its subdomains, or the README of github.com/didww/didww-api-3-openapi. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"didww-voice-and-number-management\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/didww-voice-and-number-management\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/didww-voice-and-number-management.svg\" alt=\"DIDWW Voice and Number Management API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![DIDWW Voice and Number Management API on Anchor Terminal](https://www.anchorterminal.com/badges/didww-voice-and-number-management.svg)](https://www.anchorterminal.com/tools/didww-voice-and-number-management)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/didww-voice-and-number-management\"\u003eDIDWW Voice and Number Management API on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say DIDWW Voice and Number Management API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/didww-voice-and-number-management-dark.png\n- Light: https://www.anchorterminal.com/assets/share/didww-voice-and-number-management-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Phone calling \u0026 voice transport", "url": "https://www.anchorterminal.com/categories/voice-calling" }, { "name": "DIDWW Voice and Number Management API", "url": "" } ], "description": "DIDWW is a telecoms carrier selling phone numbers in more than 90 countries with inbound and outbound SIP trunking. Its REST API v3 orders numbers and configures trunks and capacity, and a remote MCP server covers the same account tasks.", "facts": [ "rank #330 of 950", "API key auth", "0 desk reviews" ], "h1": "DIDWW Voice and Number Management API", "image": "https://www.anchorterminal.com/assets/og/tools-didww-voice-and-number-management.png", "path": "/tools/didww-voice-and-number-management", "published": "2026-10-01", "section": "tools", "title": "DIDWW Voice and Number Management review (2026), grade B", "toc": null, "updated": "2026-10-10", "url": "https://www.anchorterminal.com/tools/didww-voice-and-number-management" }, "tokens": { "markdown": 9050, "slim": 1880 }, "version": 1 }