AgentsAugust 25, 2026via Vercel Blog
The end of credential sprawl for agents
Why it matters
Agents touching multiple systems need credentials to operate, but long-lived tokens create systemic risk. Vercel Connect shifts to runtime-requested, auto-expiring, task-scoped credentials with full audit trails—enabling agents to scale safely in production without credential management overhead.
Key signals
- Vercel Connect GA: 100+ preset connectors (Slack, GitHub, Linear, Salesforce, Notion, Shopify, Workday)
- Runtime-scoped tokens auto-expire; no long-lived secrets stored in app or vault
- OIDC identity per request; tokens act as app or named user with one-time consent
- Per-environment attachment, RBAC for connector management, full audit logs of access and connector activity
- Pricing: Hobby free (500 token requests, 1,000 triggers/month); Pro $3/1K requests, $0.95/1K triggers
- Integration with eve agents, Chat SDK, AI SDK, MCP servers; v0 auto-setup during build
- Triggers handled server-side without bot token in app; events forwarded even with Deployment Protection
- Production examples: Moonpig Group internal legal agent, KERNEL voice-driven browser agent
- Beta users' pricing frozen until Sept 25, 2026
The hook
Vercel Connect replaces long-lived tokens with runtime-scoped credentials—solving the credential sprawl problem that makes agents dangerous in production.
Every useful agent reaches beyond your codebase. It posts to Slack, opens pull requests, queries Snowflake, or calls an internal API. That reach is what makes it valuable, and it's also where the risk lives, because for years, granting it meant provisioning a long-lived token and hoping it never lea…