Integration Ecosystem and Environment Variables

Relevant source files

• v0 Prompts and Tools/Prompt.txt
• v0 Prompts and Tools/Tools.json

This document describes v0's comprehensive integration system for connecting Code Projects to external services including databases, AI providers, and payment processors. It covers the GetOrRequestIntegration tool, environment variable management, and service-specific implementation requirements.

For general v0 architecture and file operations, see CodeProject Architecture and File Operations. For AI SDK usage patterns, see Script Execution and Debugging System.

---

Overview

v0 provides first-class support for specific integrations that automatically configure environment variables and provide live schema information. The system handles three categories of external services: storage/databases, AI/ML providers, and payment processors. All integration setup occurs within the v0 UI without requiring users to leave the platform.

Sources: v0 Prompts and Tools/Prompt.txt531-543 v0 Prompts and Tools/Tools.json285-323

---

Integration Categories and Supported Services

Integration Ecosystem Architecture

Sources: v0 Prompts and Tools/Prompt.txt547-579 v0 Prompts and Tools/Tools.json293-309

Supported Integrations Table

Category	Integration	Package(s)	Environment Variables	Auto-Schema
Storage	Supabase	@supabase/ssr	DATABASE_URL, auth vars	Yes (tables, columns, RLS)
	Neon	@neondatabase/serverless	DATABASE_URL	Yes (tables, columns)
	Upstash for Redis	Built-in	KV_REST_API_URL, KV_REST_API_TOKEN	No
	Vercel Blob	Built-in	BLOB_READ_WRITE_TOKEN	No
	Upstash Search	Built-in	Search-specific vars	No
	Edge Config	Built-in	Config-specific vars	No
AI/ML	xAI (Grok)	AI SDK	XAI_API_KEY	No
	Groq	AI SDK	GROQ_API_KEY	No
	Fal AI	@fal-ai/serverless	FAL_KEY	No
	DeepInfra	AI SDK	DEEPINFRA_API_KEY	No
	Vercel AI Gateway	AI SDK (default)	None (automatic)	No
Payments	Stripe	Built-in	STRIPE_SECRET_KEY, STRIPE_PUBLISHABLE_KEY, NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY	No

Sources: v0 Prompts and Tools/Prompt.txt547-687 v0 Prompts and Tools/Tools.json293-309

---

Environment Variable System

Variable Scope and Access

v0 supports environment variables from Vercel but does not support .env files in the browser runtime. Variables follow Next.js conventions for server/client access:

• Server-only variables: Available in Server Actions and Route Handlers without prefix
• Client-accessible variables: Must be prefixed with NEXT_PUBLIC_
• Automatic injection: Integration-provided variables are automatically added to the project

Environment Variable Flow

Sources: v0 Prompts and Tools/Prompt.txt456-458 v0 Prompts and Tools/Prompt.txt534-536

Variable Verification and Troubleshooting

When generated code references environment variables, v0 automatically prompts users to verify they are added to the Vercel project. Users troubleshoot integration issues by:

1. Checking integrations in the Connect section of the in-chat sidebar
2. Verifying environment variables in the Vars section of the in-chat sidebar

Sources: v0 Prompts and Tools/Prompt.txt534-542

---

GetOrRequestIntegration Tool

Tool Purpose and Behavior

The GetOrRequestIntegration tool performs three critical functions:

1. Status checking: Verifies which integrations are connected and configured
2. Schema retrieval: Fetches live database schemas for SQL integrations (tables, columns, RLS policies)
3. Automatic requesting: Stops execution and requests user setup for missing required integrations

Tool Workflow

Sources: v0 Prompts and Tools/Tools.json285-323

Tool Parameters

Parameter	Type	Required	Description
names	string[]	No	Specific integration names to check. Omit or use empty array for overview of all integrations. Valid values: "Upstash for Redis", "Upstash Search", "Neon", "Supabase", "Groq", "Grok", "fal", "Deep Infra", "Stripe", "Blob", "Edge Config", "Vercel AI Gateway"
taskNameActive	string	Yes	2-5 words describing running task (e.g., "Checking Database Setup")
taskNameComplete	string	Yes	2-5 words describing completed task (e.g., "Database Setup Verified")

Usage Patterns

Before building integration features:

For database schema retrieval:

For project discovery:

Sources: v0 Prompts and Tools/Tools.json285-323

---

Storage Integration Details

Supabase Integration

Package Requirements

v0 MUST use the @supabase/ssr package for both client-side and server-side Supabase operations. The standard @supabase/supabase-js package is not used.

