Sinch Conversation (BYOK)
Read your Sinch Conversation API apps, conversations and message metadata (no message content or credentials) with your own access keys
Read your Exa Websets, their items, monitors, imports, events and webhooks with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_websetsget_websetlist_webset_itemsget_webset_itemlist_monitorslist_importsExa (BYOK) lets an AI assistant read your own Exa data through the Exa API with a key you supply (API key). Read-only: 8 tools (list_websets, get_webset, list_webset_items, get_webset_item, list_monitors, list_imports, list_events, list_webhooks). 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.exa.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Exa. Exa and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Exa API (api.exa.ai) with a BYOK key; documentation: https://docs.exa.ai/websets/api/overview. 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.
8 tools, grouped by job. Every one is read-only or compute-only.
https://byok-exa.connectorbay.com/mcpThree ways in, the same 8 tools.
https://byok-exa.connectorbay.com/mcpPOST https://byok-exa.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-exa.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at dashboard.exa.ai).Exa (BYOK) lets an AI assistant read your own Exa data through the Exa API with a key you supply (API key). It is a hosted MCP server with 8 tools such as List websets, Get webset, List webset items, Get webset item, List monitors, List imports, published by Unify Dynamics LLC. It is independent and not affiliated with Exa.
Add the MCP endpoint https://byok-exa.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-exa.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-exa.json.
Yes: this is a bring-your-own-key connector. Create a API key at https://dashboard.exa.ai/api-keys 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 Sinch Conversation API apps, conversations and message metadata (no message content or credentials) with your own access keys
Read your Sinch fax history, fax services, service phone numbers and email domains with your own access key and secret (fax contents are not fetched)
Read your Sinch phone numbers, search numbers that are available with prices, list supported regions and check number orders with your own access key and secret
Read your Sinch Elastic SIP Trunking setup: call records, trunks, endpoints, phone numbers, country permissions, access lists and call blocking rules with your own access key and secret
Read your SingleStore Helios clusters, projects, starter deployments, Flow instances, billing usage and regions with your own Management API key
Read your Sinric Pro smart home and IoT cloud account: devices, homes, rooms and device activity logs with your own API key
https://byok-exa.connectorbay.com/mcpPOST https://byok-exa.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-exa.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-exa.connectorbay.com/health · Tool schemas: https://byok-exa.connectorbay.com/tools.jsonExa (BYOK) lets an AI assistant read your own Exa data through the Exa API with a key you supply (API key). Read-only: 8 tools (list_websets, get_webset, list_webset_items, get_webset_item, list_monitors, list_imports, list_events, list_webhooks). 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.exa.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Exa. Exa 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:
list_websets: List your Websets (saved Exa searches that collect and enrich web entities) with status, title, the searches that were run and timestamps.get_webset: Get one Webset: status, title, its searches with progress, imports, enrichments and monitors.list_webset_items: List the items (people, companies, articles, papers) a Webset collected, with their properties and how well each satisfies the search criteria.get_webset_item: Get one item of a Webset with its properties and criteria evaluations.list_monitors: List monitors that re-run a Webset search or refresh on a schedule, with status, cron cadence, last run and next run time.list_imports: List imports (CSV or Webset data brought in as a source) with status, format, row count and any failure message.list_events: List recent Webset events (created, item added, search completed, import completed and so on), newest first, optionally by time window.list_webhooks: List webhooks registered for Webset events with URL, subscribed event types and status (signing secrets are not returned).You bring your own Exa API key (https://dashboard.exa.ai/api-keys). 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.exa.ai 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.
Read-only: this connector lists and reads Websets you already have. It never runs Exa searches or creates Websets, so it does not use credits.
Live from the Exa API (api.exa.ai) with a BYOK key; documentation: https://docs.exa.ai/websets/api/overview. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Exa. Exa 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 Exa account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Exa (BYOK) is. Exa (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Exa data: Read your Exa Websets, their items, monitors, imports, events and webhooks with your own API key. You bring your own Exa API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Exa 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.exa.ai, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Exa 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 Exa receives. The request we make on your behalf, including the key and the arguments, under Exa's own terms and privacy policy. Exa acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Exa 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 Exa 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. Exa (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 Exa at any time to end all access.
Children. Exa (BYOK) is a general-audience service operated by the adult using the assistant, under Exa'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 Exa (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-exa.connectorbay.com/mcphttps://byok-exa.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. Exa (BYOK) never asks for them.