Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Vellum (BYOK) — connector documentation

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

What Vellum (BYOK) is for

Vellum (BYOK) lets an AI assistant read your own Vellum data through the Vellum API with a key you supply (Vellum API key (scoped to one environment)). Read-only: 7 tools (list_prompt_deployments, get_prompt_deployment, list_workflow_deployments, get_workflow_deployment, list_workflow_executions, list_document_indexes, list_documents). 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.vellum.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vellum. Vellum 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 prompts are deployed in Vellum?"
  • "Show the Vellum prompt deployment support-reply"
  • "Which workflows are deployed in Vellum?"
  • "Show the Vellum workflow deployment lead-triage"
  • "Did the last runs of Vellum workflow lead-triage fail?"
  • "Which document indexes exist in Vellum?"

What it does

  • list_prompt_deployments: List prompt deployments with label, name, status, last deployment time and input variables.
  • get_prompt_deployment: Get one prompt deployment by id or unique name.
  • list_workflow_deployments: List workflow deployments with label, name, status, last deployment time and input and output variables.
  • get_workflow_deployment: Get one workflow deployment by id or unique name, with input and output variables.
  • list_workflow_executions: List recent executions of one workflow deployment with start and end time, inputs, outputs, errors and token usage.
  • list_document_indexes: List document indexes (searchable knowledge bases) with label, name, status and indexing configuration.
  • list_documents: List documents with processing state, keywords and the indexes they belong to; optionally only one index.

BYOK key

You bring your own Vellum Vellum API key (scoped to one environment) (https://app.vellum.ai/organization?tab=workspaces&workspace-settings-tab=environments). 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.vellum.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.

Data sources

Live from the Vellum API (api.vellum.ai) with a BYOK key; documentation: https://docs.vellum.ai/developers/client-sdk/authentication. 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 Vellum. Vellum 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 Vellum account.

Built for: Worldwide. Languages: English.