What problem does it solve? Applications and agents often need scoped OAuth tokens to call third-party APIs like Slack, GitHub, Linear, Snowflake, or MCP servers, but managing OAuth consent flows, token rotation, and credential storage is complex. Vercel Connect exchanges Vercel OIDC tokens for scoped third-party tokens so apps never handle raw provider credentials. ## Core Features & Use Cases - Token Exchange via CLI, SDK, or HTTP API: Use vercel connect CLI commands, the @vercel/connect JavaScript/TypeScript SDK, or direct HTTP calls authenticated with VERCEL_OIDC_TOKEN to obtain user-scoped, app-scoped, or JWT-bearer tokens. - Eve Agent Integrations: Helpers like connect, connectSlackCredentials, connectGitHubCredentials, and connectLinearCredentials wire token lifecycle and webhook verification into Eve connection and channel definitions without env vars. - Auth Framework Plugins: Plug connectors into Better Auth (@vercel/connect/betterauth) or Auth.js (@vercel/connect/authjs) as OAuth providers. - Use Case: An Eve agent needs to post Slack messages as a bot and receive verified Slack webhooks; registering a Slack connector and calling connectSlackCredentials("slack/myagent") handles both outbound tokens and inbound signature verification. ## Quick Start Run "vercel connect create slack" from your project folder, complete the browser registration, then use "vercel connect token <connector>" or the @vercel/connect SDK to get a token and call the Slack API.