Vercel Connect Is GA — End of Credential Sprawl for Agents

What shipped? Vercel Connect graduated from public beta to general availability today, bringing runtime-scoped credentials to agents instead of long-lived secrets.

What changed? Instead of storing API keys in environment variables, your code requests a token at runtime using the deployment's OIDC identity. Tokens are short-lived, scoped per-request (down to a single repo with read-only on GitHub), and expire automatically. Vercel now ships 100+ preset connectors for Slack, GitHub, Linear, Salesforce, Notion, Shopify, and more — plus support for custom OAuth services and MCP servers.

GA additions include fine-grained RBAC for connector management, audit logs for token and trigger activity, and per-environment connector attachment. Pricing starts at 500 token requests/month free on Hobby, $3/1k on Pro.

Why a builder cares? Every agent that touches Slack, GitHub, or an internal API currently needs a long-lived token that a vault can't limit once stolen. Connect flips the model: your app has no secrets to leak, tokens scope to exactly what the step needs, and human-in-the-loop triggers mean a refund action pauses until approved. This is the credential model agent platforms should have shipped years ago.