HelpDesk

# Fix list: HelpDesk

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/helpdesk, the October 2026 research run, assessed 9 October 2026. Grade D, 50.3 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on HelpDesk: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Security & auth, 50 out of 100, up to 8.8 more on the total

Why it scored 50: OAuth 2.1 authorisation code grant with PKCE and refresh tokens, or personal access tokens sent as Basic auth. The API asks only for the `accounts--my:ro` scope, and the scopes page lists no ticket scopes, so a token carries its user's whole role (20). Three roles exist (`owner`, `normal`, `viewer`), settings are read-only for the last two, and deleted tickets stay in trash for 30 days. No confirmation step for destructive calls, and the docs state that any role can read administrator-managed settings through the API (10). Ticket text is customer-written, and no prompt-injection guidance was found (0). `GET /v1/auditLog` records configuration changes with an `api` author type, not ticket actions. The help article gives 30 or 180 days of history under older plan names, and the pricing page lists audit logs under Enterprise (9). SOC 2 Type 2 is claimed on the pricing page and in Text's llms.txt, with annual penetration tests, enforced 2FA and SAML SSO on Enterprise. No security.txt (404), and no bug bounty or disclosure policy found. The trust centre is script-drawn and was not read (11).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 2. Agent ergonomics, 47 out of 100, up to 8.6 more on the total

Why it scored 47: List size is set with `pageSize` (default 20, maximum 100). The docs advise `eventsScope=none` to drop events, but that parameter is missing from the parameter list, and there is no field selection (15). Cursor pagination on tickets, `X-Total-Pages` and `X-Total-Results` headers, about 39 filters, full-text `query` and three sort keys (18). Error codes and bodies are not documented (3). No idempotency key. An upload transaction created first fixes the ID of the ticket made from it, which is not presented as a retry guard (4). Creating a ticket needs little beyond a requester email, and defaults are stated for status and priority. No official SDK for this API was found (7).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 3. Payments & pricing, 35 out of 100, up to 8.1 more on the total

Why it scored 35: No x402, MPP or L402 (0). Seat prices are public ($19 and $79 a user a month billed yearly, $25 and $99 monthly, Enterprise by quote). API calls are metered, and two published prices disagree. Text's docs give 10,000 calls a month on Essential, 20,000 on Growth and $29.50 for 100,000 more, while platform.text.com gives $0.27 per 1,000 private requests. 15 of 20 for that disagreement. 14-day trial without a card (20). A person signs up in a browser and creates the token in a console (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 4. Reliability, 60 out of 100, up to 8 more on the total

Why it scored 60: Graded on the hosted REST API at api.helpdesk.com. Status page at status.helpdesk.com on incident.io with five components, the API among them, and a history view (20). The history for July to 9 October 2026 lists no incidents and one scheduled maintenance on 30 September (30). No rate limit found in the API description or in Text's docs (0). No 429 or backoff guidance and no idempotency keys found. Webhook deliveries are retried for about 24 hours, which is a different matter (0). The pricing page lists SLAs under Enterprise, but no SLA document was found and the terms disclaim availability (0). The API is v1, described as the public API (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 5. Schema & documentation, 63 out of 100, up to 6 more on the total

Why it scored 63: OpenAPI 3.0.3 description, version 1.0.0, with 139 operations on 90 paths and 190 schemas, embedded in the Redoc page at api.helpdesk.com/docs and repeated in Text's docs as the Ticketing API (25). Text's docs publish an llms.txt index and a Markdown page per method (10). Only 10 of 139 operations carry a description, though the tag sections explain pagination, attachments, silos and webhooks well (7). Enums for status, priority, silo and webhook events, UUID formats and required fields are present, with some free-form objects such as `customFields` and `requester` filters (11). 27 operations carry examples, but every operation documents only a 200 response except one 403 (5). The path is versioned at v1. Text's API changelog has 26 dated entries and none is tagged for this API (5).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Maintenance & community, 39 out of 100, up to 5.3 more on the total

