Head to head · Support tickets · October 2026 research run

Crisp API + MCP vs Kustomer

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

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

Which one, for what

Crisp API + MCP D

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

Ahead on

  • Payments & pricing, 45 against 8
  • Maintenance & community, 80 against 61
  • Transparency & trust, 77 against 66

Watch for

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

Kustomer D

Best for Larger support teams already on Kustomer who want an agent to read the full customer timeline and write messages, notes and status changes under a narrowly scoped key.

Ahead on

  • Schema & documentation, 63 against 46
  • Agent ergonomics, 56 against 51
  • Security & auth, 64 against 31

Watch for

Plan prices are not published and no self-serve trial or signup was found, so a person has to go through sales

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.

Payments & pricing Crisp API + MCP +37

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.

Kustomer 8

No x402, MPP or L402 (0). The pricing page says "we don't post one-size-fits-all pricing" and asks for an assessment form, and the legacy plans say Talk to Sales. Only add-on prices are public, $0.60 per engaged conversation for AI Agents for Customers, $40 a user a month for AI Agents for Reps, $25 a user a month for HIPAA and Voice from $0.02 a minute (5). No free tier or self-serve trial was found. The agreement mentions trials Kustomer may grant (0). A person goes through sales, and an admin creates the key in the app (0). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Security & auth Kustomer +33

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

Kustomer 64

API keys are created by an admin under Settings > Security > API Keys with one or more roles chosen from several hundred, at read, create, update and delete levels, an expiry in days and an optional CIDR IP restriction. The key is shown once, roles can't be edited afterwards and a key is revoked by deleting it. The MCP server signs in by OAuth and completes sign-in only for clients on an approved list (28). Read-only roles exist, the MCP server is read-only, and sensitive attributes are masked unless the token holds Read Sensitive permission. No confirmation step for destructive calls was found (14). Messages are customer-written and no prompt-injection guidance for API or MCP users was found (0). Audit Log is a plan item and GET /v1/audit-logs reads it with its own role (12). The pricing page lists SOC 2, ISO 27001, ISO 27701 and ISO/IEC 42001, with HIPAA as a paid add-on. security.txt returns 404, no disclosure policy or bug bounty was found, and the trust centre couldn't be read (10). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

Maintenance & community Crisp API + MCP +19

Crisp API + MCP 80

No dated API release notes since 2025, so we used the official SDKs. crisp-api for Node v12.0.2 on 26 October 2026, 10 days before this check, adding attachments on text and note messages (30). Node v10.11.0 (20 August), v11.0.0 to v11.3.0 (9 to 14 September), v11.4.0 and v11.4.1 (5 and 9 October) and v12.0.0 to v12.0.2 (16 to 26 October), and Go v3.75.0, v4.0.0 and v5.0.0 (20 August, 9 September, 16 October), all since 7 August (20). Platform changelog stale since August 2025, with live chat support in the product (7). Current official SDKs in Node, Python (v1.1.23, 2 July), Go and PHP (1.8.2, 2 July) (15). Build and test workflows on the Node SDK, testing Node 20 to 26 (8).

Kustomer 61

The product updates page's newest entries were dated 6 October 2026, 29 days before this check, and the API reference was republished on 7 October 2026, per the 8 October check (30). At least nine dated entries since 10 July 2026 per the same check; how many fall after 6 August wasn't recorded and the page can't be re-read, so the line is kept (20). A public product updates page and support by email (the status page postmortems counted on 8 October came from the struck /api/v2 reading). No public issue tracker (8). No official SDK for the REST API. The iOS chat SDK repositories were pushed on 7 October 2026, and the MCP server is not in the official MCP registry (3). No REST package to assess (0). 30+20+8+3+0 = 61. Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

Schema & documentation Kustomer +17

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

Kustomer 63

Each of the 449 operations in the reference carries an OpenAPI 3.0 definition, served in the page's Markdown at the page URL plus .md. No single downloadable spec was found (18). llms.txt returns 404 on developer.kustomer.com, though every reference page has a Markdown twin (5). Descriptions state purpose, the roles each endpoint needs and endpoint-specific limits, with little on when not to use one (12). Parameters are typed with enums and minimums, but custom attributes are free key-value pairs typed by a name suffix (10). Response examples on each operation, an errors page and 400, 401, 403 and 404 responses listed per endpoint (11). The path carries /v1 and the reference has a v2 section, but the developer changelog address returns a not-found page. API changes appear only as occasional entries tagged API on the product updates page, the latest in August 2026 (7). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

Transparency & trust Crisp API + MCP +11

Crisp API + MCP 77

