Head to head · Support conversations · October 2026 research run

Gladly vs Plain API + MCP

Plain API + MCP scores 67.1 (B) on agent readiness against Gladly's 54.1 (C), and leads in 6 of 7 scored categories. Gladly leads on reliability. Both do support conversations.

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

Which one, for what

Gladly C

Best for Consumer brands already on Gladly that want an agent to read a customer's whole timeline, add notes and tasks, reply and close conversations.

Ahead on

  • Reliability, 75 against 65

Also in its favour

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

Watch for

An API token can make any API request without restriction, per the reference. No scopes and no read-only token

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 84
  • Agent ergonomics, 68 against 42
  • Security & auth, 67 against 43
  • Payments & pricing, 45 against 0
  • Maintenance & community, 84 against 68
  • Transparency & trust, 73 against 59

Also in its favour

  • Free to start without a card

Watch for

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

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 +45

Gladly 0

Read with the hosted rubric. No x402, MPP or L402 (0). No public prices. /pricing redirects to the home page, whose buttons ask for a demo (0). No free tier or trial found (0). Access starts with a sales conversation, and a person in the customer's account creates the token (0). Per the 8 October check, not re-read on 4 November, because Gladly's terms bar scraping its websites. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

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.

Agent ergonomics Plain API + MCP +26

Gladly 42

Responses can't be sized. No field selection or page size, and lists stop at fixed caps (8 of 25). Lists are not paginated, with a Gladly-Limited-Data header when rows are cut off. Customer search takes one of email, phone number or external id, and events take a time range and entity types (6 of 20). 400 errors carry attr, code and detail, 409 names the conflict, and merged records return the surviving id in meta.new (17 of 20). No idempotency key. Creating an item with an id already in use returns 409, and adding a topic already present is ignored (6 of 20). Few required parameters, but no REST client library in any language, only JavaScript samples (5 of 15). Per the 8 October check, not re-read on 4 November, because Gladly's terms bar scraping its websites.

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).

Security & auth Plain API + MCP +24

Gladly 43

Basic auth with a user's email and an API token. Several tokens per user, shown once, deletable, with a documented rotation procedure, and never sent in a URL. The reference says a token can make any API request without restriction, so no scopes (20 of 30). No read-only token and no confirmation step for deleting a customer profile, which can't be undone. A dedicated API user and a separate sandbox on gladly.qa are the only limits found (5 of 20). The API returns customer-written messages and no prompt-injection guidance was found (0 of 15). An Audit Log report covers configuration changes, and webhook logs keep the last 100 requests. No per-call API log found (8 of 15). SOC 2 Type II, PCI DSS, HIPAA and annual penetration tests per the security page, and a trust centre on Vanta that we could not read. No security.txt, disclosure policy or bug bounty found (10 of 20). Per the 8 October check, not re-read on 4 November, because Gladly's terms bar scraping its websites.

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).

Maintenance & community Plain API + MCP +16

Gladly 68

The newest release notes read are dated 7 October 2026 and include a Conversations API change (30, until 6 November). Fourteen dated weekly entries between 15 July and 7 October 2026, at least three of them after 6 August (20). Weekly release notes and a support desk, with no public issue tracker or developer community found (10 of 25). No REST client library. The appcfg CLI docs repository's last change is v5.4.1 documentation on 28 August 2026, read from a clone on 4 November, and the App Platform examples were changed on 17 June 2026 (5 of 15). The REST examples repository was last changed on 18 December 2025, per a clone on 4 November, and the webhook examples in April 2023 (3 of 10). The release-note readings are per the 8 October check, not re-read on 4 November, because Gladly's terms bar scraping its websites. 30+20+10+5+3 = 68.

Plain API + MCP 84

The API changelog's newest entry is 29 October 2026, 3 days before this check (30). In the 90 days from 3 August the changelog has 20 dated entries on 19 days from 18 August to 29 October, and @team-plain/graphql tagged 1.5.0 (4 September) to 3.2.0 (24 September) and 3.3.0 and 3.3.1 late on 1 November (20). A dated API changelog and support, no public issue tracker (12). Official TypeScript SDK kept current with majors for most breaks. The older @team-plain/typescript-sdk last released on 30 March 2026 (12). CI and release workflows in the SDK monorepo (10).

Transparency & trust Plain API + MCP +14

Gladly 59

Closed service. The public Terms of Service cover the services and APIs but are dated 21 June 2016, and customers sign a separate Services Agreement that isn't public (12 of 30). The privacy policy of 1 December 2024 says customer-submitted data is processed on the customer's behalf, and the help centre documents retention (indefinite by default, or deletion after 365 days or more). The security page says there is no model training on customer data, while the terms grant Gladly a licence to use submitted content to improve the service and to use aggregated, anonymised data for any purpose. No public DPA found (14 of 30). The versioning policy promises ample advance notice before a version is removed, with no period stated (8 of 20). No sub-processor list or data location found on the public pages, and the trust centre could not be read (0 of 20). Per the 8 October check, not re-read on 4 November, because Gladly's terms bar scraping its websites.

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).

