# Best customer support and helpdesk APIs for AI agents

> Intercom API + MCP (BB), Zendesk Support API (B) and Zoho Desk (B) lead the 18 ranked customer support and helpdesk APIs. Picks by need, strengths, weaknesses and prices from the Anchor benchmark.

- Canonical: https://www.anchorterminal.com/best/support/
- Markdown: https://www.anchorterminal.com/best/support/index.md (~5,550 tokens)
- Slim: https://www.anchorterminal.com/best/support/index.min.md (~1,480 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/best/support/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

The 10 highest-scoring of 18 customer support and helpdesk APIs on the Anchor benchmark, with a pick for each need and where each one falls short. Scores come from public evidence, re-checked as vendors change.

- Ranked: 18 · agent-ready (BB or better): 1 · accept x402: 0 · hosted endpoints: 15
- Full ranked table: https://www.anchorterminal.com/categories/support.md
- Head-to-head comparisons: https://www.anchorterminal.com/compare/support/index.md (153)
- Methodology: https://www.anchorterminal.com/benchmark/index.md

## The shortlist

| # | Tool | Grade | Score | Best for | Price | Where |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | [Intercom API + MCP](https://www.anchorterminal.com/tools/intercom.md) | BB | 71.5 | Teams on Intercom who want an agent to research conversations and leave internal notes without any chance of messaging a customer. | $29 / seat-mo | hosted |
| 2 | [Zendesk Support API](https://www.anchorterminal.com/tools/zendesk.md) | B | 68.7 | Larger support teams that want an agent to work tickets through a mature REST API with real audit trails. | $19 / seat-mo | local |
| 3 | [Zoho Desk](https://www.anchorterminal.com/tools/zoho-desk.md) | B | 66.6 | Teams already on Zoho who want an agent to read tickets, draft replies for review, add private comments and change status with narrow scopes, and small teams that want a free edition with API access. | $7 / seat-mo | local |
| 4 | [Plain API + MCP](https://www.anchorterminal.com/tools/plain.md) | B | 65.5 | B2B teams that want an API-first helpdesk where an agent can do everything a person can, with scoped machine keys. | $35 / mo | hosted |
| 5 | [Front API + MCP](https://www.anchorterminal.com/tools/front.md) | B | 63.6 | Teams on Front who want an agent to draft, tag and route mail as a teammate while a person sends. | $25 / seat-mo | hosted |
| 6 | [Kustomer](https://www.anchorterminal.com/tools/kustomer.md) | C | 57.3 | Larger support teams already on Kustomer who want an agent to read the full customer timeline and write messages, notes and status changes under a narrowly scoped key. | $0.60 / tx | hosted |
| 7 | [Help Scout API + MCP](https://www.anchorterminal.com/tools/help-scout.md) | C | 56.1 | Research, summaries and reporting over a live inbox where nobody wants an agent able to write. | $25 / seat-mo | hosted |
| 8 | [Chatwoot API](https://www.anchorterminal.com/tools/chatwoot.md) | C | 55.8 | Teams that want to own the helpdesk and its data, or need the cheapest per-seat cloud. | $19 / seat-mo | hosted |
| 9 | [LiveAgent](https://www.anchorterminal.com/tools/liveagent.md) | C | 54.9 | A team already on LiveAgent that wants an agent to triage, tag, route and draft through MCP under an agent's own permissions, or to sync tickets and contacts through v3 keys. | $15 / seat-mo | hosted |
| 10 | [Missive API + MCP](https://www.anchorterminal.com/tools/missive.md) | C | 54.3 | Small teams that already run their mail in Missive and want an agent to triage, label, post internal notes and draft replies for a person to send. | $14 / seat-mo | hosted |

## Picks by need

- Highest score overall: [Intercom API + MCP](https://www.anchorterminal.com/tools/intercom.md), BB, 71.5/100 on the benchmark. Also [Zendesk Support API](https://www.anchorterminal.com/tools/zendesk.md), B, 68.7/100.
- Reliability: [Help Scout API + MCP](https://www.anchorterminal.com/tools/help-scout.md), 77/100 on reliability, against 73 for the overall leader.
- Agent ergonomics: [Zendesk Support API](https://www.anchorterminal.com/tools/zendesk.md), 77/100 on agent ergonomics, against 74 for the overall leader.
- Security & auth: [Zendesk Support API](https://www.anchorterminal.com/tools/zendesk.md), 75/100 on security & auth, against 72 for the overall leader.
- Maintenance & community: [Zammad](https://www.anchorterminal.com/tools/zammad.md), 95/100 on maintenance & community, against 72 for the overall leader.
- Transparency & trust: [Zendesk Support API](https://www.anchorterminal.com/tools/zendesk.md), 87/100 on transparency & trust, against 79 for the overall leader.
- Self-hosting under an open licence: [Chatwoot API](https://www.anchorterminal.com/tools/chatwoot.md), self-hosted, MIT licence. Also [Zammad](https://www.anchorterminal.com/tools/zammad.md), self-hosted, AGPL-3 licence.

## How to choose

- Draft replies without sending: Check that an agent can draft a reply without sending it, since an unreviewed message that reaches a customer cannot be recalled.
- Handoff to a person: Check how an agent hands a conversation to a person, including assignee, priority and a summary, so the person can pick it up without rereading.
- Audit trail for agent actions: Check that every change an agent makes is logged with its identity and a timestamp, since a support team needs to trace which replies came from automation.
- API coverage for tickets: Check that the API covers listing and updating tickets, notes and statuses, since gaps in write coverage force an agent into a manual step.

- How the benchmark tests this category: A sandbox queue of ten tickets in every helpdesk. An agent retrieves context, drafts a reply, adds an internal note and changes status. We score permissions, safe handoff, audit trail and API coverage, and never send the test replies to real customers.

## Each one in detail

### 1. Intercom API + MCP, BB 71.5/100

Intercom's REST API (conversations, contacts, companies, tickets, notes, tags, articles, data attributes and webhooks) and its official hosted MCP server.

- Verdict: Versioned OpenAPI per API version, 235 operations in 2.16, with breaking changes only in new versions. MCP can't reply, assign, snooze or close, those need the REST API.
- Choose it for: Teams on Intercom who want an agent to research conversations and leave internal notes without any chance of messaging a customer.
- Strength: Versioned OpenAPI per API version, 235 operations in 2.16, with breaking changes only in new versions
- Strength: MCP writes are limited to internal notes and help centre articles
- Strength: 10,000 calls a minute per app with reset headers and backoff guidance
- Weakness: MCP can't reply, assign, snooze or close, those need the REST API
- Weakness: No MCP server for Australian workspaces
- Weakness: Every REST call must pin `Intercom-Version`, and behaviour changes between versions
- Price: $29 / seat-mo · Auth: OAuth or key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/intercom.md

### 2. Zendesk Support API, B 68.7/100

REST API for Zendesk Support.

- Verdict: OAuth 2.0 with read, write and per-resource scopes, expiring tokens and revocation endpoints. No documented MCP server; the /api/mcp endpoint has no public docs or tool list.
- Choose it for: Larger support teams that want an agent to work tickets through a mature REST API with real audit trails.
- Strength: OAuth 2.0 with read, write and per-resource scopes, expiring tokens and revocation endpoints
- Strength: Ticket Audits API records every change and who made it
- Strength: Dated deprecations with end-of-life dates, such as API tokens from 28 July 2026 to 30 April 2027
- Weakness: No documented MCP server; the /api/mcp endpoint has no public docs or tool list
- Weakness: API tokens are being retired, so Basic-auth integrations must move to OAuth by 30 April 2027
- Weakness: 30 updates per 10 minutes per user per ticket
- Price: $19 / seat-mo · Auth: OAuth or key · x402: no · Where: local
- Full assessment: https://www.anchorterminal.com/tools/zendesk.md
- Against #1: https://www.anchorterminal.com/compare/intercom-vs-zendesk.md

### 3. Zoho Desk, B 66.6/100

Zoho Desk is a hosted helpdesk from Zoho for tickets, contacts, knowledge base articles and support channels. Agents reach it through the REST API v1 behind OAuth 2.0, described in public OpenAPI 3.1 files.

- Verdict: Public OpenAPI 3.1 files cover 911 operations, OAuth scopes separate read, create, update and delete per module, and replies can be saved as drafts or sent for review before a customer sees them. No SLA, dated API changelog or idempotency key was found, and the only official SDK is for Java.
- Choose it for: Teams already on Zoho who want an agent to read tickets, draft replies for review, add private comments and change status with narrow scopes, and small teams that want a free edition with API access.
- Strength: OpenAPI 3.1 files for 185 resources and 911 operations are public on GitHub, last changed on 9 September 2026
- Strength: OAuth scopes split tickets, contacts, tasks, articles and events into READ, CREATE, UPDATE and DELETE
- Strength: `draftReply`, `sendDraft` and `sendForReview` let an agent stage a reply for a person before it is sent
- Weakness: No SLA found, and the Terms of Service disclaim uninterrupted service
- Weakness: No dated API changelog. Changes are announced in a community forum that loads by script
- Weakness: No idempotency key on writes, and Retry-After is absent on concurrency 429s
- Price: $7 / seat-mo · Auth: OAuth · x402: no · Where: local
- Full assessment: https://www.anchorterminal.com/tools/zoho-desk.md
- Against #1: https://www.anchorterminal.com/compare/intercom-vs-zoho-desk.md

### 4. Plain API + MCP, B 65.5/100

API-first B2B support platform.

- Verdict: Machine-user API keys with fine-grained permissions and several keys per user for rotation. Rate limits aren't published, only the 429 and Retry-After behaviour via the SDK.
- Choose it for: B2B teams that want an API-first helpdesk where an agent can do everything a person can, with scoped machine keys.
- Strength: Machine-user API keys with fine-grained permissions and several keys per user for rotation
- Strength: Downloadable GraphQL schema, llms.txt and a dated API changelog
- Strength: Typed `MutationError` with codes, field errors and explicit retry guidance
- Weakness: Rate limits aren't published, only the 429 and Retry-After behaviour via the SDK
- Weakness: GraphQL API isn't versioned, and several fields were removed days after deprecation in September 2026
- Weakness: 32 MCP tools with no toolsets
- Price: $35 / mo · Auth: OAuth or key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/plain.md
- Against #1: https://www.anchorterminal.com/compare/intercom-vs-plain.md

### 5. Front API + MCP, B 63.6/100

Front's Core API for its shared inbox (conversations, messages, drafts, comments, tags, contacts, accounts, inboxes, teammates and webhooks) and its official hosted MCP server at https://mcp.frontapp.com/mcp.

- Verdict: MCP sending needs its own `send` scope, separate from read and write. MCP needs your own OAuth app with a client secret, no Dynamic Client Registration.
- Choose it for: Teams on Front who want an agent to draft, tag and route mail as a teammate while a person sends.
- Strength: MCP sending needs its own `send` scope, separate from read and write
- Strength: destructiveHint on every user-visible MCP write, and version tokens on draft edits
- Strength: Public OpenAPI 3.0 file with 246 operations, updated on 10 days in the last 90
- Weakness: MCP needs your own OAuth app with a client secret, no Dynamic Client Registration
- Weakness: Core API limit is 50 requests a minute on Starter, and more costs $200 per 100 a minute a month
- Weakness: No dated developer changelog we could find
- Price: $25 / seat-mo · Auth: OAuth or key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/front.md
- Against #1: https://www.anchorterminal.com/compare/front-vs-intercom.md

### 6. Kustomer, C 57.3/100

Kustomer is a customer service CRM that keeps conversations, messages, notes and custom objects on one customer timeline. Agents reach it through a REST API and a read-only hosted MCP server. It is sold through sales.

- Verdict: API keys carry granular roles, an expiry and an optional CIDR restriction, and the reference documents 449 operations with an OpenAPI definition on each page. Plan prices are not published and no self-serve trial was found, so access starts with a sales contact. The MCP server is read-only and limited to approved clients.
- Choose it for: Larger support teams already on Kustomer who want an agent to read the full customer timeline and write messages, notes and status changes under a narrowly scoped key.
- Strength: API keys take one or more of several hundred roles with read, create, update and delete levels, an expiry in days and an optional CIDR restriction
- Strength: The reference covers 449 operations, each page served as Markdown with an OpenAPI 3.0 definition, required roles and response examples
- Strength: Rate limits are published per plan (1,000 requests a minute on Enterprise, 2,000 on Ultimate) with `x-ratelimit-*` headers on responses
- Weakness: Plan prices are not published and no self-serve trial or signup was found, so a person has to go through sales
- Weakness: No idempotency keys, `Retry-After` header or backoff guidance were found in the reviewed documentation
- Weakness: No single OpenAPI file, `llms.txt`, developer changelog or official REST SDK was found
- Price: $0.60 / tx · Auth: OAuth or key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/kustomer.md
- Against #1: https://www.anchorterminal.com/compare/intercom-vs-kustomer.md

### 7. Help Scout API + MCP, C 56.1/100

Help Scout's Inbox API 2.0 (conversations, threads, replies, notes, customers, mailboxes, tags, users, workflows, reports and webhooks) and its official hosted MCP server at https://mcp.helpscout.net/mcp, GA since July 2026.

- Verdict: MCP server read-only for new connections and limited by each user's mailbox permissions. MCP can't write, so a draft, note and status loop needs the REST API.
- Choose it for: Research, summaries and reporting over a live inbox where nobody wants an agent able to write.
- Strength: MCP server read-only for new connections and limited by each user's mailbox permissions
- Strength: MCP docs warn that customer-pasted text and credentials reach the agent unchanged
- Strength: Rate limits published by plan, with writes counted as two and `X-RateLimit-Retry-After` on 429
- Weakness: MCP can't write, so a draft, note and status loop needs the REST API
- Weakness: MCP tool list isn't published
- Weakness: No OpenAPI file and no developer changelog
- Price: $25 / seat-mo · Auth: OAuth · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/help-scout.md
- Against #1: https://www.anchorterminal.com/compare/help-scout-vs-intercom.md

### 8. Chatwoot API, C 55.8/100

Open-source omnichannel inbox with REST Application, Client and Platform APIs over conversations, contacts, messages and webhooks.

- Verdict: MIT-licensed core you can self-host for free, same API as Chatwoot Cloud. No MCP server, official or hosted.
- Choose it for: Teams that want to own the helpdesk and its data, or need the cheapest per-seat cloud.
- Strength: MIT-licensed core you can self-host for free, same API as Chatwoot Cloud
- Strength: OpenAPI 3.1 files in the repo, 124 Application operations, plus llms.txt
- Strength: Agent bot tokens restricted to bot-permitted conversation endpoints
- Weakness: No MCP server, official or hosted
- Weakness: User access tokens carry the user's full role, with no scopes
- Weakness: Cloud rate limits, 429 behaviour and any SLA aren't published
- Price: $19 / seat-mo · Auth: API key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/chatwoot.md
- Against #1: https://www.anchorterminal.com/compare/chatwoot-vs-intercom.md

### 9. LiveAgent, C 54.9/100

LiveAgent is a hosted helpdesk from Quality Unit with ticketing, live chat, a call centre and a knowledge base. Agents reach it through a REST API with per-key permissions and a built-in MCP server on each account.

- Verdict: API v3 keys carry per-key permissions and are limited to 180 requests a minute, and a built-in MCP server adds notes, email replies and ticket routing under the connecting agent's role. The v3 REST API has no reply or note operation, error bodies hold one message field, and no 429 or retry behaviour is documented.
- Choose it for: A team already on LiveAgent that wants an agent to triage, tag, route and draft through MCP under an agent's own permissions, or to sync tickets and contacts through v3 keys.
- Strength: API v3 publishes a Swagger 2.0 definition with 107 operations, and each operation names the key permission it needs, such as `ticket.read` or `contact.edit`
- Strength: The built-in MCP server at `/api/mcp` accepts OAuth 2.1 with PKCE or bearer tokens that expire after two years and can be revoked one by one
- Strength: The rate limit is published, 180 requests a minute for each API key on cloud accounts
- Weakness: API v3 has no operation to reply to a ticket or add a note. Those go through the legacy v1 API or the MCP server
- Weakness: The v1 API documents its key as a URL or form parameter (`apikey=value`), not a header
- Weakness: No 429 status, rate-limit header, retry guidance or idempotency key was found in the reviewed documentation
- Price: $15 / seat-mo · Auth: OAuth or key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/liveagent.md
- Against #1: https://www.anchorterminal.com/compare/intercom-vs-liveagent.md

### 10. Missive API + MCP, C 54.3/100

Missive is a shared team inbox for email, SMS, WhatsApp and live chat from Heliom Inc. of Quebec City. Agents reach it through a REST API at public.missiveapp.com/v1 or a hosted MCP server with OAuth permissions.

- Verdict: The MCP server separates eight OAuth permissions, so an agent can draft replies without being able to send them, and the REST API publishes numeric rate limits with `Retry-After`. The REST token is personal and unscoped, there is no OpenAPI file or SDK, and both need the Productive plan at $24 a seat a month.
- Choose it for: Small teams that already run their mail in Missive and want an agent to triage, label, post internal notes and draft replies for a person to send.
- Strength: MCP access uses OAuth with PKCE and eight permissions, with drafting and sending granted separately and ungranted tools hidden from the client
- Strength: REST limits are published as 5 concurrent requests, 300 a minute and 900 per 15 minutes, with `Retry-After` and `X-RateLimit-*` headers on 429
- Strength: Every docs page has a Markdown twin and the docs publish an llms.txt index
- Weakness: REST tokens are personal with no scopes and reach every account the user can open, shared accounts included
- Weakness: No OpenAPI file, no official SDK and no idempotency key were found in the reviewed documentation
- Weakness: Error responses are barely documented. The reference names a few 400 and 404 cases and gives no error format
- Price: $14 / seat-mo · Auth: OAuth or key · x402: no · Where: hosted
- Full assessment: https://www.anchorterminal.com/tools/missive.md
- Against #1: https://www.anchorterminal.com/compare/intercom-vs-missive.md

8 more are ranked in the full table: https://www.anchorterminal.com/categories/support.md

## Head to head

- [Intercom API + MCP vs Zendesk Support API](https://www.anchorterminal.com/compare/intercom-vs-zendesk.md)
- [Intercom API + MCP vs Zoho Desk](https://www.anchorterminal.com/compare/intercom-vs-zoho-desk.md)
- [Intercom API + MCP vs Plain API + MCP](https://www.anchorterminal.com/compare/intercom-vs-plain.md)
- [Front API + MCP vs Intercom API + MCP](https://www.anchorterminal.com/compare/front-vs-intercom.md)
- [Zendesk Support API vs Zoho Desk](https://www.anchorterminal.com/compare/zendesk-vs-zoho-desk.md)
- [Plain API + MCP vs Zendesk Support API](https://www.anchorterminal.com/compare/plain-vs-zendesk.md)
- [Front API + MCP vs Zendesk Support API](https://www.anchorterminal.com/compare/front-vs-zendesk.md)
- [Plain API + MCP vs Zoho Desk](https://www.anchorterminal.com/compare/plain-vs-zoho-desk.md)
- [Front API + MCP vs Zoho Desk](https://www.anchorterminal.com/compare/front-vs-zoho-desk.md)
- [Front API + MCP vs Plain API + MCP](https://www.anchorterminal.com/compare/front-vs-plain.md)

## Questions

### What are the highest-rated customer support and helpdesk APIs for AI agents?

Intercom API + MCP has the highest benchmark score of the 18 ranked customer support and helpdesk APIs, 71.5 (BB). Zendesk Support API is second with 68.7 (B).

### How many customer support and helpdesk APIs are agent-ready?

1 of the 18 ranked here grade BB or better, the bar for agent-ready on the Anchor benchmark.

### Which customer support and helpdesk APIs accept x402 payments?

None of the ranked listings here accepts x402 for its main call yet.

### How is this list ranked?

By the Anchor benchmark score out of 100, a weighted mean of the scored categories minus deductions for negative events, from public evidence re-checked as vendors change. Listings cannot pay for a place. The latest assessment behind this page is from 9 October 2026.

## How this list is made

The order is the Anchor benchmark score, the same number as on each listing. Each listing is graded from public evidence against the benchmark checklist, and the picks are worked out from those grades, prices and facts. No listing pays for its place, and paid audits or listing help never change a score.