Crisp vs Zendesk for AI agents
As of 6 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Crisp it was stopped at sign up (needs a human), with Zendesk it was stopped at sign up (blocked).
- 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.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person to sign up: L1 · Needs a person. Our agent stopped at workspace sign-up, where a visible hCaptcha puzzle blocks the only form for creating an account. The documented API has no account-creation route. It read the REST API, website and plugin token guides, and the MCP server quickstart without logging in. It then got a plugin development token through a separate Marketplace flow and called the live API with it, but that call returned no workspace data: every working token, including the Website Token and MCP Server token, is issued inside the workspace dashboard. No plan was reachable, so paying and cancelling a workspace were never reached; only the separate Marketplace account was deleted, in the browser.
Driven 6 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent sign up on its own
Needs a person to sign up: L1 · Needs a person. Our agent stopped at the trial form, which demands a phone number its identity doesn't have; the reseller accounts API is the only other path in, and it needs a reseller-only token plus a phone too. No bot check appeared. Discovery is decent: a full OpenAPI reference and an official per-account MCP server with a server card, though still on the older MCP spec with DCR-only OAuth. Buy-now links lead back to the same phone-gated form, so paying needs a person as well.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
CrispStopped at sign up: needs a human
ZendeskStopped at sign up: blocked
| Checkpoint | Crisp | Zendesk |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Blocked |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Headless | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Crisp | Zendesk | |
|---|---|---|
| Headless (checkpoints) | 2 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 6 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | Yes | No |
| llms.txt | No | Yes |
Bot checks, and where a person was needed.
| Crisp | Zendesk | |
|---|---|---|
| Bot check | hCaptcha stopped it at sign up, with a visible challenge | None met |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | hCaptcha puzzle on the workspace sign-up form | Phone number required on trial sign-up |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Crisp | Zendesk | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 55 of 100, fair | 100 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) | MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Crisp | Zendesk | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Crisp: Payment not reached.
- Zendesk: Payment not reached.
Crisp vs Zendesk: the short answers.
Which can an AI agent use, Crisp or Zendesk?
Both reach L1 · Needs a person, and our agent got as far with each: with Crisp it was stopped at sign up (needs a human), with Zendesk it was stopped at sign up (blocked). Both driven 6 Oct 2026.
Can an AI agent sign up for Crisp and Zendesk on its own?
Crisp: no, needs a human. Zendesk: no, blocked.
Do Crisp and Zendesk have an MCP server?
Crisp: yes (official). Zendesk: yes (official).
Can an AI agent delete its Crisp or Zendesk account?
Crisp: not reached. Zendesk: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.