Front 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 Front it was stopped at sign up (needs a human).
- 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: needs a human. Next: let an agent sign up on its own
L1 · Needs a person: front.com/signup requires a phone number our agent didn't have, so it stopped there. No CAPTCHA blocked it; the form itself did. Docs are strong for an agent: llms.txt, Markdown pages, an OpenAPI spec and an official MCP server. But tokens and MCP OAuth clients are only made by an admin inside an account, with no sign-up API, no DCR and no device flow. With no account, no call, no core work and no purchase were reached: Front never let our agent past the door.
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.
FrontStopped at sign up: needs a human
IntercomIn; 60% of the work done
| Checkpoint | Front | 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
| Front | 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 | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Front | Intercom | |
|---|---|---|
| Bot check | None met | Google reCAPTCHA (invisible) on the sign-up form let it through at sign up |
| Wall type | No bot-check wall | No bot-check wall |
| First wall | Phone number required on trial sign-up form | None |
| A person helped | No | No |
Level and part scores.
| Front | Intercom | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Holds up | Not measured | 74 of 100, fair |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | OpenAPI 3.0.0 (2 versions 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.
| Front | Intercom | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Front: Payment not reached.
- Intercom: Reaches the checkout: stopped at the $39 a month charge.
Front vs Intercom: the short answers.
Which can an AI agent use, Front 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 Front it was stopped at sign up (needs a human). Driven 6 Oct 2026 (Front) and 15 Oct 2026 (Intercom).
Can an AI agent sign up for Front and Intercom on its own?
Front: no, needs a human. Intercom: yes, in a browser, but a later step stopped it.
Do Front and Intercom have an MCP server?
Front: yes (official). Intercom: yes (official).
Can an AI agent delete its Front or Intercom account?
Front: 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.