{ "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": "Vonage Voice API + MCP scores 59 (C) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 5 of 7 scored categories. didlogic Voice API leads on transparency \u0026 trust.", "b": { "slug": "vonage-voice", "name": "Vonage Voice API + MCP", "vendor": "Vonage (Ericsson)", "vendorUrl": "https://www.vonage.com", "kind": "http-api", "category": "voice-calling", "summary": "Voice API that controls calls with NCCO, a JSON list of actions such as talk, input, record, connect and transfer.", "url": "https://www.anchorterminal.com/tools/vonage-voice", "markdownUrl": "https://www.anchorterminal.com/tools/vonage-voice.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vonage-voice.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vonage-voice.json", "dns": "vonage-voice.grade.anchorterminal.com", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://api.nexmo.com/v1", "packages": [ { "registry": "npm", "name": "@vonage/server-sdk" }, { "registry": "pypi", "name": "vonage" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings" } ], "auth": "mixed", "authNotes": "The Voice API takes a Vonage Application JWT signed RS256 with the application's private key. Signed webhooks carry an HS256 JWT to verify with the signature secret. The MCP server reads the API key, secret, application ID and a base64 private key from env vars.", "pricing": "usage", "pricingNotes": "Pay as you go, billed per second. US outbound $0.01446 a minute, inbound $0.00495 on local numbers and $0.0154 on toll-free. Calls to or from SIP, in-app (WebRTC) and websocket endpoints $0.00492 a minute. US numbers €1.81 a month. New accounts get test credit with no card. Rates are from Vonage's downloadable pricing sheet, since the pricing page blocks automated requests (https://www.vonage.com/communications-apis/voice/pricing/).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).", "endpoints": [] }, "toolCount": 14, "popularity": { "githubStars": null, "npmWeekly": 154249, "pypiWeekly": 67062, "asOf": "2026-09-30" }, "docsUrl": "https://developer.vonage.com/en/voice/voice-api/overview", "llmsTxt": "https://developer.vonage.com/llms.txt", "openapi": "https://developer.vonage.com/api/v1/developer/api/file/voice?format=json", "registryName": "io.github.Vonage/vonage-documentation-mcp", "capabilities": [ "voice.calls", "voice.numbers", "voice.streaming", "voice.sip", "voice.recording", "voice.transfer" ], "tags": [ "hosted", "no-card", "mcp", "llms-txt", "openapi", "typescript", "python", "webhooks", "streaming", "enterprise" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 59, "grade": "C", "agentReady": false, "rank": 717, "ranked": true, "rankOf": 1486, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 51, "payments": 35, "reliability": 45, "schema": 88, "security": 73, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": 0, "verdict": "Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.", "bestFor": "Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.", "strengths": [ "Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions", "Per-second billing on every call", "Short-lived application JWTs whose ACLs can limit a token to named paths and methods, and signed webhooks with a body hash", "OpenAPI spec and an llms.txt that tells agents which hosts to use", "€2 test credit without a card" ], "weaknesses": [ "First call needs an application, a private key and a signed JWT", "No Voice API rate limit or SLA found, and the error catalogue's throttling advice is to wait an amount that differs per API", "Pricing page returns 403 to automated requests, rates live in a spreadsheet", "MCP server has no tools for live call control, only a one-way voice message", "No security.txt, and the API runs on the legacy nexmo.com domain" ], "agentNotes": [ "Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts", "Use a `connect` action with a websocket endpoint and `audio/l16;rate=16000` for speech models", "Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it", "Enable signed webhooks and verify the HS256 JWT on each event", "Expect RFC 7807 errors (`type`, `title`, `detail`, `instance`) and back off on a throttling error, since no Voice rate limit is published" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59 } ], "editorialScores": { "ergonomics": 60, "maintenance": 51, "payments": 35, "reliability": 45, "schema": 88, "security": 73, "transparency": 28 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://api.nexmo.com/v1/calls -H \"Authorization: Bearer $VONAGE_JWT\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"to\":[{\"type\":\"phone\",\"number\":\"14155550100\"}],\"from\":{\"type\":\"phone\",\"number\":\"14155550101\"},\"ncco\":[{\"action\":\"talk\",\"text\":\"Hello from Vonage\"}]}'", "claudeCode": "claude mcp add --transport http vonage-docs https://documentation-mcp.vonage.dev/mcp", "config": { "mcpServers": { "vonage": { "args": [ "-y", "@vonage/vonage-mcp-server-api-bindings" ], "command": "npx", "env": { "VONAGE_API_KEY": "${VONAGE_API_KEY}", "VONAGE_API_SECRET": "${VONAGE_API_SECRET}", "VONAGE_APPLICATION_ID": "${VONAGE_APPLICATION_ID}", "VONAGE_PRIVATE_KEY64": "${VONAGE_PRIVATE_KEY64}", "VONAGE_VIRTUAL_NUMBER": "${VONAGE_VIRTUAL_NUMBER}" } } } } }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/vonage-voice" }, "sameCompany": [ "vonage" ], "area": "voice", "unitPrices": [ { "item": "Outbound call, US", "unit": "call-minute", "usd": 0.01446, "note": "billed per second" }, { "item": "Inbound call, US local number", "unit": "call-minute", "usd": 0.00495, "note": "billed per second" }, { "item": "Inbound call, US toll-free number", "unit": "call-minute", "usd": 0.0154 }, { "item": "Websocket, SIP or in-app leg", "unit": "call-minute", "usd": 0.00492 } ], "provenance": { "legalEntity": "Vonage Holdings Corp.", "domain": "vonage.com", "domainRegistered": "2000-12-12", "domainNote": "The API endpoints sit on the legacy nexmo.com domain, from Nexmo's acquisition in 2016.", "endpointOnVendorDomain": false, "terms": "https://www.vonage.com/legal/communications-apis/terms-of-use/", "privacy": "https://www.vonage.com/legal/privacy-policy/", "statusPage": "https://vonageapi.statuspage.io", "changelog": "https://developer.vonage.com/en/changelogs", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The privacy notice names Vonage Holdings Corp. as controller where one entity applies. The API terms set the contracting entity by customer region in Schedule 1, which we couldn't read because vonage.com returned 403 to automated requests." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage-voice.json", "live": { "slug": "vonage-voice", "probe": { "target": "https://api.nexmo.com/v1", "method": "get", "lastAt": "2026-11-07T18:21:04.658291283Z", "lastOk": true, "lastStatus": 404, "lastMs": 154, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 58, "p95ms24h": 154, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "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": 253 }, { "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": 248 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-07T18:22:09.12272428Z" }, "versions": [ { "registry": "npm", "name": "@vonage/server-sdk", "version": "3.30.1", "seenAt": "2026-11-07T00:16:19.389560127Z" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings", "version": "1.5.1", "seenAt": "2026-11-07T00:16:20.487519922Z" }, { "registry": "pypi", "name": "vonage", "version": "4.9.1", "released": "2026-10-21", "seenAt": "2026-11-07T00:16:20.254079395Z" } ], "npmWeekly": 194366, "pypiWeekly": 82322, "securityTxt": { "url": "https://vonage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:47.6413736Z" }, "llmsTxt": { "url": "https://developer.vonage.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:18.781250832Z" }, "domain": { "domain": "vonage.com", "registered": "2000-12-12", "source": "https://rdap.verisign.com/com/v1/domain/vonage.com", "checkedAt": "2026-11-01T14:09:16.438838847Z" }, "pages": [ { "url": "https://developer.vonage.com/en/changelogs", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:03:29.971312167Z", "changedAt": "2026-11-05T12:27:45.0611175Z", "fingerprint": "fb6ba0c38d69" }, { "url": "https://www.vonage.com/communications-apis/voice/pricing/", "kind": "pricing", "status": 403, "checkedAt": "2026-11-07T14:36:37.674199164Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "efeb31a58cfc" }, { "url": "https://www.vonage.com/legal/privacy-policy/", "kind": "privacy", "status": 403, "checkedAt": "2026-11-07T14:36:42.430115163Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef11a28348cd" }, { "url": "https://www.vonage.com/legal/communications-apis/terms-of-use/", "kind": "terms", "status": 403, "checkedAt": "2026-11-07T14:36:42.390874884Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "004c80c35ffa" } ], "mcpTools": { "url": "https://documentation-mcp.vonage.dev/mcp", "checkedAt": "2026-11-07T01:48:57.782666429Z", "status": "ok", "protocol": "2025-06-18", "tools": [ { "name": "vonage_docs_search", "description": "Searches the official Vonage developer documentation for guides, tutorials, and API references. This is the primary tool for general queries about Vonage's products, services, and APIs, and should be used when the user asks for information, documentation, or how-to guides.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "The user's search query, which can be a keyword, phrase, or a question about Vonage's APIs or documentation", "type": "string" } }, "required": [ "query" ], "type": "object" } }, { "name": "vonage_code_generator", "description": "Generates a complete, runnable code snippet in a specified programming language for a given Vonage API task. This is the preferred tool when the user explicitly asks for a 'code snippet,' 'example,' or 'code in a specific language' like Node.js, Python, or cURL.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "A clear and concise description of the task for which the code snippet is needed (e.g., 'send an SMS', 'make a voice call').", "type": "string" } }, "required": [ "query" ], "type": "object" } }, { "name": "vonage_api_reference", "description": "Provides a direct link or detailed information from the Vonage API reference documentation for a specific API endpoint. Use this when the user's query is highly technical and related to a specific endpoint, like API parameters, request bodies, or response schemas.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "The name of the Vonage API (e.g., 'SMS API', 'Voice API', 'Messages API').", "type": "string" } }, "required": [ "query" ], "type": "object" } }, { "name": "vonage_troubleshooter", "description": "Provides troubleshooting steps, common error code explanations, and debugging advice for Vonage API issues. Use this when the user is reporting a problem, error, or something not working as expected.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "A description of the problem or error the user is experiencing, including any error messages, codes, or unexpected behavior.", "type": "string" } }, "required": [ "query" ], "type": "object" } }, { "name": "vonage_tutorial_finder", "description": "Finds and provides a link to a step-by-step tutorial or a blog post on the Vonage Developer blog. This tool is for when the user asks for a 'tutorial' or a 'guide' on a specific topic.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "The topic of the tutorial or guide (e.g., 'building a voice proxy', 'two-factor authentication', 'receiving a delivery receipt').", "type": "string" } }, "required": [ "query" ], "type": "object" } }, { "name": "vonage_sdk_info", "description": "Retrieves information about a specific Vonage SDK, including installation instructions, supported features, and version numbers. This is for queries focused on the SDKs themselves, not the underlying APIs.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "The programming language of the SDK (e.g., 'Node.js', 'Python', 'PHP').", "type": "string" } }, "required": [ "query" ], "type": "object" } }, { "name": "vonage_use_case_examples", "description": "Finds and describes real-world use cases or customer stories for a specific Vonage product. Use this when the user asks for examples of how a product is used in a specific industry or for a particular purpose.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "query": { "description": "The Vonage product (e.g., 'Video API', 'Voice API', 'Messages API').", "type": "string" } }, "required": [ "query" ], "type": "object" } } ], "schemaTokens": 994, "changedAt": "2026-11-07T01:48:57.782666429Z", "check": { "checker": "anchor-check/1.0", "totalTokens": 994, "counts": { "error": 0, "note": 1, "warn": 7 }, "findings": [ { "rule": "TC16", "severity": "warn", "tool": "vonage_api_reference", "message": "no readOnlyHint or destructiveHint", "fix": "Set readOnlyHint: true if it only reads; otherwise set destructiveHint and idempotentHint." }, { "rule": "TC16", "severity": "warn", "tool": "vonage_code_generator", "message": "no readOnlyHint or destructiveHint", "fix": "Set readOnlyHint: true if it only reads; otherwise set destructiveHint and idempotentHint." }, { "rule": "TC16", "severity": "warn", "tool": "vonage_docs_search", "message": "no readOnlyHint or destructiveHint", "fix": "Its name starts with \"search\"; if it only reads, set readOnlyHint: true so harnesses can run it without asking." }, { "rule": "TC16", "severity": "warn", "tool": "vonage_sdk_info", "message": "no readOnlyHint or destructiveHint", "fix": "Its name starts with \"info\"; if it only reads, set readOnlyHint: true so harnesses can run it without asking." }, { "rule": "TC16", "severity": "warn", "tool": "vonage_troubleshooter", "message": "no readOnlyHint or destructiveHint", "fix": "Set readOnlyHint: true if it only reads; otherwise set destructiveHint and idempotentHint." }, { "rule": "TC16", "severity": "warn", "tool": "vonage_tutorial_finder", "message": "no readOnlyHint or destructiveHint", "fix": "Set readOnlyHint: true if it only reads; otherwise set destructiveHint and idempotentHint." }, { "rule": "TC16", "severity": "warn", "tool": "vonage_use_case_examples", "message": "no readOnlyHint or destructiveHint", "fix": "Set readOnlyHint: true if it only reads; otherwise set destructiveHint and idempotentHint." }, { "rule": "TC24", "severity": "note", "message": "7 of 7 tools have no outputSchema", "fix": "Declare outputSchema for tools that return structured data, and return structuredContent that matches it." } ] } }, "updatedAt": "2026-11-07T18:22:09.12272428Z" } }, "edges": [ { "by": 27, "category": "security", "leads": "vonage-voice", "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": "Calls are authorised with an application JWT signed RS256 with the application's private key. Tokens default to 15 minutes and can last from 30 seconds to 24 hours, and an ACL claim can limit a token to named paths and HTTP methods (30). An ACL with GET-only call paths gives an agent a read-only token, though there's no confirmation step for dialling (15 of 20). Calls carry untrusted caller speech. Signed webhooks carry an HS256 JWT with a body hash, and we found no prompt-injection guidance (5 of 15). Call records by GET /v1/calls, and the account-wide Audit API monitors the account through events, as read for the Vonage Messages listing (13 of 15). Per the 2 October reading of www.vonage.com/security/ (bot check since), Vonage holds ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR across its product lines without saying which cover the Communications APIs. No security.txt, disclosure policy or bug bounty found. OSV lists no advisory for @vonage/server-sdk, vonage or the MCP package. The same page and reading give the Vonage Messages listing 10 (10 of 20). 30 + 15 + 5 + 13 + 10 = 73." }, "scores": { "a": 46, "b": 73 } }, { "by": 19, "category": "reliability", "leads": "vonage-voice", "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": "Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 4 November, list Voice entries from 6 August labelled minor or none. Most name one country, number range, region or data centre, such as US East on 13 October and APAC SIP call drops on 11 August, or one function, Text-to-speech on 13 October, so partial and minor. 'Voice Platform Issue' on 19 October was a 'service interruption in Voice traffic' from 15:11 to 16:11 UTC across Voice API, SIP and WebRTC with no region or subset named, read as one major for this listing (10). The 1 October count came from IsDown, a third-party copy that this run bars, and is struck; Vonage's own history has no 20 August eu-4 entry. Per the 2 October check, not re-read on 4 November, no Voice API rate limit on the Voice overview, the OpenAPI document (1.10.0), the API error catalogue or llms.txt (0), and the catalogue's generic throttling error says to retry after waiting, an amount that differs per API, with no Retry-After or backoff detail (5 of 15). No SLA found (0). Voice API is generally available (10). 20 + 10 + 0 + 5 + 0 + 10 = 45." }, "scores": { "a": 26, "b": 45 } }, { "by": 13, "category": "maintenance", "leads": "vonage-voice", "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": "Vonage's SDKs bundle every Vonage API, so their releases count here only where they change voice code, as the Groq speech-to-text and Gemini embedding listings read their SDKs. vonage-java-sdk v9.15.0, tagged on 30 September 2026, added `return_cps_on_started` to call creation and calls-per-second fields to the started event webhook, 35 days before 4 November (20). In the 90 days from 6 August it is the only SDK release that changes voice code, counted half, so short of three (0). vonage-node-sdk v3.30.0 and v3.30.1, vonage-python-sdk v4.9.0 and v4.9.1, vonage-java-sdk v9.13.0, v9.13.1, v9.14.0 and v9.15.1, vonage-php-sdk-core 4.15.0 and vonage-ruby-sdk 7.36.0 change other APIs, shared client code or formatting. The Python voice package last changed on 20 July (1.5.1, in v4.8.2), and the Node voice package had only version bumps and a lint reformat. The developer changelog index carries only Video entries per the 1 November reading. Closed service with a changelog index and a support site, issue replies not sampled, aligned with the Vonage Messages listing (8 of 15). Official SDKs in six languages (15). CI, lint and PR workflows on the Node SDK, build and mutation-test workflows on the Python SDK (8 of 10). 20 + 0 + 8 + 15 + 8 = 51." }, "scores": { "a": 38, "b": 51 } }, { "by": 9, "category": "transparency", "leads": "didlogic", "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": "Closed service. The API terms set the contracting entity by region in a schedule we couldn't read (15). Per the 2 October check (www.vonage.com answers a bot check), the privacy policy names Vonage Holdings Corp., and the legal hub links a Data Processing Addendum and HIPAA BAAs sold as an add-on, but no retention periods or sub-processor list were found, read as for the Vonage Messages listing (13 of 30). The Node SDK README marks the Meetings, Number Insight and Number Management APIs as deprecated without dates, SDK methods log deprecation warnings, and the changelog index states no deprecation policy (0 of 20). No sub-processor list or data locations found (0). 15 + 13 + 0 + 0 = 28." }, "scores": { "a": 58, "b": 49 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "DID Logic PTE. LTD.", "b": "Vonage (Ericsson)", "name": "Vendor" }, { "a": "https://mcp.didlogic.com/mcp", "b": "https://api.nexmo.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, websocket, Streamable HTTP", "b": "HTTP, stdio, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$2 per month (plan)", "b": "$0.005 per minute of call", "name": "Price for phone numbers" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the didlogic Terms of Service", "b": "none", "name": "Licence" }, { "a": "none", "b": "14", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.Vonage/vonage-documentation-mcp", "name": "MCP registry" }, { "a": "2026-09-30", "b": "2026-10-21", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "154k npm/wk, 67k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Vonage Voice API + MCP scores 59 (C) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 5 of 7 scored categories. didlogic Voice API leads on transparency \u0026 trust.", "question": "Which is better for AI agents, didlogic Voice API or Vonage Voice API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do didlogic Voice API and Vonage Voice API + MCP need an API key?" }, { "answer": "Yes. didlogic Voice API has a hosted endpoint at https://mcp.didlogic.com/mcp and Vonage Voice API + MCP at https://api.nexmo.com/v1.", "question": "Can an agent call didlogic Voice API and Vonage Voice API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 58 against 49" ], "also": null, "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, 45 against 26", "Security \u0026 auth, 73 against 46", "Maintenance \u0026 community, 51 against 38" ], "also": [ "Runs on your own machine" ], "goodFor": "Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.", "slug": "vonage-voice", "watchFor": "First call needs an application, a private key and a signed JWT" } ], "history": { "didlogic": null, "vonage-voice": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": 0, "from": 59, "fromGrade": "C", "to": 59, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 58.9, "fromGrade": "C", "to": 59, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 59.1, "fromGrade": "C", "to": 58.9, "toGrade": "C" } ] }, "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/46elks-vs-vonage-voice.json", "title": "46elks Voice API vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice" }, { "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/bandwidth-voice-vs-vonage-voice.json", "title": "Bandwidth Voice API + MCP vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-vonage-voice" }, { "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/exotel-voice-vs-vonage-voice.json", "title": "Exotel Voice API + MCP vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/exotel-voice-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/infobip-calls-vs-vonage-voice.json", "title": "Infobip Calls API + MCP vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-calls-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.json", "title": "jambonz vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.json", "title": "LiveKit Telephony vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/plivo-voice-vs-vonage-voice.json", "title": "Plivo Voice API vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/plivo-voice-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/signalwire-voice-vs-vonage-voice.json", "title": "SignalWire Voice API vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/signalwire-voice-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/sinch-voice-vs-vonage-voice.json", "title": "Sinch Voice API + MCP vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/sinch-voice-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/telnyx-voice-vs-vonage-voice.json", "title": "Telnyx Voice API + MCP vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/telnyx-voice-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/twilio-voice-vs-vonage-voice.json", "title": "Twilio Programmable Voice API + MCP vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/twilio-voice-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/vonage-voice-vs-voximplant.json", "title": "Vonage Voice API + MCP vs Voximplant", "url": "https://www.anchorterminal.com/compare/vonage-voice-vs-voximplant" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-didww-voice-and-number-management.json", "title": "didlogic Voice API vs DIDWW Voice and Number Management API", "url": "https://www.anchorterminal.com/compare/didlogic-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-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-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" } ], "panel": null, "scores": [ { "by": 19, "didlogic": 26, "edge": "vonage-voice", "key": "reliability", "name": "Reliability", "vonage-voice": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "didlogic": 87, "edge": "vonage-voice", "key": "schema", "name": "Schema \u0026 documentation", "vonage-voice": 88, "weight": 13 }, { "by": 3, "didlogic": 57, "edge": "vonage-voice", "key": "ergonomics", "name": "Agent ergonomics", "vonage-voice": 60, "weight": 13 }, { "by": 27, "didlogic": 46, "edge": "vonage-voice", "key": "security", "name": "Security \u0026 auth", "vonage-voice": 73, "weight": 14 }, { "by": 3, "didlogic": 38, "edge": "didlogic", "key": "payments", "name": "Payments \u0026 pricing", "vonage-voice": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 13, "didlogic": 38, "edge": "vonage-voice", "key": "maintenance", "name": "Maintenance \u0026 community", "vonage-voice": 51, "weight": 7 }, { "by": 9, "didlogic": 58, "edge": "didlogic", "key": "transparency", "name": "Transparency \u0026 trust", "vonage-voice": 49, "weight": 7 } ], "summary": "Vonage Voice API + MCP scores 59 (C) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 5 of 7 scored categories. didlogic Voice API leads on transparency \u0026 trust. 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.", "vonage-voice": "Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice", "json": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.min.md" }, "markdown": "Vonage Voice API + MCP scores 59 (C) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 5 of 7 scored categories. didlogic Voice API leads on transparency \u0026 trust. 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- Vonage Voice API + MCP: grade C, 59/100, rank #717 of 1486. Markdown https://www.anchorterminal.com/tools/vonage-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage-voice.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- Transparency \u0026 trust, 58 against 49\n\nWatch for: No status page or incident history found\n\n### Vonage Voice API + MCP (C)\n\nGood for: Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.\n\nAhead on:\n- Reliability, 45 against 26\n- Security \u0026 auth, 73 against 46\n- Maintenance \u0026 community, 51 against 38\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: First call needs an application, a private key and a signed JWT\n\n\n## Why the edge\n\n### Security \u0026 auth: Vonage Voice API + MCP +27\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- Vonage Voice API + MCP (73): Calls are authorised with an application JWT signed RS256 with the application's private key. Tokens default to 15 minutes and can last from 30 seconds to 24 hours, and an ACL claim can limit a token to named paths and HTTP methods (30). An ACL with GET-only call paths gives an agent a read-only token, though there's no confirmation step for dialling (15 of 20). Calls carry untrusted caller speech. Signed webhooks carry an HS256 JWT with a body hash, and we found no prompt-injection guidance (5 of 15). Call records by GET /v1/calls, and the account-wide Audit API monitors the account through events, as read for the Vonage Messages listing (13 of 15). Per the 2 October reading of www.vonage.com/security/ (bot check since), Vonage holds ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR across its product lines without saying which cover the Communications APIs. No security.txt, disclosure policy or bug bounty found. OSV lists no advisory for @vonage/server-sdk, vonage or the MCP package. The same page and reading give the Vonage Messages listing 10 (10 of 20). 30 + 15 + 5 + 13 + 10 = 73.\n\n### Reliability: Vonage Voice API + MCP +19\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- Vonage Voice API + MCP (45): Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 4 November, list Voice entries from 6 August labelled minor or none. Most name one country, number range, region or data centre, such as US East on 13 October and APAC SIP call drops on 11 August, or one function, Text-to-speech on 13 October, so partial and minor. 'Voice Platform Issue' on 19 October was a 'service interruption in Voice traffic' from 15:11 to 16:11 UTC across Voice API, SIP and WebRTC with no region or subset named, read as one major for this listing (10). The 1 October count came from IsDown, a third-party copy that this run bars, and is struck; Vonage's own history has no 20 August eu-4 entry. Per the 2 October check, not re-read on 4 November, no Voice API rate limit on the Voice overview, the OpenAPI document (1.10.0), the API error catalogue or llms.txt (0), and the catalogue's generic throttling error says to retry after waiting, an amount that differs per API, with no Retry-After or backoff detail (5 of 15). No SLA found (0). Voice API is generally available (10). 20 + 10 + 0 + 5 + 0 + 10 = 45.\n\n### Maintenance \u0026 community: Vonage Voice API + MCP +13\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- Vonage Voice API + MCP (51): Vonage's SDKs bundle every Vonage API, so their releases count here only where they change voice code, as the Groq speech-to-text and Gemini embedding listings read their SDKs. vonage-java-sdk v9.15.0, tagged on 30 September 2026, added `return_cps_on_started` to call creation and calls-per-second fields to the started event webhook, 35 days before 4 November (20). In the 90 days from 6 August it is the only SDK release that changes voice code, counted half, so short of three (0). vonage-node-sdk v3.30.0 and v3.30.1, vonage-python-sdk v4.9.0 and v4.9.1, vonage-java-sdk v9.13.0, v9.13.1, v9.14.0 and v9.15.1, vonage-php-sdk-core 4.15.0 and vonage-ruby-sdk 7.36.0 change other APIs, shared client code or formatting. The Python voice package last changed on 20 July (1.5.1, in v4.8.2), and the Node voice package had only version bumps and a lint reformat. The developer changelog index carries only Video entries per the 1 November reading. Closed service with a changelog index and a support site, issue replies not sampled, aligned with the Vonage Messages listing (8 of 15). Official SDKs in six languages (15). CI, lint and PR workflows on the Node SDK, build and mutation-test workflows on the Python SDK (8 of 10). 20 + 0 + 8 + 15 + 8 = 51.\n\n### Transparency \u0026 trust: didlogic Voice API +9\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- Vonage Voice API + MCP (49): Closed service. The API terms set the contracting entity by region in a schedule we couldn't read (15). Per the 2 October check (www.vonage.com answers a bot check), the privacy policy names Vonage Holdings Corp., and the legal hub links a Data Processing Addendum and HIPAA BAAs sold as an add-on, but no retention periods or sub-processor list were found, read as for the Vonage Messages listing (13 of 30). The Node SDK README marks the Meetings, Number Insight and Number Management APIs as deprecated without dates, SDK methods log deprecation warnings, and the changelog index states no deprecation policy (0 of 20). No sub-processor list or data locations found (0). 15 + 13 + 0 + 0 = 28.\n\n## Score by category\n\n| Category | Weight | didlogic Voice API | Vonage Voice API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 26 | 45 | Vonage Voice API + MCP +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 88 | Vonage Voice API + MCP +1 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 60 | Vonage Voice API + MCP +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 46 | 73 | Vonage Voice API + MCP +27 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 38 | 35 | didlogic Voice API +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 38 | 51 | Vonage Voice API + MCP +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 49 | didlogic Voice API +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.8 · D** | **59 · C** | |\n\n## Facts side by side\n\n| Fact | didlogic Voice API | Vonage Voice API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | DID Logic PTE. LTD. | Vonage (Ericsson) |\n| Hosted endpoint | `https://mcp.didlogic.com/mcp` | `https://api.nexmo.com/v1` |\n| Transports | HTTP, websocket, Streamable HTTP | HTTP, stdio, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for phone numbers | $2 per month (plan) | $0.005 per minute of call |\n| x402 | no | no |\n| Licence | Proprietary service under the didlogic Terms of Service | none |\n| Tools exposed | none | 14 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |\n| Last release | 2026-09-30 | 2026-10-21 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | none | 154k npm/wk, 67k PyPI/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## How the scores have moved\n\n### didlogic Voice API\n\nNo score change since it was listed.\n\n### Vonage Voice API + MCP\n\n- no change on 4 November 2026: correction\n- +0.1 on 27 October 2026: checklist\n- -0.2 on 8 October 2026: checklist\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**Vonage Voice API + MCP.** Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.\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### Vonage Voice API + MCP\n\n1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts\n2. Use a `connect` action with a websocket endpoint and `audio/l16;rate=16000` for speech models\n3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it\n4. Enable signed webhooks and verify the HS256 JWT on each event\n5. Expect RFC 7807 errors (`type`, `title`, `detail`, `instance`) and back off on a throttling error, since no Voice rate limit is published\n\n## Questions\n\n### Which is better for AI agents, didlogic Voice API or Vonage Voice API + MCP?\n\nVonage Voice API + MCP scores 59 (C) on agent readiness against didlogic Voice API's 49.8 (D), and leads in 5 of 7 scored categories. didlogic Voice API leads on transparency \u0026 trust.\n\n### Do didlogic Voice API and Vonage Voice API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call didlogic Voice API and Vonage Voice API + MCP without installing anything?\n\nYes. didlogic Voice API has a hosted endpoint at https://mcp.didlogic.com/mcp and Vonage Voice API + MCP at https://api.nexmo.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.json, and with the fewest tokens: https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"didlogic\", \"b\": \"vonage-voice\"}`. From a terminal: `anchor compare didlogic vonage-voice`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/didlogic.json and https://www.anchorterminal.com/api/v1/tools/vonage-voice.json\n\n## Other comparisons with didlogic Voice API or Vonage Voice API + MCP\n\n- [46elks Voice API vs didlogic Voice API](https://www.anchorterminal.com/compare/46elks-vs-didlogic.md)\n- [46elks Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.md)\n- [Bandwidth Voice API + MCP vs didlogic Voice API](https://www.anchorterminal.com/compare/bandwidth-voice-vs-didlogic.md)\n- [Bandwidth Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/bandwidth-voice-vs-vonage-voice.md)\n- [didlogic Voice API vs jambonz](https://www.anchorterminal.com/compare/didlogic-vs-jambonz.md)\n- [Exotel Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/exotel-voice-vs-vonage-voice.md)\n- [Infobip Calls API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/infobip-calls-vs-vonage-voice.md)\n- [jambonz vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.md)\n- [LiveKit Telephony vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.md)\n- [Plivo Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/plivo-voice-vs-vonage-voice.md)\n- [SignalWire Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/signalwire-voice-vs-vonage-voice.md)\n- [Sinch Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/sinch-voice-vs-vonage-voice.md)\n- [Telnyx Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/telnyx-voice-vs-vonage-voice.md)\n- [Twilio Programmable Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/twilio-voice-vs-vonage-voice.md)\n- [Vonage Voice API + MCP vs Voximplant](https://www.anchorterminal.com/compare/vonage-voice-vs-voximplant.md)\n- [didlogic Voice API vs DIDWW Voice and Number Management API](https://www.anchorterminal.com/compare/didlogic-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 Voximplant](https://www.anchorterminal.com/compare/didlogic-vs-voximplant.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", "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 Vonage Voice API + MCP", "url": "" } ], "description": "Vonage Voice scores 59 (C) 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", "Vonage Voice API + MCP C 59", "scores" ], "h1": "didlogic Voice API vs Vonage Voice API + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/didlogic-vs-vonage-voice", "published": "2026-10-01", "section": "tools", "title": "didlogic Voice vs Vonage Voice for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/didlogic-vs-vonage-voice" }, "tokens": { "markdown": 4400, "slim": 2480 }, "version": 1 }