Chat through Vercel AI Gateway
A Dome-managed chat agent that uses Vercel AI Gateway for model routing and observability.
- chat
- vercel-ai-gateway-chat
- vercel-ai-gateway-chat
vercel-ai-gateway-pool
- vercel-ai-gateway-model
What this template gives you
Interface
A chat window, in your browser
Use the included interface to send a request to this template.
Gateway
vercel-ai-gateway-chat gateway
This template sends its requests through vercel-ai-gateway-chat gateway, where its access rules and limits apply.
Model
vercel-ai-gateway-model
This template uses vercel-ai-gateway-model through the vercel-ai-gateway-pool pool.
Usage
Hand this template to an AI agent to set up this template
Node.js and npm to run npx.
Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.
Docker Compose to run the companion app locally.
- 1
Create a workspace
dome workspaces create --name <workspace-name>The CLI creates and selects a workspace context for you.
- 2
Confirm the workspace context
dome context listThe workspace you just created is already selected.
- 3
Pull the template
npx @domesystems/templates pull im2nguyen/vercel-ai-gateway-chat@0.1.2 --dir vercel-ai-gateway-chatDownloads this immutable release and verifies its digest.
- 4
Run the template
npx @domesystems/templates up --dir vercel-ai-gateway-chatImports it into Dome and starts the companion app.
Dome import variables
npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.
Required values
DOME_IMPORT_VAR_vercel_ai_gateway_api_key
Setup guide
Follow this template's setup guidance for agent variables and upstream connections.
Create a Vercel AI Gateway API key for the Vercel team that should own this
agent's model usage, then paste `Bearer <your API key>` into
`vercel_ai_gateway_api_key`. Dome uses the value only to create the shared
model connection for this deployment; Sandbox does not retain it.Runtime environment
These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.
No .env.example is included in this release.Agent instructions
You are a concise, helpful general-purpose chat assistant.
Answer the user's question directly and clearly. Be transparent about
uncertainty, and do not claim to have browsed the web, used tools, or taken
actions outside this conversation unless such capability is explicitly present.