Head to head · Support conversations · October 2026 research run

Tobira Site Agent vs Zoho Desk

Zoho Desk scores 69.1 (B) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in every scored category. Both do support conversations.

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

Which one, for what

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.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

Zoho Desk B

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

Ahead on

  • Reliability, 75 against 33
  • Schema & documentation, 72 against 63
  • Agent ergonomics, 67 against 52
  • Security & auth, 66 against 53
  • Payments & pricing, 60 against 55
  • Maintenance & community, 63 against 25
  • Transparency & trust, 79 against 62

Watch for

No SLA found, and the Terms of Service disclaim uninterrupted service

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 Zoho Desk +42

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.

Zoho Desk 75

Graded on the REST API v1, read as a hosted service. status.zoho.com redirects to us.zohostatus.com, which has a Zoho Desk component (20). Per the 8 October check, the status feed showed the Desk component returning to Operational on 3 September 2026 at the same minute as Zoho CRM, Books, Flow, SalesIQ and Deluge, with no other Desk entry since July, read as minor incidents only. us.zohostatus.com's robots.txt now answers a 404 carrying an access-denied page, so the host is treated as blocked and 9 October to 1 November is unread. The line holds on the recorded incidents and credits nothing for the unread stretch (20 of 30). Daily credits and concurrency are published with numbers per edition (15). A 429 at the daily limit carries Retry-After, and every response reports credits used and remaining. Concurrency 429s carry no Retry-After, and no idempotency or retry guidance for writes was found (10 of 15). No SLA found, and the Terms of Service disclaim uninterrupted service (0). v1 is the current documented version (10). 20+20+15+10+0+10 = 75.

Maintenance & community Zoho Desk +38

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.

Zoho Desk 63

The OpenAPI files were last changed on 29 October 2026, adding 176 operations and 25 resource files, three days before this check (30). Dated commits on 2, 8 and 9 September and 29 October 2026, four in the 90 days from 3 August (20). The developer forum named as the place for API notices loads by script, so replies and dates were unread, and no dated changelog was found (6 of 15). The only official SDK is for Java, version 1.3.0 for Java 7 and above, with no release date found (5 of 15). No public repository or CI for the SDK (2 of 10). 30+20+6+5+2 = 63.

Transparency & trust Zoho Desk +17

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.

Zoho Desk 79

Closed service under the Zoho Terms of Service, last updated 2 March 2022. The OpenAPI repository has no licence file (15 of 30). The privacy policy of 22 December 2025 says data is deleted from the active database within six months of account termination and from backups three months later. The DPA is sent on request by email (24 of 30). The API document promises forum notice and a transition period for deprecations without stating a length, and marks deprecated fields without dates (8 of 20). A sub-processor page exists, but its directory loads by script and we could not read the list. The data centre page names regions and cities (15 of 20).

Agent ergonomics Zoho Desk +15

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.

Zoho Desk 67

Graded on the REST API. Lists default to 10 records with at most 50, include adds related resources on request, and fields exists on some list calls only (18 of 25). from and limit, saved views, sortBy and module search with field filters. Deep offsets cost up to 100 credits a call and search stops at offset 4,999 (18 of 20). Errors carry errorCode, message, errorType and the field as a JSON Pointer (18 of 20). No idempotency key. Drafts can be saved before sending (6 of 20). One official SDK, for Java, and setup needs an hourly token refresh and the right regional host (7 of 15).

Security & auth Zoho Desk +13

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.

Zoho Desk 66

OAuth 2.0 with scopes per module and operation, one-hour access tokens and revocable refresh tokens (30). Less 10 because Zoho's OAuth guide documents the refresh call with the refresh token and client secret in the URL query string as one of three options (20 of 30). READ-only scopes, calls bound by the user's profile permissions, a draft and send-for-review path for replies, and a 60-day recycle bin for deleted tickets. Spam deletion is permanent and no approval step guards bulk updates (15 of 20). Tickets hold customer-written text and no prompt-injection guidance was found (3 of 15). A ticket history endpoint lists actions per ticket and a dashboard shows credit use. A portal-wide audit log for Desk was not established (8 of 15). security.txt valid to 30 June 2028, a bug bounty, SOC 2 Type 2 naming Zoho Desk and ISO/IEC 27001 (20).

