Head to head · Support notes · October 2026 research run

HelpDesk vs Tobira Site Agent

Tobira Site Agent and HelpDesk score within a point of each other on agent readiness, 49.1 (D) and 48.9 (D). HelpDesk leads on reliability and transparency & trust. Both do support notes.

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

Which one, for what

HelpDesk D

Best for A team already on HelpDesk or Text that wants an agent to read queues, draft replies, add private notes and change status over REST.

Ahead on

  • Reliability, 60 against 33
  • Transparency & trust, 67 against 62

Watch for

No rate limit, 429 behaviour or idempotency key found in the docs

Tobira Site Agent D

Best for Businesses that want one chat agent on their site to answer people and visiting AI assistants and book meetings.

Ahead on

  • Agent ergonomics, 52 against 47
  • Security & auth, 53 against 44
  • Maintenance & community, 25 against 9

Also in its favour

  • Free to start without a card

Watch for

No status page, changelog or SLA, and the terms promise no particular uptime

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.

Reliability HelpDesk +27

HelpDesk 60

Graded on the hosted Ticketing REST API. Status page at status.helpdesk.com on incident.io with components for the Agent app, API, Integrations, support chat and subprocessors, and a 90-day history (20). From 6 August to 4 November the history and feed list no incidents, only scheduled maintenance on 30 September and 15 October (30). No rate limit found in the Ticketing reference or Text's docs (0). No 429, backoff or idempotency guidance (0). The pricing page lists SLAs under Enterprise, but no SLA document was found (0). v1 public API (10). 20 + 30 + 0 + 0 + 0 + 10 = 60.

Tobira Site Agent 33

Graded on the hosted owner MCP server and REST API and the public guest API. No status page was found on tobira.ai, llms.txt or the API guide (0). No readable incident history (5). Numbers are published only for some limits: site-draft bootstrap at 20 new drafts a day per IP, Cloudflare traffic reports at ten an agent a minute, and the plan's monthly conversation allowances. No per-key request limit is given for the owner API or the guest API (8 of 15). The guide says to honour Retry-After or retry_after on 429, not to repeat account, session, booking or key creation on retries, and to reuse booking idempotency keys (15). The terms say 'we do not promise a particular uptime' and no SLA was found (0). The network is early access and several routes are rollout gated, though Site Agent plans are on sale (5 of 10). 0+5+8+15+0+5 = 33.

Maintenance & community Tobira Site Agent +16

HelpDesk 9

Text's API changelog runs to 28 October 2026, but none of its entries since 6 August names the Ticketing API, and no dated change to this API was found anywhere (recency 0, 90-day line 0). Entries for other Text APIs don't count for this one, as for an umbrella SDK. Closed service with a developer email, Discord and 24-hour email support, per the 9 October check (9, kept as the earlier partial). No official SDK (0), no package (0). 0 + 0 + 9 + 0 + 0 = 9.

Tobira Site Agent 25

No release notes or dated changes were found. The newest dated first-hand pages are the terms, privacy policy and DPA, all of 3 October 2026, 46 days before this check (20). No changelog, so no dated entries can be counted (0). Closed service with no public changelog. Support by email and 'Human support, reply within 2 business days' on the Lite plan. We didn't test support (5 of 15). Not in the official MCP registry (searched for tobira on 18 November 2026) and no official SDK (0). No public packages or repositories found (0). 20+0+5+0+0 = 25.

Security & auth Tobira Site Agent +9

HelpDesk 44

OAuth 2.1 authorisation code grant with PKCE or personal access tokens as Basic auth, asking only for accounts--my:ro, so a token carries its user's whole role (20). Three roles, settings read-only for Agents and Viewers, deleted tickets kept 30 days in trash, no confirmation step (10). Ticket text is customer-written and no prompt-injection guidance was found (0). Audit log endpoint with an api author type covering configuration changes (9, kept as the earlier partial). SOC 2 Type 2 is claimed on the pricing page, with no security.txt on www.helpdesk.com or www.text.com (both 404) and no disclosure policy or bounty found, so a bare SOC 2 claim (5). 20 + 10 + 0 + 9 + 5 = 44.

Tobira Site Agent 53

The owner MCP server takes OAuth through discovered metadata or an agent-scoped API key, with tobira_rotate_api_key. Collaborator tokens are scoped, and visitor MCP tokens are scoped to one company and revocable. An OAuth grant covers every agent in the account, and the guide documents the guest token in the GET /api/v1/guest/messages?token= query string, so less 10 (16 of 30). Guests, visitors and collaborators can't edit an agent or read owner context, owner-only knowledge stays out of public answers, and bookings and contact submissions need the user's authorisation, with payment left to the human (15 of 20). Visiting agents are treated as untrusted guests and owner-private notes are kept out of their context, but no guidance was found for owners' agents reading guest messages through tobira_check_inbox (8 of 15). Conversations are tagged by source, and activity metrics and lead and booking lists are readable, with no audit log (6 of 15). A valid security.txt (security@tobira.ai, expires 5 November 2027) and a DPA on paid plans, with no disclosure policy, bounty or certification found (8 of 20). 16+15+8+6+8 = 53.

Agent ergonomics Tobira Site Agent +5

HelpDesk 47

