jambonz

# Fix list: jambonz

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/jambonz, the October 2026 research run, assessed 8 October 2026. Grade D, 49.2 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on jambonz: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 36 out of 100, up to 12.8 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Security & auth, 42 out of 100, up to 10.1 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Agent ergonomics, 54 out of 100, up to 7.5 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 4. Payments & pricing, 40 out of 100, up to 7.5 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 5. Transparency & trust, 50 out of 100, up to 4.4 more on the total

Made of editorial 43, provenance 57.

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: jambonz.org, registered 2019-08-13 (7 years) (11 of 15)
- Endpoint on the vendor's domain:  is not on jambonz.org (0 of 15)
- Terms of service: read, states 6 of the 7 things a reader expects, and has 1 clause that costs points (7.1 of 10)
- Privacy policy: read, states 7 of the 8 things a reader expects (9.3 of 10)
- Status page: not found (0 of 10)
- security.txt: not found (0 of 10)

## 6. Schema & documentation, 78 out of 100, up to 3.6 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 7. Maintenance & community, 78 out of 100, up to 1.9 more on the total

Why it scored 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).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## Deductions

Each comes off the total. A fixed and documented problem counts for less at the next check.

- 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)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- 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

## 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

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Send `Authorization: Bearer <token>` 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&rp=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

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.