# Intercom: L1 · Needs a person

As of 15 Oct 2026, an AI agent can't reliably get into Intercom on its own, but once it is in it does 60% of the core work.

Source: https://agentdrives.com/tools/intercom?via=md · driven 15 Oct 2026 by AgentDrives's agent · Same level in 3 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

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.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- 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)
- Next: let an agent get in on its own in every drive
- With an account set up by a person: not measured yet.
- robots.txt asks crawlers to stay off sign-up and the API. Nothing to fix. It keeps these pages out of search and doesn't stop agents signing up.

## Level history

- 1 Oct 2026: L4 · Runs on its own
- 1 Oct 2026: L1 · Needs a person (sign-up varies)
- 6 Oct 2026: L1 · Needs a person
- 15 Oct 2026: L1 · Needs a person

## Part scores

- Holds up: 74/100
- Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI not found
- Not measured in this drive: Docs match
- Security: reported privately to the owner

## Who gets in

- Agents on a server: Can't get in on their own.
- Signed agents: The sign-up page opens.
- Agents in a person's browser: Not measured yet.

Sign-up page checked 15 Oct 2026. Signed agents: the ones Cloudflare verifies.

## Ways in

- Email and password: Got in, 9 min
- Sign-in for apps (OAuth, MCP): Got in, 4 min

## The docs

600 of 13,299 pages read. Complete.

- A getting-started page
- An auth page
- Errors listed with their codes
- Code examples on most pages
- Newest page updated 15 Oct 2026
- A page for 10 of 10 core tasks

## Tried as documented

3 of 7 documented ways to do the core work worked when tried.

- 4 documented ways didn't work
- 1 thing worked that the docs don't describe

## Checkpoints

- **Docs**: Headless: developers.intercom.com/llms.txt and .md pages, 2.16 API reference with a downloadable OpenAPI 3.0.1 (266 operations), MCP guide.
- **Sign up**: In a browser: Web form at www.intercom.com/signup/email (email, name + password, company, company size) with an invisible reCAPTCHA that let our agent's browser through; starts a 14-day Advanced trial without a card. No sign-up API. The developer sign-up link in the API auth docs (app.intercom.com/admins/sign_up/developer) showed an AWS WAF 'Let's confirm you are human' page instead.
- **Verify**: In a browser: Verification mail from team@intercom.io arrived within a minute; the link logged the browser in.
- **Key**: In a browser: Access token only from the web: Developer Hub > New app > Configure > Authentication (masked, eye button). No API or CLI to create, scope or revoke a token. MCP: OAuth with DCR and two consent pages.
- **First call**: Headless: GET https://api.intercom.io/me with the token, Intercom-Version 2.16: 200.
- **First action**: Headless: POST /contacts and POST /conversations created a contact and a customer conversation, read back with GET.
- **Pay**: In a browser: No 402, x402, MPP or billing API. In-app 'Buy Intercom' opens teams-checkout: Monthly Essential $39/seat/mo, Continue to payment shows a Stripe Elements card form (Google Pay, Stripe invisible hCaptcha), optional Tax ID, last button 'Pay now'. Stopped there: no card.
- **Cancel**: Not needed: Nothing to cancel: our agent started no paid plan.
- **Delete**: In a browser: Settings > Workspace > General > Delete workspace (type your full name, then the workspace name). The page says deletion completes within 14 days; the REST token then answered 401 token_suspended and the MCP token 401. The teammate login still signs in, to a 'Create a new workspace' page; no control to delete the login itself was found.

## Does Intercom have an MCP server, and can an agent connect to it?

Yes. Intercom has an official MCP server. The server lists 15 tools.

A new agent can't reliably get in on its own (drive of 15 Oct 2026). Through the MCP server, 4 of our agent's 5 attempts worked.

## How does an AI agent get an Intercom API key?

In the drive of 15 Oct 2026, our agent got its Intercom API key in a browser, without a person. Access token only from the web: Developer Hub > New app > Configure > Authentication (masked, eye button). No API or CLI to create, scope or revoke a token. MCP: OAuth with DCR and two consent pages.

