Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Vercel Routing and Releases (BYOK) icon

Vercel Routing and Releases (BYOK)

Read your Vercel project route versions, bulk redirect versions, rolling release configuration and state and custom environments with your own access token

Unify Dynamics LLC

Documentation
Tools6read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderVercel Routing and Releasesunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which routing rule version is live on my Vercel project?
Tools called
list_route_versions
Which bulk redirect version is live?
Tools called
list_redirect_versions
Is a rolling release in progress for my project?
Tools called
get_rolling_release
How is rolling release configured for my project?
Tools called
get_rolling_release_config
Which custom environments does my Vercel project have?
Tools called
list_custom_environments
What domains does the staging environment use?
Tools called
get_custom_environment

About

Vercel Routing and Releases (BYOK) lets an AI assistant read your own Vercel Routing and Releases data through the Vercel Routing and Releases API with a key you supply (access token). Read-only: 6 tools (list_route_versions, list_redirect_versions, get_rolling_release, get_rolling_release_config, list_custom_environments, get_custom_environment). 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.vercel.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Routing and Releases. Vercel Routing and Releases and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Vercel Routing and Releases API (api.vercel.com) with a BYOK key; documentation: https://vercel.com/docs/rest-api/reference/endpoints/project-routes. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

6 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data6 tools
  • List route versionsList the versions of a project's routing rules with id, live and staging flags, rule count, author and last-modified time.
  • List redirect versionsList the versions of a project's bulk redirects with id, name, live and staging flags, redirect count and last-modified time.
  • Get rolling releaseGet the current rolling release of a project: state, canary percentage, advancement type, current stage and start time.
  • Get rolling release configGet a project's rolling release settings: target environment, stages, advancement gate and canary header flag.
  • List custom environmentsList a project's custom environments with slug, type, description, domains, current aliases and dates.
  • Get custom environmentGet one custom environment of a project.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-vercel-routing.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 6 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-vercel-routing.connectorbay.com/mcp
RESTPOST https://byok-vercel-routing.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-vercel-routing.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your access token in the X-Upstream-Key header (get one at vercel.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Vercel Routing and Releases connector: questions and answers

What is the Vercel Routing and Releases connector?

Vercel Routing and Releases (BYOK) lets an AI assistant read your own Vercel Routing and Releases data through the Vercel Routing and Releases API… It is a hosted MCP server with 6 tools such as List route versions, List redirect versions, Get rolling release, Get rolling release config, List custom environments, Get custom environment, published by Unify Dynamics LLC. It is independent and not affiliated with Vercel Routing and Releases.

How do I connect Vercel Routing and Releases to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-vercel-routing.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-vercel-routing.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-vercel-routing.json.

Do I need a Vercel Routing and Releases account or API key?

Yes: this is a bring-your-own-key connector. Create a access token at https://vercel.com/account/tokens and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Vercel Routing and Releases read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Vercel Routing and Releases connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Zuplo Platform (BYOK)

Read your Zuplo accounts, projects, environments, deployments, custom domains, tunnels and API key buckets with your own account API key

Live · MCP + REST12 tools

Abstract Public Holidays (BYOK)

Look up public holidays for a country, year, month or day with BYOK

Live · MCP + REST1 tools

Acryl Cloud (BYOK)

Search and read your DataHub Cloud (Acryl) catalog: datasets, dashboards, glossary, domains, lineage and ingestion sources, with your own personal access token

Live · MCP + REST9 tools

Activepieces (BYOK)

Read your Activepieces projects, flows, flow runs, tables and connections with your own platform API key

Live · MCP + REST9 tools

Affinda (BYOK)

Read your Affinda document extraction organizations, workspaces, document types, document processing status, usage and data sources with your own API key

Live · MCP + REST10 tools

AfterShip (BYOK)

Read your AfterShip parcel trackings and their checkpoints and look up supported couriers with your own API key

