GitHub Copilot
Get AI coding suggestions, code explanations, reviews and agent assistance across GitHub and supported development environments.
Vercel Connect
vercel.com
Manage runtime credentials and third-party service connections for applications and AI agents across projects and environments.
Visit website
Pricing
Freemium
Available on
Vercel, External CI/CD, TypeScript SDK, Python SDK
Category
Developer Tools
What is Vercel Connect?
Vercel Connect manages connections that applications and AI agents use to access third-party services. Developers configure connections at the team level, authorize projects and environments, and request credentials at runtime. Supported services include Slack, GitHub, Microsoft, Snowflake and Salesforce, alongside custom OAuth and API-key services.
It serves developers building shared service integrations or applications that act on behalf of users. For Stripe, the Managed API Key method creates a separate restricted key for an agent or task, with selected permissions and rotation through connector settings.
Key features
Runtime credential access
Request credentials from application code. The SDK authenticates through Vercel OIDC on Vercel or a Vercel access token in external environments.
Reusable team connections
Make provider connections available to authorized projects and environments. Authentication methods and capabilities vary by connector.
Managed Stripe permissions
Create separate restricted Stripe keys with permissions selected during setup. Vercel creates and stores each managed key.
Stripe key rotation
Rotate a managed key in connector settings without redeployment. The old key remains valid for up to 24 hours during the transition.
Token caching
Reuse cached credentials until they enter the validity buffer, reducing Connect token requests across repeated provider calls.
Framework adapters
Integrate through adapters for AI SDK, TanStack AI, MCP clients, eve, Chat SDK, Better Auth and Auth.js.
Who is it for?
Restrict a reporting agent
A developer can give a Stripe reporting agent read access to charges using permissions selected for that task.
Separate onboarding permissions
A product team can configure a different Stripe connection for an onboarding agent that creates customers.
Share a service connection
A platform team can make an authorized provider connection available to selected projects and environments.
Connect user accounts
An application developer can request runtime service access on behalf of an authorized user.
How to use Vercel Connect
- Create a Vercel account, install the Vercel CLI and link your project.
- Choose a supported provider, create a connector and complete its authorization flow.
- Attach the connector to the intended project and environment.
- Install the TypeScript or Python SDK and request a runtime token from application code.
- For managed Stripe access, choose Managed API Key during setup and select the required permissions.
Vercel Connect pricing
Freemium
Hobby includes 500 token requests and 1,000 triggers per month at no extra charge. Paid usage measures token requests and triggers separately, while Enterprise has custom pricing. See the official pricing page for current rates and billing details.
Check current pricing ↗What to know before you use it
- The quickstart requires Node.js 18 or later for TypeScript, or Python 3.10 or later with uv for Python, plus a Vercel account and CLI.
- Authentication methods and capabilities differ between connectors. External-environment use still requires a Vercel account and authorized connector access.
- The platform limit is three trigger destinations per connector. API rate limits reset after one minute; exceeding them returns 429 responses, and SDK token methods throw errors.
- Each webhook destination counts separately toward trigger usage. An incoming webhook with no destinations still counts as one trigger, so removing destinations alone does not stop that usage.
Frequently asked questions
Can I use Connect outside Vercel deployments?
Yes. The SDK supports Vercel access-token authentication in external CI/CD and non-Vercel environments, subject to authorized connector access.
Does every provider API call count as a token request?
No. Provider API calls and Connect token requests are different units. Token caching can reuse credentials across multiple provider calls.
Must I supply my own Stripe API key?
No. Managed API Key lets Vercel create and store a restricted Stripe key with selected permissions. MCP and user-supplied API-key methods also remain available.