Introducing Vercel Connect
Vercel just killed the long-lived API token. Agents now request scoped credentials at runtime instead—no secrets stored, no rotation headaches.
Why it matters
Vercel Connect shifts agent security from 'store broad tokens and hope they don't leak' to runtime credential exchange with per-task scoping. For founders building agents, this is table-stakes infrastructure that moves secret management from app code to a managed platform layer.
The key facts
9 to knowRuntime credential exchange replaces long-lived provider tokens
Supports Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma, Snowflake with more coming
Token scoping: agents request only the access needed for each task (e.g., read-only on one GitHub repo)
OIDC identity proof—no provider secret stored in app
Trigger forwarding in beta for Slack, GitHub, Linear (webhook event-driven agents)
Per-user token scoping available
Pricing: Hobby 5K token requests/month free; Pro/Enterprise $3 per 10K requests
Integrates with AI SDK, MCP, Better Auth, Auth.js, Eve framework
Environment-level isolation (dev/preview/prod connectors separate)
Go to the source
Vercel Blogvercel.com
Publisher excerpt: Giving your agents access to your tools, data, and services is what makes them useful. As agents perform deeper work across systems, authenticating and authorizing that access becomes central to your application architecture. Today, agent access is usually granted through long-lived provider tokens…