Intercom vs Zendesk 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 Zendesk it was stopped at sign up (blocked).
- 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 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.
IntercomIn; 60% of the work done
ZendeskStopped at sign up: blocked
| Checkpoint | Intercom | Zendesk |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Blocked |
| Verify | In a browser | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | In a browser | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | 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
| Intercom | Zendesk | |
|---|---|---|
| Headless (checkpoints) | 3 | 1 |
| In a browser (checkpoints) | 5 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 60% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Intercom | Zendesk | |
|---|---|---|
| Bot check | Google reCAPTCHA (invisible) on the sign-up form let it through at sign up | None met |
| Wall type | No bot-check wall | No bot-check wall |
| First wall | None | Phone number required on trial sign-up |
| A person helped | No | No |
Level and part scores.
| Intercom | Zendesk | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Holds up | 74 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 100 of 100, good |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.0.1 (2 versions behind) | MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) |
| Security | Reported privately to the owner | No review in this drive |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Intercom | Zendesk | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- Intercom: Reaches the checkout: stopped at the $39 a month charge.
- Zendesk: Payment not reached.
Intercom vs Zendesk: the short answers.
Which can an AI agent use, Intercom or Zendesk?
Both reach L1 · Needs a person. Our agent got further with Intercom: with Intercom it got in and did 60% of the work, with Zendesk it was stopped at sign up (blocked). Driven 15 Oct 2026 (Intercom) and 6 Oct 2026 (Zendesk).
Can an AI agent sign up for Intercom and Zendesk on its own?
Intercom: yes, in a browser, but a later step stopped it. Zendesk: no, blocked.
Do Intercom and Zendesk have an MCP server?
Intercom: yes (official). Zendesk: yes (official).
Can an AI agent delete its Intercom or Zendesk account?
Intercom: yes, in a browser. 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.