Trint US (BYOK)
Read your Trint US tenant transcripts, folders and Shared Drives with your own API key ID and secret
Read your Crisp inbox conversations, messages, customer profiles, operators and availability with BYOK
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_websiteget_availabilitylist_operatorslist_operator_availabilitieslist_conversationsget_conversationCrisp (BYOK) lets an AI assistant read your own Crisp data through the Crisp API with a key you supply (Crisp token identifier). Read-only: 9 tools (get_website, get_availability, list_operators, list_operator_availabilities, list_conversations, get_conversation, list_messages, list_people_profiles, get_people_profile). 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.crisp.chat. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Crisp API (api.crisp.chat) with a BYOK key; documentation: https://docs.crisp.chat/references/rest-api/v1/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://byok-crisp.connectorbay.com/mcpThree ways in, the same 9 tools.
https://byok-crisp.connectorbay.com/mcpPOST https://byok-crisp.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-crisp.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.crisp.chat).Crisp (BYOK) lets an AI assistant read your own Crisp data through the Crisp API with a key you supply (Crisp token identifier). It is a hosted MCP server with 9 tools such as Get website, Get availability, List operators, List operator availabilities, List conversations, Get conversation, published by Unify Dynamics LLC. It is independent and not affiliated with Crisp.
Add the MCP endpoint https://byok-crisp.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-crisp.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-crisp.json.
Yes: this is a bring-your-own-key connector. Create a Crisp token identifier at https://docs.crisp.chat/guides/rest-api/authentication/website-token/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Trint US tenant transcripts, folders and Shared Drives with your own API key ID and secret
Read your Trint EU tenant transcripts, folders and Shared Drives with your own API key ID and secret
Read your Tulip frontline operations setup: stations, station groups, interfaces, roles, user groups, app groups, machine types and tables with your own API token
Read public Tumblr blogs, their posts, likes and notes, and posts under a tag, with your own API key (OAuth consumer key)
Read your Twilio account, phone numbers, call and message logs and usage records with BYOK (read-only; never sends anything)
Read your Twilio Content Templates (rich messages for WhatsApp, SMS and more) and their approval status with your own credentials (read-only)
https://byok-crisp.connectorbay.com/mcpPOST https://byok-crisp.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-crisp.connectorbay.com/openapi.jsonX-Upstream-Key header and the Crisp token key (secret) in X-Upstream-Key-2 of every request (never stored, logged or cached)https://byok-crisp.connectorbay.com/health · Tool schemas: https://byok-crisp.connectorbay.com/tools.jsonCrisp (BYOK) lets an AI assistant read your own Crisp data through the Crisp API with a key you supply (Crisp token identifier). Read-only: 9 tools (get_website, get_availability, list_operators, list_operator_availabilities, list_conversations, get_conversation, list_messages, list_people_profiles, get_people_profile). 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.crisp.chat. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp 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:
get_website: Get a Crisp website (workspace): name, domain, logo and verification status.get_availability: Show whether the Crisp chatbox currently appears online, away or offline to visitors.list_operators: List the operator members of a Crisp website with name, email, role and availability. Invite keys are never returned.list_operator_availabilities: List each Crisp operator's current availability (online, away or offline).list_conversations: List Crisp conversations, 20 to 50 per page, with state, visitor contact, last message, topic and times. Filter by unread, resolved, assignment, inbox or date; or search.get_conversation: Get one Crisp conversation by session id: state, assignee, unread counters, visitor nickname and email, topic and times.list_messages: List the latest messages of a Crisp conversation (the most recent batch), with sender, type, text or file content and time. Page towards older messages with timestamp_before.list_people_profiles: List Crisp customer (people) profiles, 20 to 50 per page, with email, name, phone, company, segments and activity. Supports a quick text search.get_people_profile: Get one Crisp customer profile by people id or email address.You bring your own Crisp Crisp token identifier (https://docs.crisp.chat/guides/rest-api/authentication/website-token/). 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.crisp.chat 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.
Live from the Crisp API (api.crisp.chat) with a BYOK key; documentation: https://docs.crisp.chat/references/rest-api/v1/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp 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 Crisp account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Crisp (BYOK) is. Crisp (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Crisp data: Read your Crisp inbox conversations, messages, customer profiles, operators and availability with BYOK. You bring your own Crisp Crisp token identifier; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Crisp 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.crisp.chat, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Crisp 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 Crisp receives. The request we make on your behalf, including the key and the arguments, under Crisp's own terms and privacy policy. Crisp acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Crisp 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 Crisp 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. Crisp (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 Crisp at any time to end all access.
Children. Crisp (BYOK) is a general-audience service operated by the adult using the assistant, under Crisp's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Crisp (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-crisp.connectorbay.com/mcphttps://byok-crisp.connectorbay.com/openapi.jsonWhen 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. Crisp (BYOK) never asks for them.