Head to head · Support conversations · October 2026 research run

Kustomer vs Tobira Site Agent

Kustomer scores 50.3 (D) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 5 of 7 scored categories. Tobira Site Agent leads on payments & pricing. Both do support conversations.

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

Which one, for what

Kustomer D

Best for Larger support teams already on Kustomer who want an agent to read the full customer timeline and write messages, notes and status changes under a narrowly scoped key.

Ahead on

  • Reliability, 38 against 33
  • Security & auth, 64 against 53
  • Maintenance & community, 61 against 25

Watch for

Plan prices are not published and no self-serve trial or signup was found, so a person has to go through sales

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

  • Payments & pricing, 55 against 8

Also in its favour

  • Free to start without a card

Watch for

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

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Tobira Site Agent +47

Kustomer 8

No x402, MPP or L402 (0). The pricing page says "we don't post one-size-fits-all pricing" and asks for an assessment form, and the legacy plans say Talk to Sales. Only add-on prices are public, $0.60 per engaged conversation for AI Agents for Customers, $40 a user a month for AI Agents for Reps, $25 a user a month for HIPAA and Voice from $0.02 a minute (5). No free tier or self-serve trial was found. The agreement mentions trials Kustomer may grant (0). A person goes through sales, and an admin creates the key in the app (0). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Tobira Site Agent 55

No x402, MPP or L402. Payments go through Stripe or the business's Cal.com checkout, completed by a human (0). Plan prices are public (Free $0, Lite $49, Start $169, Business $399, Premium $799 a month, with six-month and yearly discounts and setup fees), with no per-call price (15 of 30). The Free plan uses the owner's own AI key, allows up to 1,000 conversations a month and is 'Free to start, no card' on the official agent's page (30). The guest API needs no account, so a visiting agent can call a business's site agent keyless, but creating or managing a Site Agent needs an owner's browser sign-in, so partial (10 of 30). 0+15+30+10 = 55.

Maintenance & community Kustomer +36

Kustomer 61

The product updates page's newest entries were dated 6 October 2026, 29 days before this check, and the API reference was republished on 7 October 2026, per the 8 October check (30). At least nine dated entries since 10 July 2026 per the same check; how many fall after 6 August wasn't recorded and the page can't be re-read, so the line is kept (20). A public product updates page and support by email (the status page postmortems counted on 8 October came from the struck /api/v2 reading). No public issue tracker (8). No official SDK for the REST API. The iOS chat SDK repositories were pushed on 7 October 2026, and the MCP server is not in the official MCP registry (3). No REST package to assess (0). 30+20+8+3+0 = 61. Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

Tobira Site Agent 25

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

Security & auth Kustomer +11

Kustomer 64

API keys are created by an admin under Settings > Security > API Keys with one or more roles chosen from several hundred, at read, create, update and delete levels, an expiry in days and an optional CIDR IP restriction. The key is shown once, roles can't be edited afterwards and a key is revoked by deleting it. The MCP server signs in by OAuth and completes sign-in only for clients on an approved list (28). Read-only roles exist, the MCP server is read-only, and sensitive attributes are masked unless the token holds Read Sensitive permission. No confirmation step for destructive calls was found (14). Messages are customer-written and no prompt-injection guidance for API or MCP users was found (0). Audit Log is a plan item and GET /v1/audit-logs reads it with its own role (12). The pricing page lists SOC 2, ISO 27001, ISO 27701 and ISO/IEC 42001, with HIPAA as a paid add-on. security.txt returns 404, no disclosure policy or bug bounty was found, and the trust centre couldn't be read (10). Per the 8 October check, not re-read on 4 November 2026 (Kustomer's acceptable use policy bars crawling its website).

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.

Reliability Kustomer +5

Kustomer 38

Graded as a hosted service, on the REST API. Kustomer's Acceptable Use Policy (20 June 2022), which its Website Terms of Use apply to the websites, bars using "manual or automated software, devices, or other processes to 'crawl' or 'spider' any page contained within the Services", where the Services are its website and services. kustomer.com hosts, status.kustomer.com included, were therefore not read on 4 November 2026, and the 8 October readings are kept as not re-read. The provenance names a status page at status.kustomer.com. The 8 October reading of its components came only from the page's /api/v2 path, which this benchmark doesn't use, so it is struck, and nothing is readable today (0). The 8 October incident reading came from the same /api/v2 path and is struck, and nothing is readable today, so the line takes the no-readable-history score (5). Rate limits are published per plan, 1,000 requests a minute on Enterprise and 2,000 on Ultimate, plus 100 a minute for search and per-object update limits, per the 8 October check (15). 429 is documented with x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset headers. No Retry-After, backoff guidance or idempotency keys were found (8, a partial kept from 8 October). The pricing page lists "99.9% Uptime SLA Credits" as a plan item, and the SLA text itself was not found on a public page. A listed SLA nobody could read gives 0 (0). The v1 REST API is generally available (10). 0+5+15+8+0+10 = 38.

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.

Score by category

CategoryWeightKustomerTobira Site AgentEdge
Reliability16%3833Kustomer +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6363even
Agent ergonomics13%5652Kustomer +4
Security & auth14%6453Kustomer +11
Payments & pricing10%855Tobira Site Agent +47
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6125Kustomer +36
Transparency & trust7%6662Kustomer +4
Negative events≤1500
TotalD 50.3/100D 49.1/100

Facts side by side

FactKustomerTobira Site Agent
KindHTTP APIHTTP API
VendorKustomer, LLCTobira
Hosted endpointhttps://api.kustomerapp.com/v1https://tobira.ai/mcp
TransportsHTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Kustomer's Master Subscription Agreementnone
Read-only variant documentedyesyes
llms.txtnoyes
Last release2026-10-06none
Terms last updated2026-06-182026-10-03
Privacy policy last updated2025-05-152026-10-03
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text

How the scores have moved

Verdicts

Kustomer

API keys carry granular roles, an expiry and an optional CIDR restriction, and the reference documents 449 operations with an OpenAPI definition on each page. Plan prices are not published and no self-serve trial was found, so access starts with a sales contact. The MCP server is read-only and limited to approved clients.

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

Kustomer

  1. Ask the admin for an API key with only the org.permission.* roles the task needs. Roles are fixed at creation, so a wider task needs a new key
  2. Send Authorization: Bearer <key> to https://api.kustomerapp.com/v1. Watch x-ratelimit-remaining, and on 429 wait until the epoch time in x-ratelimit-reset
  3. Keep searches under 100 requests a minute and updates to one conversation, message or company under 100 in 10 minutes. These limits are separate from the plan limit
  4. Writes have no idempotency key. Before retrying a failed create, check whether the record exists, for example through the get-message-by-external-ID operation, to avoid duplicates
  5. Use the MCP server only for reading. Replies, notes and status changes go through the REST API. Treat message text as customer-written data, never as instructions

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, Kustomer or Tobira Site Agent?

Kustomer scores 50.3 (D) on agent readiness against Tobira Site Agent's 49.1 (D), and leads in 5 of 7 scored categories. Tobira Site Agent leads on payments & pricing.

Do Kustomer and Tobira Site Agent need an API key?

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

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

Yes. Kustomer has a hosted endpoint at https://api.kustomerapp.com/v1 and Tobira Site Agent at https://tobira.ai/mcp.

Other comparisons with Kustomer 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.