{ "data": { "a": { "slug": "didlogic", "name": "didlogic Voice API", "vendor": "DID Logic PTE. LTD.", "vendorUrl": "https://didlogic.com", "kind": "http-api", "category": "voice-calling", "summary": "didlogic sells SIP trunking, outbound voice and phone numbers in 140 or more countries, with a REST API for numbers, SIP accounts, call records, recordings, SMS and click-to-call, WebSocket calls for voice AI and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/didlogic", "markdownUrl": "https://www.anchorterminal.com/tools/didlogic.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/didlogic.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/didlogic.json", "dns": "didlogic.grade.anchorterminal.com", "license": "Proprietary service under the didlogic Terms of Service", "transports": [ "http", "websocket", "streamable-http" ], "remoteUrl": "https://mcp.didlogic.com/mcp", "packages": [], "auth": "mixed", "authNotes": "Bearer API keys generated and revoked in the portal under API \u0026 Webhooks since July 2026, each with full access to the account. The MCP server signs in by OAuth and creates a separate key per sign-in, or takes a key in a header. The get-started page still says to ask an account manager for a key.", "pricing": "usage", "pricingNotes": "Prepaid pay as you go. Outbound calls by destination, for example UK landlines from $0.05 a minute and UK mobiles from $0.0175. Numbers from $2 a month for local and $3 for mobile, plus inbound from $0.01 a minute. Free test credit with no card. The MCP server needs the Plus plan (checked 2026-11-06).", "priceSummary": "$2 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, OpenAPI file or pricing pages (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.didlogic.com/docs/api/get-started/", "llmsTxt": "https://docs.didlogic.com/llms.txt", "openapi": "https://docs.didlogic.com/public_api.openapi.yaml", "capabilities": [ "voice.numbers", "voice.sip", "voice.calls", "voice.streaming", "voice.recording", "messaging.sms" ], "tags": [ "hosted", "official", "closed-source", "usage", "prepaid", "no-card", "openapi", "llms-txt", "mcp", "remote-mcp", "oauth", "webhooks", "websocket", "sip", "phone-numbers", "iso27001" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 49.8, "grade": "D", "agentReady": false, "rank": 1074, "ranked": true, "rankOf": 1486, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 38, "payments": 38, "reliability": 26, "schema": 87, "security": 46, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "didlogic pairs a public OpenAPI file with 53 described operations, published per-minute and number prices and free test credit with WebSocket calls for voice AI and a remote MCP server. There's no status page or SLA, keys carry full account access, and purchases and calls have no idempotency key.", "bestFor": "Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent.", "strengths": [ "Public OpenAPI 3.0.3 file with 53 described operations and llms.txt", "Per-minute call rates and number prices published by country, with free test credit and no card", "WebSocket calls and click-to-call for voice AI since September 2026", "Remote MCP server with OAuth sign-in", "ISO/IEC 27001:2022 certificate with a registration number" ], "weaknesses": [ "No status page or incident history found", "No SLA in the Terms, despite a 99.999 per cent uptime claim on the site", "API keys have full account access, with no scopes or read-only keys", "No idempotency keys on number purchases or click-to-call", "No retention periods in the privacy policy" ], "agentNotes": [ "Create the key under API \u0026 Webhooks in the portal; ignore the older get-started line about asking an account manager", "Confirm with the user before `POST /api/v2/numbers/purchase` or click-to-call; both spend the prepaid balance with no idempotency key", "For WebSocket calls, set `a_type: stream` and implement didlogic's message protocol on your endpoint", "Back off on 429 from recording endpoints using Retry-After", "Expect the MCP server only on the Plus plan" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.8 } ], "editorialScores": { "ergonomics": 57, "maintenance": 38, "payments": 38, "reliability": 26, "schema": 87, "security": 46, "transparency": 37 }, "provenanceScore": 79, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X GET \"https://api.didlogic.com/v2/numbers\" \\\n -H \"Authorization: Bearer YOUR_TOKEN\" \\\n -H \"Content-Type: application/json\"", "claudeCode": "claude mcp add --transport http didlogic https://mcp.didlogic.com/mcp", "config": { "mcpServers": { "didlogic": { "url": "https://mcp.didlogic.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/voice.numbers", "tool": "https://letme.dev/didlogic" }, "area": "voice", "unitPrices": [ { "item": "Outbound call, UK landline", "unit": "call-minute", "usd": 0.05, "note": "from, indicative standard-account rate" }, { "item": "Outbound call, UK mobile", "unit": "call-minute", "usd": 0.0175, "note": "from, Vodafone mobile route" }, { "item": "Local number", "unit": "month", "usd": 2, "note": "from, plus inbound from $0.01 a minute" }, { "item": "Mobile number", "unit": "month", "usd": 3, "note": "from, plus inbound from $0.01 a minute" } ], "provenance": { "legalEntity": "DID Logic PTE. LTD.", "domain": "didlogic.com", "domainRegistered": "2007-10-24", "endpointOnVendorDomain": true, "terms": "https://didlogic.com/terms-and-conditions/", "privacy": "https://didlogic.com/privacy-and-security/", "statusPage": "", "changelog": "https://docs.didlogic.com/docs/release-notes", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Terms of Service name DID Logic PTE. LTD., a Singapore company at 15 Scotts Road, with ICDR arbitration. No clause on automated access to the website was found; automated list dialling on the services is barred.", "didlogic.com/robots.txt allows all agents except /wp-admin/. The docs site serves llms.txt.", "The network status page linked from the footer is a marketing page with no components or incident history, so no status page is recorded.", "/.well-known/security.txt returns 404. RDAP gives didlogic.com a registration date of 24 October 2007." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/didlogic.json", "live": { "slug": "didlogic", "probe": { "target": "https://mcp.didlogic.com/mcp", "method": "get", "lastAt": "2026-11-07T18:20:20.921736Z", "lastOk": true, "lastStatus": 401, "lastMs": 185, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 98, "p95ms24h": 183, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "securityTxt": { "url": "https://didlogic.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:26.525637047Z" }, "llmsTxt": { "url": "https://docs.didlogic.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:17.001857789Z" }, "pages": [ { "url": "https://docs.didlogic.com/docs/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:09.15338969Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ac3b4a97e7ff" }, { "url": "https://didlogic.com/privacy-and-security/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:04:46.42500505Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c012e842c316" }, { "url": "https://didlogic.com/terms-and-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:04:48.65331055Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "730ca804743f" } ], "mcpTools": { "url": "https://mcp.didlogic.com/mcp", "checkedAt": "2026-11-07T01:43:42.469443076Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:43:42.469443076Z" }, "updatedAt": "2026-11-07T18:20:20.921736Z" } }, "answer": "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 \u0026 pricing.", "b": { "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", "dns": "didww-voice-and-number-management.grade.anchorterminal.com", "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": "Number prices are public per prefix and country (monthly price, setup price and inbound per-minute rate), for example United States local numbers from $1.20 a month and $0.010 a minute inbound, with toll-free from $5.00 and UIFN from $25.00. Starting outbound per-minute rates are public per destination country (United States from $0.004 a minute); exact outbound rates and flat-rate channel prices come in price lists sent on request, inside an account or through the API. Accounts are free and prepaid in US dollars, with a $30 minimum balance before ordering. A number's one-time fee equals one month's charge and is waived for API orders. The sandbox is free and takes Stripe test cards (https://www.didww.com/pricing.md, prices generated 2026-10-30, checked 2026-11-02).", "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": 64.7, "grade": "B", "agentReady": false, "rank": 456, "ranked": true, "rankOf": 1486, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 83, "payments": 27, "reliability": 71, "schema": 87, "security": 57, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -3, "negativeNotes": [ "2026-10-06: DIDWW changed how callbacks are signed and when they are sent on the released API version 2026-04-16. The OpenAPI revision of that day says it follows a platform change, after which callbacks are signed with a separate callback secret created in the User Panel instead of an API key with callbacks enabled, and nothing is sent to an account with no enabled callback secret. Receivers verifying with an API key, and accounts without a secret, are affected. No advance notice was found, the version's changelog page has no entry on 2 November, and the configuration page describes no migration. A published behaviour changed for existing clients with notice no earlier than the day it took effect takes -3 (https://github.com/didww/didww-api-3-openapi/commit/9ee36774515e26b433cf84c742ce7d30f8beed89, https://doc.didww.com/api3/2026-04-16/callbacks-details.html)" ], "verdict": "An OpenAPI 3.0.3 document with 107 operations, Markdown docs, a free sandbox, public number prices and SDKs in seven languages cover number ordering and SIP trunk set-up. API keys carry no scopes, orders have no idempotency key, and the 6 October change to callback signing came with no advance notice. 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 TypeScript v3.1.1 and Python v3.2.0 tagged on 7 October 2026", "Every number prefix is priced publicly, with monthly, setup and inbound per-minute rates by country" ], "weaknesses": [ "Only starting outbound rates per country are public, and flat-rate channel prices aren't, though number prices are. 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 with no advance notice found, and the 2026-04-16 changelog page doesn't 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": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.7 } ], "editorialScores": { "ergonomics": 77, "maintenance": 83, "payments": 27, "reliability": 71, "schema": 87, "security": 57, "transparency": 55 }, "provenanceScore": 86, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "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" }, "area": "voice", "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-11-02", "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 on 2026-10-09 and again on 2026-11-02.", "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.", "status.didww.com's robots.txt answered a plain 404 (no rules) on 2026-11-02; its history.rss was read." ], "score": 86 }, "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-11-07T18:20:20.951790821Z", "lastOk": true, "lastStatus": 401, "lastMs": 492, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.97, "p50ms24h": 407, "p95ms24h": 554, "samples24h": 239, "samples30d": 7205, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 252 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 247 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.didww.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:38.652340336Z" }, "versions": [ { "registry": "npm", "name": "@didww/sdk", "version": "3.1.1", "seenAt": "2026-11-06T23:21:14.088263657Z" }, { "registry": "pypi", "name": "didww", "version": "3.2.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:21:18.719106102Z" } ], "githubStars": 10, "npmWeekly": 685, "pypiWeekly": 1356, "securityTxt": { "url": "https://didww.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:00.662782916Z" }, "llmsTxt": { "url": "https://doc.didww.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:17.236935847Z" }, "domain": { "domain": "didww.com", "registered": "2006-01-16", "source": "https://rdap.verisign.com/com/v1/domain/didww.com", "checkedAt": "2026-11-01T14:11:41.435438414Z" }, "pages": [ { "url": "https://doc.didww.com/api3/2026-04-16/changelog.html", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:04:50.724453534Z", "changedAt": "2026-11-06T13:27:24.565918009Z", "fingerprint": "6661f4d6d221" }, { "url": "https://www.didww.com/pricing.md", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:27:54.057234776Z", "changedAt": "2026-11-06T13:48:43.145837843Z", "fingerprint": "f9ed686a776d" }, { "url": "https://www.didww.com/privacy-notice", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:27:56.045397148Z", "changedAt": "2026-11-06T13:48:45.714959363Z", "fingerprint": "66980ed17be7" }, { "url": "https://www.didww.com/DIDWW-Terms-and-Agreements", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:27:52.027440948Z", "changedAt": "2026-11-06T13:48:40.395284975Z", "fingerprint": "5f4241812a08" } ], "github": { "repo": "didww/didww-api-3-openapi", "checkedAt": "2026-11-02T08:44:10.261176733Z", "stars": 10, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-22T11:53:49Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 24, "ci": { "branch": "main", "runs": 11, "success": 10, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-10-22T11:07:21Z" } }, "updatedAt": "2026-11-07T18:20:20.951790821Z" } }, "edges": [ { "by": 45, "category": "reliability", "leads": "didww-voice-and-number-management", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 26, "b": 71 } }, { "by": 45, "category": "maintenance", "leads": "didww-voice-and-number-management", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 38, "b": 83 } }, { "by": 20, "category": "ergonomics", "leads": "didww-voice-and-number-management", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 57, "b": 77 } }, { "by": 13, "category": "transparency", "leads": "didww-voice-and-number-management", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 58, "b": 71 } }, { "by": 11, "category": "security", "leads": "didww-voice-and-number-management", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 46, "b": 57 } }, { "by": 11, "category": "payments", "leads": "didlogic", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 38, "b": 27 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "DID Logic PTE. LTD.", "b": "DIDWW Ireland Limited", "name": "Vendor" }, { "a": "https://mcp.didlogic.com/mcp", "b": "https://api.didww.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, websocket, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$2 per month (plan)", "b": "not published", "name": "Price for phone numbers" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the didlogic Terms of Service", "b": "Proprietary service under the DIDWW Terms and Agreements (Rev 3.1). The OpenAPI repository and the official SDKs are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-10-07", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "10 stars, 462 npm/wk", "name": "Popularity" }, { "a": "none", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, didlogic Voice API or DIDWW Voice and Number Management API?" }, { "answer": "didlogic Voice API takes an API key or an OAuth sign-in. DIDWW Voice and Number Management API needs an API key.", "question": "Do didlogic Voice API and DIDWW Voice and Number Management API need an API key?" }, { "answer": "Yes. didlogic Voice API has a hosted endpoint at https://mcp.didlogic.com/mcp and DIDWW Voice and Number Management API at https://api.didww.com/mcp.", "question": "Can an agent call didlogic Voice API and DIDWW Voice and Number Management API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 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" ], "goodFor": "Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent.", "slug": "didlogic", "watchFor": "No status page or incident history found" }, { "aheadOn": [ "Reliability, 71 against 26", "Agent ergonomics, 77 against 57", "Security \u0026 auth, 57 against 46", "Maintenance \u0026 community, 83 against 38", "Transparency \u0026 trust, 71 against 58" ], "also": null, "goodFor": "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.", "slug": "didww-voice-and-number-management", "watchFor": "Only starting outbound rates per country are public, and flat-rate channel prices aren't, though number prices are. A $30 balance is needed before ordering" } ], "history": { "didlogic": null, "didww-voice-and-number-management": [ { "causes": [ "pricing", "correction", "event" ], "date": "2026-11-02", "delta": -0.5, "from": 65.2, "fromGrade": "B", "to": 64.7, "toGrade": "B" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.1, "from": 65.1, "fromGrade": "B", "to": 65.2, "toGrade": "B" } ] }, "job": { "capability": "voice.numbers", "name": "Phone numbers" }, "others": [ { "json": "https://www.anchorterminal.com/compare/46elks-vs-didlogic.json", "title": "46elks Voice API vs didlogic Voice API", "url": "https://www.anchorterminal.com/compare/46elks-vs-didlogic" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-didlogic.json", "title": "Bandwidth Voice API + MCP vs didlogic Voice API", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-didlogic" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-jambonz.json", "title": "didlogic Voice API vs jambonz", "url": "https://www.anchorterminal.com/compare/didlogic-vs-jambonz" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management.json", "title": "46elks Voice API vs DIDWW Voice and Number Management API", "url": "https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-didww-voice-and-number-management.json", "title": "Bandwidth Voice API + MCP vs DIDWW Voice and Number Management API", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-didww-voice-and-number-management" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-exotel-voice.json", "title": "didlogic Voice API vs Exotel Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didlogic-vs-exotel-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls.json", "title": "didlogic Voice API vs Infobip Calls API + MCP", "url": "https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony.json", "title": "didlogic Voice API vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-plivo-voice.json", "title": "didlogic Voice API vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/didlogic-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-signalwire-voice.json", "title": "didlogic Voice API vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/didlogic-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-sinch-voice.json", "title": "didlogic Voice API vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didlogic-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-telnyx-voice.json", "title": "didlogic Voice API vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didlogic-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-twilio-voice.json", "title": "didlogic Voice API vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didlogic-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.json", "title": "didlogic Voice API vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-voximplant.json", "title": "didlogic Voice API vs Voximplant", "url": "https://www.anchorterminal.com/compare/didlogic-vs-voximplant" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-exotel-voice.json", "title": "DIDWW Voice and Number Management API vs Exotel Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-exotel-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-infobip-calls.json", "title": "DIDWW Voice and Number Management API vs Infobip Calls API + MCP", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-infobip-calls" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.json", "title": "DIDWW Voice and Number Management API vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-plivo-voice.json", "title": "DIDWW Voice and Number Management API vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-signalwire-voice.json", "title": "DIDWW Voice and Number Management API vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-sinch-voice.json", "title": "DIDWW Voice and Number Management API vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-telnyx-voice.json", "title": "DIDWW Voice and Number Management API vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-twilio-voice.json", "title": "DIDWW Voice and Number Management API vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice.json", "title": "DIDWW Voice and Number Management API vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-voximplant.json", "title": "DIDWW Voice and Number Management API vs Voximplant", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-voximplant" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-jambonz.json", "title": "DIDWW Voice and Number Management API vs jambonz", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-jambonz" } ], "panel": null, "scores": [ { "by": 45, "didlogic": 26, "didww-voice-and-number-management": 71, "edge": "didww-voice-and-number-management", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 0, "didlogic": 87, "didww-voice-and-number-management": 87, "edge": "", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 20, "didlogic": 57, "didww-voice-and-number-management": 77, "edge": "didww-voice-and-number-management", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 11, "didlogic": 46, "didww-voice-and-number-management": 57, "edge": "didww-voice-and-number-management", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 11, "didlogic": 38, "didww-voice-and-number-management": 27, "edge": "didlogic", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 45, "didlogic": 38, "didww-voice-and-number-management": 83, "edge": "didww-voice-and-number-management", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 13, "didlogic": 58, "didww-voice-and-number-management": 71, "edge": "didww-voice-and-number-management", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \u0026 pricing. Both do phone numbers.", "tasks": null, "tutorials": [], "verdicts": { "didlogic": "didlogic pairs a public OpenAPI file with 53 described operations, published per-minute and number prices and free test credit with WebSocket calls for voice AI and a remote MCP server. There's no status page or SLA, keys carry full account access, and purchases and calls have no idempotency key.", "didww-voice-and-number-management": "An OpenAPI 3.0.3 document with 107 operations, Markdown docs, a free sandbox, public number prices and SDKs in seven languages cover number ordering and SIP trunk set-up. API keys carry no scopes, orders have no idempotency key, and the 6 October change to callback signing came with no advance notice. Calls travel over SIP only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management", "json": "https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.min.md" }, "markdown": "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 \u0026 pricing. Both do phone numbers.\n\n- didlogic Voice API: grade D, 49.8/100, rank #1074 of 1486. Markdown https://www.anchorterminal.com/tools/didlogic.md · JSON https://www.anchorterminal.com/api/v1/tools/didlogic.json\n- DIDWW Voice and Number Management API: grade B, 64.7/100, rank #456 of 1486. Markdown https://www.anchorterminal.com/tools/didww-voice-and-number-management.md · JSON https://www.anchorterminal.com/api/v1/tools/didww-voice-and-number-management.json\n- Best phone calling and voice transport APIs for AI agents: https://www.anchorterminal.com/best/voice-calling/index.md\n- All 105 calling comparisons: https://www.anchorterminal.com/compare/voice-calling/index.md\n\n## Which one, for what\n\n### didlogic Voice API (D)\n\nGood for: Teams that need numbers and SIP termination in many countries and a WebSocket bridge to a voice agent.\n\nAhead on:\n- Payments \u0026 pricing, 38 against 27\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where DIDWW Voice and Number Management API loses 3 points for them\n\nWatch for: No status page or incident history found\n\n### DIDWW Voice and Number Management API (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 71 against 26\n- Agent ergonomics, 77 against 57\n- Security \u0026 auth, 57 against 46\n- Maintenance \u0026 community, 83 against 38\n- Transparency \u0026 trust, 71 against 58\n\nWatch for: Only starting outbound rates per country are public, and flat-rate channel prices aren't, though number prices are. A $30 balance is needed before ordering\n\n\n## Why the edge\n\n### Reliability: DIDWW Voice and Number Management API +45\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: DIDWW Voice and Number Management API +45\n\n- 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.\n- 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.\n\n### Agent ergonomics: DIDWW Voice and Number Management API +20\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: DIDWW Voice and Number Management API +13\n\n- 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.\n- 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.\n\n### Security \u0026 auth: DIDWW Voice and Number Management API +11\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: didlogic Voice API +11\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | didlogic Voice API | DIDWW Voice and Number Management API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 26 | 71 | DIDWW Voice and Number Management API +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 87 | even |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 77 | DIDWW Voice and Number Management API +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 57 | DIDWW Voice and Number Management API +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 38 | 27 | didlogic Voice API +11 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 38 | 83 | DIDWW Voice and Number Management API +45 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 71 | DIDWW Voice and Number Management API +13 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **49.8 · D** | **64.7 · B** | |\n\n## Facts side by side\n\n| Fact | didlogic Voice API | DIDWW Voice and Number Management API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | DID Logic PTE. LTD. | DIDWW Ireland Limited |\n| Hosted endpoint | `https://mcp.didlogic.com/mcp` | `https://api.didww.com/mcp` |\n| Transports | HTTP, websocket, Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for phone numbers | $2 per month (plan) | not published |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-10-07 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 10 stars, 462 npm/wk |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### didlogic Voice API\n\nNo score change since it was listed.\n\n### DIDWW Voice and Number Management API\n\n- -0.5 on 2 November 2026: pricing, correction, negative event\n- +0.1 on 27 October 2026: new evidence\n\n## Verdicts\n\n**didlogic Voice API.** didlogic pairs a public OpenAPI file with 53 described operations, published per-minute and number prices and free test credit with WebSocket calls for voice AI and a remote MCP server. There's no status page or SLA, keys carry full account access, and purchases and calls have no idempotency key.\n\n**DIDWW Voice and Number Management API.** An OpenAPI 3.0.3 document with 107 operations, Markdown docs, a free sandbox, public number prices and SDKs in seven languages cover number ordering and SIP trunk set-up. API keys carry no scopes, orders have no idempotency key, and the 6 October change to callback signing came with no advance notice. Calls travel over SIP only.\n\n## Before you call either\n\n### didlogic Voice API\n\n1. Create the key under API \u0026 Webhooks in the portal; ignore the older get-started line about asking an account manager\n2. Confirm with the user before `POST /api/v2/numbers/purchase` or click-to-call; both spend the prepaid balance with no idempotency key\n3. For WebSocket calls, set `a_type: stream` and implement didlogic's message protocol on your endpoint\n4. Back off on 429 from recording endpoints using Retry-After\n5. Expect the MCP server only on the Plus plan\n\n### DIDWW Voice and Number Management API\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## Questions\n\n### Which is better for AI agents, didlogic Voice API or DIDWW Voice and Number Management API?\n\nDIDWW 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 \u0026 pricing.\n\n### Do didlogic Voice API and DIDWW Voice and Number Management API need an API key?\n\ndidlogic Voice API takes an API key or an OAuth sign-in. DIDWW Voice and Number Management API needs an API key.\n\n### Can an agent call didlogic Voice API and DIDWW Voice and Number Management API without installing anything?\n\nYes. didlogic Voice API has a hosted endpoint at https://mcp.didlogic.com/mcp and DIDWW Voice and Number Management API at https://api.didww.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.json, and with the fewest tokens: https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"didlogic\", \"b\": \"didww-voice-and-number-management\"}`. From a terminal: `anchor compare didlogic didww-voice-and-number-management`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/didlogic.json and https://www.anchorterminal.com/api/v1/tools/didww-voice-and-number-management.json\n\n## Other comparisons with didlogic Voice API or DIDWW Voice and Number Management API\n\n- [46elks Voice API vs didlogic Voice API](https://www.anchorterminal.com/compare/46elks-vs-didlogic.md)\n- [Bandwidth Voice API + MCP vs didlogic Voice API](https://www.anchorterminal.com/compare/bandwidth-voice-vs-didlogic.md)\n- [didlogic Voice API vs jambonz](https://www.anchorterminal.com/compare/didlogic-vs-jambonz.md)\n- [46elks Voice API vs DIDWW Voice and Number Management API](https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management.md)\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)\n- [didlogic Voice API vs Exotel Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-exotel-voice.md)\n- [didlogic Voice API vs Infobip Calls API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-infobip-calls.md)\n- [didlogic Voice API vs LiveKit Telephony](https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony.md)\n- [didlogic Voice API vs Plivo Voice API](https://www.anchorterminal.com/compare/didlogic-vs-plivo-voice.md)\n- [didlogic Voice API vs SignalWire Voice API](https://www.anchorterminal.com/compare/didlogic-vs-signalwire-voice.md)\n- [didlogic Voice API vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-sinch-voice.md)\n- [didlogic Voice API vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-telnyx-voice.md)\n- [didlogic Voice API vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-twilio-voice.md)\n- [didlogic Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.md)\n- [didlogic Voice API vs Voximplant](https://www.anchorterminal.com/compare/didlogic-vs-voximplant.md)\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)\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)\n- [DIDWW Voice and Number Management API vs LiveKit Telephony](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.md)\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)\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)\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)\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)\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)\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)\n- [DIDWW Voice and Number Management API vs Voximplant](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-voximplant.md)\n- [DIDWW Voice and Number Management API vs jambonz](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-jambonz.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "didlogic Voice API vs DIDWW Voice and Number Management API", "url": "" } ], "description": "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.", "facts": [ "didlogic Voice API D 49.8", "DIDWW Voice and Number Management API B 64.7", "scores" ], "h1": "didlogic Voice API vs DIDWW Voice and Number Management API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/didlogic-vs-didww-voice-and-number-management", "published": "2026-10-01", "section": "tools", "title": "didlogic Voice vs DIDWW Voice and Number Management (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management" }, "tokens": { "markdown": 5650, "slim": 3230 }, "version": 1 }