# Using coding agents to procure Vercel Marketplace integrations **Author:** Delba de Oliveira --- When you're building a production application, you’ll likely need to integrate external services, such as databases, auth providers, and logging tools. Setting these up manually means creating accounts, navigating through dashboards and copying credentials, then wiring everything together yourself. It works. But what if your coding agent could automatically discover and integrate these services for you? The [Vercel CLI](https://vercel.com/docs/cli) exposes a set of structured `vercel integration` commands that agents can invoke to handle the procurement lifecycle. You tell the agent what integration you need. It runs the right commands to browse the [Vercel Marketplace](https://vercel.com/marketplace), provision resources, pull credentials into your project, and manage connected services. ## Example As an example, we'll walk through setting up a Next.js calendar application that needs three integrations: [Supabase](https://vercel.com/integrations/supabase) for the database, [Clerk](https://vercel.com/integrations/clerk) for authentication, and [Stripe](https://vercel.com/integrations/stripe) for payments. ## Getting started ### Step 1: Install or update the Vercel CLI Install or update the Vercel CLI to the latest version. `npm i -g vercel@latest` ### Step 2: Log in Use the `vercel login` command to log in. Once you authenticate, both you and your agent have access to all Marketplace integrations. No need to authenticate separately with each provider. `vercel login` ### Step 3: Install the Vercel CLI skill To help your agent use the Vercel CLI, you can install the available `vercel-cli` skill: `npx skills add vercel/vercel --skill vercel-cli` ### Step 4: Discover available integrations You can prompt your agent to discover the available Vercel Marketplace integrations. Your agent will then run the `discover` command: `vercel integration discover --format=json` The `--format=json` flag gives the agent structured output it can parse and reason about. ### Step 5: Provision and connect integrations When you prompt the agent to add Supabase, it runs the `add` command. This installs the integration, provisions a resource at the provider and connects it to your project. `vercel integration add supabase --name calendar-db` The `--name` flag sets the resource name. Without it, a default name will be generated. After provisioning, the agent can run`vercel env pull` to pull the credentials into your local environment file. If you ask your agent to provision multiple services at once, it provisions each service sequentially: `vercel integration add clerk --name calendar-auth vercel integration add stripe --name calendar-payments` After adding an integration, the agent can pull the setup guide to get framework-specific instructions for wiring the integration into your application. `vercel integration guide clerk --framework nextjs` ### Handling metadata, plans, and legal terms Some integrations require decisions provisioning (e.g., a region or plan). The agent can pass these with the `--metadata` or `--plan` `vercel integration add neon -m region=us-east-1 --plan free` If an integration requires terms acceptance for the first time, the CLI will prompt you to review and accept in your browser. The CLI polls in the background and resumes automatically once you accept. Currently agent cannot bypass this step. ### Step 6: Manage integrations After setup, you can ask the agent to manage your integrations. Here are some examples: - **List connected resources** with `vercel integration list` - **Open a provider dashboard** with `vercel integration open ` - **Check billing and set spending thresholds** with `vercel integration balance ` - **Disconnect a resource** from a project with `vercel integration resource disconnect ` - **Remove a resource or integration** with `vercel integration resource remove ` or `vercel integration remove ` For the full command reference, see the [Vercel CLI](https://vercel.com/docs/cli/integration) `integration` [docs](https://vercel.com/docs/cli/integration). ## Security The Vercel CLI exposes integrations through structured commands that agents can invoke. The agent does not execute arbitrary code. It interacts with a fixed set of CLI commands (`discover`, `add`, `guide`, `list`, `open`, `balance`, `remove`) that each have a limited scope. Commands accept `--format=json` flag, so the agent gets structured data it can parse and reason about instead of free-form text. Environment variables are managed automatically through `vercel env pull`. For critical actions, such as choosing a paid plan or accepting a provider's terms of service, the CLI pauses and redirects to the Vercel dashboard for you human review. You stay in control of the decisions that require judgment, while the agent handles the mechanical work of provisioning and wiring up services. ## Next steps - [Vercel CLI overview](https://vercel.com/docs/cli/integration) for the full command reference. - [Vercel Marketplace](https://vercel.com/marketplace) to browse available integrations. - [Environment variables](https://vercel.com/docs/environment-variables) to learn how credentials are managed across environments. --- [View full KB sitemap](/kb/sitemap.md)