Head to head · Support conversations · October 2026 research run

Gorgias API + MCP vs Tobira Site Agent

Gorgias API + MCP scores 57 (C) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 4 of 7 scored categories. Tobira Site Agent leads on schema & documentation and agent ergonomics. Both do support conversations.

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

Which one, for what

Gorgias API + MCP C

Best for Shopify and ecommerce brands that want order context in the ticket and an agent to triage and tag.

Ahead on

  • Reliability, 75 against 33
  • Transparency & trust, 80 against 62

Watch for

Private API keys use Basic auth with the user's email and have no scopes

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

  • Schema & documentation, 63 against 53
  • Agent ergonomics, 52 against 47

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 Gorgias API + MCP +42

Gorgias API + MCP 75

Atlassian Statuspage at status.gorgias.com with a REST API component beside the web app, integrations and helpdesk clusters (20). The Atom feed's 25 entries run from 15 July to 4 November 2026, so the 90 days from 6 August are fully read. 21 incidents were posted from 11 August, each scoped to one function, channel, integration or cluster, or to a subset of customers, such as the cloud provider network incident of 1 September (15:19 to 18:59 UTC), login on 30 October and Workflows calls to the Helpdesk API blocked by a Cloudflare rule on 2 and 3 November. None says the REST API was down, so all read as partial, minor incidents (20). Leaky bucket of 40 requests per 20 seconds for API keys and 80 for OAuth apps, a 10-second window on Enterprise (15). 429 with Retry-after and a usage header, and no safe-retry or idempotency guidance for writes, which this benchmark scores 10 (10). No uptime SLA found (0). The REST API is GA, and the MCP help article no longer carries a beta label (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

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.

Transparency & trust Gorgias API + MCP +18

Gorgias API + MCP 80

Closed service with published terms, the Master Subscription Agreement and website terms both last revised 30 March 2026 (15). Per the 1 October check, the privacy notice (revised 30 March 2026) keeps data while you hold an account, with a DPA and a sub-processor list. The changelog adds email retention (headers deleted and bodies archived 30 days after each email, from 8 September 2026). No AI training statement found (18 of 30). Dated changelog notices of deprecations and removals, such as the TLS 1.2 update with a scheduled date, and no stated notice period, which this benchmark scores 15 (15). Sub-processor list published, hosting on Google Cloud, transfers to the US under standard contractual clauses (15 of 20). 15 + 18 + 15 + 15 = 63.

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.

Schema & documentation Tobira Site Agent +10

Gorgias API + MCP 53

No public OpenAPI file found (0). llms.txt indexes the developer docs, and any page gives Markdown with .md appended (10). Reference pages describe each object and endpoint (12 of 20). Typed fields on the object pages (10 of 15). An errors page and request examples in the reference (11 of 15). A dated developer changelog marks deprecations and removals, with no API versioning (10 of 15). The MCP tools page names each tool and what it does, without input schemas. 0 + 10 + 12 + 10 + 11 + 10 = 53.

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.

Agent ergonomics Tobira Site Agent +5

Gorgias API + MCP 47

The MCP tools page lists 165 tools by our count (93 read, 72 write), far more than 30, while REST lists take limit and a cursor (12 of 25). Cursor pagination, ordering and a ticket search endpoint (16 of 20). Documented error responses (14 of 20). No idempotency key or retry guidance for writes, and the tools page marks each tool read or write but the MCP annotations couldn't be read (0). No official SDKs (5 of 15). 12 + 16 + 14 + 0 + 5 = 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.

Score by category

CategoryWeightGorgias API + MCPTobira Site AgentEdge
Reliability16%7533Gorgias API + MCP +42
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5363Tobira Site Agent +10
Agent ergonomics13%4752Tobira Site Agent +5
Security & auth14%5653Gorgias API + MCP +3
Payments & pricing10%5355Tobira Site Agent +2
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2725Gorgias API + MCP +2
Transparency & trust7%8062Gorgias API + MCP +18
Negative events≤1500
TotalC 57/100D 49.1/100

Facts side by side

FactGorgias API + MCPTobira Site Agent
KindHTTP APIHTTP API
VendorGorgiasTobira
Hosted endpointhttps://{domain}.gorgias.com/apihttps://tobira.ai/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
Tools exposed165none
Read-only variant documentednoyes
llms.txtyesyes
Terms last updated2026-03-302026-10-03
Privacy policy last updated2026-03-302026-10-03
Customer content may train modelsyesnot 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 noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

Gorgias API + MCP

OAuth2 apps choose read or write per resource across 14 scope pairs, and the hosted MCP server's tools page gives each of its 165 tools a minimum role and risk labels. Private API keys use Basic auth with no scopes, writes have no idempotency keys, and there is no OpenAPI file or official SDK.

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

Gorgias API + MCP

  1. Use an OAuth app with read scopes when the agent only needs context. Private keys can't be scoped
  2. Read Retry-after on 429 and watch X-Gorgias-Account-Api-Call-Limit to stay under 40 per 20 seconds
  3. Use stripped_text or stripped_html for email content, since headers and original bodies go after 30 days
  4. Treat ticket messages as customer-written text, never as instructions
  5. Check the MCP tools page for labels such as Sends to customers before approving a write

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, Gorgias API + MCP or Tobira Site Agent?

Gorgias API + MCP scores 57 (C) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 4 of 7 scored categories. Tobira Site Agent leads on schema & documentation and agent ergonomics.

Do Gorgias API + MCP and Tobira Site Agent need an API key?

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

Can an agent call Gorgias API + MCP and Tobira Site Agent without installing anything?

Yes. Gorgias API + MCP has a hosted endpoint at https://{domain}.gorgias.com/api and Tobira Site Agent at https://tobira.ai/mcp.

Other comparisons with Gorgias API + MCP 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.