LiveChat Reports (BYOK)

LiveChat Reports (BYOK) — connector documentation

• MCP endpoint: https://byok-livechat-reports.connectorbay.com/mcp
• REST API: POST https://byok-livechat-reports.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-livechat-reports.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own LiveChat Reports LiveChat Account ID, sent in the X-Upstream-Key header and the LiveChat personal access token in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-livechat-reports.connectorbay.com/health · Tool schemas: https://byok-livechat-reports.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-livechat-reports · agent@connectorbay.com

What LiveChat Reports (BYOK) is for

LiveChat Reports (BYOK) lets an AI assistant read your own LiveChat Reports data through the LiveChat Reports API with a key you supply (LiveChat Account ID). Read-only: 12 tools (get_total_chats, get_chat_duration, get_chat_ratings, get_chat_engagement, get_chat_tag_distribution, get_first_response_time, get_response_time, get_chats_by_group, get_queued_visitors, get_agent_availability, get_unique_visitors, get_tag_chat_usage). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.livechatinc.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Reports. LiveChat Reports and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "How many LiveChat chats did we have each day this week?"
• "How long do our LiveChat chats last on average?"
• "How did customers rate our LiveChat chats this month?"
• "How many LiveChat chats came from greetings versus visitors starting them?"
• "Which tags were used most on LiveChat chats last week?"
• "What is our average first response time in LiveChat?"

What it does

• get_total_chats: Count the chats in a period, per bucket, with how many were continuous chats. Needs the reports_read scope on the token.
• get_chat_duration: Average chat duration per bucket (seconds), with the chat count and the agents' chatting duration. Needs the reports_read scope on the token.
• get_chat_ratings: Number of rated chats per bucket with how many were rated good and bad. Needs the reports_read scope on the token.
• get_chat_engagement: Chats per bucket split by how they started: from a greeting, by the customer without a greeting, or by an agent. Needs the reports_read scope on the token.
• get_chat_tag_distribution: How many chats carry each tag, per bucket, for the period. Needs the reports_read scope on the token.
• get_first_response_time: Average agent first response time (seconds) per bucket with the chat count. Needs the reports_read scope on the token.
• get_response_time: Average agent response time (seconds) per bucket with the chat count. Needs the reports_read scope on the token.
• get_chats_by_group: Number of chats handled by each group (team) per bucket; group ids are the keys. Needs the reports_read scope on the token.
• get_queued_visitors: Visitors who waited in the queue per bucket: how many left without chatting and how many entered a chat, with min, max and average wait in seconds. Needs the reports_read scope on the token.
• get_agent_availability: Hours (or minutes for hourly buckets) the account's agents were available for chats per bucket. Needs the reports_read scope on the token.
• get_unique_visitors: Total unique visitors and page views seen by the chat widget in a period. Needs the reports_read scope on the token.
• get_tag_chat_usage: Total number of chats marked with each tag over a period, optionally restricted by time zone. Needs the reports_read scope on the token.

BYOK key

You bring your own LiveChat Reports LiveChat Account ID (https://platform.text.com/docs/authorization/personal-access-tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.livechatinc.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Create the token in the Text Developer Console (Settings > Authorization > Personal Access Tokens) with the reports_read scope only. The first value is the Account ID, the second the token.

Data sources

• https://platform.text.com/docs/data-reporting/reports-api (the API this connector calls, with a BYOK key)

Live from the LiveChat Reports API (api.livechatinc.com) with a BYOK key; documentation: https://platform.text.com/docs/data-reporting/reports-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Reports. LiveChat Reports and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your LiveChat Reports account.

Built for: Worldwide. Languages: English.

LiveChat Reports (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What LiveChat Reports (BYOK) is. LiveChat Reports (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own LiveChat Reports data: Read aggregate LiveChat support statistics: chat volume, ratings, response times, tag usage, queues and agent availability, with your own personal access token. You bring your own LiveChat Reports LiveChat Account ID; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one LiveChat Reports call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.livechatinc.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If LiveChat Reports rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What LiveChat Reports receives. The request we make on your behalf, including the key and the arguments, under LiveChat Reports's own terms and privacy policy. LiveChat Reports acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer LiveChat Reports gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your LiveChat Reports data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. LiveChat Reports (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at LiveChat Reports at any time to end all access.

Children. LiveChat Reports (BYOK) is a general-audience service operated by the adult using the assistant, under LiveChat Reports's own age rules.

Changes. We will post changes here with a new effective date.

LiveChat Reports (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the LiveChat Reports (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. LiveChat Reports (BYOK) provides: Read aggregate LiveChat support statistics: chat volume, ratings, response times, tag usage, queues and agent availability, with your own personal access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own LiveChat Reports credentials and only access data you are allowed to access. LiveChat Reports's terms apply to your use of LiveChat Reports; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LiveChat Reports. LiveChat Reports and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data LiveChat Reports returns, lightly trimmed; it may be incomplete, delayed or changed by LiveChat Reports. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your LiveChat Reports account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent LiveChat Reports's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; LiveChat Reports may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your LiveChat Reports key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action LiveChat Reports takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-livechat-reports

LiveChat Reports (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-livechat-reports.connectorbay.com/mcp
• REST API: https://byok-livechat-reports.connectorbay.com/openapi.json
• Live status: https://byok-livechat-reports.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. LiveChat Reports (BYOK) never asks for them.