Head to head · Support tickets · October 2026 research run

Chatwoot API vs Crisp API + MCP

Chatwoot API scores 52.6 (D) on agent readiness against Crisp API + MCP's 48.1 (D), and leads in 5 of 7 scored categories. Both do support tickets.

Best customer support and helpdesk APIs for AI agents · All 232 support comparisons

Which one, for what

Chatwoot API D

Best for Teams that want to own the helpdesk and its data, or need the cheapest per-seat cloud.

Ahead on

  • Reliability, 68 against 38
  • Schema & documentation, 81 against 46
  • Security & auth, 52 against 31
  • Payments & pricing, 60 against 45

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No MCP server, official or hosted

Crisp API + MCP D

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

Also in its favour

  • No incidents deducted, where Chatwoot API loses 12 points for them

Watch for

The MCP token holds the website tier with no scopes, and the docs allow it in a ?token= URL parameter

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Chatwoot API +35

Chatwoot API 81

Four OpenAPI 3.1 files in the repo. The Application one has 124 operations (25). llms.txt with about 200 links and Markdown copies of each docs page (10). Every operation has a description, though the API introduction says the reference can trail the real behaviour and suggests reading the web app's own requests (12). 88 enums and typed request bodies in the Application spec (12). 380 examples and 401, 403, 404 and 422 responses in the spec, no 429 (12). Product changelog with dated entries and tagged GitHub releases, but the API itself sits at v1 with no API-specific changelog (10).

Crisp API + MCP 46

No OpenAPI file. The REST reference (updated 25 October 2026) links a Postman collection as a visible download, which we counted as half a contract (10). docs.crisp.chat/llms.txt returns 404 on 5 November 2026 (0). Each route has a description and lists the token tier and scope it needs (12). URI parameters and bodies carry types and required flags, and per_page is bounded 20 to 50 (11). Response schemas are shown, error codes and reasons per route aren't (6). The platform changelog's newest entry is still August 2025, while the SDK changelogs record API changes up to October 2026 (7).

Reliability Chatwoot API +30

Chatwoot API 68

Better Stack status page with 13 components, among them Application (Dashboard & API), and monthly incident history at status.chatwoot.com/incidents (20). In the 90 days to 4 November 2026 the history lists no incident for any component; the last ones were email delivery disruptions on 20 and 26 July and a Meta permissions incident on Instagram, Messenger and WhatsApp that began on 24 July and was resolved on 5 August, all before the window, and the Application bar reads 99.987% for 30 days (30). Rate limits are published only for self-hosted installs (3,000 requests a minute per IP by default, widget routes from 6 requests per 12 hours to 60 an hour), not for Cloud (8, partly met, kept). No documented 429 or Retry-After behaviour and no idempotency guidance (0). No SLA found on any Cloud plan (0). The Application API is GA (10).

Crisp API + MCP 38

status.crisp.chat runs Vigil and on 5 November 2026 shows live state for the API service, the MCP service, hooks and the realtime sockets, but no incident history. We gave 10 of 20 for a component page without history, a partial kept under the in-between rule. No readable history (5). The rate-limit page (updated 21 September 2021) names four limiters (load balancer, global, per route, plugin quota) without numbers, and the authentication page (updated 1 April 2026) gives daily quotas of 10,000 requests for website tokens and 5,000 for plugin tokens, so the per-route limits still carry no numbers and the partial 8 of 15 is kept. 429 and 420 are documented and GET routes are cached with a Bloom-Status header, but there's no Retry-After or backoff guidance, a partial 5 kept. No SLA found (0). REST API v1 is GA (10).

Security & auth Chatwoot API +21

Chatwoot API 52

Per-user access tokens that act with the user's full role, revocable by reset, header only. Bearer auth shipped in v4.19.0 (20 October 2026) and the spec says the api_access_token header will be deprecated in a future release (20). Agent bot tokens can reach only bot-permitted endpoints (show and toggle status or priority, create messages, assignments and labels), which is a usable least-privilege mode. No approval step for writes (10). Conversations carry customer-written text straight to the model and we found no injection guidance (0). Audit logs on Enterprise with an audit_logs API endpoint (10). SECURITY.md routes reports through GitHub advisories and mentions rewards, and Chatwoot has published advisories in public, three of them in 2026 (CVE-2026-44706, CVE-2026-44707, CVE-2026-72719). No security.txt, and the trust centre at trust.chatwoot.com rendered nothing we could read (12).

Crisp API + MCP 31

