Crispcrisp.chat

Can an AI agent use Crisp (crisp.chat)?

As of 6 Oct 2026, an AI agent can't use Crisp on its own: hCaptcha puzzle on the workspace sign-up form.

Level 1 · Needs a personAgents can't get in on their own.

Find: Some docs for agents: An MCP server.
Access: Can't sign up.
Use: Work not reached.
Pay: Payment not reached.
Leave: Leaving not reached.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean

Visit Crisp Follow changes

Driven 6 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

Agents on a serverStopped by a CAPTCHA on the sign-up form.
Signed agentsThe sign-up page opens. The CAPTCHA on the form stops them too.
Agents in a person's browserNot measured yet.

Sign-up page checked 13 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Crisp (crisp.chat).

On its own

Read all the product's documentation and API reference without logging in
See the list of available automation tools without a workspace
Sign up for a separate 'developer' account (for building plugins) and later delete it, but this account cannot use the actual chat product

What it can't, and why

Create a usable Crisp account/workspaceThe sign-up form shows an image puzzle (CAPTCHA) only a person can solve
Get a working access key for the chat productKeys are only issued inside the workspace, which could not be created
Use any real feature: chatting, replying, managing contacts, publishing help articlesAll of these need a workspace, which the sign-up puzzle blocked

Needs a person

No. Sign-up: needs a human. Workspace sign-up exists only as a web form (app.crisp.chat/initiate/signup); on submit it shows a visible hCaptcha image puzzle. The documented API has no account-creation route. (A separate Marketplace developer account signed up in the browser without a CAPTCHA, but it cannot log in to the Crisp app.)

Official server · 2 of 6 calls worked

Does Crisp (crisp.chat) have an MCP server, and can an agent connect to it?

Yes. Crisp has an official MCP server. The server lists 27 tools and speaks the older 25 Nov 2025 MCP spec.

A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 2 of our agent's 6 attempts worked.

What the drive found

API–OpenAPIMCP · official–CLISDK–llms.txtWebhooks–Sandbox

Not reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail

For the team behind Crisp.

Where agents stop in Crisp (crisp.chat) today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

Let verified signed agents skip the sign-up hCaptchaStep-by-step guide
Add a headless way to create a workspace tokenStep-by-step guide
Support MCP (the 28 Jul 2026 spec) server/discover

1 more fix

Publish OpenAPI and llms.txt for the REST API Step-by-step guide

Claim it free and reply next to the result.
A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

Get a Drive Claim it free

See the example report

Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

<a href="https://agentdrives.com/tools/crisp" rel="nofollow"><img src="https://agentdrives.com/badge/crisp.svg" alt="AgentDrives · Driven · L1 · Needs a person" height="24"></a>

Behind the level.

Our agent couldn't get into Crisp (crisp.chat), so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

llms.txt: not found
OpenAPI: not found
MCP server: found
CLI: not found

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

1 Oct 2026L1Needs a person
6 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 25 attempts.

How an agent connects · 4 tips

/api/tools/crisp.json /tools/crisp.mdMCP get_tool {"slug":"crisp"}

