What you can do

Projects — List all projects in your account or team, and inspect their configuration.
Deployments — Browse recent deployments, check their build status, and inspect build logs.
Domains — View domains attached to projects and check DNS configuration status.
Environment Variables — List environment variable keys across projects (values are never exposed).
Teams — View team memberships and project access across your Vercel organisation.
User Account — Fetch your Vercel account details and subscription tier.

Getting your Vercel API Token

Flarite uses a Vercel API Token to access your account. Tokens can be scoped to your personal account or to a specific team.

Go to vercel.com → Account Settings → Tokens.
Click "Create".
Give it a descriptive name like "Flarite Access".
Choose a scope:

Full Account      — Access all personal projects and teams (recommended)
Specific Team     — Limit access to one Vercel team only

✨

TipIf your projects live inside a Vercel Team, select Full Account scope or the specific team scope. Using a personal token without team access won't show team projects.

Set an optional expiry (90 days recommended for security).
Click "Create Token" and copy it immediately — it won't be shown again.
Paste it into Flarite → Vercel → API Tokens.
Add an optional nickname like "Production Vercel" or "My Team".
Click "Save & Verify" — Flarite will confirm your account name and team memberships.

⚠️

ImportantVercel API tokens are displayed only once. Copy the token before closing the page. Flarite encrypts it with AES-256 and never returns it to the browser.

Example prompts

"List all my Vercel projects and their last deployment status"

"Show me the build logs for the latest failed deployment of my-app"

"Which projects have domains that aren't verified?"

"List all environment variables in my-store project (without values)"

"What's the deployment history for the production branch of my-api?"

"Show me all team members and their roles in my Vercel organisation"

Supported tools

Flarite exposes the following Vercel tools to the AI model: get_user, list_projects, get_project, list_deployments, get_deployment, get_deployment_logs, list_domains, get_domain, list_env_vars, list_teams, get_team, and more.

💡

NoteEnvironment variable values are never fetched or shown — only keys and metadata are accessible. This is enforced at the tool level, not just the UI, so your secrets stay private even during AI interactions.

Team vs Personal account

Vercel has two account scopes — personal and team. When you save a token, Flarite auto-discovers which teams you belong to and displays them as selectable accounts. Switch between them using the account picker in the API Tokens tab.

Personal projects live under your username and are always accessible.
Team projects require your token to have the correct team scope or Full Account access.
If a project is missing, check that your token scope includes the team that owns it.