Vercel Connect can now mint a scoped Stripe key per agent
A new Managed API Key option creates a restricted Stripe key for each agent or task, rotates without a redeploy, and keeps the old key valid for 24 hours during the switch.
Vercel Connect added Managed API Key as a connection method for its Stripe connector on 23 October. Choosing it creates a Stripe API key inside your own Stripe account, scoped to whatever permissions you pick, rather than wiring in one full-access secret key by hand.
The point is per-agent scoping: a daily revenue report agent can get read-only access to charges, while a separate onboarding agent gets write access to customers and nothing else. Vercel creates and stores the key, so there is no secret to paste into an environment variable. Rotating it happens from the connector’s settings without a redeploy, and the previous key stays valid for up to 24 hours while the new one takes over. The existing MCP and bring-your-own-key methods on Stripe still work unchanged.
Stripe connector → Managed API Key → pick scopes (e.g. charges:read)Why it matters: giving every agent in a pipeline the same master Stripe key is the kind of shortcut that turns one compromised task into full account access. Scoping keys per agent, with rotation that doesn’t need a deploy, is the more boring and more correct default for anyone wiring Stripe into an agent workflow.