You need a human to create the Crisp workspace (hCaptcha) and generate the Website/MCP token under Settings > Workspace Settings > Advanced configuration; after that everything is headless.
MCP at https://api.crisp.chat/mcp/ speaks 2025-11-25 only: use initialize, Bearer token. No send-message tool: use REST POST /v1/website/{id}/conversation/{session}/message for replies.
REST auth: Basic token_id:token_key plus X-Crisp-Tier: website (or plugin). Errors are JSON {error, reason, data.message} and name the problem (e.g. restricted_route_tier).
A Marketplace account is separate from a Crisp account; its dev token only works on a trusted workspace you already own.

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessdocs.crisp.chat: REST API v1 reference, website/plugin token guides, MCP server quickstart, five official API libraries; fetched without login.
Sign upNeeds a humanWorkspace sign-up exists only as a web form (app.crisp.chat/initiate/signup); on submit it shows a visible hCaptcha image puzzle. The documented API has no account-creation route. (A separate Marketplace developer account signed up in the browser without a CAPTCHA, but it cannot log in to the Crisp app.)
VerifyNot reachedNever reached: no workspace account was created.
KeyNot reachedWebsite Token and MCP Server token are generated in the Crisp app (Settings > Workspace Settings > Advanced configuration), which needs a workspace. A Marketplace plugin development token was obtained in the browser, but it 'will not be usable until you link a trusted workspace' (a Website ID).
First callHeadlessGET /v1/plugin/connect/websites/all/1 with the plugin dev token (the token itself was obtained via a browser Marketplace flow) -> 200 {error:false, reason:listed, data:[]}. The call itself was made through the documented API, not a browser. No workspace data reachable.
First actionNot reachedNothing can be created without a workspace token.
PayNot reachedNo x402/MPP/L402/UCP/ACP anywhere (subdomains do not resolve, well-knowns 404, not in x402 Bazaar, mpp.dev or projects.dev). Free plan plus a 14-day trial 'No card required'. Billing routes in the API (POST/DELETE /v1/plans/subscription/{website_id}) are 'user' tier only, which documented token types cannot use. Checkout not observed; a human is needed before any purchase because sign-up is behind hCaptcha.
CancelNot reachedNo plan was started. The API's DELETE /v1/plans/subscription/{website_id} is 'user' tier only.
DeleteNot reachedNo Crisp workspace was ever created, so there was no product account/workspace to delete. Only the separate Marketplace developer account and its plugin (not the Crisp product itself) were deleted in the browser (typed name + password); the dev token then returned 401 invalid_session. Workspace deletion in the API (DELETE /v1/website/{website_id}) is 'user' tier only and was never reachable.

The attempt log · 25 attempts

