Vercel Connect can now mint per-agent restricted Stripe API keys

Vercel Connect, Vercel's service for linking external tools into applications, can now generate a restricted Stripe API key for each individual agent or task. According to the Vercel blog, the Stripe connector has gained a Managed API Key connection method, joining the existing MCP and bring-your-own-key options, which remain unchanged.

How managed keys work

When you create a Stripe connector and choose the managed option, Vercel creates the key inside your Stripe account and limits it to the permissions you select. Vercel also stores the key, which means there is no secret to copy, paste into an environment variable, or risk committing to a repository.

The motivation, according to Vercel, is that most applications and agents today run against Stripe's default secret key, which grants full access to the account. Under that model, one compromised or misbehaving agent can touch anything the account allows. Per-agent keys shrink that blast radius: Vercel's examples include a daily revenue-reporting agent restricted to read-only access on charges, and an onboarding agent restricted to write access on customers.

Rotation is handled from the connector's settings and requires no redeploy. During a rotation, the outgoing key stays valid for up to 24 hours, a grace period intended to keep running instances working while they move over to the replacement key.

Setting one up

A connector can be created from the connectors directory in the Vercel dashboard: pick Stripe, choose Managed API Key, select the permissions, and attach the connector to a project. The same flow is available from the CLI, where vercel connect create provisions a Stripe connector with the managed-api-key connection method and vercel connect attach then binds it to a named project and environment such as production.

At runtime, an application imports the official Stripe SDK and calls getToken from the @vercel/connect package, passing the connector's UID and a subject such as an app. The call returns the restricted key, which is handed directly to the Stripe client. The key is fetched rather than configured, so it never sits in application configuration at all.

Why it matters

Agentic systems are moving from demos into jobs that touch production billing data, and credential handling has not kept pace. A single full-access Stripe key shared across agents violates basic least-privilege principles, but restricted keys are tedious to mint, distribute and rotate by hand. Vercel is packaging that workflow: scoped keys created on demand, held by the platform, and rotatable without a deploy.

For teams building agents on Vercel, this closes a practical gap between giving an agent some Stripe access and giving it all Stripe access. The 24-hour overlap makes key rotation a routine operation rather than an incident. More broadly, it signals where platform tooling is heading: infrastructure that issues narrowly scoped, per-workload credentials instead of relying on long-lived secrets pasted into configuration.