Chatwoot vs Intercom for AI agents
As of 15 Oct 2026, both reach L1 · Needs a person. Our agent got further with Intercom: with Intercom it got in and did 60% of the work, with Chatwoot it was stopped at sign up (needs a human).
- Find: Some docs for agents: llms.txt and an OpenAPI.
- 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 today: L1 · Needs a person. Our agent stopped right at the form: Create account led to a visible hCaptcha puzzle asking to drag a screw into place, and it got no further, so no account, token or verification mail followed. Chatwoot's developer docs are strong: llms.txt, Markdown pages, an OpenAPI spec, an official CLI with an agent skill, and a docs MCP server. None of that reached first action, since no credentials ever came through. Paying, cancelling and deleting the account were never reached: the human gate at sign-up stopped the drive before checkout or billing opened up.
Driven 6 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: Signs up sometimes.
- Use: 60% of the work.
- Pay: Reaches the checkout: Stopped at the $39 a month charge.
- Leave: Nothing to cancel: Deletes its data, but the login stays.
In; 60% of the work done. Next: let an agent get in on its own in every drive
Needs a person opens Intercom: the sign-up form and developer sign-up link need a browser, and the access token only comes from the Developer Hub web page, so our agent could not get in on its own. Past that, headless calls ran the helpdesk cleanly: contacts, conversations, tickets, ticket types and articles all worked by API, and Fin and Copilot answered from content our agent added. The Fin Agent API refused the trial, saying it is "not enabled for your app." Buying runs through a Stripe card form; our agent stopped there with no card, then deleted the workspace from Settings, though the teammate login itself had no delete control our agent could find.
Gets furtherDriven 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.
ChatwootStopped at sign up: needs a human
IntercomIn; 60% of the work done
| Checkpoint | Chatwoot | Intercom |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| Verify | Not reached | In a browser |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | In a browser |
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
| Chatwoot | Intercom | |
|---|---|---|
| Headless (checkpoints) | 1 | 3 |
| In a browser (checkpoints) | 0 | 5 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 60% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | No | Yes (official) |
| CLI | Yes | No |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Chatwoot | Intercom | |
|---|---|---|
| Bot check | hCaptcha stopped it at sign up, with a visible challenge | Google reCAPTCHA (invisible) on the sign-up form let it through at sign up |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | Visible hCaptcha puzzle on the sign-up form | None |
| 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.
| Chatwoot | Intercom | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Holds up | Not measured | 74 of 100, fair |
| Agent-ready setup | 85 of 100, fair | 100 of 100, good |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · OpenAPI 3.1.0 (1 version behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.0.1 (2 versions behind) |
| Security | No review in this drive | Reported privately to the owner |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Chatwoot | Intercom | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Chatwoot: Payment not reached.
- Intercom: Reaches the checkout: stopped at the $39 a month charge.
Chatwoot vs Intercom: the short answers.
Which can an AI agent use, Chatwoot or Intercom?
Both reach L1 · Needs a person. Our agent got further with Intercom: with Intercom it got in and did 60% of the work, with Chatwoot it was stopped at sign up (needs a human). Driven 6 Oct 2026 (Chatwoot) and 15 Oct 2026 (Intercom).
Can an AI agent sign up for Chatwoot and Intercom on its own?
Chatwoot: no, needs a human. Intercom: yes, in a browser, but a later step stopped it.
Do Chatwoot and Intercom have an MCP server?
Chatwoot: none found. Intercom: yes (official).
Can an AI agent delete its Chatwoot or Intercom account?
Chatwoot: not reached. Intercom: yes, in a browser.
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.