## Paying the agent way

Reaches the checkout: stopped at the $39 a month charge.

The checkout: Reached the card form and stopped: Essential, $39 a month; Checkout: a Stripe card form; An invisible bot check loaded at checkout; Wallets: Google Pay.

No card needed to start.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
Ways to pay checked 15 Oct 2026.

## What an agent can do

- Create a customer conversation, reply as a teammate, close and delete it through the REST API
- Create, update, resolve, search and delete tickets through the REST API
- Define ticket types and attributes through the REST API (archive, no hard delete)
- Add Fin knowledge (content import sources and external pages) by API and see Fin and Copilot answer from it
- Manage contacts, companies, tags, events, help center articles and collections, news items by API
- Read conversations and contacts and add internal notes or write articles over the official MCP server

## What it cannot do

- Use the Fin Agent API (ask, run a procedure, escalate): 403 api_plan_restricted 'Fin Agent API is not enabled for your app': access is granted on request from Settings, even on the trial
- Get an API token without a browser: tokens exist only in the Developer Hub web UI or through an OAuth install; no token API
- Place or answer phone calls: the API only lists and searches calls; calls need a phone number in the Inbox
- Set a Workflow live or chat through the Messenger: Set live waits for the Messenger install; our Messenger test page did not boot the widget
- Send a reply from MCP: the MCP server has no reply tool, only internal notes

## Tips for the owner

1. Open the Fin Agent API to trial workspaces
2. Add a token API or device login
3. Fix MCP token revocation
4. Support MCP (the 28 Jul 2026 spec) server/discover
5. Let agents pay without a card form
6. Add a reply tool to the MCP server

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in Customer support

- [Chatwoot](https://agentdrives.com/tools/chatwoot.md?via=md): L1 · Needs a person · [Intercom vs Chatwoot](https://agentdrives.com/compare/chatwoot-vs-intercom?via=md)
- [Crisp](https://agentdrives.com/tools/crisp.md?via=md): L1 · Needs a person · [Intercom vs Crisp](https://agentdrives.com/compare/crisp-vs-intercom?via=md)
- [Freshdesk](https://agentdrives.com/tools/freshdesk.md?via=md): L1 · Needs a person · [Intercom vs Freshdesk](https://agentdrives.com/compare/freshdesk-vs-intercom?via=md)
- [Front](https://agentdrives.com/tools/front.md?via=md): L1 · Needs a person · [Intercom vs Front](https://agentdrives.com/compare/front-vs-intercom?via=md)
- [Gorgias](https://agentdrives.com/tools/gorgias.md?via=md): L1 · Needs a person · [Intercom vs Gorgias](https://agentdrives.com/compare/gorgias-vs-intercom?via=md)
- [Help Scout](https://agentdrives.com/tools/helpscout.md?via=md): L1 · Needs a person · [Intercom vs Help Scout](https://agentdrives.com/compare/helpscout-vs-intercom?via=md)
- [Plain](https://agentdrives.com/tools/plain.md?via=md): L1 · Needs a person · [Intercom vs Plain](https://agentdrives.com/compare/intercom-vs-plain?via=md)
- [tawk.to](https://agentdrives.com/tools/tawk.md?via=md): L1 · Needs a person · [Intercom vs tawk.to](https://agentdrives.com/compare/intercom-vs-tawk?via=md)
- [Zendesk](https://agentdrives.com/tools/zendesk.md?via=md): L1 · Needs a person · [Intercom vs Zendesk](https://agentdrives.com/compare/intercom-vs-zendesk?via=md)

## Tips for agent builders

- Send Intercom-Version: 2.16; errors come as error.list with a code and message, not problem+json.
- Ticket list attributes take list_items as a comma string; a list_options object gets a vague 400.
- A contact's company link can read empty right after attaching; read again a moment later.
- There is no idempotency key: a repeated POST /tickets makes a second ticket.
- MCP update_article wants the id as a string.
- The sign-up wizard keeps its state in the page: do it in one browser session.