Client Initialization Pattern

v0 implements the singleton pattern for Supabase clients to prevent initialization errors:

Sources: v0 Prompts and Tools/Prompt.txt587-591

Authentication Implementation

Email/Password Authentication:

• v0 MUST use only default email and password authentication unless user explicitly requests other methods
• OAuth and other authentication methods are NEVER implemented unless explicitly requested
• Client-side authentication is preferred; server actions only when explicitly requested

Required Pattern for signUp:

The emailRedirectTo option MUST be set using environment variable for development and window.location.origin for production:

Server-side middleware for token refresh:

v0 MUST use createServerClient in middleware.ts (or proxy.js in Next.js 16) to refresh tokens and set cookies:

Sources: v0 Prompts and Tools/Prompt.txt599-633

Row Level Security (RLS) Mandate

v0 MUST use Row Level Security to protect data. Security is non-negotiable. When retrieving database schema via GetOrRequestIntegration, RLS policies are included in the response and must be respected in code generation.

Sources: v0 Prompts and Tools/Prompt.txt637-638

Dashboard Access Restrictions

• v0 NEVER tells users to go to Supabase dashboard for integration setup (done in v0 UI)
• v0 NEVER recommends using Supabase SQL editor to run scripts (scripts run from /scripts folder directly)

Sources: v0 Prompts and Tools/Prompt.txt592-595

Neon Integration

Package and Connection Pattern

v0 MUST use the @neondatabase/serverless package and the neon() function for creating SQL clients:

v0 NEVER uses the @vercel/postgres package for Neon databases.

Sources: v0 Prompts and Tools/Prompt.txt643-648

Upstash for Redis Integration

Uses two environment variables:

• KV_REST_API_URL: Redis instance REST endpoint
• KV_REST_API_TOKEN: Authentication token for REST API

Sources: v0 Prompts and Tools/Prompt.txt650-653

---

AI Provider Integrations

AI SDK and Vercel AI Gateway

Default AI Provider Pattern

The AI SDK uses the Vercel AI Gateway by default. Provider packages are not necessary—v0 passes a model string to the model parameter, and Next.js automatically handles API keys and configurations.

Supported providers in AI Gateway (no API key required):

• AWS Bedrock
• Google Vertex
• OpenAI (e.g., "openai/gpt-5-mini")
• Fireworks AI
• Anthropic (e.g., "anthropic/claude-sonnet-4.5")

Sources: v0 Prompts and Tools/Prompt.txt319-343

xAI (Grok) Integration

Environment Variable

• XAI_API_KEY: API key for xAI Grok models

Usage Pattern

v0 MUST use model: xai("grok-4") unless user requests a different Grok model. The xAI integration should ONLY be used if Grok is explicitly requested; otherwise, v0 uses the Vercel AI Gateway.

Sources: v0 Prompts and Tools/Prompt.txt655-661

Groq Integration

Environment Variable

• GROQ_API_KEY: API key for Groq LLM inference

Groq should ONLY be used if explicitly requested by the user. Otherwise, v0 uses the Vercel AI Gateway to avoid requiring user configuration.

Sources: v0 Prompts and Tools/Prompt.txt663-667

Fal AI Integration

Package and Client Pattern

v0 MUST use the @fal-ai/serverless package and the fal() function:

Environment Variable

• FAL_KEY: API key for Fal AI image generation services

Sources: v0 Prompts and Tools/Prompt.txt669-674

DeepInfra Integration

Environment Variable

• DEEPINFRA_API_KEY: API key for DeepInfra AI infrastructure

DeepInfra should ONLY be used if explicitly requested. Otherwise, v0 uses the Vercel AI Gateway.

Sources: v0 Prompts and Tools/Prompt.txt676-680

---

Payment Integration: Stripe

Environment Variables

Stripe integration uses three environment variables:

• STRIPE_SECRET_KEY: Server-side secret key
• STRIPE_PUBLISHABLE_KEY: Public key for server-side usage
• NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY: Public key for client-side usage

Sandbox and Production Workflow

1. By default, Stripe integration creates a claimable sandbox
2. Users claim the sandbox from the Connect section of the in-chat sidebar
3. To go live, users replace test environment variables with live environment variables from the Stripe dashboard

Usage Requirements

• v0 MUST use a payment integration to create e-commerce, checkout, and subscription experiences
• v0 MUST prompt the user to install the payment integration before building UI to display products

Sources: v0 Prompts and Tools/Prompt.txt682-687

