Crisp vs Help Scout for AI agents
As of 15 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 Help Scout 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; a docs page for each core task.
- 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 before an agent can do anything: L1 · Needs a person. Our agent signed up with an email and no bot check appeared, but Help Scout then asked for an SMS code to a phone number before the account exists, and stopped there. With no account, there was no OAuth app, no Docs API key, no call to the Inbox API and no MCP connection, since all of them sit behind that same phone step. Paying, canceling and deleting wait on the same account, so none were reached either. The docs and the MCP server's OAuth metadata read fine without a browser, so an agent can study Help Scout before it ever tries to sign up.
Driven 15 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
Help ScoutStopped at sign up: blocked
| Checkpoint | Crisp | Help Scout |
|---|---|---|
| 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 | Help Scout | |
|---|---|---|
| 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 | No |
| MCP server | Yes (official) | – |
| CLI | No | No |
| SDK | Yes | Yes |
| llms.txt | No | Yes |
Bot checks, and where a person was needed.
| Crisp | Help Scout | |
|---|---|---|
| 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 SMS verification at 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 | Help Scout | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 55 of 100, fair | 75 of 100, fair |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) | MCP client registration (behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Crisp | Help Scout | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Crisp: Payment not reached.
- Help Scout: Payment not reached.
Crisp vs Help Scout: the short answers.
Which can an AI agent use, Crisp or Help Scout?
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 Help Scout it was stopped at sign up (blocked). Driven 6 Oct 2026 (Crisp) and 15 Oct 2026 (Help Scout).
Can an AI agent sign up for Crisp and Help Scout on its own?
Crisp: no, needs a human. Help Scout: no, blocked.
Do Crisp and Help Scout have an MCP server?
Crisp: yes (official). Help Scout: none found.
Can an AI agent delete its Crisp or Help Scout account?
Crisp: not reached. Help Scout: 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.