Schema & documentation Zoho Desk +9

Tobira Site Agent 63

Each public handle publishes an OpenAPI 3.1 file for its guest transport. @tobira-ai's has five operations (ask, guest session, message, messages poll and action) with typed parameters such as q at 1 to 2,000 characters. The owner REST API has no published OpenAPI found, and the owner MCP server's schemas are only in tools/list, which answered 401 without a token (15 of 25). llms.txt, AGENTS.md, for-ai pages and a Markdown API and MCP guide (10). The guide says which credential fits which job and when not to use a surface (the read-only ask cannot book or take contact details), and lists tools by area, but no tool descriptions were readable (14 of 20). Action inputs are listed with ranges (days 1 to 31, default 7) and required fields, and guest OpenAPI parameters carry length limits (10 of 15). Request examples throughout and error classes 400, 401, 403, 404, 409, 422 and 429 with named codes such as stale_revision, csrf_failed and bootstrap_ip_limit (11 of 15). The guest OpenAPI carries a dated version (2026-05-27.stage1) but no public changelog was found (3 of 15). 15+10+14+10+11+3 = 63.

Zoho Desk 72

zoho/zohodesk-oas on GitHub holds OpenAPI 3.1.0 files for 210 resources and 1,077 operations after the 29 October 2026 update (185 and 911 before) (25). No llms.txt at zoho.com or desk.zoho.com and no Markdown docs found (0). Every operation carries a description that states the purpose, often with a note on limits, and little on when not to use one (14 of 20). Parameters carry enums, patterns and length limits, and replies use a discriminated schema per channel. Custom fields make record bodies open (12 of 15). The API document has a curl sample and response per endpoint and a list of error codes, and 802 operations declare an error response (14 of 15). The version is in the path and a compatibility statement promises forum notice of changes, with no dated changelog found (7 of 15). 25+0+14+12+14+7 = 72.

Score by category

CategoryWeightTobira Site AgentZoho DeskEdge
Reliability16%3375Zoho Desk +42
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6372Zoho Desk +9
Agent ergonomics13%5267Zoho Desk +15
Security & auth14%5366Zoho Desk +13
Payments & pricing10%5560Zoho Desk +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2563Zoho Desk +38
Transparency & trust7%6279Zoho Desk +17
Negative events≤1500
TotalD 49.1/100B 69.1/100

Facts side by side

FactTobira Site AgentZoho Desk
KindHTTP APIHTTP API
VendorTobiraZoho
Hosted endpointhttps://tobira.ai/mcpno (local only)
TransportsStreamable HTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service under Zoho's Terms of Service. The OpenAPI repository on GitHub has no licence file
Read-only variant documentedyesno
llms.txtyesno
Last releasenone2026-10-29
Terms last updated2026-10-032022-03-02
Privacy policy last updated2026-10-032025-12-22
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviewsnone3.5/5 (4)

How the scores have moved

Verdicts

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.

Zoho Desk

Public OpenAPI 3.1 files cover 1,077 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.

Before you call either

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

Zoho Desk

  1. Use the api_domain returned with the token. Each data centre has its own host, such as desk.zoho.com, desk.zoho.eu and desk.zoho.in
  2. Send Authorization: Zoho-oauthtoken <token> and refresh hourly. Put refresh parameters in the POST body, not the URL
  3. Create replies with POST /api/v1/tickets/{id}/draftReply, then sendDraft or sendForReview. sendReply emails the customer
  4. Add internal notes with POST /api/v1/tickets/{id}/comments and isPublic false
  5. Page with from and limit (50 at most). Deep offsets cost more credits, from 3 a call under 2,000 records to 100 above 100,000

Questions

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

Zoho Desk scores 69.1 (B) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in every scored category.

Do Tobira Site Agent and Zoho Desk need an API key?

Tobira Site Agent takes an API key or an OAuth sign-in. Zoho Desk uses an OAuth sign-in.

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

Tobira Site Agent has a hosted endpoint at https://tobira.ai/mcp. No hosted endpoint is listed for Zoho Desk.

Other comparisons with Tobira Site Agent or Zoho Desk

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.