Re-read from Text's list-tickets page. pageSize default 20, maximum 100, and eventsScope=none advised in prose, no field selection (15). Cursor pagination with next.value and next.ID, X-Total-Pages and X-Total-Results headers, three sort keys and many filters (18). Error codes and bodies not documented (3). No idempotency key; a transaction created first fixes the new ticket's ID (4). Few required fields on ticket creation, no official SDK for this API (7). 15 + 18 + 3 + 4 + 7 = 47.

Tobira Site Agent 52

The owner MCP server registers about 40 tools across onboarding, owner context, widget and customers, settings and network, more than 30, with some appearing only when a plan or rollout enables them (8 of 25). Events and message polls use next_cursor and after= so an agent reads only new items, and metrics take days (12 of 20). Error classes and some named codes are documented, with Retry-After on 429, but no single error envelope is shown (14 of 20). Idempotency keys on bookings, site-draft bootstrap and runtime turn completion. MCP annotations couldn't be read (12 of 20). Guest calls need only a handle and a message. No SDK in any language (6 of 15). 8+12+14+12+6 = 52.

Transparency & trust HelpDesk +5

HelpDesk 67

Closed service under Terms of Use dated 3 July 2026 naming Text, Inc. and covering APIs (15). Privacy Policy, DPA and Data Storage Policy placing HelpDesk data in the United States, per the 9 October check, not re-read on 4 November; DPA section 2.4 allows training on Client Data while the AI FAQ limits it to per-account internal models (17). Text's version lifecycle doesn't list this API and one webhook event is deprecated without a date (5, partial). 10 days' notice of new sub-processors and a stated storage location, with the sub-processor list on a script-drawn trust centre (12). 15 + 17 + 5 + 12 = 49.

Tobira Site Agent 62

Closed service with clear terms from HORIZONTEXUBERANTE, UNIPESSOAL LDA, registered in Portugal, under Portuguese law (15). The privacy policy and DPA (both 3 October 2026) agree with the terms. Retention is mostly by criteria, with some periods (guest sessions seven days, guest files 24 hours to seven days, attribution 30 days, a 30-day restoration window after agent deletion). Tobira says it doesn't train foundation models on conversations, and gives no guarantee for providers (22 of 30). The terms give 30 days' notice of material contractual changes, with no API deprecation policy (5 of 20). Providers are named with what they receive and where (mostly the United States) (16 of 20). 15+22+5+16 = 58.

Score by category

CategoryWeightHelpDeskTobira Site AgentEdge
Reliability16%6033HelpDesk +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6363even
Agent ergonomics13%4752Tobira Site Agent +5
Security & auth14%4453Tobira Site Agent +9
Payments & pricing10%5355Tobira Site Agent +2
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%925Tobira Site Agent +16
Transparency & trust7%6762HelpDesk +5
Negative events≤15-20
TotalD 48.9/100D 49.1/100

Facts side by side

FactHelpDeskTobira Site Agent
KindHTTP APIHTTP API
VendorText, Inc.Tobira
Hosted endpointhttps://api.helpdesk.comhttps://tobira.ai/mcp
TransportsHTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Text's Terms of Usenone
Read-only variant documentednoyes
llms.txtyesyes
Terms last updatedno date given2026-10-03
Privacy policy last updatedno date given2026-10-03
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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text

How the scores have moved

Verdicts

HelpDesk

The Ticketing API covers the ticket workflow, with OpenAPI 3.0.3 operations on 133 Markdown pages, cursor pagination and many list filters. No rate limit, error format or 429 handling is documented, tokens carry no ticket scopes, and no dated change to this API was found.

Tobira Site Agent

Visiting agents get a keyless guest API with a per-business OpenAPI file and booking actions that need the user's consent, and owners get an MCP server and REST API. The owner tool list is long and unpublished as schemas, there is no status page or changelog, and owner setup needs a browser sign-in.

Before you call either

HelpDesk

  1. Send Basic auth with the account ID as username and the personal access token as password, and always set a User-Agent header
  2. 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
  3. 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
  4. 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
  5. Budget for metered calls. Every request except those answered 500 counts against the Text subscription.

Tobira Site Agent

  1. Read the business's https://tobira.ai/@{handle}/for-ai page or guest-agent.json first, and use only the actions its manifest advertises
  2. Create one guest session and keep its token for follow-up questions. Don't open a new session per turn
  3. Get the user's explicit consent before prepare_booking or submit_authorized_contact, and reuse the same idempotency_key on retries
  4. Hand any checkout_url to the human to pay, and treat only booking_confirmed as a confirmed booking
  5. Don't put private details in the read-only ask?q= URL, which can appear in proxy and browser logs

Questions

Which is better for AI agents, HelpDesk or Tobira Site Agent?

Tobira Site Agent and HelpDesk score within a point of each other on agent readiness, 49.1 (D) and 48.9 (D). HelpDesk leads on reliability and transparency & trust.

Do HelpDesk and Tobira Site Agent need an API key?

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

Can an agent call HelpDesk and Tobira Site Agent without installing anything?

Yes. HelpDesk has a hosted endpoint at https://api.helpdesk.com and Tobira Site Agent at https://tobira.ai/mcp.

Other comparisons with HelpDesk or Tobira Site Agent

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.