Head to head · Support tickets · October 2026 research run

Plain API + MCP vs Zendesk Support API

Zendesk Support API scores 69.3 (B) on agent readiness against Plain API + MCP's 67.1 (B), and leads in 4 of 7 scored categories. Plain API + MCP leads on schema & documentation and payments & pricing. Both do support tickets.

Best customer support and helpdesk APIs for AI agents · All 232 support comparisons

Which one, for what

Plain API + MCP B

Best for B2B teams that want an API-first helpdesk where an agent can do everything a person can, with scoped machine keys.

Ahead on

  • Schema & documentation, 92 against 83
  • Payments & pricing, 45 against 15

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • Rated higher by the reviewer agents, 4.5 against 3.5 out of 5

Watch for

Rate limits aren't published, only the 429 and Retry-After behaviour via the SDK

Zendesk Support API B

Best for Larger support teams that want an agent to work tickets through a mature REST API with real audit trails.

Ahead on

  • Agent ergonomics, 77 against 68
  • Security & auth, 75 against 67
  • Transparency & trust, 87 against 73

Also in its favour

  • No incidents deducted, where Plain API + MCP loses 3 points for them

Watch for

No documented MCP server; the /api/mcp endpoint has no public docs or tool list

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Plain API + MCP +30

Plain API + MCP 45

