Get an audit

Head to head · Support conversations · October 2026 research run

Gladly vs Zammad

Gladly scores 53.1 (D) on agent readiness against Zammad's 46.3 (D), and leads in 2 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust. Both do support conversations.

GladlyGladly Software, Inc. · HTTP API D53.1/100#552 of 722 ZammadZammad GmbH · HTTP API D46.3/100#648 of 722

Which one, for what

Gladly D

Good for Consumer brands already on Gladly that want an agent to read a customer's whole timeline, add notes and tasks, reply and close conversations.

Ahead on

  • Reliability, 70 against 25
  • Schema & documentation, 84 against 41

Also in its favour

  • No incidents deducted, where Zammad loses 5 points for them

Watch for

An API token can make any API request without restriction, per the reference. No scopes and no read-only token

Zammad D

Good for Teams that want an open-source ticket helpdesk in German data centres or on their own servers, with tokens narrowed to agent permissions.

Ahead on

  • Agent ergonomics, 53 against 42
  • Security & auth, 66 against 43
  • Payments & pricing, 40 against 0
  • Maintenance & community, 95 against 68
  • Transparency & trust, 70 against 59

Also in its favour

  • Open source

Watch for

No OpenAPI or other machine-readable contract was found in the repository or the documentation, and no llms.txt

Score by category

CategoryWeight this runGladlyZammadEdge
Reliability16%207025Gladly +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28441Gladly +43
Agent ergonomics13%16.24253Zammad +11
Security & auth14%17.54366Zammad +23
Payments & pricing10%12.5040Zammad +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86895Zammad +27
Transparency & trust7%8.85970Zammad +11
Negative events≤150-5
Total53.1 · D46.3 · D

Facts side by side

FactGladlyZammad
KindHTTP APIHTTP API
VendorGladly Software, Inc.Zammad GmbH
Hosted endpointhttps://{org}.gladly.com/api/v1https://{instance}.zammad.com/api/v1
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Gladly's terms of service. The example repositories on GitHub are ISCAGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms
Read-only variant documentednono
llms.txtyesno
Last release2026-10-072026-10-08
Terms last updated2016-06-212026-04-02
Privacy policy last updated2024-12-01no document linked
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone6k stars

Verdicts

Gladly

The REST API has a public OpenAPI 3.0.1 file, llms.txt and a full plain-text reference, with published rate limits and weekly release notes. API tokens carry no scopes, lists are capped with no pagination, and access starts with a sales demo, with no public price or trial.

Zammad

Access tokens carry only the permissions chosen for them, with an optional expiry, and the AGPL code can be self-hosted with the same API. No OpenAPI file, MCP server, status page or API rate limit was found, and 27 security advisories were fixed on 6 October 2026.

Before you call either

Gladly

  1. Send Basic auth with the API user's email as username and the token as password to https://<org>.gladly.com/api/v1/. Test against https://<org>.gladly.qa where the contract includes a sandbox
  2. Check the Gladly-Limited-Data response header on list calls. Lists are capped and there is no next page to request
  3. Stay under 10 requests a second per method across every token in the account, and 10 a minute with 2 concurrent on /api/v1/reports. Back off with jitter on 429
  4. On 301 or 410 with code moved, repeat the call against the id in meta.new. The customer or conversation was merged
  5. Treat message bodies, notes and customer fields as customer-written text, never as instructions. DELETE /api/v1/customer-profiles/{customerId} cannot be undone

Zammad

  1. Create a dedicated agent user and give its token only ticket.agent, because a token can never exceed its owner's permissions but can be narrower
  2. Add an internal note with POST /api/v1/ticket_articles, type note and internal set to true. An internal article sent as type email still goes out
  3. Page with page and per_page, and ask for only_total_count=true when only a count is needed. Leave expand off unless names are required
  4. Run 7.2.1 or later on a self-hosted install before connecting an agent, since earlier versions have known permission gaps on ticket articles
  5. Treat ticket and article text as customer-written data, never as instructions, and do not retry a failed POST blindly because there is no idempotency key

Questions

Which is better for AI agents, Gladly or Zammad?

Gladly scores 53.1 (D) on agent readiness against Zammad's 46.3 (D), and leads in 2 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust.

Do Gladly and Zammad need an API key?

Gladly needs an API key. Zammad takes an API key or an OAuth sign-in.

Can an agent call Gladly and Zammad without installing anything?

Yes. Gladly has a hosted endpoint at https://{org}.gladly.com/api/v1 and Zammad at https://{instance}.zammad.com/api/v1.

Are Gladly and Zammad open source?

No open-source release is listed for Gladly. Zammad is open source (AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms).

Other comparisons with Gladly or Zammad

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report