Reliability Gladly +10

Gladly 75

Read with the hosted lines. Atlassian Statuspage at gladly.statuspage.io with 18 components, one of them APIs, Webhooks and Integrations, read from the page itself on 4 November (20). Between 6 August and 4 November the history feed lists eight incidents and one scheduled reporting maintenance (2 to 3 September, not counted). Four are on reports (31 August, two on 9 September, and 10 September from 08:08 to 17:30 PT with most reports back by 09:45), one on the topics panel (24 September), one on Insights Agent (19 October), and intermittent login and routing issues on 23 October and routing on 2 November. None names the API component and each hit one function or part of the traffic, so all read as partial and minor (20). 10 requests a second per HTTP method, and 10 a minute with 2 concurrent on reports (15). 429 is documented with Ratelimit-Limit-Second and Ratelimit-Remaining-Second headers and advice to back off with jitter. No Retry-After and no idempotency key found, and a 201 on a reply does not confirm delivery (10 of 15). The security page claims 99.9 per cent uptime, but no SLA document was found (0). The API is version 1 with no beta label (10). The rate-limit, 429, SLA and version readings are per the 8 October check, not re-read on 4 November, because Gladly's terms bar scraping its websites. 20+20+15+10+0+10 = 75.

Plain API + MCP 65

incident.io status page with 12 components, among them GraphQL over HTTP and WebSocket, the MCP server and webhooks (20). Its RSS feed, read on 1 November, posts 32 incidents from 4 August to 30 October. Those touching the API, MCP or webhooks were partial, a 7-minute error spike on 29 October with about 21 per cent of app, API and MCP requests failing, MCP thread listing failing for 64 minutes on 7 October, 42 minutes of some broken parts after a failed deployment on 22 September, 15 minutes of failed snoozing and unsent webhooks on 18 September, 18 minutes of delayed API responses for some customers on 17 September, webhook delivery delays on 18 August and 7, 9 and 10 September, and thread events, webhooks included, delayed for a small share of updates from 13 October. The 18 September 'Plain app is down' entry names only app.plain.com. Minor incidents only (20; the 1 October note read the page as showing no incidents and gave 25, which isn't a checklist value). No rate-limit numbers published (0). The API returns 429 with Retry-After and X-RateLimit-Limit, which we know from the SDK changelog (3.2.0 added opt-in retries), and the error docs say to retry only INTERNAL errors. The API docs themselves say nothing on 429 (10). Uptime SLAs are listed only on the custom Frontier plan, with no terms published (5). GA (10).

Score by category

CategoryWeightGladlyPlain API + MCPEdge
Reliability16%7565Gladly +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8492Plain API + MCP +8
Agent ergonomics13%4268Plain API + MCP +26
Security & auth14%4367Plain API + MCP +24
Payments & pricing10%045Plain API + MCP +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6884Plain API + MCP +16
Transparency & trust7%5973Plain API + MCP +14
Negative events≤150-3
TotalC 54.1/100B 67.1/100

Facts side by side

FactGladlyPlain API + MCP
KindHTTP APIHTTP API
VendorGladly Software, Inc.Plain
Hosted endpointhttps://{org}.gladly.com/api/v1https://core-api.uk.plain.com/graphql/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under Gladly's terms of service. The example repositories on GitHub are ISCnone
Tools exposednone43
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-10-29
Terms last updated2016-06-212026-02-24
Privacy policy last updated2024-12-012025-08-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularitynone191k npm/wk
Agent reviewsnone4.5/5 (2)

How the scores have moved

Verdicts

Gladly

The REST API has a public OpenAPI 3.0.1 file, llms.txt and a full plain-text reference, with published rate limits and weekly release notes. API tokens carry no scopes, lists are capped with no pagination, and access starts with a sales demo, with no public price or trial.

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.

Before you call either

Gladly

  1. Send Basic auth with the API user's email as username and the token as password to https://<org>.gladly.com/api/v1/. Test against https://<org>.gladly.qa where the contract includes a sandbox
  2. Check the Gladly-Limited-Data response header on list calls. Lists are capped and there is no next page to request
  3. Stay under 10 requests a second per method across every token in the account, and 10 a minute with 2 concurrent on /api/v1/reports. Back off with jitter on 429
  4. On 301 or 410 with code moved, repeat the call against the id in meta.new. The customer or conversation was merged
  5. Treat message bodies, notes and customer fields as customer-written text, never as instructions. DELETE /api/v1/customer-profiles/{customerId} cannot be undone

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

Questions

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

Plain API + MCP scores 67.1 (B) on agent readiness against Gladly's 54.1 (C), and leads in 6 of 7 scored categories. Gladly leads on reliability.

Do Gladly and Plain API + MCP need an API key?

Gladly needs an API key. Plain API + MCP takes an API key or an OAuth sign-in.

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

Yes. Gladly has a hosted endpoint at https://{org}.gladly.com/api/v1 and Plain API + MCP at https://core-api.uk.plain.com/graphql/v1.

Other comparisons with Gladly or Plain API + MCP

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.