Vercel Connect adds managed Stripe API keys

Vercel Connect can now create a separate restricted Stripe API key for each agent or task. When you create a Stripe connector, you can now choose Managed API Key as the connection method.

Vercel creates the key in your Stripe account, limited to the permissions you pick. The existing MCP and bring-your-own API key methods are unchanged.

Most apps and agents run on Stripe’s default secret key, which has full access to the account. With per-agent keys, each agent gets only the access its job needs. For example, a daily revenue report agent can be limited to read-only access to charges, and an onboarding agent can be limited to write access to customers.

Vercel creates and stores the key, so there is no secret key to paste. You can rotate it from the connector's settings without redeploying, and the old key stays valid for up to 24 hours while you switch.

Copy link to headingAdd the Stripe connector

Create a Stripe connector from the connectors directory, choose Managed API Key, pick its permissions, and attach it to your project. You can also start from the CLI, which opens the browser to finish setup:

1
vercel connect create stripe --connection-method managed-api-key --name acme-stripe
2
vercel connect attach stripe/acme-stripe --project my-app --environment production

1
import Stripe from 'stripe';
2
import { getToken } from '@vercel/connect';
3
const key = await getToken('stripe/acme-stripe', {
4
  subject: { type: 'app' },
5
});
6
const stripe = new Stripe(key);
7
const customers = await stripe.customers.list({ limit: 10 });

To get started, add the Stripe connector or read the documentation.