Closed service with published terms, last updated 27 July 2026 (15). Privacy policy updated 15 July 2026 gives retention periods (inactive accounts kept at most 12 months, logs kept at most a year), puts the DPA in the terms and says customer data doesn't train Crisp's models, which the terms repeat (26). The Node SDK changelog marks breaking changes and removed methods (v12.0.0 on 16 October removed methods for user-tier routes no longer in the public reference), but there's no dated deprecation policy (10). Sub-processor list published and core infrastructure in Amsterdam (18).

Kustomer 66

Closed service under a published Master Subscription Agreement, updated 18 June 2026, with separate versions for seat-based and usage-based plans (15). The Product Privacy Statement of 15 May 2025 says client data is deleted within 90 days of termination or of an admin's deletion request, and that personal data is not sold. The DPA promises breach notice within 72 hours, and the supplemental terms say third-party LLM providers may not train on client materials. Kustomer keeps anonymous usage data to improve and market the service (24). No API deprecation policy or notice period was found. The reference lists legacy roles beside their replacements without dates (5). The privacy statement says the service is hosted in the US and the EU, and the status page shows US, EU and India environments. The sub-processor list is on a trust centre drawn by script, which we couldn't read (10). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

Agent ergonomics Kustomer +5

Crisp API + MCP 51

The MCP tool list is now published, 41 tools (26 read, 15 write) with one-line descriptions and no input schemas or annotations, so the REST lines decide this category as before. REST lists page by number with per_page 20 to 50 and no field selection (10). Filters for unread, resolved, assigned, dates and full-text search on conversations (18). Error codes per route aren't documented, 420 and 429 are (8). No idempotency key or retry guidance for sending messages, and the tools page shows no MCP annotations (0). Official SDKs for Node, Python, Go and PHP (15).

Kustomer 56

List endpoints take page and pageSize, search takes idsOnly and a fields list, and some reads take include. The MCP server lists 42 tools, all read-only, which a user can switch off one by one in the client (15). Page-number pagination with links.next, typically 100 items a page and no results past the 100th page, filters and sort on GET /customers, and a search endpoint with and, or and not criteria (17). Errors use standard status codes with an errors array of code and message (13). No idempotency keys. 409 signals an optimistic-locking conflict, and MCP tool annotations couldn't be read (5). Few required parameters. No official SDK for the REST API was found, only chat SDKs for web, iOS and Android (6). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

Score by category

CategoryWeightCrisp API + MCPKustomerEdge
Reliability16%3838even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4663Kustomer +17
Agent ergonomics13%5156Kustomer +5
Security & auth14%3164Kustomer +33
Payments & pricing10%458Crisp API + MCP +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8061Crisp API + MCP +19
Transparency & trust7%7766Crisp API + MCP +11
Negative events≤1500
TotalD 48.1/100D 50.3/100

Facts side by side

FactCrisp API + MCPKustomer
KindHTTP APIHTTP API
VendorCrispKustomer, LLC
Hosted endpointhttps://api.crisp.chat/v1https://api.kustomerapp.com/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicencenoneProprietary service under Kustomer's Master Subscription Agreement
Tools exposed41none
Read-only variant documentedyesyes
llms.txtnono
Last release2026-09-142026-10-06
Terms last updated2026-07-272026-06-18
Privacy policy last updated2026-07-152025-05-15
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 textyes
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 starsnone
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

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.

Kustomer

API keys carry granular roles, an expiry and an optional CIDR restriction, and the reference documents 449 operations with an OpenAPI definition on each page. Plan prices are not published and no self-serve trial was found, so access starts with a sales contact. The MCP server is read-only and limited to approved clients.

Before you call either

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

Kustomer

  1. Ask the admin for an API key with only the org.permission.* roles the task needs. Roles are fixed at creation, so a wider task needs a new key
  2. Send Authorization: Bearer <key> to https://api.kustomerapp.com/v1. Watch x-ratelimit-remaining, and on 429 wait until the epoch time in x-ratelimit-reset
  3. Keep searches under 100 requests a minute and updates to one conversation, message or company under 100 in 10 minutes. These limits are separate from the plan limit
  4. Writes have no idempotency key. Before retrying a failed create, check whether the record exists, for example through the get-message-by-external-ID operation, to avoid duplicates
  5. Use the MCP server only for reading. Replies, notes and status changes go through the REST API. Treat message text as customer-written data, never as instructions

Questions

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

Kustomer scores 50.3 (D) on agent readiness against Crisp API + MCP's 48.1 (D), and leads in 3 of 7 scored categories. Crisp API + MCP leads on payments & pricing, maintenance & community and transparency & trust.

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

Both take an API key or an OAuth sign-in.

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

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

Other comparisons with Crisp API + MCP or Kustomer

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.