Attempt log
Capability	Route	Result	Evidence
MCP server/discover: POST server/discover to https://api.crisp.chat/mcp/ with 2026-07-28	mcp	done ✓	HTTP 400 application/json, JSON-RPC -32000 'Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)' -> legacy server
Agent cards / well-known: Probe ai-catalog, agent-card, agent.json, mcp server-card, oauth-protected-resource, oauth-authorization-server, ucp, auth.md, SKILL.md on crisp.chat, api.crisp.chat, docs.crisp.chat; /mcp/server-card	none	done ✓	All absent: api.crisp.chat 404 JSON; crisp.chat 301 -> /en/... 404 HTML; docs.crisp.chat 403/404 HTML; api.crisp.chat/mcp/server-card 406 'Client must accept text/event-stream'
llms.txt / markdown / aipref: crisp.chat/llms.txt, docs.crisp.chat/llms.txt, Accept: text/markdown on docs page, .md URL, robots.txt Content-Usage	none	done ✓	llms.txt 404 on both hosts; Accept text/markdown -> text/html, Vary: Accept-Encoding only; .md URL 404; robots.txt 'User-agent: * Allow: /' + Disallows, no Content-Usage/Content-signal; no Content-Usage header
MCP initialize fallback + tools/list: initialize offering 2026-07-28, then tools/list (no auth)	mcp	done ✓	initialize -> protocolVersion 2025-11-25, serverInfo crisp-mcp/api 2.0.0 'Crisp MCP', SSE reply, no Mcp-Session-Id; tools/list without auth -> 27 tools
Sign up: Create Crisp account: documented REST API has no account-creation route (POST /v1/website is user tier, needs an existing user); web form at app.crisp.chat/initiate/signup/	browser	blocked	Filled first/last name, email the agent's inbox, password, accepted Terms, clicked Continue -> hCaptcha image puzzle 'Click the flower the bee never lands on' (screenshot browser/shots/004.png, visible_challenge true)
Sign up: Ask a human to solve the hCaptcha (live handoff)	browser	blocked
Sign up (Marketplace developer account): Sign up at marketplace.crisp.chat (the documented route to plugin tokens)	browser	done ✓	Form first/last name, email, password, company, terms -> 'Welcome on Crisp Marketplace, AgentDrives. Go to your dashboard now!' (shots/010.png); no CAPTCHA shown
Log in to Crisp app with the Marketplace account: Login at app.crisp.chat/initiate/login with the Marketplace credentials	browser	failed ✓	Both fields marked red, stays on /initiate/login/ (shots/012.png): Marketplace and Crisp app accounts are separate
Get API credentials (plugin development token): Marketplace > New Plugin (private) > Tokens: development token keypair	browser	partial ✓	Plugin 8d7d30b7-… created; Tokens page shows Identifier/Key/Signing Secret (saved to secrets.env) and 'The development token will not be usable until you link a trusted workspace.' Limit 500 req/24h.
First authenticated API call: GET https://api.crisp.chat/v1/plugin/connect/websites/all/1 with plugin dev token (Basic, X-Crisp-Tier: plugin)	api	done ✓	HTTP 200 application/json {"error":false,"reason":"listed","data":[]} (no workspaces connected)
Link a trusted workspace for the dev token: Marketplace Settings > Add Trusted Workspace	browser	blocked ✓	Dialog: 'Please fill your Website ID. You can find it in the Crisp app: Settings > Workspace Settings > Setup & Integrations > Website ID.' We have no workspace: Crisp app sign-up is behind a visible hCaptcha.
Chat with visitors/customers in a shared omnichannel inbox: Drive via mcp (GET/POST /v1/website/{website_id}/conversations/{page_number})	mcp	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Send a message in a conversation (text, file, note, etc.): Drive via api (POST /v1/website/{website_id}/conversation/{session_id}/message)	api	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Resolve / change state of a conversation (pending, unresolved, resolved): Drive via mcp (PATCH /v1/website/{website_id}/conversation/{session_id}/state)	mcp	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Assign a conversation to a teammate / route via rules: Drive via api (PATCH /v1/website/{website_id}/conversation/{session_id}/assign)	api	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Install a website/app chat widget to talk to visitors in real time: Drive via none (UI only)	none	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Build and publish a no-code chatbot/AI Agent workflow across channels: Drive via none (UI only)	none	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Train the AI agent on data sources (website crawl, Knowledge Base, file import, Q&A snippets, conversation history): Drive via none (UI only)	none	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Get AI co-pilot suggested replies / predict, transcribe, translate, summarize, categorize, rephrase during a conversation: Drive via none (UI only)	none	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
View and edit a unified customer profile (contact data, custom data, segments): Drive via mcp (GET/PATCH /v1/website/{website_id}/people/profile/{people_id})	mcp	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Create, edit and publish a help center article: Drive via mcp (POST/PUT /v1/website/{website_id}/helpdesk/locale/{locale}/article)	mcp	blocked	No Crisp workspace: app sign-up stopped at a visible hCaptcha image puzzle; plugin dev token returns only an empty website list
Delete created resources (Marketplace plugin): Marketplace plugin Settings > Danger Zone > Delete Plugin (type name + password)	browser	done ✓	'Plugin deleted', dashboard shows 0 plugins; dev token now 401 {reason: invalid_session}
Delete the Marketplace account: Marketplace Account > Danger Zone > Delete My Account (confirm + password)	browser	done ✓	Toast 'Your user account has been successfully removed.' (shots/045.png); re-login -> 'Your credentials are invalid. Please retry.'
Agent purchase rails: Probe x402./mpp./agents.crisp.chat, /.well-known/ucp, oauth metadata, auth.md, x402 Bazaar, mpp.dev services, projects.dev, pricing page, API billing routes	api	done ✓	x402/mpp/agents subdomains: no DNS answer (curl 000); /.well-known/ucp 404 on all hosts; Bazaar, mpp.dev, projects.dev: no 'crisp' entry; pricing page: Free plan 'Free Forever', Mini $45, Essentials $95 /month per workspace, 'Start my trial for free', '14 days free trial, All Crisp features, No card required'; no x402/402/MPP/agentic text. API reference has POST/DELETE /v1/plans/subscription/{website_id} with 'Tiers user' only.
Find API docs: Fetch docs.crisp.chat REST API v1 reference, auth guides, MCP server guides	api	done ✓	REST API v1 reference (HTML, ~227 documented method+path pairs), auth guide (website token, plugin token), MCP quickstart: https://api.crisp.chat/mcp/ Streamable HTTP, Bearer token from Settings > Workspace Settings > Advanced configuration; SDKs node/go/php/python/ruby; no OpenAPI file found, no llms.txt

Also in Customer support.

All of Customer support, by level

IntercomL1Can't get in on its ownCrisp vs Intercom
ChatwootL1Can't sign up on its ownCrisp vs Chatwoot
FreshdeskL1Can't sign up on its ownCrisp vs Freshdesk
FrontL1Can't sign up on its ownCrisp vs Front