Integrations / Vercel Connect
Short-lived Bird tokens for Vercel workloads
Give your deployed AI agents and backend services on-demand access to Bird without storing static API keys in environment variables. Register the Bird connector once at the Vercel team level, link authorized projects, and mint short-lived tokens at runtime.
Drag an icon onto the dots. Use arrow keys to move a focused icon. Press Escape to cancel a drag.
Exchange workload identity for short-lived tokens
When your Vercel deployment runs, it authenticates to Vercel Connect using its built-in OIDC workload identity. Connect exchanges that authorization with Bird and returns a short-lived, scoped bearer token for your request, eliminating long-lived secrets that need manual rotation.
- Create
- vercel connect create bird --name acme-bird
- Install
- npm install @vercel/connect
The same connector can be created from the dashboard.
Zero static secrets in your deployment environment.On-demand runtime tokens for agents and services, or static environment variables when you prefer them.
Mint tokens on demand via OIDC. Skip storing long-lived Bird API keys in project settings. Every deployment proves its identity with Vercel's OIDC token and receives a short-lived Bird token that expires automatically.
$ getToken
$ OIDC
Act on behalf of a user or your service. Request a token scoped to an individual signed-in operator or to your background service from the same team-level connector.
$ user
$ app
Prefer static environment variables? If your application just needs a standard workspace API key and regional base URL injected into project environment variables, use the Vercel Marketplace integration instead. See the Marketplace integration.
$ Marketplace
Put it into practice.
Continue with the documentation, guides and examples for this topic.