vibizStack
Console
Vibiz Stack developer docs

One API for the whole business.

Hosting, a Postgres database, sign-in, email, AI, payments and company formation, behind one key, with usage and limits in one place. Built for builders and the agents that work for them.

llms.txt·llms-full.txt·Agent skills

vibiz — zsh
$ vibiz --help
vibiz — website, database and sign-in for a new business, in one command

  vibiz login                                log in from the browser: prints a link, you click
                                             Authorize, a new agent key is saved here
       [--key <vz_sk_…>] [--api <url>] [--no-browser]   or save a key you already have
  vibiz signup                               the same as login: no account yet? one is opened
                                             for you on the way
  vibiz whoami                               the account and key this machine uses
  vibiz logout                               forget this machine's key (a browser login's key is
                                             revoked too)
  vibiz init <name> [--resources a,b|none]   create a project here (default: hosting, database,
                                             auth, analytics). Any one alone works for an app on
                                             another host: --resources email, auth, ai, analytics…
                                             or none (payments, files, web data, social, company
  …
In your code

The parts that take money and sign people in.

Server-side calls on one key, VIBIZ_APP_KEY. Every example below is on its product page, with plain HTTP for when the package isn't installed.

app/pricing/page.tsx
import { redirect } from 'next/navigation';
import { vibiz } from '@vibiz/app';
import { currentUser } from '@/lib/auth/server';
 
export default function Pricing() {
  async function upgrade() {
    'use server';
    const user = await currentUser();
    if (!user) redirect('/sign-in');
    const { url } = await vibiz.payments.checkout({
      lookup_key: 'pro-monthly',
      user: user.id,
      success_url: 'https://acme-bakery.vibiz.app/billing/success',
      cancel_url: 'https://acme-bakery.vibiz.app/pricing',
    });
    redirect(url);
  }
 
  return (
    <form action={upgrade}>
      <button type="submit">Upgrade to Pro · $15/month</button>
    </form>
  );
}
app/pricingTypeScript React · UTF-8 · LF

A hosted checkout per click. Vibiz is the merchant, so it works from the first call. Read the docs

For agents

Built for the agent doing the work.

Claude Code, Codex and Cursor get every product as MCP tools, the facts they would otherwise guess from vibiz_docs, and skills that load when a task needs them.

  • Agent keys can't leak production. They build and run; live money and production secrets answer 403 owner_only with the step to tell you.
  • Development by default. An empty database branch, its own sign-in and test-mode payments.
  • Readable by machines. Every page as markdown, plus llms.txt and llms-full.txt.
acme — zsh
$ claude mcp add vibiz --env VIBIZ_API_KEY=vz_sk_… -- vibiz mcp

$ curl -fsSL https://app.vibiz.app/skills/vibiz-payments.tar.gz | tar -xz -C ~/.claude/skills

$ vibiz docs
  vibiz docs payments     Payments: how money moves
  vibiz docs app-payments Payments in the app (@vibiz/app)
  vibiz docs webhooks     Webhooks: Vibiz tells the app when someone pays
  vibiz docs company      Company formation: cost and what is needed
  vibiz docs keys         Keys and environments
  vibiz docs usage        Usage, cost and limits
  vibiz docs connectors   Custom connectors: the user’s own APIs through Vibiz
  vibiz docs social       Social: posting, approvals and ads
  vibiz docs console-urls Console links

$ vibiz docs payments | grep 96.80

Open the console, get a key, deploy.

Vibiz Stack is in private beta. Sign in with your Vibiz account to see your projects, payments, spend and keys.