{
  "data": {
    "a": {
      "slug": "helpdesk",
      "name": "HelpDesk",
      "vendor": "Text, Inc.",
      "vendorUrl": "https://www.text.com",
      "company": "helpdesk.com",
      "kind": "http-api",
      "category": "support",
      "summary": "HelpDesk is a ticketing system from Text, Inc. Its REST API at api.helpdesk.com, which Text also documents as the Ticketing API, creates, lists and updates tickets, messages, private notes, tags, teams, rules, reports and webhooks.",
      "url": "https://www.anchorterminal.com/tools/helpdesk",
      "markdownUrl": "https://www.anchorterminal.com/tools/helpdesk.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/helpdesk.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/helpdesk.json",
      "dns": "helpdesk.grade.anchorterminal.com",
      "license": "Proprietary service under Text's Terms of Use",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.helpdesk.com",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Self-serve. A personal access token is created in Text's Developer Console (or in the Text app under Settings, API access) with the `accounts--my:ro` scope and sent as Basic auth, with the account ID as username and the token as password. OAuth 2.1 authorisation code grant with PKCE is recommended for production, with access tokens valid 28,800 seconds and refresh tokens. No ticket-level scopes exist. A token acts with its user's role (Administrator, Agent or Viewer), and scopes on a personal access token can't be changed after creation.",
      "pricing": "paid",
      "pricingNotes": "Essential $19 a user a month billed yearly ($25 monthly), Growth $79 ($99 monthly), Enterprise by quote. 14-day trial with no card and no free plan found. API calls count against the Text subscription, which includes 10,000 a month on Essential and 20,000 on Growth, with 100,000 more for $29.50; requests answered 500 aren't counted (checked 2026-11-04).",
      "priceSummary": "$19 / seat-mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in Text's Ticketing docs, API pricing page or the HelpDesk pricing page (checked 2026-11-04).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://www.text.com/docs/api/ticketing/index.md",
      "llmsTxt": "https://www.text.com/docs/llms.txt",
      "openapi": "https://www.text.com/docs/api/ticketing/openapi.json",
      "capabilities": [
        "support.tickets",
        "support.notes",
        "support.webhooks"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "paid",
        "trial",
        "openapi",
        "llms-txt",
        "oauth",
        "pat",
        "webhooks",
        "status-page",
        "audit-log",
        "soc2"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 48.9,
        "grade": "D",
        "agentReady": false,
        "rank": 1193,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 16,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 47,
          "maintenance": 9,
          "payments": 53,
          "reliability": 60,
          "schema": 63,
          "security": 44,
          "transparency": 67
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": -2,
        "negativeNotes": [
          "2026-10-09, still true on 2026-11-04. 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) counts every API request against the subscription and sells 100,000 more for $29.50. Two points for a pricing claim the vendor's own API pages contradict."
        ],
        "verdict": "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.",
        "bestFor": "A team already on HelpDesk or Text that wants an agent to read queues, draft replies, add private notes and change status over REST.",
        "strengths": [
          "OpenAPI 3.0.3 operations embedded in 133 Markdown method pages, linked from Text's llms.txt",
          "Ticket lists take cursor pagination, `pageSize` up to 100, three sort keys and many filters",
          "Status page shows no incidents from 6 August to 4 November 2026",
          "14-day trial without a card, with plan prices in Markdown at www.helpdesk.com/pricing.md"
        ],
        "weaknesses": [
          "No rate limit, 429 behaviour or idempotency key found in the docs",
          "Only 200 responses documented, so error bodies are unknown before a call",
          "No ticket-level scopes, so a token has its user's full role",
          "No changelog entry names the Ticketing API",
          "The HelpDesk pricing page omits the metered API calls that Text's API pricing page charges"
        ],
        "agentNotes": [
          "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. Every request except those answered 500 counts against the Text subscription."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 48.9
          }
        ],
        "editorialScores": {
          "ergonomics": 47,
          "maintenance": 9,
          "payments": 53,
          "reliability": 60,
          "schema": 63,
          "security": 44,
          "transparency": 49
        },
        "provenanceScore": 84,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl \"https://api.helpdesk.com/v1/tickets?pageSize=3\" \\\n  -H \"Authorization: Basic \u003cbase64_encoded_token\u003e\" \\\n  -H \"User-Agent: my-agent/1.0\""
      },
      "letme": {
        "capability": "https://letme.dev/support.tickets",
        "tool": "https://letme.dev/helpdesk"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Essential",
          "unit": "seat-month",
          "usd": 19,
          "note": "billed yearly; $25 billed monthly"
        },
        {
          "item": "Growth",
          "unit": "seat-month",
          "usd": 79,
          "note": "billed yearly; $99 billed monthly"
        },
        {
          "item": "Extra API calls",
          "unit": "1k-requests",
          "usd": 0.295,
          "note": "$29.50 per 100,000 beyond the plan's allowance, per Text's docs; platform.text.com lists $0.27 per 1,000 private requests"
        }
      ],
      "provenance": {
        "legalEntity": "Text, Inc.",
        "domain": "helpdesk.com",
        "domainRegistered": "1994-03-29",
        "endpointOnVendorDomain": true,
        "terms": "https://www.helpdesk.com/legal/terms-of-use/",
        "privacy": "https://www.helpdesk.com/legal/privacy-policy/",
        "statusPage": "https://status.helpdesk.com",
        "changelog": "https://www.text.com/docs/api/changelog.md",
        "securityTxt": "none",
        "checked": "2026-11-04",
        "notes": [
          "The Terms of Use (last update 07/03/2026, read as 3 July 2026) name Text, Inc., 101 Arch Street, 8th Floor, Boston, MA 02110, define the Services to include APIs, and incorporate the Privacy Policy and the DPA.",
          "The Privacy Policy (last update 09/03/2026, read as 3 September 2026) covers Text as controller and as processor of Client Personal Data.",
          "The API answers at api.helpdesk.com. Sign-in, the Developer Console and the developer docs are on livechat.com, platform.text.com and text.com, other domains of the same vendor.",
          "The changelog link is Text's API changelog. It has no entry tagged for the Ticketing API.",
          "www.helpdesk.com/.well-known/security.txt returns 404.",
          "A Developer Terms addendum at platform.text.com/developer-terms also governs API use.",
          "api.helpdesk.com answers robots.txt with 403 RBAC access denied (4 November 2026), so the API is read from Text's docs at www.text.com.",
          "www.text.com/.well-known/security.txt also returns 404."
        ],
        "score": 84
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/helpdesk.json",
      "live": {
        "slug": "helpdesk",
        "probe": {
          "target": "https://api.helpdesk.com",
          "method": "get",
          "lastAt": "2026-11-18T23:01:34.2567778Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 320,
          "authRequired": false,
          "uptime24h": 98.76,
          "uptime30d": 99.92,
          "p50ms24h": 359,
          "p95ms24h": 661,
          "samples24h": 241,
          "samples30d": 7840,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 247
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 242
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 243
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 231,
              "ok": 228
            }
          ],
          "since": "2026-10-09T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.helpdesk.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T23:00:31.326766025Z"
        },
        "securityTxt": {
          "url": "https://helpdesk.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:32:01.198550087Z"
        },
        "llmsTxt": {
          "url": "https://www.text.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:38.458975266Z"
        },
        "domain": {
          "domain": "helpdesk.com",
          "registered": "1994-03-29",
          "source": "https://rdap.verisign.com/com/v1/domain/helpdesk.com",
          "checkedAt": "2026-11-15T15:29:37.677565756Z"
        },
        "pages": [
          {
            "url": "https://www.text.com/docs/api/changelog.md",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T22:10:21.669275123Z",
            "changedAt": "2026-11-16T20:48:40.823788791Z",
            "fingerprint": "5839c9ce737a"
          },
          {
            "url": "https://www.helpdesk.com/legal/privacy-policy/",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-18T22:04:02.630790024Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "76b6334d3759"
          },
          {
            "url": "https://www.helpdesk.com/legal/terms-of-use/",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-18T22:04:04.946497618Z",
            "changedAt": "2026-11-13T18:40:13.569828917Z",
            "fingerprint": "233f4e16f48a"
          }
        ],
        "updatedAt": "2026-11-18T23:01:34.2567778Z"
      },
      "streak": {
        "days": 40,
        "from": "2026-10-09",
        "sinceWatching": true,
        "best": 40
      }
    },
    "answer": "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 \u0026 trust.",
    "b": {
      "slug": "tobira-site-agent",
      "name": "Tobira Site Agent",
      "vendor": "Tobira",
      "vendorUrl": "https://tobira.ai",
      "company": "tobira.ai",
      "kind": "http-api",
      "category": "support",
      "summary": "Tobira Site Agent is a hosted chat agent for business websites. It answers visitors and visiting AI agents from approved content and books meetings, through a public guest API, with an MCP server and REST API for owners.",
      "url": "https://www.anchorterminal.com/tools/tobira-site-agent",
      "markdownUrl": "https://www.anchorterminal.com/tools/tobira-site-agent.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tobira-site-agent.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tobira-site-agent.json",
      "dns": "tobira-site-agent.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://tobira.ai/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Owner MCP and REST: an agent-scoped API key or OAuth after the owner signs in through Clerk in a browser. Keys rotate through `tobira_rotate_api_key`. Collaborators get scoped tokens, visitors company-scoped visitor MCP tokens. The guest API needs no account and issues a session token.",
      "pricing": "freemium",
      "pricingNotes": "Free $0 with the owner's own OpenAI or OpenRouter key, up to 1,000 conversations a month, no card. Lite $49, Start $169, Business $399, Premium $799 a month (lower on six-month or yearly billing), plus optional setup. 14-day money-back. Visiting agents pay nothing.",
      "priceSummary": "$49 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, the API guide, the guest OpenAPI or the pricing section (checked 2026-11-18). Bookings return a checkout URL for a human to pay.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://tobira.ai/for-agents.md",
      "llmsTxt": "https://tobira.ai/llms.txt",
      "openapi": "https://tobira.ai/@tobira-ai/openapi.json",
      "capabilities": [
        "support.conversations",
        "support.contacts",
        "support.notes",
        "support.webhooks"
      ],
      "tags": [
        "hosted",
        "mcp",
        "remote-mcp",
        "oauth",
        "api-key",
        "no-auth",
        "closed-source",
        "freemium",
        "free-tier",
        "no-card",
        "llms-txt",
        "openapi",
        "webhooks",
        "security-txt",
        "no-status-page"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 49.1,
        "grade": "D",
        "agentReady": false,
        "rank": 1185,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 15,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 52,
          "maintenance": 25,
          "payments": 55,
          "reliability": 33,
          "schema": 63,
          "security": 53,
          "transparency": 62
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "Businesses that want one chat agent on their site to answer people and visiting AI assistants and book meetings.",
        "strengths": [
          "A public, keyless guest API per business (`/api/v1/guest/session`, `message`, `messages`, `action`) described by a per-handle OpenAPI 3.1 file",
          "Bookings and contact submissions need `authorized_by_user: true` and an idempotency key, and payment goes to the human through a checkout URL",
          "Separate credentials for guests, visitors, collaborators and owners, with agent-scoped owner API keys and OAuth on the owner MCP server",
          "A free plan with the owner's own OpenAI or OpenRouter key, up to 1,000 conversations a month, with no card",
          "llms.txt, AGENTS.md, a per-handle for-ai page and a 46,000-character API and MCP guide written for agents"
        ],
        "weaknesses": [
          "No status page, changelog or SLA, and the terms promise no particular uptime",
          "The owner MCP server lists about 40 tools with no toolsets, and their schemas are only in `tools/list` behind a sign-in",
          "Creating or claiming a Site Agent needs the owner's browser sign-in. An API key only manages an existing agent",
          "The guest messages poll documents the session token as a URL query parameter",
          "Many routes are 'rollout gated' or early access, and the guide says a listed tool may not be enabled for a given account"
        ],
        "agentNotes": [
          "Read the business's `https://tobira.ai/@{handle}/for-ai` page or `guest-agent.json` first, and use only the actions its manifest advertises",
          "Create one guest session and keep its token for follow-up questions. Don't open a new session per turn",
          "Get the user's explicit consent before `prepare_booking` or `submit_authorized_contact`, and reuse the same `idempotency_key` on retries",
          "Hand any `checkout_url` to the human to pay, and treat only `booking_confirmed` as a confirmed booking",
          "Don't put private details in the read-only `ask?q=` URL, which can appear in proxy and browser logs"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 49.1
          }
        ],
        "editorialScores": {
          "ergonomics": 52,
          "maintenance": 25,
          "payments": 55,
          "reliability": 33,
          "schema": 63,
          "security": 53,
          "transparency": 58
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://tobira.ai/api/v1/guest/session -H 'Content-Type: application/json' -d '{\"handle\":\"tobira-ai\",\"visitor_type\":\"visitor_ai_agent\",\"transport\":\"json_guest_api\",\"source\":\"site_agent\",\"response_format\":\"json_with_structured\"}'",
        "claudeCode": "claude mcp add --transport http tobira \"https://tobira.ai/mcp?agent=YOUR_HANDLE\""
      },
      "letme": {
        "capability": "https://letme.dev/support.conversations",
        "tool": "https://letme.dev/tobira-site-agent"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Lite plan",
          "unit": "month",
          "usd": 49,
          "note": "$39 a month billed yearly, about 300 conversations with Tobira's model"
        },
        {
          "item": "Start plan",
          "unit": "month",
          "usd": 169,
          "note": "$139 a month billed yearly, about 900 conversations"
        },
        {
          "item": "Business plan",
          "unit": "month",
          "usd": 399,
          "note": "$319 a month billed yearly, about 2,400 conversations"
        },
        {
          "item": "Premium plan",
          "unit": "month",
          "usd": 799,
          "note": "$639 a month billed yearly, about 4,800 conversations"
        }
      ],
      "provenance": {
        "legalEntity": "HORIZONTEXUBERANTE, UNIPESSOAL LDA",
        "domain": "tobira.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://tobira.ai/terms",
        "privacy": "https://tobira.ai/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The terms, privacy policy and DPA, each effective 3 October 2026, name HORIZONTEXUBERANTE, UNIPESSOAL LDA, registered in Portugal, under Portuguese law with Lisbon courts for businesses. No registration number or address appears on them.",
          "tobira.ai/robots.txt allows all agents, disallows /dashboard, /onboarding and /api/ but allows /api/v1/guest/ and guest-agent.json files.",
          "/.well-known/security.txt names security@tobira.ai and expires on 5 November 2027.",
          "No status page or changelog found.",
          "The site's for-ai pages carry instructions addressed to AI assistants. We read them as data."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/tobira-site-agent.json",
      "live": {
        "slug": "tobira-site-agent",
        "probe": {
          "target": "https://tobira.ai/mcp",
          "method": "get",
          "lastAt": "2026-11-18T23:02:00.614656145Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 250,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 356,
          "p95ms24h": 625,
          "samples24h": 14,
          "samples30d": 14,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 14,
              "ok": 14
            }
          ],
          "since": "2026-11-18T21:38:35.715051143Z"
        },
        "updatedAt": "2026-11-18T23:02:00.614656145Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 27,
        "category": "reliability",
        "leads": "helpdesk",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 60,
          "b": 33
        }
      },
      {
        "by": 16,
        "category": "maintenance",
        "leads": "tobira-site-agent",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 9,
          "b": 25
        }
      },
      {
        "by": 9,
        "category": "security",
        "leads": "tobira-site-agent",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 44,
          "b": 53
        }
      },
      {
        "by": 5,
        "category": "ergonomics",
        "leads": "tobira-site-agent",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 47,
          "b": 52
        }
      },
      {
        "by": 5,
        "category": "transparency",
        "leads": "helpdesk",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 67,
          "b": 62
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Text, Inc.",
        "b": "Tobira",
        "name": "Vendor"
      },
      {
        "a": "https://api.helpdesk.com",
        "b": "https://tobira.ai/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Text's Terms of Use",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "no date given",
        "b": "2026-10-03",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-10-03",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 trust.",
        "question": "Which is better for AI agents, HelpDesk or Tobira Site Agent?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do HelpDesk and Tobira Site Agent need an API key?"
      },
      {
        "answer": "Yes. HelpDesk has a hosted endpoint at https://api.helpdesk.com and Tobira Site Agent at https://tobira.ai/mcp.",
        "question": "Can an agent call HelpDesk and Tobira Site Agent without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 60 against 33",
          "Transparency \u0026 trust, 67 against 62"
        ],
        "also": null,
        "goodFor": "A team already on HelpDesk or Text that wants an agent to read queues, draft replies, add private notes and change status over REST.",
        "slug": "helpdesk",
        "watchFor": "No rate limit, 429 behaviour or idempotency key found in the docs"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 52 against 47",
          "Security \u0026 auth, 53 against 44",
          "Maintenance \u0026 community, 25 against 9"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Businesses that want one chat agent on their site to answer people and visiting AI assistants and book meetings.",
        "slug": "tobira-site-agent",
        "watchFor": "No status page, changelog or SLA, and the terms promise no particular uptime"
      }
    ],
    "history": {
      "helpdesk": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.3,
          "from": 46.6,
          "fromGrade": "D",
          "to": 48.9,
          "toGrade": "D"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-04",
          "delta": -3.7,
          "from": 50.3,
          "fromGrade": "D",
          "to": 46.6,
          "toGrade": "D"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-10-28",
          "delta": -0.1,
          "from": 50.4,
          "fromGrade": "D",
          "to": 50.3,
          "toGrade": "D"
        }
      ],
      "tobira-site-agent": null
    },
    "job": {
      "capability": "support.notes",
      "name": "Support notes"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/chatwoot-vs-helpdesk.json",
        "title": "Chatwoot API vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/chatwoot-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crisp-vs-helpdesk.json",
        "title": "Crisp API + MCP vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/crisp-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dixa-vs-helpdesk.json",
        "title": "Dixa vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/dixa-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/drag-vs-helpdesk.json",
        "title": "Drag vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/drag-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/freescout-vs-helpdesk.json",
        "title": "FreeScout vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/freescout-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/freshdesk-vs-helpdesk.json",
        "title": "Freshdesk API + MCP vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/freshdesk-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/front-vs-helpdesk.json",
        "title": "Front API + MCP vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/front-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gorgias-vs-helpdesk.json",
        "title": "Gorgias API + MCP vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/gorgias-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/help-scout-vs-helpdesk.json",
        "title": "Help Scout API + MCP vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/help-scout-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-intercom.json",
        "title": "HelpDesk vs Intercom API + MCP",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-intercom"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-kustomer.json",
        "title": "HelpDesk vs Kustomer",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-kustomer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-liveagent.json",
        "title": "HelpDesk vs LiveAgent",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-liveagent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-plain.json",
        "title": "HelpDesk vs Plain API + MCP",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-plain"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-pylon.json",
        "title": "HelpDesk vs Pylon API + MCP",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-pylon"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-zammad.json",
        "title": "HelpDesk vs Zammad",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-zammad"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-zendesk.json",
        "title": "HelpDesk vs Zendesk Support API",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-zendesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-zoho-desk.json",
        "title": "HelpDesk vs Zoho Desk",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-zoho-desk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chatway-mcp-vs-tobira-site-agent.json",
        "title": "Chatway MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/chatway-mcp-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chatwoot-vs-tobira-site-agent.json",
        "title": "Chatwoot API vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/chatwoot-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crisp-vs-tobira-site-agent.json",
        "title": "Crisp API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/crisp-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dixa-vs-tobira-site-agent.json",
        "title": "Dixa vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/dixa-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/drag-vs-tobira-site-agent.json",
        "title": "Drag vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/drag-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/freescout-vs-tobira-site-agent.json",
        "title": "FreeScout vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/freescout-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/freshdesk-vs-tobira-site-agent.json",
        "title": "Freshdesk API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/freshdesk-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/front-vs-tobira-site-agent.json",
        "title": "Front API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/front-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gladly-vs-tobira-site-agent.json",
        "title": "Gladly vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/gladly-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gorgias-vs-tobira-site-agent.json",
        "title": "Gorgias API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/gorgias-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/help-scout-vs-tobira-site-agent.json",
        "title": "Help Scout API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/help-scout-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/intercom-vs-tobira-site-agent.json",
        "title": "Intercom API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/intercom-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kustomer-vs-tobira-site-agent.json",
        "title": "Kustomer vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/kustomer-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/liveagent-vs-tobira-site-agent.json",
        "title": "LiveAgent vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/liveagent-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/missive-vs-tobira-site-agent.json",
        "title": "Missive API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/missive-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plain-vs-tobira-site-agent.json",
        "title": "Plain API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/plain-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pylon-vs-tobira-site-agent.json",
        "title": "Pylon API + MCP vs Tobira Site Agent",
        "url": "https://www.anchorterminal.com/compare/pylon-vs-tobira-site-agent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tobira-site-agent-vs-zammad.json",
        "title": "Tobira Site Agent vs Zammad",
        "url": "https://www.anchorterminal.com/compare/tobira-site-agent-vs-zammad"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tobira-site-agent-vs-zendesk.json",
        "title": "Tobira Site Agent vs Zendesk Support API",
        "url": "https://www.anchorterminal.com/compare/tobira-site-agent-vs-zendesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tobira-site-agent-vs-zoho-desk.json",
        "title": "Tobira Site Agent vs Zoho Desk",
        "url": "https://www.anchorterminal.com/compare/tobira-site-agent-vs-zoho-desk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/chatway-mcp-vs-helpdesk.json",
        "title": "Chatway MCP vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/chatway-mcp-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gladly-vs-helpdesk.json",
        "title": "Gladly vs HelpDesk",
        "url": "https://www.anchorterminal.com/compare/gladly-vs-helpdesk"
      },
      {
        "json": "https://www.anchorterminal.com/compare/helpdesk-vs-missive.json",
        "title": "HelpDesk vs Missive API + MCP",
        "url": "https://www.anchorterminal.com/compare/helpdesk-vs-missive"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 27,
        "edge": "helpdesk",
        "helpdesk": 60,
        "key": "reliability",
        "name": "Reliability",
        "tobira-site-agent": 33,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 0,
        "edge": "",
        "helpdesk": 63,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "tobira-site-agent": 63,
        "weight": 13
      },
      {
        "by": 5,
        "edge": "tobira-site-agent",
        "helpdesk": 47,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "tobira-site-agent": 52,
        "weight": 13
      },
      {
        "by": 9,
        "edge": "tobira-site-agent",
        "helpdesk": 44,
        "key": "security",
        "name": "Security \u0026 auth",
        "tobira-site-agent": 53,
        "weight": 14
      },
      {
        "by": 2,
        "edge": "tobira-site-agent",
        "helpdesk": 53,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "tobira-site-agent": 55,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 16,
        "edge": "tobira-site-agent",
        "helpdesk": 9,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "tobira-site-agent": 25,
        "weight": 7
      },
      {
        "by": 5,
        "edge": "helpdesk",
        "helpdesk": 67,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "tobira-site-agent": 62,
        "weight": 7
      }
    ],
    "summary": "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 \u0026 trust. Both do support notes.",
    "tasks": null,
    "tutorials": [],
    "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent",
    "json": "https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent.min.md"
  },
  "markdown": "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 \u0026 trust. Both do support notes.\n\n- HelpDesk: grade D, 48.9/100, rank #1193 of 1557. Markdown https://www.anchorterminal.com/tools/helpdesk.md · JSON https://www.anchorterminal.com/api/v1/tools/helpdesk.json\n- Tobira Site Agent: grade D, 49.1/100, rank #1185 of 1557. Markdown https://www.anchorterminal.com/tools/tobira-site-agent.md · JSON https://www.anchorterminal.com/api/v1/tools/tobira-site-agent.json\n- Best customer support and helpdesk APIs for AI agents: https://www.anchorterminal.com/best/support/index.md\n- All 232 support comparisons: https://www.anchorterminal.com/compare/support/index.md\n\n## Which one, for what\n\n### HelpDesk (D)\n\nGood 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.\n\nAhead on:\n- Reliability, 60 against 33\n- Transparency \u0026 trust, 67 against 62\n\nWatch for: No rate limit, 429 behaviour or idempotency key found in the docs\n\n### Tobira Site Agent (D)\n\nGood for: Businesses that want one chat agent on their site to answer people and visiting AI assistants and book meetings.\n\nAhead on:\n- Agent ergonomics, 52 against 47\n- Security \u0026 auth, 53 against 44\n- Maintenance \u0026 community, 25 against 9\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No status page, changelog or SLA, and the terms promise no particular uptime\n\n\n## Why the edge\n\n### Reliability: HelpDesk +27\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: Tobira Site Agent +16\n\n- 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.\n- 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.\n\n### Security \u0026 auth: Tobira Site Agent +9\n\n- 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.\n- 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.\n\n### Agent ergonomics: Tobira Site Agent +5\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: HelpDesk +5\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | HelpDesk | Tobira Site Agent | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 60 | 33 | HelpDesk +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 63 | 63 | even |\n| Agent ergonomics | 13% | 47 | 52 | Tobira Site Agent +5 |\n| Security \u0026 auth | 14% | 44 | 53 | Tobira Site Agent +9 |\n| Payments \u0026 pricing | 10% | 53 | 55 | Tobira Site Agent +2 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 9 | 25 | Tobira Site Agent +16 |\n| Transparency \u0026 trust | 7% | 67 | 62 | HelpDesk +5 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **48.9 · D** | **49.1 · D** | |\n\n## Facts side by side\n\n| Fact | HelpDesk | Tobira Site Agent |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Text, Inc. | Tobira |\n| Hosted endpoint | `https://api.helpdesk.com` | `https://tobira.ai/mcp` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Text's Terms of Use | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Terms last updated | no date given | 2026-10-03 |\n| Privacy policy last updated | no date given | 2026-10-03 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## How the scores have moved\n\n### HelpDesk\n\n- +2.3 on 13 November 2026: checklist\n- -3.7 on 4 November 2026: correction\n- -0.1 on 28 October 2026: correction\n\n### Tobira Site Agent\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### HelpDesk\n\n1. Send Basic auth with the account ID as username and the personal access token as password, and always set a `User-Agent` header\n2. 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\n3. 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\n4. 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\n5. Budget for metered calls. Every request except those answered 500 counts against the Text subscription.\n\n### Tobira Site Agent\n\n1. Read the business's `https://tobira.ai/@{handle}/for-ai` page or `guest-agent.json` first, and use only the actions its manifest advertises\n2. Create one guest session and keep its token for follow-up questions. Don't open a new session per turn\n3. Get the user's explicit consent before `prepare_booking` or `submit_authorized_contact`, and reuse the same `idempotency_key` on retries\n4. Hand any `checkout_url` to the human to pay, and treat only `booking_confirmed` as a confirmed booking\n5. Don't put private details in the read-only `ask?q=` URL, which can appear in proxy and browser logs\n\n## Questions\n\n### Which is better for AI agents, HelpDesk or Tobira Site Agent?\n\nTobira 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 \u0026 trust.\n\n### Do HelpDesk and Tobira Site Agent need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call HelpDesk and Tobira Site Agent without installing anything?\n\nYes. HelpDesk has a hosted endpoint at https://api.helpdesk.com and Tobira Site Agent at https://tobira.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent.json, and with the fewest tokens: https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"helpdesk\", \"b\": \"tobira-site-agent\"}`. From a terminal: `anchor compare helpdesk tobira-site-agent`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/helpdesk.json and https://www.anchorterminal.com/api/v1/tools/tobira-site-agent.json\n\n## Other comparisons with HelpDesk or Tobira Site Agent\n\n- [Chatwoot API vs HelpDesk](https://www.anchorterminal.com/compare/chatwoot-vs-helpdesk.md)\n- [Crisp API + MCP vs HelpDesk](https://www.anchorterminal.com/compare/crisp-vs-helpdesk.md)\n- [Dixa vs HelpDesk](https://www.anchorterminal.com/compare/dixa-vs-helpdesk.md)\n- [Drag vs HelpDesk](https://www.anchorterminal.com/compare/drag-vs-helpdesk.md)\n- [FreeScout vs HelpDesk](https://www.anchorterminal.com/compare/freescout-vs-helpdesk.md)\n- [Freshdesk API + MCP vs HelpDesk](https://www.anchorterminal.com/compare/freshdesk-vs-helpdesk.md)\n- [Front API + MCP vs HelpDesk](https://www.anchorterminal.com/compare/front-vs-helpdesk.md)\n- [Gorgias API + MCP vs HelpDesk](https://www.anchorterminal.com/compare/gorgias-vs-helpdesk.md)\n- [Help Scout API + MCP vs HelpDesk](https://www.anchorterminal.com/compare/help-scout-vs-helpdesk.md)\n- [HelpDesk vs Intercom API + MCP](https://www.anchorterminal.com/compare/helpdesk-vs-intercom.md)\n- [HelpDesk vs Kustomer](https://www.anchorterminal.com/compare/helpdesk-vs-kustomer.md)\n- [HelpDesk vs LiveAgent](https://www.anchorterminal.com/compare/helpdesk-vs-liveagent.md)\n- [HelpDesk vs Plain API + MCP](https://www.anchorterminal.com/compare/helpdesk-vs-plain.md)\n- [HelpDesk vs Pylon API + MCP](https://www.anchorterminal.com/compare/helpdesk-vs-pylon.md)\n- [HelpDesk vs Zammad](https://www.anchorterminal.com/compare/helpdesk-vs-zammad.md)\n- [HelpDesk vs Zendesk Support API](https://www.anchorterminal.com/compare/helpdesk-vs-zendesk.md)\n- [HelpDesk vs Zoho Desk](https://www.anchorterminal.com/compare/helpdesk-vs-zoho-desk.md)\n- [Chatway MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/chatway-mcp-vs-tobira-site-agent.md)\n- [Chatwoot API vs Tobira Site Agent](https://www.anchorterminal.com/compare/chatwoot-vs-tobira-site-agent.md)\n- [Crisp API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/crisp-vs-tobira-site-agent.md)\n- [Dixa vs Tobira Site Agent](https://www.anchorterminal.com/compare/dixa-vs-tobira-site-agent.md)\n- [Drag vs Tobira Site Agent](https://www.anchorterminal.com/compare/drag-vs-tobira-site-agent.md)\n- [FreeScout vs Tobira Site Agent](https://www.anchorterminal.com/compare/freescout-vs-tobira-site-agent.md)\n- [Freshdesk API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/freshdesk-vs-tobira-site-agent.md)\n- [Front API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/front-vs-tobira-site-agent.md)\n- [Gladly vs Tobira Site Agent](https://www.anchorterminal.com/compare/gladly-vs-tobira-site-agent.md)\n- [Gorgias API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/gorgias-vs-tobira-site-agent.md)\n- [Help Scout API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/help-scout-vs-tobira-site-agent.md)\n- [Intercom API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/intercom-vs-tobira-site-agent.md)\n- [Kustomer vs Tobira Site Agent](https://www.anchorterminal.com/compare/kustomer-vs-tobira-site-agent.md)\n- [LiveAgent vs Tobira Site Agent](https://www.anchorterminal.com/compare/liveagent-vs-tobira-site-agent.md)\n- [Missive API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/missive-vs-tobira-site-agent.md)\n- [Plain API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/plain-vs-tobira-site-agent.md)\n- [Pylon API + MCP vs Tobira Site Agent](https://www.anchorterminal.com/compare/pylon-vs-tobira-site-agent.md)\n- [Tobira Site Agent vs Zammad](https://www.anchorterminal.com/compare/tobira-site-agent-vs-zammad.md)\n- [Tobira Site Agent vs Zendesk Support API](https://www.anchorterminal.com/compare/tobira-site-agent-vs-zendesk.md)\n- [Tobira Site Agent vs Zoho Desk](https://www.anchorterminal.com/compare/tobira-site-agent-vs-zoho-desk.md)\n- [Chatway MCP vs HelpDesk](https://www.anchorterminal.com/compare/chatway-mcp-vs-helpdesk.md)\n- [Gladly vs HelpDesk](https://www.anchorterminal.com/compare/gladly-vs-helpdesk.md)\n- [HelpDesk vs Missive API + MCP](https://www.anchorterminal.com/compare/helpdesk-vs-missive.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "HelpDesk vs Tobira Site Agent",
        "url": ""
      }
    ],
    "description": "Tobira Site Agent and HelpDesk score within a point of each other for support notes, 49.1 and 48.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "HelpDesk D 48.9",
      "Tobira Site Agent D 49.1",
      "scores"
    ],
    "h1": "HelpDesk vs Tobira Site Agent",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/helpdesk-vs-tobira-site-agent",
    "published": "2026-10-01",
    "section": "tools",
    "title": "HelpDesk vs Tobira Site Agent for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/helpdesk-vs-tobira-site-agent"
  },
  "tokens": {
    "markdown": 4650,
    "slim": 930
  },
  "version": 1
}
