{ "data": { "a": { "slug": "46elks", "name": "46elks Voice API", "vendor": "46elks AB", "vendorUrl": "https://46elks.com", "kind": "http-api", "category": "voice-calling", "summary": "46elks is a Swedish telecom operator's REST API for phone calls, SMS and virtual numbers in 48 countries, with JSON call actions, call recording, SIP and WebRTC clients, and a WebSocket Realtime Voice API for connecting AI agents to calls.", "url": "https://www.anchorterminal.com/tools/46elks", "markdownUrl": "https://www.anchorterminal.com/tools/46elks.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/46elks.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/46elks.json", "dns": "46elks.grade.anchorterminal.com", "repo": "https://github.com/46elks/46elks-getting-started", "license": "Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository", "transports": [ "http", "websocket" ], "remoteUrl": "https://api.46elks.com/a1", "packages": [], "auth": "api-key", "authNotes": "HTTP Basic auth with an API username and password from the dashboard after a browser signup. Subaccounts have their own credentials. No scopes or read-only credentials found. Webhook origin can be verified per the Verify Callback Origin guide.", "pricing": "usage", "pricingNotes": "Per started minute, published by destination. UK calls cost €0.02 to landlines and €0.456 to mobiles, forwarding to a WebSocket €0.015 and to a SIP trunk €0.01. Incoming calls are free. Numbers usually €3 a month. Prepaid balance or invoice (checked 2026-11-06).", "priceSummary": "$3.50 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the docs or the pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://46elks.com/docs/make-call", "llmsTxt": "https://46elks.com/llms.txt", "openapi": "https://raw.githubusercontent.com/46elks/46elks-getting-started/master/code-examples/Swagger/46elksAPI.yaml", "capabilities": [ "voice.calls", "voice.numbers", "voice.streaming", "voice.sip", "voice.recording", "messaging.sms" ], "tags": [ "hosted", "official", "closed-source", "usage", "prepaid", "llms-txt", "openapi", "webhooks", "websocket", "sip", "phone-numbers", "status-page", "eu" ], "graded": true, "anchor": { "graded": true, "score": 44.4, "grade": "E", "agentReady": false, "rank": 1203, "ranked": true, "rankOf": 1486, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 51, "maintenance": 12, "payments": 20, "reliability": 47, "schema": 66, "security": 40, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.", "bestFor": "European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.", "strengths": [ "Realtime Voice WebSocket API with bidirectional audio and interrupt messages for AI agents", "Per-minute prices published by destination, with incoming calls free", "llms.txt maps tasks to endpoints and gives retry guidance", "Concrete retention periods (60 days traffic data, 14 days logs) and EU-only storage", "A registered Swedish telecom operator with numbers in 48 countries" ], "weaknesses": [ "No changelog or dated API release found", "The SLA covers support hours only, with no uptime commitment", "No idempotency key on `POST /calls`, and no documented call rate limits", "HTTP Basic credentials with no scopes or read-only option", "The Swagger 2.0 file doesn't cover the Realtime Voice API" ], "agentNotes": [ "Send numbers in E.164 format, such as +46700000000, or the request fails", "Pass `whenhangup` on `POST /calls` to learn when a call ends or fails to connect", "Don't retry a call request on a 4xx; retry 5xx with backoff, and check call history first to avoid a second call", "Treat caller speech, DTMF and SMS replies as untrusted input, and verify webhook origin", "Costs in responses are in ten-thousandths of the account currency (3500 means 0.35)" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.4 } ], "editorialScores": { "ergonomics": 51, "maintenance": 12, "payments": 20, "reliability": 47, "schema": 66, "security": 40, "transparency": 49 }, "provenanceScore": 74, "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 https://api.46elks.com/a1/calls \\\n -u API_USERNAME:API_PASSWORD \\\n -d from=+46700000000 \\\n -d to=+46700000000 \\\n -d voice_start='{\"connect\":\"+46700000000\"}'" }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/46elks" }, "area": "voice", "unitPrices": [ { "item": "Call to a UK landline", "unit": "call-minute", "usd": 0.023, "note": "€0.02 per started minute" }, { "item": "Call to a UK mobile", "unit": "call-minute", "usd": 0.53, "note": "€0.456 per started minute" }, { "item": "Forward a call to a WebSocket", "unit": "call-minute", "usd": 0.017, "note": "€0.015 per started minute" }, { "item": "Virtual number", "unit": "month", "usd": 3.5, "note": "usually €3 a month" } ], "provenance": { "legalEntity": "46elks AB", "domain": "46elks.com", "domainRegistered": "2011-04-27", "endpointOnVendorDomain": true, "terms": "https://46elks.com/terms", "privacy": "https://46elks.com/privacy-policy", "statusPage": "https://stats.uptimerobot.com/320XQh70w", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Terms of Service, effective 12 March 2024, are with 46elks AB (Sweden, 556838-8184) under Swedish law. No clause on automated access to the website was found.", "46elks.com/status redirects to an UptimeRobot page that draws its data by script from /api/, which its robots.txt disallows, so no history was read.", "/.well-known/security.txt returns 404. No changelog was found; the newest blog post in the sitemap is from 2014.", "Euro prices converted at about 1.16 dollars to the euro for unitPrices; the pricing page lists euro and kronor.", "RDAP gives 46elks.com a registration date of 27 April 2011." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/46elks.json", "live": { "slug": "46elks", "probe": { "target": "https://api.46elks.com/a1", "method": "get", "lastAt": "2026-11-07T18:07:39.601947951Z", "lastOk": true, "lastStatus": 401, "lastMs": 322, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 317, "p95ms24h": 458, "samples24h": 198, "samples30d": 198, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 185, "ok": 185 } ] }, "vendorStatus": { "page": "https://stats.uptimerobot.com/320XQh70w", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:03.46439958Z" }, "githubStars": 57, "securityTxt": { "url": "https://46elks.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:02:02.719722143Z" }, "llmsTxt": { "url": "https://46elks.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:04.362648825Z" }, "pages": [ { "url": "https://46elks.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T13:58:27.545226578Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bff2a55e1a02" }, { "url": "https://46elks.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T13:58:29.648545838Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "be068526a0d6" } ], "updatedAt": "2026-11-07T18:07:39.601947951Z" } }, "answer": "Vonage Voice API + MCP scores 59 (C) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks 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:08:27.52680576Z", "lastOk": true, "lastStatus": 404, "lastMs": 62, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 58, "p95ms24h": 135, "samples24h": 239, "samples30d": 7908, "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": 185, "ok": 185 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-07T18:10:19.77728149Z" }, "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:10:19.77728149Z" } }, "edges": [ { "by": 39, "category": "maintenance", "leads": "vonage-voice", "name": "Maintenance \u0026 community", "reasons": { "a": "No changelog, release notes or dated API change was found, the sitemap's newest blog post is from 2014, and the Swagger file predates Realtime Voice (0). No dated changes in the 90 days from 8 August (0). Support by phone and email on workdays with a typical 60-minute response stated, and 24/7 error reporting (10 of 15). No official SDK (0). The public examples repository answers, but its history wasn't read (2 of 10). 0+0+10+0+2 = 12.", "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": 12, "b": 51 } }, { "by": 33, "category": "security", "leads": "vonage-voice", "name": "Security \u0026 auth", "reasons": { "a": "HTTP Basic credentials per account, with separate credentials per subaccount and no scopes found (18 of 30). Subaccounts separate traffic, with no read-only credential or confirmation for paid actions (6 of 20). Callers' speech, DTMF and SMS replies reach the agent as untrusted input. The docs show how to verify callback origin, with no prompt-injection guidance (5 of 15). Call, SMS and recording history through the API for 90 days (8 of 15). A registered Swedish telecom operator, but no security.txt (404), disclosure policy, bug bounty or certification was found (3 of 20). 18+6+5+8+3 = 40.", "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": 40, "b": 73 } }, { "by": 22, "category": "schema", "leads": "vonage-voice", "name": "Schema \u0026 documentation", "reasons": { "a": "A Swagger 2.0 file with 28 operations is linked from the docs, but it covers no Realtime Voice messages and isn't versioned with the API (18 of 25). An llms.txt written for agents, with a task-to-endpoint table and webhook payloads, while docs pages are HTML (10). Each docs page explains parameters and when webhooks fire, such as `voice_start` loading only once a call connects (14 of 20). Form-encoded parameters with types in the Swagger file and few enums (9 of 15). Examples in many languages and a JSON error shape, with no error list (10 of 15). The `/a1/` path, with no changelog found (5 of 15). 18+10+14+9+10+5 = 66.", "b": "OpenAPI spec for the Voice API on developer.vonage.com, version 1.10.0 (25). llms.txt that tells agents to keep the api.nexmo.com and rest.nexmo.com hostnames (10). The NCCO reference explains each action, talk, input, record, connect, transfer, with notes on which to choose (14 of 20). Typed fields from the spec (12 of 15). Examples per action, a webhook reference and a shared API error catalogue in RFC 7807 form at developer.vonage.com/en/api-errors, though the Voice spec documents only a 201 for POST /v1/calls (12 of 15). Versioned /v1 path and a public changelog index (15). Per the 2 October check, not re-read on 4 November." }, "scores": { "a": 66, "b": 88 } }, { "by": 15, "category": "payments", "leads": "vonage-voice", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-minute prices by destination are public without login, also in kronor, with incoming calls free (20). No free credit; only SMS to the test number +46700000000 costs nothing, and accounts are prepaid or invoiced against a deposit (0). A person signs up in a browser and copies the credentials (0). 0+20+0+0 = 20.", "b": "No x402, MPP or L402 (0). Per-minute rates are in a downloadable pricing sheet, and the pricing page returns 403 to automated readers (15 of 20). €2 of test credit without a card (20). A person signs up in a browser (0). Per the 2 October check, not re-read on 4 November." }, "scores": { "a": 20, "b": 35 } }, { "by": 13, "category": "transparency", "leads": "46elks", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with clear terms naming 46elks AB with its Swedish registration (15 of 30). The privacy policy gives concrete retention, 60 days of traffic data under Swedish law, 14 days of troubleshooting logs and a 90-day history for the customer, with EU storage, and a GDPR page and data protection page exist (24 of 30). No deprecation policy or dated notices found (0 of 20). Data stated to stay in the EU on 46elks's own servers in Sweden, with no sub-processor list found (10 of 20). 15+24+0+10 = 49.", "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": 62, "b": 49 } }, { "by": 9, "category": "ergonomics", "leads": "vonage-voice", "name": "Agent ergonomics", "reasons": { "a": "Compact JSON responses, and call actions returned as small JSON objects (18 of 25). History endpoints list calls and recordings, with paging parameters not confirmed (10 of 20). Errors carry `error` and `detail` (12 of 20). No idempotency key on `POST /calls` or number allocation (3 of 20). Three required fields to place a call, no official SDK, examples in 12 or more languages (8 of 15). 18+10+12+3+8 = 51.", "b": "List calls takes page_size from 1 to 100 (default 10) and record_index, with no field selection (15 of 25). Filters on status, date_start, date_end and conversation_uuid, with ordering (20). A shared API error catalogue with codes an agent can look up (15 of 20). No idempotency key or safe-retry guidance found (0). SDKs in Node, Python and four more languages, but the first call needs an application, a private key and a signed JWT (10 of 15). Per the 2 October check, not re-read on 4 November." }, "scores": { "a": 51, "b": 60 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "46elks AB", "b": "Vonage (Ericsson)", "name": "Vendor" }, { "a": "https://api.46elks.com/a1", "b": "https://api.nexmo.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP, websocket", "b": "HTTP, stdio, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.017 per minute of call", "b": "$0.005 per minute of call", "name": "Price for phone calls" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository", "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": "none", "b": "2026-10-21", "name": "Last release" }, { "a": "2024-03-12", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2018-05-20", "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": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "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 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks Voice API leads on transparency \u0026 trust.", "question": "Which is better for AI agents, 46elks Voice API or Vonage Voice API + MCP?" }, { "answer": "Vonage Voice API + MCP, at $0.005 per minute of call against $0.017 per minute of call for 46elks Voice API. These are the vendors' published prices for the job.", "question": "Which is cheaper for phone calls, 46elks Voice API or Vonage Voice API + MCP?" }, { "answer": "46elks Voice API needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.", "question": "Do 46elks Voice API and Vonage Voice API + MCP need an API key?" }, { "answer": "Yes. 46elks Voice API has a hosted endpoint at https://api.46elks.com/a1 and Vonage Voice API + MCP at https://api.nexmo.com/v1.", "question": "Can an agent call 46elks Voice API and Vonage Voice API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 62 against 49" ], "also": null, "goodFor": "European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.", "slug": "46elks", "watchFor": "No changelog or dated API release found" }, { "aheadOn": [ "Schema \u0026 documentation, 88 against 66", "Agent ergonomics, 60 against 51", "Security \u0026 auth, 73 against 40", "Payments \u0026 pricing, 35 against 20", "Maintenance \u0026 community, 51 against 12" ], "also": [ "Cheaper for phone calls, $0.005 against $0.017 per minute of call", "Runs on your own machine", "Free to start without a card" ], "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": { "46elks": 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.calls", "name": "Phone calls" }, "others": [ { "json": "https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice.json", "title": "46elks Voice API vs Bandwidth Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice" }, { "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-exotel-voice.json", "title": "46elks Voice API vs Exotel Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-exotel-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.json", "title": "46elks Voice API vs Infobip Calls API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-infobip-calls" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-jambonz.json", "title": "46elks Voice API vs jambonz", "url": "https://www.anchorterminal.com/compare/46elks-vs-jambonz" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.json", "title": "46elks Voice API vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-plivo-voice.json", "title": "46elks Voice API vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/46elks-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice.json", "title": "46elks Voice API vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-sinch-voice.json", "title": "46elks Voice API vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.json", "title": "46elks Voice API vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-twilio-voice.json", "title": "46elks Voice API vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-voximplant.json", "title": "46elks Voice API vs Voximplant", "url": "https://www.anchorterminal.com/compare/46elks-vs-voximplant" }, { "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/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/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/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/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": [ { "46elks": 47, "by": 2, "edge": "46elks", "key": "reliability", "name": "Reliability", "vonage-voice": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "46elks": 66, "by": 22, "edge": "vonage-voice", "key": "schema", "name": "Schema \u0026 documentation", "vonage-voice": 88, "weight": 13 }, { "46elks": 51, "by": 9, "edge": "vonage-voice", "key": "ergonomics", "name": "Agent ergonomics", "vonage-voice": 60, "weight": 13 }, { "46elks": 40, "by": 33, "edge": "vonage-voice", "key": "security", "name": "Security \u0026 auth", "vonage-voice": 73, "weight": 14 }, { "46elks": 20, "by": 15, "edge": "vonage-voice", "key": "payments", "name": "Payments \u0026 pricing", "vonage-voice": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "46elks": 12, "by": 39, "edge": "vonage-voice", "key": "maintenance", "name": "Maintenance \u0026 community", "vonage-voice": 51, "weight": 7 }, { "46elks": 62, "by": 13, "edge": "46elks", "key": "transparency", "name": "Transparency \u0026 trust", "vonage-voice": 49, "weight": 7 } ], "summary": "Vonage Voice API + MCP scores 59 (C) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks Voice API leads on transparency \u0026 trust. Both do phone calls. Vonage Voice API + MCP is cheaper for phone calls, $0.005 against $0.017 per minute of call.", "tasks": null, "tutorials": [], "verdicts": { "46elks": "46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.", "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/46elks-vs-vonage-voice", "json": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.min.md" }, "markdown": "Vonage Voice API + MCP scores 59 (C) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks Voice API leads on transparency \u0026 trust. Both do phone calls. Vonage Voice API + MCP is cheaper for phone calls, $0.005 against $0.017 per minute of call.\n\n- 46elks Voice API: grade E, 44.4/100, rank #1203 of 1486. Markdown https://www.anchorterminal.com/tools/46elks.md · JSON https://www.anchorterminal.com/api/v1/tools/46elks.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### 46elks Voice API (E)\n\nGood for: European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.\n\nAhead on:\n- Transparency \u0026 trust, 62 against 49\n\nWatch for: No changelog or dated API release 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- Schema \u0026 documentation, 88 against 66\n- Agent ergonomics, 60 against 51\n- Security \u0026 auth, 73 against 40\n- Payments \u0026 pricing, 35 against 20\n- Maintenance \u0026 community, 51 against 12\n\nAlso in its favour:\n- Cheaper for phone calls, $0.005 against $0.017 per minute of call\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: First call needs an application, a private key and a signed JWT\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Vonage Voice API + MCP +39\n\n- 46elks Voice API (12): No changelog, release notes or dated API change was found, the sitemap's newest blog post is from 2014, and the Swagger file predates Realtime Voice (0). No dated changes in the 90 days from 8 August (0). Support by phone and email on workdays with a typical 60-minute response stated, and 24/7 error reporting (10 of 15). No official SDK (0). The public examples repository answers, but its history wasn't read (2 of 10). 0+0+10+0+2 = 12.\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### Security \u0026 auth: Vonage Voice API + MCP +33\n\n- 46elks Voice API (40): HTTP Basic credentials per account, with separate credentials per subaccount and no scopes found (18 of 30). Subaccounts separate traffic, with no read-only credential or confirmation for paid actions (6 of 20). Callers' speech, DTMF and SMS replies reach the agent as untrusted input. The docs show how to verify callback origin, with no prompt-injection guidance (5 of 15). Call, SMS and recording history through the API for 90 days (8 of 15). A registered Swedish telecom operator, but no security.txt (404), disclosure policy, bug bounty or certification was found (3 of 20). 18+6+5+8+3 = 40.\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### Schema \u0026 documentation: Vonage Voice API + MCP +22\n\n- 46elks Voice API (66): A Swagger 2.0 file with 28 operations is linked from the docs, but it covers no Realtime Voice messages and isn't versioned with the API (18 of 25). An llms.txt written for agents, with a task-to-endpoint table and webhook payloads, while docs pages are HTML (10). Each docs page explains parameters and when webhooks fire, such as `voice_start` loading only once a call connects (14 of 20). Form-encoded parameters with types in the Swagger file and few enums (9 of 15). Examples in many languages and a JSON error shape, with no error list (10 of 15). The `/a1/` path, with no changelog found (5 of 15). 18+10+14+9+10+5 = 66.\n- Vonage Voice API + MCP (88): OpenAPI spec for the Voice API on developer.vonage.com, version 1.10.0 (25). llms.txt that tells agents to keep the api.nexmo.com and rest.nexmo.com hostnames (10). The NCCO reference explains each action, talk, input, record, connect, transfer, with notes on which to choose (14 of 20). Typed fields from the spec (12 of 15). Examples per action, a webhook reference and a shared API error catalogue in RFC 7807 form at developer.vonage.com/en/api-errors, though the Voice spec documents only a 201 for POST /v1/calls (12 of 15). Versioned /v1 path and a public changelog index (15). Per the 2 October check, not re-read on 4 November.\n\n### Payments \u0026 pricing: Vonage Voice API + MCP +15\n\n- 46elks Voice API (20): No x402, MPP or L402 (0). Per-minute prices by destination are public without login, also in kronor, with incoming calls free (20). No free credit; only SMS to the test number +46700000000 costs nothing, and accounts are prepaid or invoiced against a deposit (0). A person signs up in a browser and copies the credentials (0). 0+20+0+0 = 20.\n- Vonage Voice API + MCP (35): No x402, MPP or L402 (0). Per-minute rates are in a downloadable pricing sheet, and the pricing page returns 403 to automated readers (15 of 20). €2 of test credit without a card (20). A person signs up in a browser (0). Per the 2 October check, not re-read on 4 November.\n\n### Transparency \u0026 trust: 46elks Voice API +13\n\n- 46elks Voice API (62): Closed service with clear terms naming 46elks AB with its Swedish registration (15 of 30). The privacy policy gives concrete retention, 60 days of traffic data under Swedish law, 14 days of troubleshooting logs and a 90-day history for the customer, with EU storage, and a GDPR page and data protection page exist (24 of 30). No deprecation policy or dated notices found (0 of 20). Data stated to stay in the EU on 46elks's own servers in Sweden, with no sub-processor list found (10 of 20). 15+24+0+10 = 49.\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### Agent ergonomics: Vonage Voice API + MCP +9\n\n- 46elks Voice API (51): Compact JSON responses, and call actions returned as small JSON objects (18 of 25). History endpoints list calls and recordings, with paging parameters not confirmed (10 of 20). Errors carry `error` and `detail` (12 of 20). No idempotency key on `POST /calls` or number allocation (3 of 20). Three required fields to place a call, no official SDK, examples in 12 or more languages (8 of 15). 18+10+12+3+8 = 51.\n- Vonage Voice API + MCP (60): List calls takes page_size from 1 to 100 (default 10) and record_index, with no field selection (15 of 25). Filters on status, date_start, date_end and conversation_uuid, with ordering (20). A shared API error catalogue with codes an agent can look up (15 of 20). No idempotency key or safe-retry guidance found (0). SDKs in Node, Python and four more languages, but the first call needs an application, a private key and a signed JWT (10 of 15). Per the 2 October check, not re-read on 4 November.\n\n## Score by category\n\n| Category | Weight | 46elks Voice API | Vonage Voice API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 47 | 45 | 46elks Voice API +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 88 | Vonage Voice API + MCP +22 |\n| Agent ergonomics | 13% (16.2 this run) | 51 | 60 | Vonage Voice API + MCP +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 73 | Vonage Voice API + MCP +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 35 | Vonage Voice API + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 12 | 51 | Vonage Voice API + MCP +39 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 49 | 46elks Voice API +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **44.4 · E** | **59 · C** | |\n\n## Facts side by side\n\n| Fact | 46elks Voice API | Vonage Voice API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 46elks AB | Vonage (Ericsson) |\n| Hosted endpoint | `https://api.46elks.com/a1` | `https://api.nexmo.com/v1` |\n| Transports | HTTP, websocket | HTTP, stdio, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for phone calls | $0.017 per minute of call | $0.005 per minute of call |\n| x402 | no | no |\n| Licence | Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository | 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 | none | 2026-10-21 |\n| Terms last updated | 2024-03-12 | couldn't be read |\n| Privacy policy last updated | 2018-05-20 | 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 | yes | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | 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### 46elks 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**46elks Voice API.** 46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.\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### 46elks Voice API\n\n1. Send numbers in E.164 format, such as +46700000000, or the request fails\n2. Pass `whenhangup` on `POST /calls` to learn when a call ends or fails to connect\n3. Don't retry a call request on a 4xx; retry 5xx with backoff, and check call history first to avoid a second call\n4. Treat caller speech, DTMF and SMS replies as untrusted input, and verify webhook origin\n5. Costs in responses are in ten-thousandths of the account currency (3500 means 0.35)\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, 46elks Voice API or Vonage Voice API + MCP?\n\nVonage Voice API + MCP scores 59 (C) on agent readiness against 46elks Voice API's 44.4 (E), and leads in 5 of 7 scored categories. 46elks Voice API leads on transparency \u0026 trust.\n\n### Which is cheaper for phone calls, 46elks Voice API or Vonage Voice API + MCP?\n\nVonage Voice API + MCP, at $0.005 per minute of call against $0.017 per minute of call for 46elks Voice API. These are the vendors' published prices for the job.\n\n### Do 46elks Voice API and Vonage Voice API + MCP need an API key?\n\n46elks Voice API needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call 46elks Voice API and Vonage Voice API + MCP without installing anything?\n\nYes. 46elks Voice API has a hosted endpoint at https://api.46elks.com/a1 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/46elks-vs-vonage-voice.json, and with the fewest tokens: https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"46elks\", \"b\": \"vonage-voice\"}`. From a terminal: `anchor compare 46elks vonage-voice`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/46elks.json and https://www.anchorterminal.com/api/v1/tools/vonage-voice.json\n\n## Other comparisons with 46elks Voice API or Vonage Voice API + MCP\n\n- [46elks Voice API vs Bandwidth Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice.md)\n- [46elks Voice API vs didlogic Voice API](https://www.anchorterminal.com/compare/46elks-vs-didlogic.md)\n- [46elks Voice API vs Exotel Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-exotel-voice.md)\n- [46elks Voice API vs Infobip Calls API + MCP](https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.md)\n- [46elks Voice API vs jambonz](https://www.anchorterminal.com/compare/46elks-vs-jambonz.md)\n- [46elks Voice API vs LiveKit Telephony](https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.md)\n- [46elks Voice API vs Plivo Voice API](https://www.anchorterminal.com/compare/46elks-vs-plivo-voice.md)\n- [46elks Voice API vs SignalWire Voice API](https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice.md)\n- [46elks Voice API vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-sinch-voice.md)\n- [46elks Voice API vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.md)\n- [46elks Voice API vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-twilio-voice.md)\n- [46elks Voice API vs Voximplant](https://www.anchorterminal.com/compare/46elks-vs-voximplant.md)\n- [Bandwidth Voice API + MCP vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/bandwidth-voice-vs-vonage-voice.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- [46elks Voice API vs DIDWW Voice and Number Management API](https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management.md)\n- [didlogic Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/didlogic-vs-vonage-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", "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": "46elks Voice API vs Vonage Voice API + MCP", "url": "" } ], "description": "Vonage Voice scores 59 (C) to 46elks Voice's 44.4 (E) for phone calls. Vonage Voice is cheaper for phone calls, $0.005 against $0.017 per minute of call. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "46elks Voice API E 44.4", "Vonage Voice API + MCP C 59", "scores" ], "h1": "46elks Voice API vs Vonage Voice API + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/46elks-vs-vonage-voice", "published": "2026-10-01", "section": "tools", "title": "46elks Voice vs Vonage Voice for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice" }, "tokens": { "markdown": 4800, "slim": 2830 }, "version": 1 }