Live · MCP + REST5 tools

Documentation

Back to top

Vercel Routing and Releases (BYOK) — connector documentation

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

What Vercel Routing and Releases (BYOK) is for

Vercel Routing and Releases (BYOK) lets an AI assistant read your own Vercel Routing and Releases data through the Vercel Routing and Releases API with a key you supply (access token). Read-only: 6 tools (list_route_versions, list_redirect_versions, get_rolling_release, get_rolling_release_config, list_custom_environments, get_custom_environment). 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.vercel.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vercel Routing and Releases. Vercel Routing and Releases 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 routing rule version is live on my Vercel project?"
  • "Which bulk redirect version is live?"
  • "Is a rolling release in progress for my project?"
  • "How is rolling release configured for my project?"
  • "Which custom environments does my Vercel project have?"
  • "What domains does the staging environment use?"

What it does

  • list_route_versions: List the versions of a project's routing rules with id, live and staging flags, rule count, author and last-modified time.
  • list_redirect_versions: List the versions of a project's bulk redirects with id, name, live and staging flags, redirect count and last-modified time.
  • get_rolling_release: Get the current rolling release of a project: state, canary percentage, advancement type, current stage and start time.
  • get_rolling_release_config: Get a project's rolling release settings: target environment, stages, advancement gate and canary header flag.
  • list_custom_environments: List a project's custom environments with slug, type, description, domains, current aliases and dates.
  • get_custom_environment: Get one custom environment of a project.

BYOK key

You bring your own Vercel Routing and Releases access token (https://vercel.com/account/tokens). 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.vercel.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.

Data sources

Live from the Vercel Routing and Releases API (api.vercel.com) with a BYOK key; documentation: https://vercel.com/docs/rest-api/reference/endpoints/project-routes. 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 Vercel Routing and Releases. Vercel Routing and Releases 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 Vercel Routing and Releases account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Vercel Routing and Releases (BYOK) — Privacy Policy

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

What Vercel Routing and Releases (BYOK) is. Vercel Routing and Releases (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Vercel Routing and Releases data: Read your Vercel project route versions, bulk redirect versions, rolling release configuration and state and custom environments with your own access token. You bring your own Vercel Routing and Releases access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Vercel Routing and Releases 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.vercel.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 Vercel Routing and Releases 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 Vercel Routing and Releases receives. The request we make on your behalf, including the key and the arguments, under Vercel Routing and Releases's own terms and privacy policy. Vercel Routing and Releases acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Vercel Routing and Releases 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 Vercel Routing and Releases 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. Vercel Routing and Releases (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 Vercel Routing and Releases at any time to end all access.

Children. Vercel Routing and Releases (BYOK) is a general-audience service operated by the adult using the assistant, under Vercel Routing and Releases's own age rules.

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

Terms of service

Back to top

Vercel Routing and Releases (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Vercel Routing and Releases (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Vercel Routing and Releases (BYOK) provides: Read your Vercel project route versions, bulk redirect versions, rolling release configuration and state and custom environments with your own access token. 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 Vercel Routing and Releases credentials and only access data you are allowed to access. Vercel Routing and Releases's terms apply to your use of Vercel Routing and Releases; 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 Vercel Routing and Releases. Vercel Routing and Releases 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 Vercel Routing and Releases returns, lightly trimmed; it may be incomplete, delayed or changed by Vercel Routing and Releases. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Vercel Routing and Releases 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 Vercel Routing and Releases'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; Vercel Routing and Releases 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 Vercel Routing and Releases 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 Vercel Routing and Releases 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-vercel-routing

Support

Back to top

Vercel Routing and Releases (BYOK) support

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

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. Vercel Routing and Releases (BYOK) never asks for them.

Get Vercel Routing and Releases (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Vercel Routing and Releases access token. Create one at https://vercel.com/account/tokens, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Vercel Routing and Releases. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Vercel Routing and Releases.