Vercel has introduced Vercel Connect, a credential layer for applications and agents that need to act inside third-party services without keeping long-lived provider secrets in the app runtime.

The product is aimed at workflows where an agent needs scoped access to tools such as Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma or Snowflake. Instead of placing provider tokens in environment variables or a database, a linked Vercel deployment requests a short-lived token when it needs to call the provider.

Vercel's docs describe the system around connectors, installations, tokens, project links, triggers and authentication. A team creates a connector for a provider, accepts installations from workspaces or organizations, links that connector to Vercel projects and environments, and then lets runtime code request credentials through that link.

The launch is notable because agent applications often need delegated access to user tools, not just a model endpoint. A support agent might need Slack and Linear access, while a coding agent might need GitHub access. Keeping those permissions broad and permanent creates a larger security surface.

Connect does not remove every operational question. Vercel says token lifetime, revocation and scope granularity still depend partly on the provider, and trigger forwarding is in beta with Slack, GitHub and Linear support. But it gives Vercel-hosted agents a clearer pattern for requesting external access only when a task requires it.