{ "data": { "a": { "slug": "jambonz", "name": "jambonz", "vendor": "FirstFive8, Inc.", "vendorUrl": "https://jambonz.org", "kind": "http-api", "category": "voice-calling", "summary": "jambonz is a programmable voice platform from FirstFive8 for calls over a customer's own SIP carriers. Applications control calls through a REST API, webhooks or a WebSocket API, on the hosted jambonz.cloud or a self-hosted cluster under a commercial licence.", "url": "https://www.anchorterminal.com/tools/jambonz", "markdownUrl": "https://www.anchorterminal.com/tools/jambonz.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/jambonz.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/jambonz.json", "repo": "https://github.com/jambonz/jambonz-feature-server", "license": "Proprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@jambonz/sdk" }, { "registry": "pypi", "name": "jambonz-python-sdk" }, { "registry": "npm", "name": "@jambonz/mcp-schema-server" } ], "auth": "api-key", "authNotes": "A bearer token sent as `Authorization: Bearer \u003ctoken\u003e`, created in the jambonz.cloud portal or with `POST /ApiKeys` by an existing token. A token belongs to one account or one service provider and reaches everything that owner can. No scopes or read-only keys were found. Access is self-serve after a browser sign-up with email, Google or GitHub. Webhooks to the application are signed with a `Jambonz-Signature` header on the hosted platform, or protected with HTTP basic authentication.", "pricing": "paid", "pricingNotes": "jambonz.cloud costs $8 a concurrent session a month for 5 to 249 sessions, $6 for 250 to 499 and $5 for 500 or more, with no per-minute charge. A three-week trial comes first, and the terms describe choosing a subscription at its end. Self-hosted licences cost $7 a session a month or $2,000 a month for unlimited sessions on one cluster, after a 30-day trial of 10 sessions. Carrier minutes, phone numbers, speech and LLM usage are bought from other vendors. Air-gapped, OEM and Enterprise support prices are by quote (https://jambonz.org/pricing, checked 2026-10-08).", "priceSummary": "$8 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the three OpenAPI files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 103, "npmWeekly": 1368, "pypiWeekly": 420, "asOf": "2026-10-08" }, "docsUrl": "https://docs.jambonz.org", "llmsTxt": "https://docs.jambonz.org/llms.txt", "openapi": "https://docs.jambonz.org/openapi/rest-call-control.json", "capabilities": [ "voice.calls", "voice.sip", "voice.streaming", "voice.recording", "voice.agent" ], "tags": [ "hosted", "self-hosted", "sip", "webrtc", "open-source", "openapi", "llms-txt", "typescript", "python", "webhooks", "websocket", "free-trial" ], "lastRelease": "2026-10-04", "graded": true, "anchor": { "graded": true, "score": 49.2, "grade": "D", "agentReady": false, "rank": 712, "ranked": true, "rankOf": 842, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 78, "payments": 40, "reliability": 36, "schema": 78, "security": 42, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -3, "negativeNotes": [ "24 September 2026, fixed and documented. The 11.1.5 release notes list API server flaws found in a security review, among them privilege escalation in user management, accounts able to write operator-only fields and limits, and a call-logs route that could read arbitrary CloudWatch log groups. The 11.0.0 notes of 8 July 2026 also mention cross-account authorisation hardening. No advisory or CVE was published. 3 points, reduced because the fixes shipped and were disclosed (https://docs.jambonz.org/changelog/2026/9/24)" ], "verdict": "OpenAPI 3.1 and AsyncAPI documents, an llms.txt and Markdown pages cover the REST and WebSocket APIs, and session prices are public. No status page, security.txt or advisory was found, API keys carry no scopes, and the 2021 privacy policy says audio is never stored while the October 2026 release notes say support keeps call audio for a few days.", "bestFor": "Teams that already have a SIP carrier and speech and LLM vendors and want call control with flat session pricing, or that must run the voice layer in their own network.", "strengths": [ "Three OpenAPI 3.1 documents (10, 116 and 4 operations) and an AsyncAPI 2.6.0 document for the WebSocket channels are public", "The docs publish an llms.txt, every page as Markdown and a docs MCP server at `https://docs.jambonz.org/_mcp/server`", "Prices are per concurrent session a month ($8, $6 or $5 on the cloud), with no per-minute charge and recording and streaming included", "Six dated release notes from 14 August to 4 October 2026, each with a component version table and self-hosted upgrade notes", "The API server, feature server and both SDKs are public under MIT, and the same platform can run in the customer's own network" ], "weaknesses": [ "No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories", "The privacy policy of 4 May 2021 says audio is never stored. The 4 October 2026 release notes say support keeps SIP and RTP from calls for a few days", "API keys are bearer tokens for a whole account or service provider, with no scopes, no read-only key and no delete operation in the published reference", "The rate limit page gives 600 requests per 5 minutes per IP address. The 4 October release notes give 4,000 call creations a minute per account", "No idempotency key was found on `POST /Accounts/{AccountSid}/Calls`, so a retried request can place a second call", "jambonz sells no phone numbers or minutes. Every call needs a SIP trunk from another carrier and the customer's own speech vendor keys" ], "agentNotes": [ "Send `Authorization: Bearer \u003ctoken\u003e` to `https://api.jambonz.cloud/v1`, the server in the OpenAPI files. The REST introduction page gives `https://jambonz.cloud/api` instead, so confirm the base URL with the operator", "Create a call with `from`, `to` and either `application_sid` or `call_hook`. Do not retry a timed-out create without checking `GET /Accounts/{AccountSid}/Calls` first", "Read `ratelimit-remaining` and `ratelimit-reset` on every response and stop when a `429` arrives", "Append `#rc=3\u0026rp=5xx,ct` to an application URL to turn on webhook retries. HTTP webhooks are not retried by default", "Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.2 } ], "editorialScores": { "ergonomics": 54, "maintenance": 78, "payments": 40, "reliability": 36, "schema": 78, "security": 42, "transparency": 43 }, "provenanceScore": 57 }, "connect": { "install": "npm install @jambonz/sdk", "http": "POST https://api.jambonz.cloud/v1/Accounts/{AccountSid}/Calls\nAuthorization: Bearer \u003ctoken\u003e\nContent-Type: application/json" }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/jambonz" }, "area": "voice", "unitPrices": [ { "item": "Cloud, concurrent session (5 to 249 sessions)", "unit": "month", "usd": 8, "note": "monthly subscription, no per-minute charge" }, { "item": "Cloud, concurrent session (250 to 499 sessions)", "unit": "month", "usd": 6, "note": "monthly subscription" }, { "item": "Cloud, concurrent session (500 or more sessions)", "unit": "month", "usd": 5, "note": "monthly subscription" }, { "item": "Self-hosted licence, concurrent session", "unit": "month", "usd": 7, "note": "one cluster, keyed to its domain" }, { "item": "Self-hosted licence, unlimited sessions", "unit": "month", "usd": 2000, "note": "one cluster, keyed to its domain" }, { "item": "Installation support package", "unit": "tx", "usd": 1000, "note": "one-time fee for one month of installation support" } ], "provenance": { "legalEntity": "FirstFive8, Inc.", "domain": "jambonz.org", "domainRegistered": "2019-08-13", "endpointOnVendorDomain": false, "terms": "https://jambonz.org/terms", "privacy": "https://jambonz.org/privacy", "statusPage": "", "changelog": "https://docs.jambonz.org/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms link is the jambonz Terms of Use, labelled Terms of Service (Cloud) in the site footer, last updated 4 May 2021, between the user and FirstFive8, Inc of Charlestown, Massachusetts. Self-hosted and OEM customers have separate terms at https://jambonz.org/legal-terms-selfhosted and https://jambonz.org/legal-terms-oem.", "The privacy policy was last updated 4 May 2021. It says it is intended for residents of the United States. No data processing addendum or sub-processor list was found.", "The hosted API answers on jambonz.cloud (`https://api.jambonz.cloud/v1` in the OpenAPI files, `https://jambonz.cloud/api` in the REST introduction), a second domain of the vendor's. The schema MCP server is on jambonz.app.", "No status page is linked from jambonz.org, the docs or the jambonz.cloud landing page.", "https://jambonz.org/.well-known/security.txt returned 404. No `SECURITY.md` was found in jambonz-api-server, jambonz-feature-server, node-sdk or python-sdk.", "RDAP for jambonz.org gives a registration date of 2019-08-13.", "The cloud terms forbid crawling, indexing or storing pages of the Service in a non-transitory manner. robots.txt on jambonz.org, docs.jambonz.org and jambonz.cloud allows every path we read. The pages were read once and the copies deleted.", "docs.jambonz.org/llms.txt opens with a block headed Instructions for AI Agents (append `.md` for Markdown, connect to the docs MCP server). We recorded it and did not act on it." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jambonz.json" }, "answer": "Vonage Voice API + MCP scores 58.9 (C) on agent readiness against jambonz's 49.2 (D), and leads in 4 of 7 scored categories. jambonz leads on payments \u0026 pricing.", "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", "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-09-16", "graded": true, "anchor": { "graded": true, "score": 58.9, "grade": "C", "agentReady": false, "rank": 512, "ranked": true, "rankOf": 842, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 78, "payments": 35, "reliability": 45, "schema": 88, "security": 60, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-01" }, "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.9 } ], "editorialScores": { "ergonomics": 60, "maintenance": 78, "payments": 35, "reliability": 45, "schema": 88, "security": 60, "transparency": 25 }, "provenanceScore": 69 }, "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": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage-voice.json", "live": { "slug": "vonage-voice", "probe": { "target": "https://api.nexmo.com/v1", "method": "get", "lastAt": "2026-10-09T12:32:56.339300883Z", "lastOk": true, "lastStatus": 404, "lastMs": 54, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 57, "p95ms24h": 83, "samples24h": 259, "samples30d": 2319, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 133, "ok": 133 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-09T12:29:42.753831139Z" }, "versions": [ { "registry": "npm", "name": "@vonage/server-sdk", "version": "3.30.1", "seenAt": "2026-10-08T16:34:31.249536688Z" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings", "version": "1.5.1", "seenAt": "2026-10-08T16:34:33.514635172Z" }, { "registry": "pypi", "name": "vonage", "version": "4.9.0", "released": "2026-09-16", "seenAt": "2026-10-08T16:34:33.311067599Z" } ], "npmWeekly": 151884, "pypiWeekly": 63193, "securityTxt": { "url": "https://vonage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:38.377472768Z" }, "llmsTxt": { "url": "https://developer.vonage.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:59.781040584Z" }, "domain": { "domain": "vonage.com", "registered": "2000-12-12", "source": "https://rdap.verisign.com/com/v1/domain/vonage.com", "checkedAt": "2026-10-04T13:04:15.703583171Z" }, "pages": [ { "url": "https://developer.vonage.com/en/changelogs", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:22.168740172Z", "changedAt": "2026-10-08T18:17:22.168740172Z", "fingerprint": "c1095b8d6512" }, { "url": "https://www.vonage.com/communications-apis/voice/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:31:30.362585474Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "efeb31a58cfc" }, { "url": "https://www.vonage.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:33.251808306Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef11a28348cd" }, { "url": "https://www.vonage.com/legal/communications-apis/terms-of-use/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:31.309243803Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "004c80c35ffa" } ], "updatedAt": "2026-10-09T12:32:56.339300883Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "FirstFive8, Inc.", "b": "Vonage (Ericsson)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.nexmo.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$0.005 per minute of call", "name": "Price for voice calls" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MIT", "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-10-04", "b": "2026-09-16", "name": "Last release" }, { "a": "2021-05-04", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2021-05-04", "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": "yes", "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": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "103 stars, 1.4k npm/wk, 420 PyPI/wk", "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 58.9 (C) on agent readiness against jambonz's 49.2 (D), and leads in 4 of 7 scored categories. jambonz leads on payments \u0026 pricing.", "question": "Which is better for AI agents, jambonz or Vonage Voice API + MCP?" }, { "answer": "jambonz needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.", "question": "Do jambonz and Vonage Voice API + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for jambonz. Vonage Voice API + MCP has a hosted endpoint at https://api.nexmo.com/v1.", "question": "Can an agent call jambonz and Vonage Voice API + MCP without installing anything?" }, { "answer": "jambonz is open source (Proprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MIT). No open-source release is listed for Vonage Voice API + MCP.", "question": "Are jambonz and Vonage Voice API + MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 35" ], "also": [ "Open source" ], "goodFor": "Teams that already have a SIP carrier and speech and LLM vendors and want call control with flat session pricing, or that must run the voice layer in their own network.", "slug": "jambonz", "watchFor": "No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories" }, { "aheadOn": [ "Reliability, 45 against 36", "Schema \u0026 documentation, 88 against 78", "Agent ergonomics, 60 against 54", "Security \u0026 auth, 60 against 42" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine", "Free to start without a card", "No incidents deducted, where jambonz loses 3 points for them" ], "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" } ], "job": { "capability": "voice.calls", "name": "Voice calls" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz.json", "title": "Bandwidth Voice API + MCP vs jambonz", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz" }, { "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-jambonz.json", "title": "Exotel Voice API + MCP vs jambonz", "url": "https://www.anchorterminal.com/compare/exotel-voice-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-jambonz.json", "title": "Infobip Calls API + MCP vs jambonz", "url": "https://www.anchorterminal.com/compare/infobip-calls-vs-jambonz" }, { "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-livekit-telephony.json", "title": "jambonz vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice.json", "title": "jambonz vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice.json", "title": "jambonz vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice.json", "title": "jambonz vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice.json", "title": "jambonz vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice.json", "title": "jambonz vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-voximplant.json", "title": "jambonz vs Voximplant", "url": "https://www.anchorterminal.com/compare/jambonz-vs-voximplant" }, { "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" } ], "scores": [ { "by": 9, "edge": "vonage-voice", "jambonz": 36, "key": "reliability", "name": "Reliability", "vonage-voice": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "vonage-voice", "jambonz": 78, "key": "schema", "name": "Schema \u0026 documentation", "vonage-voice": 88, "weight": 13 }, { "by": 6, "edge": "vonage-voice", "jambonz": 54, "key": "ergonomics", "name": "Agent ergonomics", "vonage-voice": 60, "weight": 13 }, { "by": 18, "edge": "vonage-voice", "jambonz": 42, "key": "security", "name": "Security \u0026 auth", "vonage-voice": 60, "weight": 14 }, { "by": 5, "edge": "jambonz", "jambonz": 40, "key": "payments", "name": "Payments \u0026 pricing", "vonage-voice": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "jambonz": 78, "key": "maintenance", "name": "Maintenance \u0026 community", "vonage-voice": 78, "weight": 7 }, { "by": 3, "edge": "jambonz", "jambonz": 50, "key": "transparency", "name": "Transparency \u0026 trust", "vonage-voice": 47, "weight": 7 } ], "summary": "Vonage Voice API + MCP scores 58.9 (C) on agent readiness against jambonz's 49.2 (D), and leads in 4 of 7 scored categories. jambonz leads on payments \u0026 pricing. Both do voice calls.", "verdicts": { "jambonz": "OpenAPI 3.1 and AsyncAPI documents, an llms.txt and Markdown pages cover the REST and WebSocket APIs, and session prices are public. No status page, security.txt or advisory was found, API keys carry no scopes, and the 2021 privacy policy says audio is never stored while the October 2026 release notes say support keeps call audio for a few days.", "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/jambonz-vs-vonage-voice", "json": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.md", "slim": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.min.md" }, "markdown": "Vonage Voice API + MCP scores 58.9 (C) on agent readiness against jambonz's 49.2 (D), and leads in 4 of 7 scored categories. jambonz leads on payments \u0026 pricing. Both do voice calls.\n\n- jambonz: grade D, 49.2/100, rank #712 of 842. Markdown https://www.anchorterminal.com/tools/jambonz.md · JSON https://www.anchorterminal.com/api/v1/tools/jambonz.json\n- Vonage Voice API + MCP: grade C, 58.9/100, rank #512 of 842. Markdown https://www.anchorterminal.com/tools/vonage-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage-voice.json\n\n## Which one, for what\n\n### jambonz (D)\n\nGood for: Teams that already have a SIP carrier and speech and LLM vendors and want call control with flat session pricing, or that must run the voice layer in their own network.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 35\n\nAlso in its favour:\n- Open source\n\nWatch for: No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories\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 36\n- Schema \u0026 documentation, 88 against 78\n- Agent ergonomics, 60 against 54\n- Security \u0026 auth, 60 against 42\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n- Free to start without a card\n- No incidents deducted, where jambonz loses 3 points for them\n\nWatch for: First call needs an application, a private key and a signed JWT\n\n\n## Score by category\n\n| Category | Weight | jambonz | Vonage Voice API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 36 | 45 | Vonage Voice API + MCP +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 88 | Vonage Voice API + MCP +10 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 60 | Vonage Voice API + MCP +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 60 | Vonage Voice API + MCP +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | jambonz +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 78 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 50 | 47 | jambonz +3 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **49.2 · D** | **58.9 · C** | |\n\n## Facts side by side\n\n| Fact | jambonz | Vonage Voice API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FirstFive8, Inc. | Vonage (Ericsson) |\n| Hosted endpoint | no (local only) | `https://api.nexmo.com/v1` |\n| Transports | HTTP | HTTP, stdio, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Pay per use |\n| Price for voice calls | not published | $0.005 per minute of call |\n| x402 | no | no |\n| Licence | Proprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MIT | 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-10-04 | 2026-09-16 |\n| Terms last updated | 2021-05-04 | couldn't be read |\n| Privacy policy last updated | 2021-05-04 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | 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 | not found in the text | couldn't be read |\n| Popularity | 103 stars, 1.4k npm/wk, 420 PyPI/wk | 154k npm/wk, 67k PyPI/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\n\n**jambonz.** OpenAPI 3.1 and AsyncAPI documents, an llms.txt and Markdown pages cover the REST and WebSocket APIs, and session prices are public. No status page, security.txt or advisory was found, API keys carry no scopes, and the 2021 privacy policy says audio is never stored while the October 2026 release notes say support keeps call audio for a few days.\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### jambonz\n\n1. Send `Authorization: Bearer \u003ctoken\u003e` to `https://api.jambonz.cloud/v1`, the server in the OpenAPI files. The REST introduction page gives `https://jambonz.cloud/api` instead, so confirm the base URL with the operator\n2. Create a call with `from`, `to` and either `application_sid` or `call_hook`. Do not retry a timed-out create without checking `GET /Accounts/{AccountSid}/Calls` first\n3. Read `ratelimit-remaining` and `ratelimit-reset` on every response and stop when a `429` arrives\n4. Append `#rc=3\u0026rp=5xx,ct` to an application URL to turn on webhook retries. HTTP webhooks are not retried by default\n5. Check the account has a carrier and speech credentials before dialling. jambonz does not supply numbers, minutes or speech services\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, jambonz or Vonage Voice API + MCP?\n\nVonage Voice API + MCP scores 58.9 (C) on agent readiness against jambonz's 49.2 (D), and leads in 4 of 7 scored categories. jambonz leads on payments \u0026 pricing.\n\n### Do jambonz and Vonage Voice API + MCP need an API key?\n\njambonz needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call jambonz and Vonage Voice API + MCP without installing anything?\n\nNo hosted endpoint is listed for jambonz. Vonage Voice API + MCP has a hosted endpoint at https://api.nexmo.com/v1.\n\n### Are jambonz and Vonage Voice API + MCP open source?\n\njambonz is open source (Proprietary. jambonz.cloud is under the jambonz Terms of Use and self-hosted jambonz Commercial needs a paid licence key. The API server, feature server and SDK repositories on GitHub are MIT). No open-source release is listed for Vonage Voice API + MCP.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.json, and with the fewest tokens: https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"jambonz\", \"b\": \"vonage-voice\"}`. From a terminal: `anchor compare jambonz vonage-voice`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/jambonz.json and https://www.anchorterminal.com/api/v1/tools/vonage-voice.json\n\n## Other comparisons with jambonz or Vonage Voice API + MCP\n\n- [Bandwidth Voice API + MCP vs jambonz](https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz.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 jambonz](https://www.anchorterminal.com/compare/exotel-voice-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 jambonz](https://www.anchorterminal.com/compare/infobip-calls-vs-jambonz.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 LiveKit Telephony](https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.md)\n- [jambonz vs Plivo Voice API](https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice.md)\n- [jambonz vs SignalWire Voice API](https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice.md)\n- [jambonz vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice.md)\n- [jambonz vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice.md)\n- [jambonz vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice.md)\n- [jambonz vs Voximplant](https://www.anchorterminal.com/compare/jambonz-vs-voximplant.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", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "jambonz vs Vonage Voice API + MCP", "url": "" } ], "description": "Vonage Voice API + MCP scores 58.9 (C) on agent readiness against jambonz's 49.2 (D), and leads in 4 of 7 scored categories. jambonz leads on payments \u0026 pricing. Both do voice calls. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "jambonz D 49.2", "Vonage Voice API + MCP C 58.9", "scores" ], "h1": "jambonz vs Vonage Voice API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-jambonz-vs-vonage-voice.png", "path": "/compare/jambonz-vs-vonage-voice", "published": "2026-10-01", "section": "tools", "title": "jambonz vs Vonage Voice API + MCP for AI agents, D 49.2 vs C 58.9", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice" }, "tokens": { "markdown": 2600, "slim": 830 }, "version": 1 }