Quickstart

A verified test paywall in two terminal runs

Start in your existing Next.js App Router or Vite + React project. You do not need a dashboard session, Stripe connection, or credit card.

Safe default: setup creates only sk_test_/pk_test_ keys. Test checkout cannot create a real charge. Live payments remain off until you deliberately configure live keys and Stripe.
Release status: the guided setup command is tested in the repository and ships in the next CLI release. npm currently serves 0.0.9. Until npx vibemonetize --help lists setup, use the stable commands below.
Terminal
npx vibemonetize init
npx vibemonetize signup --email you@example.com
# Repeat signup with --code, then:
npx vibemonetize app create --template saas
npx vibemonetize doctor
1

Start setup

Use your real email so the verification code can reach you.

Terminal
npx vibemonetize setup --email you@example.com

The CLI detects the project, wires the provider, adds the SDK packages, writes commit-safe environment scaffolding and MONETIZE.md, then emails a six-digit code. It prints the exact resume command.

2

Paste the code and finish

Replace 123456 with the code from your inbox.

Terminal
npx vibemonetize setup --email you@example.com --code 123456

This resumes the same setup, creates test keys, provisions the saas template (Free + Pro), and runs doctor. Use --template ai-credits or --template daily-free if that matches your product better.

Read the verdict

A successful run ends with a short checklist and a test checkout link. If something is incomplete, it names the failed check and gives the exact fix. You can rerun setup safely after an interruption.

Terminal
npx vibemonetize doctor

Run your app once, replace the generated example with the feature you actually sell, and run doctor again. Client paywalls are advisory UI; enforce paid work on the server too. The paywall guide shows the pattern.

Prefer explicit control?

The guided command composes four independent, idempotent commands: init, signup, app create, and doctor. They remain available for CI, self-hosting, and custom catalogs. See the CLI reference.

Going live is a separate decision

Do not copy test credentials into production. When the test integration is verified, complete Stripe onboarding and mint live keys in the dashboard. That is the first point at which real payments become possible.