Telnyx (BYOK)
Read your Telnyx balance, phone numbers, messaging profiles, message records, voice connections and call recordings with BYOK
Read your Linkup credit balance and the research, extract and batch search tasks run on your account with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_credit_balancelist_research_tasksget_research_tasklist_tasksget_tasklist_extract_tasksLinkup (BYOK) lets an AI assistant read your own Linkup data through the Linkup API with a key you supply (Linkup API key). Read-only: 7 tools (get_credit_balance, list_research_tasks, get_research_task, list_tasks, get_task, list_extract_tasks, get_extract_task). 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.linkup.so. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Linkup. Linkup and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Linkup API (api.linkup.so) with a BYOK key; documentation: https://docs.linkup.so/llms.txt. 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.
7 tools, grouped by job. Every one is read-only or compute-only.
https://byok-linkup.connectorbay.com/mcpThree ways in, the same 7 tools.
https://byok-linkup.connectorbay.com/mcpPOST https://byok-linkup.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-linkup.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at docs.linkup.so).Linkup (BYOK) lets an AI assistant read your own Linkup data through the Linkup API with a key you supply (Linkup API key). It is a hosted MCP server with 7 tools such as Get credit balance, List research tasks, Get research task, List tasks, Get task, List extract tasks, published by Unify Dynamics LLC. It is independent and not affiliated with Linkup.
Add the MCP endpoint https://byok-linkup.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-linkup.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-linkup.json.
Yes: this is a bring-your-own-key connector. Create a Linkup API key at https://docs.linkup.so/pages/documentation/platform/authentication 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 Telnyx balance, phone numbers, messaging profiles, message records, voice connections and call recordings with BYOK
Read your Telnyx 10DLC brand and campaign registrations, vetting status, number assignments and use-case costs with your own API key (read-only)
Read your Telnyx messaging profile settings, toll-free verification status, short codes, alphanumeric sender IDs, auto-reply rules and number health with your own API key (read-only)
Read the voice and messaging settings of your Telnyx phone numbers, number orders, block orders, bulk jobs and regulatory requirements with your own API key (read-only)
Read your Telnyx SIP connections, TeXML and fax applications, call queues, FQDN and IP routing targets and channel limits with your own API key (read-only)
Read your Telnyx WhatsApp Business accounts, registered numbers with quality ratings, message templates with approval status, calling and webhook settings with your own API key (read-only)
https://byok-linkup.connectorbay.com/mcpPOST https://byok-linkup.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-linkup.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-linkup.connectorbay.com/health · Tool schemas: https://byok-linkup.connectorbay.com/tools.jsonLinkup (BYOK) lets an AI assistant read your own Linkup data through the Linkup API with a key you supply (Linkup API key). Read-only: 7 tools (get_credit_balance, list_research_tasks, get_research_task, list_tasks, get_task, list_extract_tasks, get_extract_task). 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.linkup.so. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Linkup. Linkup 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_credit_balance: Get your current Linkup credit balance.list_research_tasks: List deep research tasks with status, question, mode and depth; the answer text is not included (use get_research_task).get_research_task: Get one research task: status, the question and settings, and when finished the answer with its sources.list_tasks: List batch tasks (asynchronous search, fetch and research calls) with type, status and the main query; results are not included.get_task: Get one batch task: type, status, error and the input it ran with (the output is not included).list_extract_tasks: List structured data extraction tasks (beta) with status, source URL, instruction, credits used and rows returned.get_extract_task: Get one extraction task (beta): status, source URL, instruction, credits used and rows returned (the result link is not shown).You bring your own Linkup Linkup API key (https://docs.linkup.so/pages/documentation/platform/authentication). 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.linkup.so 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 Linkup API (api.linkup.so) with a BYOK key; documentation: https://docs.linkup.so/llms.txt. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Linkup. Linkup 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 Linkup account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Linkup (BYOK) is. Linkup (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Linkup data: Read your Linkup credit balance and the research, extract and batch search tasks run on your account with your own API key. You bring your own Linkup Linkup API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Linkup 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.linkup.so, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Linkup 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 Linkup receives. The request we make on your behalf, including the key and the arguments, under Linkup's own terms and privacy policy. Linkup acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Linkup 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 Linkup 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. Linkup (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 Linkup at any time to end all access.
Children. Linkup (BYOK) is a general-audience service operated by the adult using the assistant, under Linkup'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 Linkup (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-linkup.connectorbay.com/mcphttps://byok-linkup.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. Linkup (BYOK) never asks for them.