Integrations / Vercel Connect
Bird tokens on demand
Vercel Connect gives your deployed agents and services short-lived access to Bird without a key in your environment. Add the Bird connector once at the team level, let the projects you choose use it, and ask for a token at the moment your code needs one.
Drag an icon onto the dots. Use arrow keys to move a focused icon. Press Escape to cancel a drag.
One connector, no stored secret
The connector authorises Bird for the user it acts on behalf of. Your code authenticates to Connect with the OIDC token Vercel injects into every deployment, Connect exchanges the authorisation with Bird, and your code receives a short, scoped token. Nothing to rotate, nothing to leak.
- Create
- vercel connect create bird --name acme-bird
- Install
- npm install @vercel/connect
The same connector can be created from the dashboard.
What the connector gives you.Credentials at runtime, and a clear line to the Marketplace integration.
Credentials on demand. No Bird key in environment variables. Each deployment proves who it is with Vercel's OIDC token and receives a Bird token that expires on its own.
$ getToken
$ OIDC
The right subject. Ask for a token that acts as a specific signed-in user, or as your service, from the same connector.
$ user
$ app
When to use the other one. If your project just needs a Bird key in its environment variables, the Marketplace integration writes it for you. See the Marketplace integration.
$ Marketplace
Put it into practice.
Continue with the documentation, guides and examples for this topic.