Vercel Connect is now generally available. It eliminates long-lived API tokens by minting short-lived, scoped credentials at runtime using OIDC identity, meaning your app never stores a provider secret. During the public beta, Vercel grew the connector catalog past 100 integrations covering Slack, GitHub, Salesforce, Snowflake, Shopify, Workday, and more, plus any OAuth-capable MCP server.
The architecture matters more than the headline number. Tokens are scoped per request, not per app. A GitHub token can be restricted to a single repository with read-only access rather than a standing org-wide grant. Identity delegation is built in: pass a named user as the subject and the token acts on their behalf, scoped to what they authorized in a one-time consent flow. Triggers close the loop on the inbound side, verifying webhook signatures server-side and re-attesting events with OIDC before forwarding them to your project. Your app holds no bot token and no signing secret, yet the full event loop runs. GA also adds fine-grained RBAC, audit logs, and token observability across projects.
Pricing starts at zero: the Hobby plan includes 500 token requests and 1,000 triggers per month. Pro bills at $3 per 1,000 token requests and $0.95 per 1,000 triggers. The full piece covers how the SDK's single getToken call unifies credential access across eve agents, AI SDK tools, MCP clients, Better Auth, and Auth.js, and includes a production case from Moonpig Group running a legal agent on this model. That implementation detail is worth reading.
[READ ORIGINAL →]