Quickstart

Version: 0.1.0 Last Updated: May 2026 Time to deploy: ~45 minutes

end

You've just bought AgentZero. This guide gets you from git clone to a live, billable AI agent product on the public internet.

If you only have time for the headline path:

›Clone the repo
›Create a Supabase project, run the migrations
›Get API keys (Vercel AI Gateway, optional: Resend, Tavily, Lemon Squeezy)
›Fill in .env.local
›Push to Vercel
›Visit your live site

That's it. Everything below expands those six steps.

end

Prerequisites

Before you start, have accounts at:

›GitHub — to fork or clone the repo
›Vercel — hosting (free tier works for testing)
›Supabase — database + auth + vector storage (free tier works for testing)
›Vercel AI Gateway — LLM inference. Single key routes to Claude, GPT, DeepSeek.

Optional but recommended:

›Resend — transactional email (waitlist confirmations, magic links)
›Tavily — web search tool for agents
›Lemon Squeezy — billing (only needed if you're selling agents to end users)

Local toolchain:

›Node.js 20+
›pnpm (or npm/yarn — pnpm is what we use)
›Git

end

1. Download & install

After purchase, Lemon Squeezy emails you a download link for the latest ZIP. Download it, then:

$  snippetread-only
unzip agentzero-v1.0.0.zip -d my-agent-product
cd my-agent-product
pnpm install

The filename includes the version you bought — substitute accordingly.

Optional but recommended: initialise a git repo so you can track your customisations and merge future updates cleanly.

$  snippetread-only
git init
git add .
git commit -m "Initial AgentZero v1.0.0"

Want to browse the stack before buying? The public lite version shows the architecture and landing page — same TypeScript, same domain layout, trimmed feature set.

This installs roughly 800 packages. Takes 30–60 seconds on a decent connection.

end

2. Set up Supabase

Create a project

›Go to supabase.com → "New project"
›Name it whatever you want. Pick the region closest to your users.
›Generate a strong DB password — save it in your password manager.
›Wait ~2 minutes for provisioning.

Run the migrations

From your project root:

$  snippetread-only
npx supabase login
npx supabase link --project-ref <your-project-ref>
npx supabase db push

The migrations create:

›Multi-tenant schema (organisations, users, agents)
›Row-level security policies (org-scoped data isolation)
›pgvector extension and embedding indexes
›Credit ledger and usage logs
›Lemon Squeezy event tables
›Waitlist table

Enable pgvector

If db push complains about the vector type, enable the extension manually:

›Supabase dashboard → Database → Extensions
›Search for vector → toggle on

Then re-run npx supabase db push.

end

3. Get your API keys

You'll need at minimum the Supabase and Vercel AI Gateway keys. Everything else can be added later.

| Service | Where to get it | |---|---| | NEXT_PUBLIC_SUPABASE_URL | Supabase dashboard → Project Settings → API | | SUPABASE_SECRET_KEY | Supabase dashboard → Project Settings → API → service_role key | | AI_GATEWAY_API_KEY | vercel.com → AI Gateway → Create token | | AUTH_SECRET | Generate: openssl rand -base64 32 | | NEXTAUTH_URL | Your production URL (e.g. https://yourdomain.com) | | RESEND_API_KEY | resend.com → API Keys (optional) | | TAVILY_API_KEY | tavily.com → API Keys (optional) | | LEMONSQUEEZY_API_KEY | lemonsqueezy.com → Settings → API (optional, for billing) |

Full env reference: see the Environment Setup guide.

end

4. Configure `.env.local`

$  snippetread-only
cp .env.example .env.local

Open .env.local and paste your keys. The bare minimum to boot:

$  snippetread-only
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SECRET_KEY=eyJ...
AI_GATEWAY_API_KEY=ai_gw_...
AUTH_SECRET=<your-generated-secret>
NEXTAUTH_URL=http://localhost:3000

end

5. Run locally

$  snippetread-only
pnpm dev

Visit http://localhost:3000. You should see the landing page.

Create an account at /signup, then visit /dashboard/agents/new to create your first agent.

If you hit "Insufficient credits", visit /dashboard/billing and check the seed credits. You can grant yourself credits manually via the Supabase SQL editor:

$  snippetread-only
update user_credits set balance = 10000 where user_id = '<your-user-id>';

end

6. Deploy to Vercel

Connect the repo

›vercel.com → Add New → Project
›Import your GitHub repo
›Framework preset: Next.js (auto-detected)
›Root directory: ./

Add environment variables

Vercel dashboard → Project → Settings → Environment Variables. Paste every variable from .env.local, but update:

›NEXTAUTH_URL → your Vercel production URL (e.g. https://my-agent-product.vercel.app)
›Add it for Production, Preview, and Development scopes

Deploy

Hit "Deploy". First build takes 2–4 minutes.

Once green, visit your Vercel URL. You're live.

end

7. Connect a domain (optional)

Vercel dashboard → Project → Settings → Domains → Add. Follow the DNS instructions. Update NEXTAUTH_URL to match.

end

Post-deploy checklist

›[ ] Sign up with a real email — confirm auth works end-to-end
›[ ] Create an agent — confirm streaming works
›[ ] Upload a PDF to knowledge base — confirm embeddings generate
›[ ] Run a query that hits the RAG — confirm context is retrieved
›[ ] Check /dashboard/billing — confirm credit balance displays
›[ ] (If selling) Wire Lemon Squeezy webhook URL: https://yourdomain.com/api/webhooks/lemonsqueezy

end

When something breaks

Build fails on Vercel: check the build logs. Most failures are missing env vars. Vercel shows you exactly which one.

Auth doesn't redirect after login: NEXTAUTH_URL is wrong. Must match your actual deployment URL exactly (no trailing slash).

Embeddings fail: the vector extension isn't enabled, or your AI Gateway key doesn't have embedding access. See Environment Setup.

Credits don't deduct: check the Supabase logs for transaction errors. The credit guard runs atomically — if it fails, no charge applies, but no inference runs either.

Email hello@boileragent.dev if you're stuck for more than 30 minutes. Include: the error message, the page you were on, and what you'd done in the last 10 minutes.

end

Next steps

›Customise the brand → Customization Guide
›Understand the architecture → Architecture Deep Dive
›Add your own tools to the agent loop → Custom Tools
›Read the licence → Commercial Use

Quickstart

Version: 0.1.0 Last Updated: May 2026 Time to deploy: ~45 minutes

end

You've just bought AgentZero. This guide gets you from git clone to a live, billable AI agent product on the public internet.

If you only have time for the headline path:

›Clone the repo
›Create a Supabase project, run the migrations
›Get API keys (Vercel AI Gateway, optional: Resend, Tavily, Lemon Squeezy)
›Fill in .env.local
›Push to Vercel
›Visit your live site

That's it. Everything below expands those six steps.

end

Prerequisites

Before you start, have accounts at:

›GitHub — to fork or clone the repo
›Vercel — hosting (free tier works for testing)
›Supabase — database + auth + vector storage (free tier works for testing)
›Vercel AI Gateway — LLM inference. Single key routes to Claude, GPT, DeepSeek.

Optional but recommended:

›Resend — transactional email (waitlist confirmations, magic links)
›Tavily — web search tool for agents
›Lemon Squeezy — billing (only needed if you're selling agents to end users)

Local toolchain:

›Node.js 20+
›pnpm (or npm/yarn — pnpm is what we use)
›Git

end

1. Download & install

After purchase, Lemon Squeezy emails you a download link for the latest ZIP. Download it, then:

$  snippetread-only
unzip agentzero-v1.0.0.zip -d my-agent-product
cd my-agent-product
pnpm install

The filename includes the version you bought — substitute accordingly.

Optional but recommended: initialise a git repo so you can track your customisations and merge future updates cleanly.

$  snippetread-only
git init
git add .
git commit -m "Initial AgentZero v1.0.0"

Want to browse the stack before buying? The public lite version shows the architecture and landing page — same TypeScript, same domain layout, trimmed feature set.

This installs roughly 800 packages. Takes 30–60 seconds on a decent connection.

end

2. Set up Supabase

Create a project

›Go to supabase.com → "New project"
›Name it whatever you want. Pick the region closest to your users.
›Generate a strong DB password — save it in your password manager.
›Wait ~2 minutes for provisioning.

Run the migrations

From your project root:

$  snippetread-only
npx supabase login
npx supabase link --project-ref <your-project-ref>
npx supabase db push

The migrations create:

›Multi-tenant schema (organisations, users, agents)
›Row-level security policies (org-scoped data isolation)
›pgvector extension and embedding indexes
›Credit ledger and usage logs
›Lemon Squeezy event tables
›Waitlist table

Enable pgvector

If db push complains about the vector type, enable the extension manually:

›Supabase dashboard → Database → Extensions
›Search for vector → toggle on

Then re-run npx supabase db push.

end

3. Get your API keys

You'll need at minimum the Supabase and Vercel AI Gateway keys. Everything else can be added later.

Full env reference: see the Environment Setup guide.

end

4. Configure `.env.local`

$  snippetread-only
cp .env.example .env.local

Open .env.local and paste your keys. The bare minimum to boot:

$  snippetread-only
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SECRET_KEY=eyJ...
AI_GATEWAY_API_KEY=ai_gw_...
AUTH_SECRET=<your-generated-secret>
NEXTAUTH_URL=http://localhost:3000

end

5. Run locally

$  snippetread-only
pnpm dev

Visit http://localhost:3000. You should see the landing page.

Create an account at /signup, then visit /dashboard/agents/new to create your first agent.

If you hit "Insufficient credits", visit /dashboard/billing and check the seed credits. You can grant yourself credits manually via the Supabase SQL editor:

$  snippetread-only
update user_credits set balance = 10000 where user_id = '<your-user-id>';

end

6. Deploy to Vercel

Connect the repo

›vercel.com → Add New → Project
›Import your GitHub repo
›Framework preset: Next.js (auto-detected)
›Root directory: ./

Add environment variables

Vercel dashboard → Project → Settings → Environment Variables. Paste every variable from .env.local, but update:

›NEXTAUTH_URL → your Vercel production URL (e.g. https://my-agent-product.vercel.app)
›Add it for Production, Preview, and Development scopes

Deploy

Hit "Deploy". First build takes 2–4 minutes.

Once green, visit your Vercel URL. You're live.

end

7. Connect a domain (optional)

Vercel dashboard → Project → Settings → Domains → Add. Follow the DNS instructions. Update NEXTAUTH_URL to match.

end

Post-deploy checklist

›[ ] Sign up with a real email — confirm auth works end-to-end
›[ ] Create an agent — confirm streaming works
›[ ] Upload a PDF to knowledge base — confirm embeddings generate
›[ ] Run a query that hits the RAG — confirm context is retrieved
›[ ] Check /dashboard/billing — confirm credit balance displays
›[ ] (If selling) Wire Lemon Squeezy webhook URL: https://yourdomain.com/api/webhooks/lemonsqueezy

end

When something breaks

Build fails on Vercel: check the build logs. Most failures are missing env vars. Vercel shows you exactly which one.

Auth doesn't redirect after login: NEXTAUTH_URL is wrong. Must match your actual deployment URL exactly (no trailing slash).

Embeddings fail: the vector extension isn't enabled, or your AI Gateway key doesn't have embedding access. See Environment Setup.

Credits don't deduct: check the Supabase logs for transaction errors. The credit guard runs atomically — if it fails, no charge applies, but no inference runs either.

Email hello@boileragent.dev if you're stuck for more than 30 minutes. Include: the error message, the page you were on, and what you'd done in the last 10 minutes.

end

Next steps

›Customise the brand → Customization Guide
›Understand the architecture → Architecture Deep Dive
›Add your own tools to the agent loop → Custom Tools
›Read the licence → Commercial Use

Quickstart

Prerequisites

1. Download & install

2. Set up Supabase

Create a project

Run the migrations

Enable pgvector

3. Get your API keys

4. Configure .env.local

5. Run locally

6. Deploy to Vercel

Connect the repo

Add environment variables

Deploy

7. Connect a domain (optional)

Post-deploy checklist

When something breaks

Next steps

Quickstart

Prerequisites

1. Download & install

2. Set up Supabase

Create a project

Run the migrations

Enable pgvector

3. Get your API keys

4. Configure .env.local

5. Run locally

6. Deploy to Vercel

Connect the repo

Add environment variables

Deploy

7. Connect a domain (optional)

Post-deploy checklist

When something breaks

Next steps

4. Configure `.env.local`

4. Configure `.env.local`