---

SQL Database Operations

Script Execution Model

v0 generates SQL scripts in the /scripts folder of Code Projects. Key characteristics:

• Users do NOT need to leave v0 to run scripts—v0 executes them directly
• v0 NEVER uses an ORM to connect to SQL databases (Supabase, Neon) unless explicitly requested
• Instead of editing existing scripts, v0 MUST create new files with version numbers

Script versioning example:

/scripts/001-create-users-table.sql
/scripts/002-add-profiles-table.sql
/scripts/003-update-users-add-email.sql

Sources: v0 Prompts and Tools/Prompt.txt556-561 v0 Prompts and Tools/Prompt.txt205-210

Live Schema vs. Script Files

When an integration is connected, v0 uses GetOrRequestIntegration to retrieve the live database schema instead of reading SQL scripts from files. This ensures accuracy and reflects the current state of the database, including:

• Tables and columns
• Data types and constraints
• RLS policies (for Supabase)

Sources: v0 Prompts and Tools/Tools.json287-288

---

Integration Setup Workflow

User-Facing Setup Process

Sources: v0 Prompts and Tools/Prompt.txt534-542 v0 Prompts and Tools/Tools.json285-323

In-Chat Sidebar Sections

Users manage integrations through the sidebar:

• Connect: Manage and add integrations to the project
• Vars: Add and manage environment variables for the project
• Settings: Manage Vercel project connection, GitHub repository connection

Sources: v0 Prompts and Tools/Prompt.txt862-869

---

Integration Selection Strategy

When to Use Specific Integrations

v0 follows these guidelines for integration selection:

AI Provider Selection:

1. Default to Vercel AI Gateway when no specific provider is requested (supports OpenAI, Anthropic, etc. without configuration)
2. Use xAI integration only when user explicitly requests Grok models
3. Use Groq integration only when user explicitly requests Groq
4. Use DeepInfra integration only when user explicitly requests DeepInfra
5. Use Fal AI integration when user requests image generation capabilities

Database Selection:

• User preference determines choice between Supabase and Neon
• Supabase is preferred when authentication is required (built-in auth)
• Neon is suitable for pure database operations without auth

Payment Processing:

• Stripe is the only supported payment integration
• Must be explicitly requested or prompted before building payment UI

Sources: v0 Prompts and Tools/Prompt.txt655-680 v0 Prompts and Tools/Prompt.txt581-585

---

Integration Code Generation Patterns

Pre-Generation Integration Check

Sources: v0 Prompts and Tools/Tools.json285-323 v0 Prompts and Tools/Prompt.txt531-543

Example Integration Usage in Generated Code

Supabase Authentication: v0 Prompts and Tools/Prompt.txt599-633

Neon Database Query: v0 Prompts and Tools/Prompt.txt643-648

AI SDK with Gateway: v0 Prompts and Tools/Prompt.txt336-341

Fal AI Client: v0 Prompts and Tools/Prompt.txt669-674

---

Integration Troubleshooting

Common Issues and Resolution

Issue	Resolution Path	Reference
Integration not working	Check Connect section in sidebar	v0 Prompts and Tools/Prompt.txt538-541
Environment variables missing	Check Vars section in sidebar	v0 Prompts and Tools/Prompt.txt538-541
Database schema mismatch	Call GetOrRequestIntegration to get live schema	v0 Prompts and Tools/Tools.json287-288
Supabase client errors	Verify singleton pattern implementation	v0 Prompts and Tools/Prompt.txt591
RLS policy violations	Check policies in GetOrRequestIntegration response	v0 Prompts and Tools/Prompt.txt637-638
AI provider not responding	Verify using Vercel AI Gateway (default)	v0 Prompts and Tools/Prompt.txt323-327

Integration Examples and Documentation

When GetOrRequestIntegration returns integration information, it includes links to example code templates when available. These provide reference implementations for common integration patterns.

Sources: v0 Prompts and Tools/Tools.json287-288

---

Summary

v0's integration ecosystem provides automatic environment variable management, live schema retrieval, and seamless service connection for 12+ external services across storage, AI, and payment categories. The GetOrRequestIntegration tool ensures integrations are configured before code generation, preventing runtime errors. All integration setup occurs within the v0 UI, and generated code follows service-specific best practices including RLS for Supabase, singleton patterns for client initialization, and Vercel AI Gateway for AI operations.

Sources: v0 Prompts and Tools/Prompt.txt531-687 v0 Prompts and Tools/Tools.json285-323