ITA Trade Data (BYOK)
Search the US International Trade Administration export screening lists, free trade agreement tariff rates, trade events, leads and offices with your own subscription key
Read your Clicksign e-signature envelopes, their status, documents, templates and folders with your own access token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_envelopesget_envelopelist_envelope_documentslist_templateslist_foldersget_folderClicksign (BYOK) lets an AI assistant read your own Clicksign data through the Clicksign API with a key you supply (Clicksign access token (production)). Read-only: 6 tools (list_envelopes, get_envelope, list_envelope_documents, list_templates, list_folders, get_folder). 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 app.clicksign.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Clicksign. Clicksign and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Clicksign API (app.clicksign.com) with a BYOK key; documentation: https://developers.clicksign.com/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.
6 tools, grouped by job. Every one is read-only or compute-only.
https://byok-clicksign.connectorbay.com/mcpThree ways in, the same 6 tools.
https://byok-clicksign.connectorbay.com/mcpPOST https://byok-clicksign.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-clicksign.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at developers.clicksign.com).Clicksign (BYOK) lets an AI assistant read your own Clicksign data through the Clicksign API with a key you supply (Clicksign access token… It is a hosted MCP server with 6 tools such as List envelopes, Get envelope, List envelope documents, List templates, List folders, Get folder, published by Unify Dynamics LLC. It is independent and not affiliated with Clicksign.
Add the MCP endpoint https://byok-clicksign.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-clicksign.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-clicksign.json.
Yes: this is a bring-your-own-key connector. Create a Clicksign access token (production) at https://developers.clicksign.com/docs/access-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.
Search the US International Trade Administration export screening lists, free trade agreement tariff rates, trade events, leads and offices with your own subscription key
Read Jira Service Management Assets: object schemas, object types and attributes, objects found with AQL, history and linked tickets with your Atlassian email and API token
Read your Jira Service Management service desks, queues, customer requests, comments, SLAs and request types with your Atlassian email and API token
Read your JobNimbus contractor CRM contacts, jobs, tasks, activity, invoices, work orders and team with your own API key
Read your JobNimbus account setup: workflows and statuses, lead sources, task, activity and file types, groups and units of measure with your own API key
Read your JobScore Hire jobs, departments, locations, workflow stages, disposition codes and sources with your own personal access token
https://byok-clicksign.connectorbay.com/mcpPOST https://byok-clicksign.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-clicksign.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-clicksign.connectorbay.com/health · Tool schemas: https://byok-clicksign.connectorbay.com/tools.jsonClicksign (BYOK) lets an AI assistant read your own Clicksign data through the Clicksign API with a key you supply (Clicksign access token (production)). Read-only: 6 tools (list_envelopes, get_envelope, list_envelope_documents, list_templates, list_folders, get_folder). 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 app.clicksign.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Clicksign. Clicksign 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_envelopes: List signature envelopes with name, status (draft, running, closed, canceled), deadline, language, auto-close and reminder settings and dates. Signers and files are not included. Production environment only (app.clicksign.com).get_envelope: Get one envelope: name, status, deadline, language, rubric, reminder and refusal settings and dates.list_envelope_documents: List the documents attached to one envelope: file name, status, template flag and dates. File download links are not returned.list_templates: List the document templates (models) of the account with name, colour and dates. Template file links are not returned.list_folders: List the folders of the account with name, path, whether it is in the root and dates.get_folder: Get one folder by ID: name, path, root flag and dates.You bring your own Clicksign Clicksign access token (production) (https://developers.clicksign.com/docs/access-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 app.clicksign.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.
Live from the Clicksign API (app.clicksign.com) with a BYOK key; documentation: https://developers.clicksign.com/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 Clicksign. Clicksign 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 Clicksign account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Clicksign (BYOK) is. Clicksign (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Clicksign data: Read your Clicksign e-signature envelopes, their status, documents, templates and folders with your own access token. You bring your own Clicksign Clicksign access token (production); the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Clicksign 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 app.clicksign.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 Clicksign 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 Clicksign receives. The request we make on your behalf, including the key and the arguments, under Clicksign's own terms and privacy policy. Clicksign acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Clicksign 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 Clicksign 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. Clicksign (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 Clicksign at any time to end all access.
Children. Clicksign (BYOK) is a general-audience service operated by the adult using the assistant, under Clicksign'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 Clicksign (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-clicksign.connectorbay.com/mcphttps://byok-clicksign.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. Clicksign (BYOK) never asks for them.