Why it scored 39: The Ticketing API has no dated release of its own. Text's API changelog reaches 6 October 2026 (a `ticket_created` system event) and the product updates page has a ticket entry on the same day, so the platform is current while this API's own last change is unknown (20 of 30). No changelog entry in the last 90 days is tagged for this API, though four product updates since 16 July touch tickets (10 of 20). Closed service with a developer email, a Discord server and 24-hour support by email (9). No official SDK for this API found (0). No package to assess (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 67 out of 100, up to 2.9 more on the total

Made of editorial 49, provenance 84.

Why it scored 67: Closed service under Terms of Use dated 3 July 2026 that name Text, Inc. and cover APIs (15). Privacy Policy of 3 September 2026, DPA of 22 May 2026 and a Data Storage Policy placing HelpDesk data in the United States. Retention is stated as long as necessary, with 30 days for trash, 60 for spam and at least 10 days of logs. DPA section 2.4 allows training AI models on Client Data, while the AI FAQ says training is per account on internal models and never on third-party ones (17). Text's version lifecycle with `Legacy` and `Deprecation` headers lists five APIs and not this one. One webhook event is marked deprecated without a date, and the terms allow discontinuing any part at any time (5). The DPA promises 10 days' notice of new sub-processors and the storage location is stated, but the sub-processor list is on a script-drawn trust centre page we could not read (12).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 5 of the 7 things a reader expects, and has 2 clauses that cost points (4.3 of 10)
- Privacy policy: read, states 7 of the 8 things a reader expects (9.3 of 10)
- security.txt: not found (0 of 10)

## Deductions

Each comes off the total. A fixed and documented problem counts for less at the next check.

- 2026-10-09. www.helpdesk.com/pricing.md states that beyond the per-user plan price the only usage-based cost is extra AI resolution packs, while Text's API pricing page (https://www.text.com/docs/getting-started/api-pricing.md) meters every API request against a monthly allowance and sells 100,000 more for $29.50, and https://platform.text.com/pricing lists $0.27 per 1,000 private requests. Two points for a pricing claim the vendor's own API pages contradict.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: the trust centre at trust.text.com and its sub-processor list, which are script-drawn (Vanta) and showed our reader only a title
- unchecked: api.helpdesk.com/robots.txt answered 403 (RBAC: access denied). The docs page on the same host answered 200 and was read once
- Which API price applies to a HelpDesk plan. Text's docs include 10,000 or 20,000 calls a month and sell 100,000 more for $29.50, platform.text.com lists $0.27 per 1,000 private requests, and the HelpDesk pricing page mentions neither
- Whether a new HelpDesk.com signup lands in the Text app. The signup link on www.helpdesk.com redirects to www.text.com/app, and Text's docs present this API as the Ticketing API
- Whether the Text MCP server at https://mcp.text.com/v2/, which lists 16 ticket tools, is open to a HelpDesk.com plan. It was not graded here
- Rate limits, error formats and 429 behaviour. None found in the reviewed documentation
- The Terms of Use (section 4.7) forbid benchmarking, testing or analysing the Services in a way that competes with or harms Text's business, and the Developer Terms forbid tests that may affect the Services. No deduction taken. This matters before any probe is run
- The date format of the legal pages is read as month/day/year because the DPA is dated 05/22/2026
- The lead named the vendor as Text. The contracting entity is Text, Inc. of Boston, and the product is also sold as part of Text's unified app

## Weaknesses

- No rate limit, 429 behaviour or idempotency key found in the API description or Text's docs
- Every operation documents only a 200 response, apart from one 403, so error bodies are unknown before a call
- The API asks only for the `accounts--my:ro` scope. No ticket-level scopes exist, so a token has its user's full role
- Webhook payloads carry no documented signature or shared secret
- The DPA (section 2.4) lets Text use Client Data to train AI models. The terms bar benchmarking or testing that harms Text's business, which matters before any probe is run

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Send Basic auth with the account ID as username and the personal access token as password, and always set a `User-Agent` header
- Create the token from a Viewer or Agent account when the task allows. A token inherits its creator's role, and only Administrators can change settings
- Reply or add a note through `PATCH /v1/tickets/{ticketID}` with `message.text`. Set `isPrivate` to true for an internal note, because the default sends to the requester
- Page `/v1/tickets` with `next.value` and `next.ID` from the last item, keep `sortBy` and `order` fixed, and pass `silo` to read archive, spam or trash
- Budget for metered calls. Text's docs count every request except those answered 500 against the plan's monthly API allowance

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.