marketplace

# Get agent-friendly setup guide for a specific integration
vercel integration guide <name>
 
# Include framework-specific steps when available
vercel integration guide <name> --framework <fw>
 
# Examples
vercel integration guide neon
vercel integration guide datadog --framework nextjs

# Install from CLI
vercel integration add <integration-name>
 
# Examples
vercel integration add neon          # Postgres database
vercel integration add upstash       # Redis / Kafka
vercel integration add clerk         # Authentication
vercel integration add sentry        # Error monitoring
vercel integration add sanity        # CMS
vercel integration add datadog       # Observability (auto-configures drain)

vercel integration open <integration-name>

# View environment variables added by integrations
vercel env ls
 
# Example: after installing Neon, these are auto-provisioned:
# POSTGRES_URL          — connection string
# POSTGRES_URL_NON_POOLING — direct connection
# POSTGRES_USER         — database user
# POSTGRES_PASSWORD     — database password
# POSTGRES_DATABASE     — database name
# POSTGRES_HOST         — database host

// app/api/users/route.ts — using Neon auto-provisioned env vars
import { neon } from "@neondatabase/serverless";
 
// POSTGRES_URL is auto-injected by the Neon integration
const sql = neon(process.env.POSTGRES_URL!);
 
export async function GET() {
  const users = await sql`SELECT * FROM users LIMIT 10`;
  return Response.json(users);
}

// app/api/cache/route.ts — using Upstash auto-provisioned env vars
import { Redis } from "@upstash/redis";
 
// KV_REST_API_URL and KV_REST_API_TOKEN are auto-injected
const redis = Redis.fromEnv();
 
export async function GET() {
  const cached = await redis.get("featured-products");
  return Response.json(cached);
}

# List installed integrations
vercel integration ls
 
# Check usage and billing for an integration
vercel integration balance <name>
 
# Remove an integration
vercel integration remove <integration-name>

# Check current usage balance for an integration
vercel integration balance datadog
vercel integration balance neon

# Create a new integration project
npx create-vercel-integration my-integration
 
# Or start from the template
npx create-next-app my-integration --example vercel-integration

// vercel-integration.json
{
  "name": "my-integration",
  "slug": "my-integration",
  "description": "Provides X for Vercel projects",
  "logo": "public/logo.svg",
  "website": "https://my-service.com",
  "categories": ["databases"],
  "scopes": {
    "project": ["env-vars:read-write"],
    "team": ["integrations:read-write"]
  },
  "installationType": "marketplace",
  "resourceTypes": [
    {
      "name": "database",
      "displayName": "Database",
      "description": "A managed database instance"
    }
  ]
}

// app/api/webhook/route.ts
import { verifyVercelSignature } from "@vercel/integration-utils";
 
export async function POST(req: Request) {
  const body = await req.json();
 
  // Verify the webhook is from Vercel
  const isValid = await verifyVercelSignature(req, body);
  if (!isValid) {
    return Response.json({ error: "Invalid signature" }, { status: 401 });
  }
 
  switch (body.type) {
    case "integration.installed":
      // Provision resources for the new installation
      await provisionDatabase(body.payload);
      break;
 
    case "integration.uninstalled":
      // Clean up resources
      await deprovisionDatabase(body.payload);
      break;
 
    case "integration.configuration-updated":
      // Handle config changes
      await updateConfiguration(body.payload);
      break;
  }
 
  return Response.json({ received: true });
}

// lib/provision.ts
async function provisionEnvVars(
  installationId: string,
  projectId: string,
  credentials: { url: string; token: string },
) {
  const response = await fetch(
    `https://api.vercel.com/v1/integrations/installations/${installationId}/env`,
    {
      method: "POST",
      headers: {
        Authorization: `Bearer ${process.env.VERCEL_INTEGRATION_TOKEN}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({
        projectId,
        envVars: [
          {
            key: "MY_SERVICE_URL",
            value: credentials.url,
            target: ["production", "preview", "development"],
            type: "encrypted",
          },
          {
            key: "MY_SERVICE_TOKEN",
            value: credentials.token,
            target: ["production", "preview", "development"],
            type: "secret",
          },
        ],
      }),
    },
  );
 
  return response.json();
}

# Discover integrations in the Marketplace catalog
vercel integration discover
vercel integration discover --category <category>
 
# Get agent-friendly setup guide
vercel integration guide <name>
vercel integration guide <name> --framework <framework>
 
# Add (install) an integration
vercel integration add <name>
 
# List installed integrations
vercel integration list    # alias: vercel integration ls
 
# Check usage / billing balance
vercel integration balance <name>
 
# Open integration dashboard in browser (fallback when add redirects)
vercel integration open <name>
 
# Remove an integration
vercel integration remove <name>

# Discover observability integrations
vercel integration discover --category monitoring
 
# Get setup guide for chosen vendor
vercel integration guide datadog

# Install — auto-provisions env vars and creates log/trace drains
vercel integration add datadog

# Confirm drain was auto-configured
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v1/drains?teamId=$TEAM_ID" | jq '.[] | {id, url, type, sources}'

# Send a test payload to the drain
curl -X POST -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v1/drains/<drain-id>/test?teamId=$TEAM_ID"

# Trigger a deployment and check logs flow through
vercel logs <deployment-url> --follow --since 5m
 
# Check integration balance to confirm data is flowing
vercel integration balance datadog

# Create a drain for Speed Insights + Web Analytics
curl -X POST -H "Authorization: Bearer $VERCEL_TOKEN" \
  -H "Content-Type: application/json" \
  "https://api.vercel.com/v1/drains?teamId=$TEAM_ID" \
  -d '{
    "url": "https://your-vendor-endpoint.example.com/vercel-analytics",
    "type": "json",
    "sources": ["lambda"],
    "environments": ["production"]
  }'