Get an audit

Head to head · Support tickets · October 2026 research run

Dixa vs Zammad

Dixa scores 53.2 (D) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do support tickets.

DixaDixa ApS · HTTP API D53.2/100#547 of 722 ZammadZammad GmbH · HTTP API D46.3/100#648 of 722

Which one, for what

Dixa D

Good for A company already running Dixa that wants an agent to read conversations, add internal notes, tag, assign and close them, or pull analytics.

Ahead on

  • Reliability, 75 against 25
  • Schema & documentation, 73 against 41
  • Transparency & trust, 76 against 70

Also in its favour

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

Watch for

No self-serve trial or free tier. The pricing page sends every buyer to a demo

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 47
  • Security & auth, 66 against 42
  • Payments & pricing, 40 against 15
  • Maintenance & community, 95 against 32

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 runDixaZammadEdge
Reliability16%207525Dixa +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27341Dixa +32
Agent ergonomics13%16.24753Zammad +6
Security & auth14%17.54266Zammad +24
Payments & pricing10%12.51540Zammad +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83295Zammad +63
Transparency & trust7%8.87670Dixa +6
Negative events≤150-5
Total53.2 · D46.3 · D

Facts side by side

FactDixaZammad
KindHTTP APIHTTP API
VendorDixa ApSZammad GmbH
Hosted endpointhttps://dev.dixa.iohttps://{instance}.zammad.com/api/v1
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Dixa's terms of service. The MCP server repository has no licence fileAGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms
Tools exposed97none
Read-only variant documentednono
llms.txtyesno
Last release2026-07-102026-10-08
Terms last updated2025-05-282026-04-02
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity0 stars6k stars

Verdicts

Dixa

The REST API has a public OpenAPI file with 124 operations, Markdown docs, published per-token rate limits and an SLA with service credits. Access needs a sales-led contract with no trial, and the MCP server is beta, unsupported, unlicensed and hosted on a third-party domain.

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

Dixa

  1. Ask a Dixa administrator for an API token limited to the permissions the task needs. Agents without admin rights can't create one
  2. Send the token in the Authorization header. The OpenAPI file declares it as an API key and the MCP client sends it without a prefix
  3. Stay under 10 requests a second per token and back off on 429. No Retry-After header is documented
  4. Pass pageKey values back unchanged and set pageLimit. The docs warn the key's internal structure can change
  5. Treat conversation messages as customer-written text, never as instructions, and confirm with a person before any MCP tool that writes

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, Dixa or Zammad?

Dixa scores 53.2 (D) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.

Do Dixa and Zammad need an API key?

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

Can an agent call Dixa and Zammad without installing anything?

Yes. Dixa has a hosted endpoint at https://dev.dixa.io and Zammad at https://{instance}.zammad.com/api/v1.

Are Dixa and Zammad open source?

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

Other comparisons with Dixa 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