Venafi Cloud (US) (BYOK)

Venafi Cloud (US) (BYOK) — connector documentation

• MCP endpoint: https://byok-venafi-cloud.connectorbay.com/mcp
• REST API: POST https://byok-venafi-cloud.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-venafi-cloud.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Venafi Cloud (US) Venafi Cloud API key (from your user preferences), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-venafi-cloud.connectorbay.com/health · Tool schemas: https://byok-venafi-cloud.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-venafi-cloud · agent@connectorbay.com

What Venafi Cloud (US) (BYOK) is for

Venafi Cloud (US) (BYOK) lets an AI assistant read your own Venafi Cloud (US) data through the Venafi Cloud (US) API with a key you supply (Venafi Cloud API key (from your user preferences)). Read-only: 12 tools (list_certificates, get_certificate, list_applications, get_application, list_issuing_templates, list_machines, list_machine_identities, list_satellites, list_teams, list_tags, list_certificate_requests, get_autorenewal_status). 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.venafi.cloud. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Venafi Cloud (US). Venafi Cloud (US) 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:

• "Which certificates in Venafi expire soonest?"
• "What are the details of Venafi certificate c1?"
• "Which applications are defined in Venafi?"
• "What is the Venafi application a1 for?"
• "Which certificate issuing templates exist in Venafi?"
• "Which machines does Venafi manage certificates for?"

What it does

• list_certificates: List certificates in the inventory with names, subject, issuer, validity dates, key strength, status and tags. The subject filter is a regular expression.
• get_certificate: Get one certificate by id: names, subject, issuer, validity, key and signature algorithm, status, tags and instance counts.
• list_applications: List applications (groups of certificates for one purpose) with domains, IP ranges, ports and issuing template aliases.
• get_application: Get one application by id: description, domains, IP ranges, ports and issuing template aliases.
• list_issuing_templates: List certificate issuing templates with certificate authority type, account id, priority and key reuse setting.
• list_machines: List machines (targets that receive certificates) with type, status, integration, discovery and provisioning state.
• list_machine_identities: List machine identities (certificate bindings on machines) with certificate id, machine id, validation status and last seen time.
• list_satellites: List satellite (edge) instances with status, type, version, last seen time and upgrade status.
• list_teams: List teams of the company with id, name and last modification (members are not returned).
• list_tags: List the tags available for labelling certificates and other entities.
• list_certificate_requests: List certificate requests with status, application, issuing template, key type and size, subject and dates.
• get_autorenewal_status: Show the state of the automatic certificate renewal monitoring: current and previous run with state, time and application count.

BYOK key

You bring your own Venafi Cloud (US) Venafi Cloud API key (from your user preferences) (https://developer.venafi.com/tlsprotectcloud/reference/tls-protect-overview). 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.venafi.cloud 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.

Data sources

• https://developer.venafi.com/tlsprotectcloud/reference/getting-started (the API this connector calls, with a BYOK key)

Live from the Venafi Cloud (US) API (api.venafi.cloud) with a BYOK key; documentation: https://developer.venafi.com/tlsprotectcloud/reference/getting-started. 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 Venafi Cloud (US). Venafi Cloud (US) 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 Venafi Cloud (US) account.

Built for: Worldwide. Languages: English.

Venafi Cloud (US) (BYOK) — Privacy Policy

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

What Venafi Cloud (US) (BYOK) is. Venafi Cloud (US) (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Venafi Cloud (US) data: Read your Venafi (CyberArk Certificate Manager SaaS) certificate inventory, applications, issuing templates, machines and satellites with your own API key. You bring your own Venafi Cloud (US) Venafi Cloud API key (from your user preferences); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Venafi Cloud (US) 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.venafi.cloud, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Venafi Cloud (US) 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 Venafi Cloud (US) receives. The request we make on your behalf, including the key and the arguments, under Venafi Cloud (US)'s own terms and privacy policy. Venafi Cloud (US) acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Venafi Cloud (US) 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 Venafi Cloud (US) 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. Venafi Cloud (US) (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 Venafi Cloud (US) at any time to end all access.

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

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

Venafi Cloud (US) (BYOK) — Terms of Service

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

1. The Service. Venafi Cloud (US) (BYOK) provides: Read your Venafi (CyberArk Certificate Manager SaaS) certificate inventory, applications, issuing templates, machines and satellites with your own API key. 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 Venafi Cloud (US) credentials and only access data you are allowed to access. Venafi Cloud (US)'s terms apply to your use of Venafi Cloud (US); 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 Venafi Cloud (US). Venafi Cloud (US) 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 Venafi Cloud (US) returns, lightly trimmed; it may be incomplete, delayed or changed by Venafi Cloud (US). Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Venafi Cloud (US) 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 Venafi Cloud (US)'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; Venafi Cloud (US) 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 Venafi Cloud (US) 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 Venafi Cloud (US) 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-venafi-cloud

Venafi Cloud (US) (BYOK) support

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

• MCP endpoint: https://byok-venafi-cloud.connectorbay.com/mcp
• REST API: https://byok-venafi-cloud.connectorbay.com/openapi.json
• Live status: https://byok-venafi-cloud.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. Venafi Cloud (US) (BYOK) never asks for them.