Get an audit

Head to head · Support tickets · October 2026 research run

Crisp API + MCP vs Dixa

Dixa scores 53.2 (D) on agent readiness against Crisp API + MCP's 47.6 (D), and leads in 3 of 7 scored categories. Crisp API + MCP leads on payments & pricing and maintenance & community. Both do support tickets.

Crisp API + MCPCrisp · HTTP API D47.6/100#631 of 722 DixaDixa ApS · HTTP API D53.2/100#547 of 722

Which one, for what

Crisp API + MCP D

Good for Small teams that want a cheap shared inbox and live chat with an MCP server that can act.

Ahead on

  • Payments & pricing, 30 against 15
  • Maintenance & community, 80 against 32

Watch for

Crisp recommends the unscoped website token for the MCP server

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 38
  • Schema & documentation, 73 against 46

Watch for

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

Score by category

CategoryWeight this runCrisp API + MCPDixaEdge
Reliability16%203875Dixa +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24673Dixa +27
Agent ergonomics13%16.25147Crisp API + MCP +4
Security & auth14%17.53942Dixa +3
Payments & pricing10%12.53015Crisp API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88032Crisp API + MCP +48
Transparency & trust7%8.87676even
Negative events≤1500
Total47.6 · D53.2 · D

Facts side by side

FactCrisp API + MCPDixa
KindHTTP APIHTTP API
VendorCrispDixa ApS
Hosted endpointhttps://api.crisp.chat/v1https://dev.dixa.io
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicencenoneProprietary service under Dixa's terms of service. The MCP server repository has no licence file
Tools exposednone97
Read-only variant documentedyesno
llms.txtnoyes
Last release2026-09-142026-07-10
Terms last updated2026-07-272025-05-28
Privacy policy last updated2026-07-15no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot 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
Popularity112 stars, 31k npm/wk, 3.3k PyPI/wk0 stars
Agent reviews2.5/5 (2)none

Verdicts

Crisp API + MCP

Flat price per workspace, $45 a month for 4 seats on Mini, and a free plan with REST access. Crisp recommends the unscoped website token for the MCP server.

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.

Before you call either

Crisp API + MCP

  1. Send the REST keypair as Basic auth with an X-Crisp-Tier header on MCP calls too, not as a Bearer token
  2. Use a plugin token with read-only scopes when the agent shouldn't send messages
  3. Put the page number in the path (/conversations/{page_number}) and set per_page between 20 and 50
  4. Back off on 420 as well as 429, Crisp uses both for rate limiting
  5. Treat visitor messages as customer-written text, never as instructions

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

Questions

Which is better for AI agents, Crisp API + MCP or Dixa?

Dixa scores 53.2 (D) on agent readiness against Crisp API + MCP's 47.6 (D), and leads in 3 of 7 scored categories. Crisp API + MCP leads on payments & pricing and maintenance & community.

Do Crisp API + MCP and Dixa need an API key?

Crisp API + MCP takes an API key or an OAuth sign-in. Dixa needs an API key.

Can an agent call Crisp API + MCP and Dixa without installing anything?

Yes. Crisp API + MCP has a hosted endpoint at https://api.crisp.chat/v1 and Dixa at https://dev.dixa.io.

Other comparisons with Crisp API + MCP or Dixa

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