Website tokens are a Basic auth keypair for one workspace with no scopes. Plugin tokens from the Marketplace pick read or write per scope and can be rolled, which revokes the old one at once. Since 7 October 2026 the MCP quickstart has the agent use an MCP Server token tied to the REST keypair and holding the website tier, sent as a Bearer header or, as a documented option, a ?token= URL parameter. The partial 22 between the two key models is kept, less the fixed 10 for a credential in a URL query string (12). The REST plugin scopes allow a read-only integration and the MCP server applies the REST ACLs, but the MCP guide no longer mentions read-only tokens and sending a message needs no confirmation, so the partial 12 is kept. Conversations carry visitor-written text to the model and we found no injection guidance (0). No operator audit log or per-call log found (0). The docs' Security Practices page (updated 3 May 2026) has a vulnerability disclosure section with an encrypted report address, security@crisp.chat, and no acknowledgement time; no security.txt (404), bug bounty or certification found (7).

Payments & pricing Chatwoot API +15

Chatwoot API 60

No x402, MPP or L402 (0). Cloud prices are public per agent per month, $0, $19, $39 and $99, with Captain AI credits at $20 per 1,000, but nothing per API call (10). Free Hacker plan for 2 agents and 500 conversations a month, and the self-hosted Community Edition is free (20). Cloud needs a person to sign up. On a self-hosted install the Platform API can create accounts, users and tokens with no human step, so we gave half (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Crisp API + MCP 45

No x402, MPP or L402 (0). Plan prices public per workspace, $0, $45, $95 and $295 a month, nothing per call (10). Free plan with 2 seats and Developer APIs, and a 14-day trial of any plan (20). A person signs up in a browser and makes the token (0). The pricing table on 5 November 2026 puts the MCP server on Essentials and Plus only. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightChatwoot APICrisp API + MCPEdge
Reliability16%6838Chatwoot API +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8146Chatwoot API +35
Agent ergonomics13%4751Crisp API + MCP +4
Security & auth14%5231Chatwoot API +21
Payments & pricing10%6045Chatwoot API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7780Crisp API + MCP +3
Transparency & trust7%7877Chatwoot API +1
Negative events≤15-120
TotalD 52.6/100D 48.1/100

Facts side by side

FactChatwoot APICrisp API + MCP
KindHTTP APIHTTP API
VendorChatwootCrisp
Hosted endpointhttps://app.chatwoot.com/api/v1https://api.crisp.chat/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (enterprise directory under a separate licence)none
Tools exposednone41
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-242026-09-14
Terms last updatedno date given2026-07-27
Privacy policy last updatedno date given2026-07-15
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
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
Popularity37k stars112 stars
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Chatwoot API higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Chatwoot API

Chatwoot's MIT-licensed core runs the same Application API on Cloud and self-hosted installs, with 124 operations in a public OpenAPI 3.1 file and five tagged releases since 19 August 2026. User tokens carry the user's full role, Cloud rate limits and 429 behaviour aren't published, and three security fixes from 3 and 4 November are in no release yet.

Crisp API + MCP

Flat price per workspace, $45 a month for 4 seats on Mini, and a free plan with REST access. The MCP server has a published list of 41 tools, but its token holds the website tier with no scopes and can be sent as a URL parameter.

Before you call either

Chatwoot API

  1. Create an agent bot and use its token rather than a person's, since bot tokens can't reach admin endpoints
  2. Post internal notes as messages with private set to true
  3. Send Authorization: Bearer on v4.19.0 and later and the api_access_token header on older self-hosted installs
  4. Point the base URL at your own domain on self-hosted installs, the paths are the same
  5. Treat message content as customer-written text, never as instructions

Crisp API + MCP

  1. Send the MCP Server token as an Authorization: Bearer header, never as the ?token= URL parameter, which ends up in logs
  2. For REST access that shouldn't send messages, use a plugin token with read-only scopes
  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

Questions

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

Chatwoot API scores 52.6 (D) on agent readiness against Crisp API + MCP's 48.1 (D), and leads in 5 of 7 scored categories.

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

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

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

Yes. Chatwoot API has a hosted endpoint at https://app.chatwoot.com/api/v1 and Crisp API + MCP at https://api.crisp.chat/v1.

Are Chatwoot API and Crisp API + MCP open source?

Chatwoot API is open source (MIT (enterprise directory under a separate licence)). No open-source release is listed for Crisp API + MCP.

Other comparisons with Chatwoot API or Crisp API + MCP

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.