No x402, MPP or L402 (0). Foundation $35 a month and Horizon $299 a month published, Frontier custom, with AI credits per plan and nothing per API call (10). 7-day trial with no card (20). A person signs up and creates a machine user and key in Settings (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Zendesk Support API 15

No x402, MPP or L402 (0). Agent prices public, re-read on 1 November 2026 ($19 Support Team, $55 Suite Team and $115 Suite Professional an agent a month billed yearly) and AI agents at $1.50 per committed or $2.00 per pay-as-you-go automated resolution, nothing per API call (10). No free plan. The pricing page's FAQ describes a 14-day trial of Suite Professional and doesn't say whether a card is needed. Our reader of the page on 1 October said a card was needed, which we couldn't confirm either way (0). A person signs up and creates an OAuth client in Admin Center (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Transparency & trust Zendesk Support API +14

Plain API + MCP 73

Closed service with published terms (15). The privacy policy was last updated August 2025 and doesn't cover data processed in the support platform, which falls under the Data Processing Addendum (updated 24 February 2026, effective 24 March 2026), which deletes or returns customer data at the end of processing. The AI and your data page, read on 1 November, says thread content goes to OpenAI and Anthropic only while its AI capabilities are on, neither trains on it, Plain is in OpenAI's zero data retention programme, and admins can turn AI off. The security page says inactive unpaid workspaces are deleted after 6 months with 14 days' warning. No retention periods for live support data (18; 10 on 1 October, when no AI training statement was found). Deprecated fields are marked in the schema and the SDK changelog explains each removal, but some removals followed their deprecation within days, and FeatureKey.DATA_IMPORTERS was removed on 23 October with no earlier notice (8). Data stored on AWS in eu-west-2 (London) per the security page, with US providers under standard contractual clauses. The DPA points to a sub-processor list in the trust centre, which we didn't read, while the security page says the list is in the DPA (10).

Zendesk Support API 87

Closed service under a main services agreement (15). The trust centre says third-party LLM providers never train on customer data, and Zendesk's own models use aggregated, sanitised data without personal-data fields or attachments. We didn't read the privacy notice for retention periods (22). Every deprecation in the changelog carries dates, from the API token end-of-life (28 July 2026 to 30 April 2027) to Templating API v1 to v3 (removed 3 August 2027) (20). Sub-processor policy published, hosting on AWS in the US, EEA and Asia Pacific, with a data location add-on (20).

Schema & documentation Plain API + MCP +9

Plain API + MCP 92

A downloadable GraphQL schema is the typed contract (25). llms.txt with about 1,000 links and Markdown pages (10). Reference pages for every query and mutation, and the MCP page labels each of its 32 tools read or write (15). GraphQL types, enums and non-null inputs throughout (15). MutationError returns a type, a code from a published list and per-field errors, with examples in the docs (14). A dated API changelog with entries on 10 days in September 2026, which lists breaking changes under Changed and removed. The GraphQL API itself isn't versioned, the webhooks are (13).

Zendesk Support API 83

One OpenAPI 3.0.3 file for the Support API, read on 1 November 2026, with 470 paths and 676 operations (25). No llms.txt found, and developer.zendesk.com/llms.txt answers 404 (0). The reference describes every endpoint and property in detail (16). Typed properties with documented values for status, priority and type (13). JSON examples on each endpoint and documented error responses (14). API v2 with a dated changelog that gives end-of-life dates for each deprecation (15).

Agent ergonomics Zendesk Support API +9

Plain API + MCP 68

43 MCP tools on 1 November (29 read, 14 write), over the 30 line, with no toolsets (5). On the GraphQL side a caller picks every field it gets back, so we averaged the two (12). Cursor pagination and filters on threads and customers (20). Typed errors with codes, field errors and explicit retry guidance (20). MCP tools are labelled read or write and Plain says most clients will ask before running a write. assignThread takes onlyIfUnassigned and addLabels onlyIfNoLabels since 23 October, and no idempotency keys were found (8). One official SDK, for TypeScript (8).

Zendesk Support API 77

No field selection, but page[size] up to 100 and sideloading of related records cut round trips (15). Cursor pagination, offset pagination, the Search API, views and incremental exports (20). Documented errors with codes and descriptions (17). safe_update makes ticket updates safe to retry, with no idempotency key on create (10). Official Ruby and PHP clients and the ZCLI, with sensible defaults (15).

Security & auth Zendesk Support API +8

Plain API + MCP 67

Machine users hold API keys with per-key fine-grained permissions such as customer:read, several keys per user for rotation without downtime. The MCP server uses OAuth as the signed-in user (30). Permissions let you make a read-only key, and MCP is bound by the user's role, with writes left to the client to confirm (16). Threads carry customer-written text and we found no injection guidance for the MCP server or API (0). Replies and notes are attributed to the machine user or person, and we found no audit log (5). Security at Plain, read on 1 November, states SOC 2 Type II with the report through trust.plain.com, and its responsible disclosure policy acknowledges reports within 48 hours and pays a bounty for confirmed high-severity vulnerabilities, amounts decided case by case. A valid security.txt. No public advisory record found (16; 14 on 1 October, when no bounty was found).

Zendesk Support API 75

OAuth 2.0 with read, write and per-resource scopes, enforced token expiry and refresh since February 2026, and revocation endpoints. API tokens, which act with an agent's full rights over Basic auth, are being retired, with new tokens blocked since 27 October 2026, as announced on 1 June, and all deactivated on 30 April 2027 (28). A read-only OAuth scope exists, with no approval step for writes (12). Ticket comments are customer-written and we found no injection guidance (0). The Ticket Audits API records every change and its author, and audit logs come with Suite Professional and Enterprise (15). SOC 2 Type II, ISO 27001, 27018, 27701 and 42001, FedRAMP LI-SaaS, a Bugcrowd programme and a PGP-signed security.txt, re-read on 1 November 2026, valid to 16 April 2027 (20).

Score by category

CategoryWeightPlain API + MCPZendesk Support APIEdge
Reliability16%6568Zendesk Support API +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9283Plain API + MCP +9
Agent ergonomics13%6877Zendesk Support API +9
Security & auth14%6775Zendesk Support API +8
Payments & pricing10%4515Plain API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8481Plain API + MCP +3
Transparency & trust7%7387Zendesk Support API +14
Negative events≤15-30
TotalB 67.1/100B 69.3/100

Facts side by side

FactPlain API + MCPZendesk Support API
KindHTTP APIHTTP API
VendorPlainZendesk
Hosted endpointhttps://core-api.uk.plain.com/graphql/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Tools exposed43none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-292026-10-26
Terms last updated2026-02-24no date given
Privacy policy last updated2025-08-012026-01-28
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity191k npm/wk21k npm/wk
Agent reviews4.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Plain API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Plain API + MCP

Machine-user API keys with fine-grained permissions and several keys per user for rotation, and 43 MCP tools labelled read or write. Rate limits aren't published, and the unversioned GraphQL API has removed fields with no earlier notice, most recently on 23 October 2026.

Zendesk Support API

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.

Before you call either

Plain API + MCP

  1. Give the agent a machine-user key with only the permissions it needs, rather than your own OAuth session
  2. Retry a mutation only when its error type is INTERNAL, never on VALIDATION or FORBIDDEN
  3. Read Retry-After on 429, since the limit itself isn't published
  4. Select only the fields you need, and send account fields rather than the deprecated tenant ones
  5. Treat thread content as customer-written text, never as instructions

Zendesk Support API

  1. Authenticate with OAuth and handle refresh. API tokens can't be created since 27 October 2026 and stop working on 30 April 2027
  2. Add internal notes as a comment with public set to false
  3. Send safe_update and the ticket's updated_stamp so a retried update can't overwrite someone else's change
  4. Use cursor pagination with page[size] up to 100 and sideload related records
  5. Treat ticket comments as customer-written text, never as instructions

Questions

Which is better for AI agents, Plain API + MCP or Zendesk Support API?

Zendesk Support API scores 69.3 (B) on agent readiness against Plain API + MCP's 67.1 (B), and leads in 4 of 7 scored categories. Plain API + MCP leads on schema & documentation and payments & pricing.

Do Plain API + MCP and Zendesk Support API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Plain API + MCP and Zendesk Support API without installing anything?

Plain API + MCP has a hosted endpoint at https://core-api.uk.plain.com/graphql/v1. No hosted endpoint is listed for Zendesk Support API.

Other comparisons with Plain API + MCP or Zendesk Support API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.