{ "data": { "similar": [ { "grade": "A", "json": "https://www.anchorterminal.com/tools/twilio-voice.json", "name": "Twilio Programmable Voice API + MCP", "score": 80.4, "shared": [ "voice.calls", "voice.streaming", "voice.sip", "voice.recording" ], "slug": "twilio-voice" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/telnyx-voice.json", "name": "Telnyx Voice API + MCP", "score": 74.2, "shared": [ "voice.calls", "voice.streaming", "voice.sip", "voice.recording" ], "slug": "telnyx-voice" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/signalwire-voice.json", "name": "SignalWire Voice API", "score": 67.1, "shared": [ "voice.calls", "voice.streaming", "voice.sip", "voice.recording" ], "slug": "signalwire-voice" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/bandwidth-voice.json", "name": "Bandwidth Voice API + MCP", "score": 63.7, "shared": [ "voice.calls", "voice.streaming", "voice.sip", "voice.recording" ], "slug": "bandwidth-voice" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/sinch-voice.json", "name": "Sinch Voice API + MCP", "score": 62.7, "shared": [ "voice.calls", "voice.streaming", "voice.sip", "voice.recording" ], "slug": "sinch-voice" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/plivo-voice.json", "name": "Plivo Voice API", "score": 60.4, "shared": [ "voice.calls", "voice.streaming", "voice.sip", "voice.recording" ], "slug": "plivo-voice" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 36, "points": 7.2, "reason": "Graded as a hosted service, the API on jambonz.cloud, which the docs name as the simplest way to start. The same software can be self-hosted under a commercial licence. No status page is linked from jambonz.org, the docs or the jambonz.cloud landing page (0), so there is no readable incident history (5). Rate limits are published with numbers, 600 requests per 5 minute fixed window per client IP address on the docs page. The 11.1.6 notes of 4 October 2026 say the API server now counts 4,000 call creations and 600 call status reads a minute per account, and the docs page has not been updated (13 of 15). Responses carry `ratelimit-policy`, `ratelimit-remaining` and `ratelimit-reset`, and a client over a limit receives 429. No backoff guidance or idempotency key was found for the REST API. Webhook and WebSocket retries towards the application are documented with a backoff schedule (8 of 15). No uptime SLA was found for jambonz.cloud. Support SLAs are sold only with Enterprise support for self-hosted systems (0). The REST and WebSocket APIs carry no beta label, though the Python SDK is marked experimental (10)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 78, "points": 12.68, "reason": "Three OpenAPI 3.1 documents are public (REST Call Control with 10 operations, REST Platform Management with 116, Webhooks with 4), with an AsyncAPI 2.6.0 document for the WebSocket channels (25). llms.txt, per-section indexes and every page as Markdown (10). Every operation has a summary and the verb pages explain use at length. Operation descriptions in the API reference are mostly one line (12 of 20). Enums for call status, direction and mid-call actions and required fields are marked. `to`, `call_hook`, `tag` and `amd` are objects, and 7 of 61 schemas in the call control document are objects with no properties (11 of 15). The SDK and verb pages carry code examples. The OpenAPI files contain no examples, errors are a single `msg` string, and 429 is not listed among the responses (8 of 15). The path is versioned `/v1` and the changelog is dated with component version tables. The REST introduction gives `https://jambonz.cloud/api` as the base URL while the OpenAPI files give `https://api.jambonz.cloud/v1` (12 of 15)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 54, "points": 8.78, "reason": "Live calls can be filtered by direction, number and status, with no field selection or limit (13 of 25). Recent calls take `page` and `count` with day and date range filters. The live call list has no pagination (14 of 20). Errors are HTTP codes 400, 404, 422 and 500 with a `msg` string, plus the rate limit headers. No error code list was found (10 of 20). No idempotency key was found on call creation, so a retried request can dial twice. Webhook retries are set with `rc` and `rp` on the application URL (5 of 20). A call needs `from`, `to` and an application or `call_hook`, with a 60 second answer timeout by default. `@jambonz/sdk` for Node.js is current and `jambonz-python-sdk` is experimental (12 of 15)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 42, "points": 7.35, "reason": "Bearer API tokens belong to an account or a service provider and carry `expires_at` and `last_used` fields. They can be created by API. No scopes and no delete operation appear in the published reference (18 of 30). No read-only key and no confirmation step before dialling were found. Call capacity limits can be set per account (4 of 20). Calls carry untrusted caller speech into the `agent` and `llm` verbs. The docs cover webhook signing with `Jambonz-Signature` and basic authentication, and no prompt-injection guidance was found in the pages read (5 of 15). Recent calls expose SIP traces, pcap files and Jaeger traces, and alerts can be pushed to a webhook, Slack, PagerDuty or email since 11.1.6. No log of API or portal actions was found (9 of 15). No security.txt, `SECURITY.md`, disclosure policy, bug bounty or certification was found, and no advisories are published on the API server or feature server repositories. The 11.1.5 notes describe fixes from a security review (4 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 40, "points": 5, "reason": "Scored on the hosted option, jambonz.cloud. No x402, MPP or L402 found (0). Prices per concurrent session a month are public without a login for the cloud and for self-hosted licences (20). A three-week cloud trial comes first. The terms ask for a name, company and email at sign-up and describe choosing a subscription when the trial ends, so we counted it as needing no card. The sign-up page itself is drawn by script and was not read (20). An account is created in a browser. `POST /ApiKeys` needs an existing token, so it does not help a new agent (0)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 78, "points": 6.83, "reason": "jambonz Commercial 11.1.6 is dated 4 October 2026 and jambonz-api-server was tagged v0.9.15 on 7 October (30). The changelog has six entries from 14 August to 4 October 2026 (20). Of the 30 newest open issues and pull requests on jambonz-feature-server, 10 have a comment, and Snyk security upgrade pull requests from December 2025 to July 2026 sit open with none. GitHub reports 244 open issues and pull requests there. A community forum is linked and was not read (10 of 25). `@jambonz/sdk` 0.10.1 dates from 29 July 2026 and `jambonz-python-sdk` 0.3.2 from 19 May 2026, marked experimental (12 of 15). The API server runs lint and tests in CI on every push. We did not see the latest run's result (6 of 10)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 50, "points": 4.38, "note": "editorial 43, provenance 57", "reason": "The API server, feature server and SDKs are public under MIT. The product on jambonz.cloud and in the self-hosted packages is jambonz Commercial, which needs a licence key and whose terms forbid modifying its proprietary portions, while the docs still call jambonz open source (20 of 30). The privacy policy is dated 4 May 2021. It gives 30 days for usage data and an opt-out for call detail records. It says audio is never stored on jambonz servers, and the 11.1.6 notes of 4 October 2026 say support keeps SIP and RTP from calls for a few days, with an opt-out added in that release. No DPA was found (10 of 30). No deprecation policy was found. Removals are announced in the release that makes them, such as SMPP and five speech vendors in July and August 2026 (6 of 20). No sub-processor list was found. The policy says servers are in the United States and names a third-party billing partner. Telemetry from self-hosted instances is listed field by field (7 of 20)." } ], "assessment": { "date": "2026-10-08", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Live calls can be filtered by direction, number and status, with no field selection or limit (13 of 25). Recent calls take `page` and `count` with day and date range filters. The live call list has no pagination (14 of 20). Errors are HTTP codes 400, 404, 422 and 500 with a `msg` string, plus the rate limit headers. No error code list was found (10 of 20). No idempotency key was found on call creation, so a retried request can dial twice. Webhook retries are set with `rc` and `rp` on the application URL (5 of 20). A call needs `from`, `to` and an application or `call_hook`, with a 60 second answer timeout by default. `@jambonz/sdk` for Node.js is current and `jambonz-python-sdk` is experimental (12 of 15).", "maintenance": "jambonz Commercial 11.1.6 is dated 4 October 2026 and jambonz-api-server was tagged v0.9.15 on 7 October (30). The changelog has six entries from 14 August to 4 October 2026 (20). Of the 30 newest open issues and pull requests on jambonz-feature-server, 10 have a comment, and Snyk security upgrade pull requests from December 2025 to July 2026 sit open with none. GitHub reports 244 open issues and pull requests there. A community forum is linked and was not read (10 of 25). `@jambonz/sdk` 0.10.1 dates from 29 July 2026 and `jambonz-python-sdk` 0.3.2 from 19 May 2026, marked experimental (12 of 15). The API server runs lint and tests in CI on every push. We did not see the latest run's result (6 of 10).", "payments": "Scored on the hosted option, jambonz.cloud. No x402, MPP or L402 found (0). Prices per concurrent session a month are public without a login for the cloud and for self-hosted licences (20). A three-week cloud trial comes first. The terms ask for a name, company and email at sign-up and describe choosing a subscription when the trial ends, so we counted it as needing no card. The sign-up page itself is drawn by script and was not read (20). An account is created in a browser. `POST /ApiKeys` needs an existing token, so it does not help a new agent (0).", "reliability": "Graded as a hosted service, the API on jambonz.cloud, which the docs name as the simplest way to start. The same software can be self-hosted under a commercial licence. No status page is linked from jambonz.org, the docs or the jambonz.cloud landing page (0), so there is no readable incident history (5). Rate limits are published with numbers, 600 requests per 5 minute fixed window per client IP address on the docs page. The 11.1.6 notes of 4 October 2026 say the API server now counts 4,000 call creations and 600 call status reads a minute per account, and the docs page has not been updated (13 of 15). Responses carry `ratelimit-policy`, `ratelimit-remaining` and `ratelimit-reset`, and a client over a limit receives 429. No backoff guidance or idempotency key was found for the REST API. Webhook and WebSocket retries towards the application are documented with a backoff schedule (8 of 15). No uptime SLA was found for jambonz.cloud. Support SLAs are sold only with Enterprise support for self-hosted systems (0). The REST and WebSocket APIs carry no beta label, though the Python SDK is marked experimental (10).", "schema": "Three OpenAPI 3.1 documents are public (REST Call Control with 10 operations, REST Platform Management with 116, Webhooks with 4), with an AsyncAPI 2.6.0 document for the WebSocket channels (25). llms.txt, per-section indexes and every page as Markdown (10). Every operation has a summary and the verb pages explain use at length. Operation descriptions in the API reference are mostly one line (12 of 20). Enums for call status, direction and mid-call actions and required fields are marked. `to`, `call_hook`, `tag` and `amd` are objects, and 7 of 61 schemas in the call control document are objects with no properties (11 of 15). The SDK and verb pages carry code examples. The OpenAPI files contain no examples, errors are a single `msg` string, and 429 is not listed among the responses (8 of 15). The path is versioned `/v1` and the changelog is dated with component version tables. The REST introduction gives `https://jambonz.cloud/api` as the base URL while the OpenAPI files give `https://api.jambonz.cloud/v1` (12 of 15).", "security": "Bearer API tokens belong to an account or a service provider and carry `expires_at` and `last_used` fields. They can be created by API. No scopes and no delete operation appear in the published reference (18 of 30). No read-only key and no confirmation step before dialling were found. Call capacity limits can be set per account (4 of 20). Calls carry untrusted caller speech into the `agent` and `llm` verbs. The docs cover webhook signing with `Jambonz-Signature` and basic authentication, and no prompt-injection guidance was found in the pages read (5 of 15). Recent calls expose SIP traces, pcap files and Jaeger traces, and alerts can be pushed to a webhook, Slack, PagerDuty or email since 11.1.6. No log of API or portal actions was found (9 of 15). No security.txt, `SECURITY.md`, disclosure policy, bug bounty or certification was found, and no advisories are published on the API server or feature server repositories. The 11.1.5 notes describe fixes from a security review (4 of 20).", "transparency": "The API server, feature server and SDKs are public under MIT. The product on jambonz.cloud and in the self-hosted packages is jambonz Commercial, which needs a licence key and whose terms forbid modifying its proprietary portions, while the docs still call jambonz open source (20 of 30). The privacy policy is dated 4 May 2021. It gives 30 days for usage data and an opt-out for call detail records. It says audio is never stored on jambonz servers, and the 11.1.6 notes of 4 October 2026 say support keeps SIP and RTP from calls for a few days, with an opt-out added in that release. No DPA was found (10 of 30). No deprecation policy was found. Removals are announced in the release that makes them, such as SMPP and five speech vendors in July and August 2026 (6 of 20). No sub-processor list was found. The policy says servers are in the United States and names a third-party billing partner. Telemetry from self-hosted instances is listed field by field (7 of 20)." }, "sources": [ { "what": "home page and footer links", "url": "https://jambonz.org/", "seen": "2026-10-08" }, { "what": "pricing", "url": "https://jambonz.org/pricing", "seen": "2026-10-08" }, { "what": "self-hosting and licence prices", "url": "https://jambonz.org/self-hosting", "seen": "2026-10-08" }, { "what": "Terms of Use (cloud)", "url": "https://jambonz.org/terms", "seen": "2026-10-08" }, { "what": "privacy policy", "url": "https://jambonz.org/privacy", "seen": "2026-10-08" }, { "what": "self-hosted terms", "url": "https://jambonz.org/legal-terms-selfhosted", "seen": "2026-10-08" }, { "what": "docs index for agents", "url": "https://docs.jambonz.org/llms.txt", "seen": "2026-10-08" }, { "what": "REST API introduction", "url": "https://docs.jambonz.org/reference/introduction.md", "seen": "2026-10-08" }, { "what": "OpenAPI, REST Call Control", "url": "https://docs.jambonz.org/openapi/rest-call-control.json", "seen": "2026-10-08" }, { "what": "OpenAPI, REST Platform Management", "url": "https://docs.jambonz.org/openapi/rest-platform-management.json", "seen": "2026-10-08" }, { "what": "AsyncAPI, WebSocket channels", "url": "https://docs.jambonz.org/asyncapi.json", "seen": "2026-10-08" }, { "what": "API rate limits", "url": "https://docs.jambonz.org/guides/features/api-rate-limits.md", "seen": "2026-10-08" }, { "what": "webhook and WebSocket retries", "url": "https://docs.jambonz.org/guides/features/webhook-and-web-socket-retries.md", "seen": "2026-10-08" }, { "what": "securing HTTP endpoints", "url": "https://docs.jambonz.org/guides/features/securing-http-endpoints.md", "seen": "2026-10-08" }, { "what": "call recording", "url": "https://docs.jambonz.org/guides/features/call-recording.md", "seen": "2026-10-08" }, { "what": "deployment options", "url": "https://docs.jambonz.org/guides/get-started/deployment-options.md", "seen": "2026-10-08" }, { "what": "support plans", "url": "https://docs.jambonz.org/guides/get-started/support-plans.md", "seen": "2026-10-08" }, { "what": "licence keys and telemetry", "url": "https://docs.jambonz.org/self-hosting/overview/licensing.md", "seen": "2026-10-08" }, { "what": "changelog index", "url": "https://docs.jambonz.org/changelog/llms.txt", "seen": "2026-10-08" }, { "what": "release notes 11.1.6", "url": "https://docs.jambonz.org/changelog/2026/10/4.md", "seen": "2026-10-08" }, { "what": "release notes 11.1.5", "url": "https://docs.jambonz.org/changelog/2026/9/24.md", "seen": "2026-10-08" }, { "what": "release notes 11.0.0", "url": "https://docs.jambonz.org/changelog/2026/7/8.md", "seen": "2026-10-08" }, { "what": "Node.js SDK", "url": "https://docs.jambonz.org/sdks/node-sdk.md", "seen": "2026-10-08" }, { "what": "Python SDK", "url": "https://docs.jambonz.org/sdks/python-sdk.md", "seen": "2026-10-08" }, { "what": "API server repository, licence, tags and CI", "url": "https://github.com/jambonz/jambonz-api-server", "seen": "2026-10-08" }, { "what": "feature server repository and open issues", "url": "https://github.com/jambonz/jambonz-feature-server", "seen": "2026-10-08" }, { "what": "SDK and schema MCP server repository", "url": "https://github.com/jambonz/node-sdk", "seen": "2026-10-08" }, { "what": "npm package", "url": "https://registry.npmjs.org/@jambonz/sdk/latest", "seen": "2026-10-08" }, { "what": "PyPI package", "url": "https://pypi.org/pypi/jambonz-python-sdk/json", "seen": "2026-10-08" }, { "what": "security.txt, 404", "url": "https://jambonz.org/.well-known/security.txt", "seen": "2026-10-08" }, { "what": "domain registration", "url": "https://rdap.org/domain/jambonz.org", "seen": "2026-10-08" } ], "openQuestions": [ "The lead gave the vendor as jambonz. The legal entity is FirstFive8, Inc., and the docs MCP server in the lead serves documentation only", "Which base URL the hosted API answers on. The REST introduction says `https://jambonz.cloud/api` and the OpenAPI files say `https://api.jambonz.cloud/v1`. No call was made to the API", "Which rate limits apply on jambonz.cloud today, the docs page's 600 per 5 minutes per IP address or the per-account figures in the 11.1.6 notes", "Whether the three-week cloud trial needs a card. The terms imply it does not", "How long support keeps SIP and RTP captures. The 11.1.6 notes say a few days", "Whether API tokens can be revoked. No delete operation is in the published reference", "unchecked: the jambonz.cloud portal and its sign-up page, which are drawn by script", "unchecked: community.jambonz.org, so support responsiveness was read from GitHub only", "unchecked: the result of the latest CI runs on the repositories, and who answered the open issues", "unchecked: the `agent` and `llm` verb pages for prompt-injection guidance, and the WebRTC SDK pages", "The last registry and GitHub requests ran shortly after midnight on 9 October 2026. Dates follow the batch date" ] }, "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" }, "notable": [ "The release notes name the product jambonz Commercial, at 11.1.6 on 4 October 2026, and list the open-source components as jambonz OSS 0.9.14 (https://docs.jambonz.org/changelog/2026/10/4)", "11.0.0 on 8 July 2026 replaced FreeSWITCH with mediajam, a media server written in Go (https://docs.jambonz.org/changelog/2026/7/8)", "The 11.1.5 notes of 24 September 2026 list fixes from a security review of the API server, among them privilege escalation in user management (https://docs.jambonz.org/changelog/2026/9/24)", "A self-hosted instance under a licence key reports hourly call counts, its domain and its public and private IP addresses to FirstFive8. Air-gapped licences are sold without this (https://docs.jambonz.org/self-hosting/overview/licensing)", "The docs say devops scripts, private repositories and early releases are kept for customers on paid support plans (https://docs.jambonz.org/guides/get-started/support-plans)", "The Python SDK is marked experimental, and `@jambonz/node-client` and `@jambonz/node-client-ws` are deprecated in favour of `@jambonz/sdk` (https://docs.jambonz.org/sdks/node-sdk)", "The cloud Terms of Use limit permitted use to connecting with construction materials suppliers or buyers, wording that appears to come from another service's terms (https://jambonz.org/terms)", "The GitHub star count is for jambonz-feature-server. The download counts are for `@jambonz/sdk` (28 September to 4 October 2026) and `jambonz-python-sdk`" ], "area": "voice", "details": [ { "label": "Countries with numbers", "value": "None sold. Numbers come from the customer's own SIP carrier and are registered in jambonz through the portal or `/PhoneNumbers`" }, { "label": "SIP", "value": "Carrier trunks with IP allow lists or registration, SIP clients, least cost routing, SIP REFER, SIPREC, TLS and SRTP. The release notes say jambonz.cloud keeps plain RTP to TLS-registered devices for now" }, { "label": "Media streams", "value": "The `listen` and `stream` verbs fork call audio to a websocket, with dual streams and per-member conference forks. A WebRTC SDK covers browsers and React Native" }, { "label": "Voice AI layer", "value": "`agent` and `llm` verbs with the customer's own keys for 14 LLM providers and for speech vendors. Model and speech charges are billed by those vendors" }, { "label": "Recording", "value": "SIPREC to an outside server, or recording uploaded to the customer's S3, Azure or Google Cloud bucket, started, paused and stopped by verb or `PUT /Accounts/{AccountSid}/Calls/{CallSid}`" }, { "label": "Transfer", "value": "`transfer` verb since 11.0.0 (8 July 2026) for blind transfer by SIP REFER or bridged dial and warm transfer by hold or three-way conference" }, { "label": "Free tier", "value": "Three-week trial on jambonz.cloud (the terms say 21 days). Self-hosted trial licence of 30 days and 10 concurrent sessions, one per domain, non-production" }, { "label": "Rate limits", "value": "The docs page gives 600 requests per 5 minute fixed window per client IP address. The 11.1.6 notes give 4,000 call creations and 600 call status reads a minute per account" }, { "label": "SLA", "value": "No uptime SLA found for jambonz.cloud. Support SLAs are sold with the Enterprise support plan for self-hosted systems, priced by quote" }, { "label": "Data retention", "value": "Usage data 30 days per the privacy policy. Call detail records can be switched off. Support keeps SIP and RTP from calls for a few days unless the account opts out (11.1.6)" }, { "label": "Self-hosting", "value": "Debian packages, AWS, Azure, GCP and OCI images and Kubernetes. A licence key tied to the domain is required and the instance reports hourly call counts to FirstFive8" }, { "label": "MCP server", "value": "Docs and schema only. `https://docs.jambonz.org/_mcp/server` and `@jambonz/mcp-schema-server` (two tools, hosted at `https://mcp-server.jambonz.app/mcp`). No MCP server for call control was found" } ], "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, "checks": [ { "check": "Legal entity named", "value": "FirstFive8, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "jambonz.org, registered 2019-08-13 (7 years)", "points": 11, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": " is not on jambonz.org", "points": 0, "max": 15, "state": "no" }, { "check": "Terms of service", "value": "read, states 6 of the 7 things a reader expects, and has 1 clause that costs points", "points": 7.1, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 7 of the 8 things a reader expects", "points": 9.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ], "policies": [ { "kind": "terms", "url": "https://jambonz.org/terms", "state": "read", "readAt": "2026-10-08", "statedDate": "2021-05-04", "words": 2185, "points": 7.1, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last updated: May 4, 2021", "says": "Last updated 2021-05-04" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "These Terms will be governed by and construed in accordance with the laws of The Commonwealth of Massachusetts without regard to its conflict of laws provisions.", "says": "The law of the Commonwealth of Massachusetts" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "IN NO EVENT SHALL THE TOTAL LIABILITY OF JAMBONZ TO YOU FOR ALL DAMAGES, LOSSES, AND CAUSES OF ACTION RESULTING FROM YOUR USE OF THE SERVICE, WHETHER IN CONTRACT, TORT (INCLUDING, BUT NOT LIMITED TO, NEGLIGENCE) OR OTHERWISE, EXCEED THE AMOUNTS PAID BY YOU TO JAMBONZ IN THE IMMEDIATELY PRECEDING TWELVE-MONTH PERIOD.", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "jambonz may terminate or suspend your access to all or part of the Service, for any reason, including without limitation your breach of these Terms." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": true, "quote": "jambonz may modify the Terms from time to time and each modification will be effective when it is posted on the Service.", "says": "Changes are posted, with no other notice named" }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "You agree that you will not use or attempt to use this Service for any purpose other than to post, view, respond or otherwise connect with construction materials suppliers or buyers, as the case may be;" }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.automated", "label": "Restricts automated access", "found": true, "quote": "that uses manual or automated software or other processes to “crawl”, “spider”, index or in any non-transitory manner store or cache information obtained from any page of the Service,", "costsPoints": true }, { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "jambonz reserves the right at all times and for any reason or for no reason at all, in its sole discretion and without notice to you, to deny your access to and use of this Service." }, { "key": "old", "label": "Has not been updated for three years or more", "found": true, "quote": "Last updated: May 4, 2021" } ], "notes": [ { "date": "2026-10-08", "text": "The terms limit use of the service to posting, viewing, responding to or connecting with construction materials suppliers or buyers.", "quote": "You agree that you will not use or attempt to use this Service for any purpose other than to post, view, respond or otherwise connect with construction materials suppliers or buyers, as the case may be" }, { "date": "2026-10-08", "text": "A claim about use of the service must be started within one year after it arises.", "quote": "Any claim or cause of action you have with respect to use of the Service must be commenced within one (1) year after the claim arises." } ] }, { "kind": "privacy", "url": "https://jambonz.org/privacy", "state": "read", "readAt": "2026-10-08", "statedDate": "2021-05-04", "words": 2664, "points": 9.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last updated: May 4, 2021", "says": "Last updated 2021-05-04" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "What personal information we collect and when it is collected" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "We will retain your usage data for 30 days from the time it is created.", "says": "Names a period of 30 days" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "To work with your preferred carriers and speech service providers, you will need to provide us some information about those vendors and services." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": false }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "In such cases, you have a right to withdraw the consent at any time." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "If you have any additional questions or concerns about this Privacy Policy, please feel free to contact us any time through this Service, or email us at support@jambonz.org.", "says": "support@jambonz.org" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "If you are accessing the Service from outside the United States, please be aware that your information may be transferred to, stored, and processed in the United States where our servers are located and our central database is operated.", "says": "Data goes to the United States" } ], "toKnow": [ { "key": "old", "label": "Has not been updated for three years or more", "found": true, "quote": "Last updated: May 4, 2021" } ], "notes": [ { "date": "2026-10-08", "text": "The vendor says it never stores audio recordings or transcriptions of them in its databases or on its servers.", "quote": "We never store audio recordings -- or transcriptions of audio recordings -- in our databases or on our servers, so this kind of information about your End User customers can never be exposed from our systems." }, { "date": "2026-10-08", "text": "By using the service the customer agrees to release the vendor from all claims arising out of unauthorised use of its information.", "quote": "by using this Service, in accordance with the Terms of Use you agree to release us from any and all claims arising out of unauthorized use of your information." } ] } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jambonz.json" }, "verify": { "accepts": "a page on jambonz.org or one of its subdomains, or the README of github.com/jambonz/jambonz-feature-server", "badgeUrl": "https://www.anchorterminal.com/badges/jambonz.svg", "body": { "slug": "jambonz", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/jambonz", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/jambonz\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/jambonz.svg\" alt=\"jambonz on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![jambonz on Anchor Terminal](https://www.anchorterminal.com/badges/jambonz.svg)](https://www.anchorterminal.com/tools/jambonz)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/jambonz\"\u003ejambonz on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/jambonz", "json": "https://www.anchorterminal.com/tools/jambonz.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/jambonz.md", "slim": "https://www.anchorterminal.com/tools/jambonz.min.md" }, "markdown": "## Overview\n\n**Grade D · 49.2/100 · rank #712 of 842 · #11 in Phone calling \u0026 voice transport · not agent-ready · confidence medium**\n\n\n## Assessment\n\nOpenAPI 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | FirstFive8, Inc. (https://jambonz.org) |\n| Kind | HTTP API |\n| Category | Phone calling \u0026 voice transport (https://www.anchorterminal.com/categories/voice-calling) |\n| Transport | HTTP |\n| Auth | API key · 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. |\n| Pricing | Paid ($8 / mo) · 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). |\n| x402 | No · No x402, MPP or L402 in the docs index, the three OpenAPI files or the pricing page (checked 2026-10-08). |\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 |\n| Packages | npm: `@jambonz/sdk`; pypi: `jambonz-python-sdk`; npm: `@jambonz/mcp-schema-server` |\n| Source | https://github.com/jambonz/jambonz-feature-server |\n| Docs | https://docs.jambonz.org |\n| llms.txt | https://docs.jambonz.org/llms.txt |\n| Last release | 2026-10-04 |\n| GitHub stars | 103 (as of 2026-10-08) |\n| npm downloads / week | 1,368 |\n| PyPI downloads / week | 420 |\n| Countries with numbers | None sold. Numbers come from the customer's own SIP carrier and are registered in jambonz through the portal or `/PhoneNumbers` |\n| SIP | Carrier trunks with IP allow lists or registration, SIP clients, least cost routing, SIP REFER, SIPREC, TLS and SRTP. The release notes say jambonz.cloud keeps plain RTP to TLS-registered devices for now |\n| Media streams | The `listen` and `stream` verbs fork call audio to a websocket, with dual streams and per-member conference forks. A WebRTC SDK covers browsers and React Native |\n| Voice AI layer | `agent` and `llm` verbs with the customer's own keys for 14 LLM providers and for speech vendors. Model and speech charges are billed by those vendors |\n| Recording | SIPREC to an outside server, or recording uploaded to the customer's S3, Azure or Google Cloud bucket, started, paused and stopped by verb or `PUT /Accounts/{AccountSid}/Calls/{CallSid}` |\n| Transfer | `transfer` verb since 11.0.0 (8 July 2026) for blind transfer by SIP REFER or bridged dial and warm transfer by hold or three-way conference |\n| Free tier | Three-week trial on jambonz.cloud (the terms say 21 days). Self-hosted trial licence of 30 days and 10 concurrent sessions, one per domain, non-production |\n| Rate limits | The docs page gives 600 requests per 5 minute fixed window per client IP address. The 11.1.6 notes give 4,000 call creations and 600 call status reads a minute per account |\n| SLA | No uptime SLA found for jambonz.cloud. Support SLAs are sold with the Enterprise support plan for self-hosted systems, priced by quote |\n| Data retention | Usage data 30 days per the privacy policy. Call detail records can be switched off. Support keeps SIP and RTP from calls for a few days unless the account opts out (11.1.6) |\n| Self-hosting | Debian packages, AWS, Azure, GCP and OCI images and Kubernetes. A licence key tied to the domain is required and the instance reports hourly call counts to FirstFive8 |\n| MCP server | Docs and schema only. `https://docs.jambonz.org/_mcp/server` and `@jambonz/mcp-schema-server` (two tools, hosted at `https://mcp-server.jambonz.app/mcp`). No MCP server for call control was found |\n| Capabilities | voice.calls, voice.sip, voice.streaming, voice.recording, voice.agent |\n| Tags | hosted, self-hosted, sip, webrtc, open-source, openapi, llms-txt, typescript, python, webhooks, websocket, free-trial |\n| JSON | https://www.anchorterminal.com/api/v1/tools/jambonz.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 36 | 7.2 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 78 | 12.7 |\n| Agent ergonomics | 13% | 16.2 | 54 | 8.8 |\n| Security \u0026 auth | 14% | 17.5 | 42 | 7.3 |\n| Payments \u0026 pricing | 10% | 12.5 | 40 | 5.0 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 78 | 6.8 |\n| Transparency \u0026 trust (editorial 43, provenance 57) | 7% | 8.8 | 50 | 4.4 |\n| Negative events | up to −15 | up to −15 | 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) | -3 |\n| **Total** | | | | **49.2 → D** |\n\n### Why each score\n\n- Reliability 36: Graded as a hosted service, the API on jambonz.cloud, which the docs name as the simplest way to start. The same software can be self-hosted under a commercial licence. No status page is linked from jambonz.org, the docs or the jambonz.cloud landing page (0), so there is no readable incident history (5). Rate limits are published with numbers, 600 requests per 5 minute fixed window per client IP address on the docs page. The 11.1.6 notes of 4 October 2026 say the API server now counts 4,000 call creations and 600 call status reads a minute per account, and the docs page has not been updated (13 of 15). Responses carry `ratelimit-policy`, `ratelimit-remaining` and `ratelimit-reset`, and a client over a limit receives 429. No backoff guidance or idempotency key was found for the REST API. Webhook and WebSocket retries towards the application are documented with a backoff schedule (8 of 15). No uptime SLA was found for jambonz.cloud. Support SLAs are sold only with Enterprise support for self-hosted systems (0). The REST and WebSocket APIs carry no beta label, though the Python SDK is marked experimental (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 78: Three OpenAPI 3.1 documents are public (REST Call Control with 10 operations, REST Platform Management with 116, Webhooks with 4), with an AsyncAPI 2.6.0 document for the WebSocket channels (25). llms.txt, per-section indexes and every page as Markdown (10). Every operation has a summary and the verb pages explain use at length. Operation descriptions in the API reference are mostly one line (12 of 20). Enums for call status, direction and mid-call actions and required fields are marked. `to`, `call_hook`, `tag` and `amd` are objects, and 7 of 61 schemas in the call control document are objects with no properties (11 of 15). The SDK and verb pages carry code examples. The OpenAPI files contain no examples, errors are a single `msg` string, and 429 is not listed among the responses (8 of 15). The path is versioned `/v1` and the changelog is dated with component version tables. The REST introduction gives `https://jambonz.cloud/api` as the base URL while the OpenAPI files give `https://api.jambonz.cloud/v1` (12 of 15).\n- Agent ergonomics 54: Live calls can be filtered by direction, number and status, with no field selection or limit (13 of 25). Recent calls take `page` and `count` with day and date range filters. The live call list has no pagination (14 of 20). Errors are HTTP codes 400, 404, 422 and 500 with a `msg` string, plus the rate limit headers. No error code list was found (10 of 20). No idempotency key was found on call creation, so a retried request can dial twice. Webhook retries are set with `rc` and `rp` on the application URL (5 of 20). A call needs `from`, `to` and an application or `call_hook`, with a 60 second answer timeout by default. `@jambonz/sdk` for Node.js is current and `jambonz-python-sdk` is experimental (12 of 15).\n- Security \u0026 auth 42: Bearer API tokens belong to an account or a service provider and carry `expires_at` and `last_used` fields. They can be created by API. No scopes and no delete operation appear in the published reference (18 of 30). No read-only key and no confirmation step before dialling were found. Call capacity limits can be set per account (4 of 20). Calls carry untrusted caller speech into the `agent` and `llm` verbs. The docs cover webhook signing with `Jambonz-Signature` and basic authentication, and no prompt-injection guidance was found in the pages read (5 of 15). Recent calls expose SIP traces, pcap files and Jaeger traces, and alerts can be pushed to a webhook, Slack, PagerDuty or email since 11.1.6. No log of API or portal actions was found (9 of 15). No security.txt, `SECURITY.md`, disclosure policy, bug bounty or certification was found, and no advisories are published on the API server or feature server repositories. The 11.1.5 notes describe fixes from a security review (4 of 20).\n- Payments \u0026 pricing 40: Scored on the hosted option, jambonz.cloud. No x402, MPP or L402 found (0). Prices per concurrent session a month are public without a login for the cloud and for self-hosted licences (20). A three-week cloud trial comes first. The terms ask for a name, company and email at sign-up and describe choosing a subscription when the trial ends, so we counted it as needing no card. The sign-up page itself is drawn by script and was not read (20). An account is created in a browser. `POST /ApiKeys` needs an existing token, so it does not help a new agent (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 78: jambonz Commercial 11.1.6 is dated 4 October 2026 and jambonz-api-server was tagged v0.9.15 on 7 October (30). The changelog has six entries from 14 August to 4 October 2026 (20). Of the 30 newest open issues and pull requests on jambonz-feature-server, 10 have a comment, and Snyk security upgrade pull requests from December 2025 to July 2026 sit open with none. GitHub reports 244 open issues and pull requests there. A community forum is linked and was not read (10 of 25). `@jambonz/sdk` 0.10.1 dates from 29 July 2026 and `jambonz-python-sdk` 0.3.2 from 19 May 2026, marked experimental (12 of 15). The API server runs lint and tests in CI on every push. We did not see the latest run's result (6 of 10).\n- Transparency \u0026 trust 50: The API server, feature server and SDKs are public under MIT. The product on jambonz.cloud and in the self-hosted packages is jambonz Commercial, which needs a licence key and whose terms forbid modifying its proprietary portions, while the docs still call jambonz open source (20 of 30). The privacy policy is dated 4 May 2021. It gives 30 days for usage data and an opt-out for call detail records. It says audio is never stored on jambonz servers, and the 11.1.6 notes of 4 October 2026 say support keeps SIP and RTP from calls for a few days, with an opt-out added in that release. No DPA was found (10 of 30). No deprecation policy was found. Removals are announced in the release that makes them, such as SMPP and five speech vendors in July and August 2026 (6 of 20). No sub-processor list was found. The policy says servers are in the United States and names a third-party billing partner. Telemetry from self-hosted instances is listed field by field (7 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (25 items): https://www.anchorterminal.com/fixes/jambonz.md (JSON https://www.anchorterminal.com/fixes/jambonz.json)\n\n### What we couldn't check\n\n- The lead gave the vendor as jambonz. The legal entity is FirstFive8, Inc., and the docs MCP server in the lead serves documentation only\n- Which base URL the hosted API answers on. The REST introduction says `https://jambonz.cloud/api` and the OpenAPI files say `https://api.jambonz.cloud/v1`. No call was made to the API\n- Which rate limits apply on jambonz.cloud today, the docs page's 600 per 5 minutes per IP address or the per-account figures in the 11.1.6 notes\n- Whether the three-week cloud trial needs a card. The terms imply it does not\n- How long support keeps SIP and RTP captures. The 11.1.6 notes say a few days\n- Whether API tokens can be revoked. No delete operation is in the published reference\n- unchecked: the jambonz.cloud portal and its sign-up page, which are drawn by script\n- unchecked: community.jambonz.org, so support responsiveness was read from GitHub only\n- unchecked: the result of the latest CI runs on the repositories, and who answered the open issues\n- unchecked: the `agent` and `llm` verb pages for prompt-injection guidance, and the WebRTC SDK pages\n- The last registry and GitHub requests ran shortly after midnight on 9 October 2026. Dates follow the batch date\n\n### Sources\n\n- home page and footer links: \u003chttps://jambonz.org/\u003e (seen 2026-10-08)\n- pricing: \u003chttps://jambonz.org/pricing\u003e (seen 2026-10-08)\n- self-hosting and licence prices: \u003chttps://jambonz.org/self-hosting\u003e (seen 2026-10-08)\n- Terms of Use (cloud): \u003chttps://jambonz.org/terms\u003e (seen 2026-10-08)\n- privacy policy: \u003chttps://jambonz.org/privacy\u003e (seen 2026-10-08)\n- self-hosted terms: \u003chttps://jambonz.org/legal-terms-selfhosted\u003e (seen 2026-10-08)\n- docs index for agents: \u003chttps://docs.jambonz.org/llms.txt\u003e (seen 2026-10-08)\n- REST API introduction: \u003chttps://docs.jambonz.org/reference/introduction.md\u003e (seen 2026-10-08)\n- OpenAPI, REST Call Control: \u003chttps://docs.jambonz.org/openapi/rest-call-control.json\u003e (seen 2026-10-08)\n- OpenAPI, REST Platform Management: \u003chttps://docs.jambonz.org/openapi/rest-platform-management.json\u003e (seen 2026-10-08)\n- AsyncAPI, WebSocket channels: \u003chttps://docs.jambonz.org/asyncapi.json\u003e (seen 2026-10-08)\n- API rate limits: \u003chttps://docs.jambonz.org/guides/features/api-rate-limits.md\u003e (seen 2026-10-08)\n- webhook and WebSocket retries: \u003chttps://docs.jambonz.org/guides/features/webhook-and-web-socket-retries.md\u003e (seen 2026-10-08)\n- securing HTTP endpoints: \u003chttps://docs.jambonz.org/guides/features/securing-http-endpoints.md\u003e (seen 2026-10-08)\n- call recording: \u003chttps://docs.jambonz.org/guides/features/call-recording.md\u003e (seen 2026-10-08)\n- deployment options: \u003chttps://docs.jambonz.org/guides/get-started/deployment-options.md\u003e (seen 2026-10-08)\n- support plans: \u003chttps://docs.jambonz.org/guides/get-started/support-plans.md\u003e (seen 2026-10-08)\n- licence keys and telemetry: \u003chttps://docs.jambonz.org/self-hosting/overview/licensing.md\u003e (seen 2026-10-08)\n- changelog index: \u003chttps://docs.jambonz.org/changelog/llms.txt\u003e (seen 2026-10-08)\n- release notes 11.1.6: \u003chttps://docs.jambonz.org/changelog/2026/10/4.md\u003e (seen 2026-10-08)\n- release notes 11.1.5: \u003chttps://docs.jambonz.org/changelog/2026/9/24.md\u003e (seen 2026-10-08)\n- release notes 11.0.0: \u003chttps://docs.jambonz.org/changelog/2026/7/8.md\u003e (seen 2026-10-08)\n- Node.js SDK: \u003chttps://docs.jambonz.org/sdks/node-sdk.md\u003e (seen 2026-10-08)\n- Python SDK: \u003chttps://docs.jambonz.org/sdks/python-sdk.md\u003e (seen 2026-10-08)\n- API server repository, licence, tags and CI: \u003chttps://github.com/jambonz/jambonz-api-server\u003e (seen 2026-10-08)\n- feature server repository and open issues: \u003chttps://github.com/jambonz/jambonz-feature-server\u003e (seen 2026-10-08)\n- SDK and schema MCP server repository: \u003chttps://github.com/jambonz/node-sdk\u003e (seen 2026-10-08)\n- npm package: \u003chttps://registry.npmjs.org/@jambonz/sdk/latest\u003e (seen 2026-10-08)\n- PyPI package: \u003chttps://pypi.org/pypi/jambonz-python-sdk/json\u003e (seen 2026-10-08)\n- security.txt, 404: \u003chttps://jambonz.org/.well-known/security.txt\u003e (seen 2026-10-08)\n- domain registration: \u003chttps://rdap.org/domain/jambonz.org\u003e (seen 2026-10-08)\n\n## Who's behind it (provenance 57/100, checked 2026-10-08)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | FirstFive8, Inc. | 20/20 |\n| Domain age | jambonz.org, registered 2019-08-13 (7 years) | 11/15 |\n| Endpoint on the vendor's domain | is not on jambonz.org | 0/15 |\n| Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 |\n| Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 |\n| Status page | not found | 0/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n\nThe 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.\n\nThe 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.\n\nThe 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.\n\nNo status page is linked from jambonz.org, the docs or the jambonz.cloud landing page.\n\nhttps://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.\n\nRDAP for jambonz.org gives a registration date of 2019-08-13.\n\nThe 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.\n\ndocs.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.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://jambonz.org/terms), read 2026-10-08, dated 2021-05-04, states 6 of the 7 things a reader expects.\n\n- To know. Restricts automated access (costs points). \"that uses manual or automated software or other processes to “crawl”, “spider”, index or in any non-transitory manner store or cache information obtained from any page of the Service,\"\n- To know. Says access can be ended without notice or for any reason. \"jambonz reserves the right at all times and for any reason or for no reason at all, in its sole discretion and without notice to you, to deny your access to and use of this Service.\"\n- To know. Has not been updated for three years or more. \"Last updated: May 4, 2021\"\n- Gives the date it was last updated. Last updated 2021-05-04.\n- Names the governing law or courts. The law of the Commonwealth of Massachusetts.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Says how changes to the terms are announced. Changes are posted, with no other notice named.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-10-08). The terms limit use of the service to posting, viewing, responding to or connecting with construction materials suppliers or buyers. \"You agree that you will not use or attempt to use this Service for any purpose other than to post, view, respond or otherwise connect with construction materials suppliers or buyers, as the case may be\"\n- Also in the text (2026-10-08). A claim about use of the service must be started within one year after it arises. \"Any claim or cause of action you have with respect to use of the Service must be commenced within one (1) year after the claim arises.\"\n\n**Privacy policy** (https://jambonz.org/privacy), read 2026-10-08, dated 2021-05-04, states 7 of the 8 things a reader expects.\n\n- To know. Has not been updated for three years or more. \"Last updated: May 4, 2021\"\n- Gives the date it was last updated. Last updated 2021-05-04.\n- Says how long data is kept. Names a period of 30 days.\n- Not found in the text. Says whether personal data is sold or shared for advertising.\n- Gives a privacy contact. support@jambonz.org.\n- Says where data is transferred or stored. Data goes to the United States.\n- Also in the text (2026-10-08). The vendor says it never stores audio recordings or transcriptions of them in its databases or on its servers. \"We never store audio recordings -- or transcriptions of audio recordings -- in our databases or on our servers, so this kind of information about your End User customers can never be exposed from our systems.\"\n- Also in the text (2026-10-08). By using the service the customer agrees to release the vendor from all claims arising out of unauthorised use of its information. \"by using this Service, in accordance with the Terms of Use you agree to release us from any and all claims arising out of unauthorized use of your information.\"\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Cloud, concurrent session (5 to 249 sessions) | $8 | per month (plan) | monthly subscription, no per-minute charge |\n| Cloud, concurrent session (250 to 499 sessions) | $6 | per month (plan) | monthly subscription |\n| Cloud, concurrent session (500 or more sessions) | $5 | per month (plan) | monthly subscription |\n| Self-hosted licence, concurrent session | $7 | per month (plan) | one cluster, keyed to its domain |\n| Self-hosted licence, unlimited sessions | $2000 | per month (plan) | one cluster, keyed to its domain |\n| Installation support package | $1000 | per transaction | one-time fee for one month of installation support |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Three OpenAPI 3.1 documents (10, 116 and 4 operations) and an AsyncAPI 2.6.0 document for the WebSocket channels are public\n- The docs publish an llms.txt, every page as Markdown and a docs MCP server at `https://docs.jambonz.org/_mcp/server`\n- Prices are per concurrent session a month ($8, $6 or $5 on the cloud), with no per-minute charge and recording and streaming included\n- Six dated release notes from 14 August to 4 October 2026, each with a component version table and self-hosted upgrade notes\n- The API server, feature server and both SDKs are public under MIT, and the same platform can run in the customer's own network\n\n## Weaknesses\n\n- No status page, uptime SLA, security.txt, `SECURITY.md` or published advisory was found for jambonz.cloud or the repositories\n- 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\n- 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\n- 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\n- No idempotency key was found on `POST /Accounts/{AccountSid}/Calls`, so a retried request can place a second call\n- jambonz sells no phone numbers or minutes. Every call needs a SIP trunk from another carrier and the customer's own speech vendor keys\n\n## Before you call it (notes for agents)\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## Connect\n\nInstall:\n\n```bash\nnpm install @jambonz/sdk\n```\n\nFirst request:\n\n```bash\nPOST https://api.jambonz.cloud/v1/Accounts/{AccountSid}/Calls\nAuthorization: Bearer \u003ctoken\u003e\nContent-Type: application/json\n```\n\nThrough letme (picks today, calling later): https://letme.dev/jambonz. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Twilio Programmable Voice API + MCP | A | 80.4 | 9 | voice.calls, voice.streaming, voice.sip, voice.recording | no | https://www.anchorterminal.com/tools/twilio-voice.md |\n| Telnyx Voice API + MCP | BB | 74.2 | 73 | voice.calls, voice.streaming, voice.sip, voice.recording | no | https://www.anchorterminal.com/tools/telnyx-voice.md |\n| SignalWire Voice API | B | 67.1 | 242 | voice.calls, voice.streaming, voice.sip, voice.recording | no | https://www.anchorterminal.com/tools/signalwire-voice.md |\n| Bandwidth Voice API + MCP | B | 63.7 | 338 | voice.calls, voice.streaming, voice.sip, voice.recording | no | https://www.anchorterminal.com/tools/bandwidth-voice.md |\n| Sinch Voice API + MCP | B | 62.7 | 381 | voice.calls, voice.streaming, voice.sip, voice.recording | no | https://www.anchorterminal.com/tools/sinch-voice.md |\n| Plivo Voice API | C | 60.4 | 466 | voice.calls, voice.streaming, voice.sip, voice.recording | no | https://www.anchorterminal.com/tools/plivo-voice.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The release notes name the product jambonz Commercial, at 11.1.6 on 4 October 2026, and list the open-source components as jambonz OSS 0.9.14 (source: \u003chttps://docs.jambonz.org/changelog/2026/10/4\u003e)\n- 11.0.0 on 8 July 2026 replaced FreeSWITCH with mediajam, a media server written in Go (source: \u003chttps://docs.jambonz.org/changelog/2026/7/8\u003e)\n- The 11.1.5 notes of 24 September 2026 list fixes from a security review of the API server, among them privilege escalation in user management (source: \u003chttps://docs.jambonz.org/changelog/2026/9/24\u003e)\n- A self-hosted instance under a licence key reports hourly call counts, its domain and its public and private IP addresses to FirstFive8. Air-gapped licences are sold without this (source: \u003chttps://docs.jambonz.org/self-hosting/overview/licensing\u003e)\n- The docs say devops scripts, private repositories and early releases are kept for customers on paid support plans (source: \u003chttps://docs.jambonz.org/guides/get-started/support-plans\u003e)\n- The Python SDK is marked experimental, and `@jambonz/node-client` and `@jambonz/node-client-ws` are deprecated in favour of `@jambonz/sdk` (source: \u003chttps://docs.jambonz.org/sdks/node-sdk\u003e)\n- The cloud Terms of Use limit permitted use to connecting with construction materials suppliers or buyers, wording that appears to come from another service's terms (source: \u003chttps://jambonz.org/terms\u003e)\n- The GitHub star count is for jambonz-feature-server. The download counts are for `@jambonz/sdk` (28 September to 4 October 2026) and `jambonz-python-sdk`\n\n## Compare\n\n- [Bandwidth Voice API + MCP vs jambonz](https://www.anchorterminal.com/compare/bandwidth-voice-vs-jambonz.md): B 63.7 vs D 49.2\n- [Exotel Voice API + MCP vs jambonz](https://www.anchorterminal.com/compare/exotel-voice-vs-jambonz.md): E 39.4 vs D 49.2\n- [Infobip Calls API + MCP vs jambonz](https://www.anchorterminal.com/compare/infobip-calls-vs-jambonz.md): C 60.3 vs D 49.2\n- [jambonz vs LiveKit Telephony](https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.md): D 49.2 vs B 67.5\n- [jambonz vs Plivo Voice API](https://www.anchorterminal.com/compare/jambonz-vs-plivo-voice.md): D 49.2 vs C 60.4\n- [jambonz vs SignalWire Voice API](https://www.anchorterminal.com/compare/jambonz-vs-signalwire-voice.md): D 49.2 vs B 67.1\n- [jambonz vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-sinch-voice.md): D 49.2 vs B 62.7\n- [jambonz vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-telnyx-voice.md): D 49.2 vs BB 74.2\n- [jambonz vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-twilio-voice.md): D 49.2 vs A 80.4\n- [jambonz vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/jambonz-vs-vonage-voice.md): D 49.2 vs C 58.9\n- [jambonz vs Voximplant](https://www.anchorterminal.com/compare/jambonz-vs-voximplant.md): D 49.2 vs D 51.7\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on jambonz.org or one of its subdomains, or the README of github.com/jambonz/jambonz-feature-server. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"jambonz\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/jambonz\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/jambonz.svg\" alt=\"jambonz on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![jambonz on Anchor Terminal](https://www.anchorterminal.com/badges/jambonz.svg)](https://www.anchorterminal.com/tools/jambonz)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/jambonz\"\u003ejambonz on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say jambonz is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/jambonz-dark.png\n- Light: https://www.anchorterminal.com/assets/share/jambonz-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Phone calling \u0026 voice transport", "url": "https://www.anchorterminal.com/categories/voice-calling" }, { "name": "jambonz", "url": "" } ], "description": "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.", "facts": [ "rank #712 of 842", "API key auth", "0 desk reviews" ], "h1": "jambonz", "image": "https://www.anchorterminal.com/assets/og/tools-jambonz.png", "path": "/tools/jambonz", "published": "2026-10-01", "section": "tools", "title": "jambonz review for AI agents, grade D (49.2/100) | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/tools/jambonz" }, "tokens": { "markdown": 8400, "slim": 1930 }, "version": 1 }