# Quickstart

> Start in Claude or ChatGPT with nothing to install, start from your coding agent with one prompt, or open an account, log in the CLI, create a project and deploy it yourself.

There are two ways in, on the same account, projects and code:

| | Best for |
| --- | --- |
| **In Claude or ChatGPT**, nothing to install | a simple site, a landing page, a small app, trying thelastapi from any device |
| **On your computer**, in Claude Code, Codex, Cursor… | real apps, existing code, anything big |

A site started in a chat comes down to your computer with `vibiz pull`, and anything deployed from your computer can be edited from a chat. [thelastapi.dev/get-started](https://thelastapi.dev/get-started) walks through both.

## Start in Claude or ChatGPT

Add thelastapi once as a custom connector with this URL:

```text
https://thelastapi.dev/mcp
```

- **Claude** (claude.ai, desktop or mobile): **Settings ▸ Connectors ▸ Add custom connector**, name it `Vibiz`, paste the URL and click **Add**. Then **Connect**, sign in and click **Authorize**. Custom connectors work on Free (one connector), Pro, Max, Team and Enterprise; on Team and Enterprise an Owner adds it.
- **ChatGPT**: turn on **Developer mode** (Settings ▸ Apps ▸ Advanced settings), then create an app with the same URL and OAuth sign-in, and sign in. Menu names vary by plan; it needs a plan that allows custom connectors.

Then, in a new chat:

```text
Use thelastapi to build and publish a landing page for my bakery, Acme Bakery, with a contact form.
```

It creates a project, writes the site and publishes it at `<slug>.vibiz.app`. To change it later, just ask: it reads the live code (`vibiz_code`) and deploys only the files that changed (`vibiz_deploy { files }`). A secret, like an API key, is never typed into the chat: you get a console link to paste it. Sites go up to about 300 files per deploy; for a bigger app or an existing codebase, start from your coding agent instead. See [Hosting](https://thelastapi.dev/docs/hosting#from-a-chat-nothing-installed).

## Start from your coding agent

Open Claude Code, Codex or Cursor and paste this one line (the **Paste to your agent** button at [thelastapi.dev/get-started](https://thelastapi.dev/get-started) copies it):

```text
Set up thelastapi for me: follow https://thelastapi.dev/get-started.md
```

The agent follows the [setup playbook](https://thelastapi.dev/get-started.md): it installs the CLI (`npm install --global @vibiz/cli`), runs `vibiz login` and shows you a link, adds the [agent skills](https://thelastapi.dev/skills) (`vibiz skills add --global`) and connects the MCP server (`vibiz mcp add --clients "<your agent>"`). You open the link, sign in with your thelastapi account and click **Authorize** (if you have no thelastapi account yet, it is opened for you). That's your only step. It ends with a short report of what is set up. New here? Create your account at [thelastapi.dev/start](https://thelastapi.dev/start).

Then, in an empty folder, ask for what you want:

```text
Use thelastapi to build and deploy a website for my bakery, Acme Bakery, with sign-in and a $15/month plan.
```

The agent creates the project, builds the app and deploys it. Anything with live money or a real company filing waits for you.

Prefer to connect it yourself? The MCP server needs nothing installed:

```bash
claude mcp add --transport http vibiz --scope user https://thelastapi.dev/mcp
```

The first time a tool is used, your agent opens the same sign-in in your browser. Codex, Cursor, VS Code, Windsurf, Gemini CLI and OpenCode take the same URL ([Agents](https://thelastapi.dev/docs/agents)).

The rest of this page is the same thing by hand.

## 1. Open an account

Create your account at [thelastapi.dev/start](https://thelastapi.dev/start): sign in with your email and create a thelastapi account, or let `vibiz login` (next step) open one for you.

When the CLI or an agent signs in, you approve it and choose what its key (`vz_sk_…`) may do: **Full access** is pre-selected and can do everything you can; pick **Limited** and it builds, deploys and runs, but never reads production secrets or moves live money. You can change any key between the two on the Keys page. See [Keys and environments](https://thelastapi.dev/docs/keys).

## 2. Log in the CLI

The CLI is the `@vibiz/cli` package on npm (the command is `vibiz`): `npx @vibiz/cli …` (Node 20+), or `npm install -g @vibiz/cli` once. Every command maps to the HTTP API, so `curl` works everywhere instead.

```bash
vibiz login                # prints a link: open it and click Authorize
```

The CLI saves its own new key, named after your computer. Already have a key? `vibiz login --key vz_sk_…`. `VIBIZ_API_KEY` and `VIBIZ_API_URL` in the environment override the saved login (`~/.vibiz/config.json`).

## 3. Create a project

```bash
mkdir acme && cd acme
vibiz init "Acme Bakery"                  # hosting, database, sign-in, analytics and session replay
vibiz init "Acme Bakery" --template nextjs-saas   # or start from the Next.js starter app
```

`vibiz init` writes `./vibiz.json` with the project id; agents read it instead of asking you. Over HTTP:

```bash
curl https://thelastapi.dev/v1/projects \
  -H "Authorization: Bearer $VIBIZ_API_KEY" -H 'content-type: application/json' \
  -d '{"name":"Acme Bakery"}'
# → 202 { "project": { "id": "prj_…", "slug": "acme-bakery", "resources": [ … "status": "pending" ] }, "operations": [ … ] }
```

Resources are provisioned in the background: each goes `pending → provisioning → ready` (or `failed` with an `error`). `GET /v1/projects/:id` shows where they are. A failed one is set up again on its own about every hour for its first 7 days (a quota or an outage clears without you), and adding it again (`vibiz add database`) retries it at once. Without `resources`, a project gets `hosting`, `database`, `auth` and `analytics`; `email`, `ai` and `replay` are opt-in (`vibiz add email`). Session replay (`vibiz add replay`) records visitors' sessions by default, masked, with no prompt (`require_consent: true` when visitors must agree first), and shows what went wrong for them: add it with analytics unless you don't want recordings. Only want one service, for an app that runs somewhere else? Ask for just that one (`--resources email`, or `none` for payments): see [Use one service](https://thelastapi.dev/docs/use-one).

## 4. Work locally

```bash
vibiz dev                  # writes .env.development.local: dev database, sign-in, AI key
npm run dev
```

The development environment has its own database branch (production's tables, none of its rows), its own sign-in that trusts `http://localhost:3000`, and its own AI key. It is safe to hand to an agent.

## 5. Deploy

```bash
vibiz deploy               # live at https://acme-bakery.vibiz.app
vibiz deploy --preview     # or a separate URL to check first, then: vibiz promote <id>
vibiz rollback             # instantly back to the previous production deployment
```

## 6. Give it to your agent

```bash
vibiz mcp add --clients "Claude Code"      # remote MCP: Codex, Cursor, "VS Code with Copilot"… too
vibiz skills add --global                  # the agent skills, for the agent this runs in
claude mcp add vibiz -- npx -y @vibiz/cli mcp   # or the local MCP server, with the CLI's login
```

Or hand it all to your agent: `Set up thelastapi for me: follow https://thelastapi.dev/get-started.md`. [Agents](https://thelastapi.dev/docs/agents) has Codex and Cursor too.

## Next

- [Payments](https://thelastapi.dev/docs/payments): sell a plan with a checkout link.
- [Sign-in](https://thelastapi.dev/docs/sign-in): turn on Google or magic links.
- [Web data](https://thelastapi.dev/docs/actions): scrape a site, search the web, pull a competitor's ads from the Meta Ad Library: `vibiz ads "Nike" --country US`.
- [API reference](https://thelastapi.dev/docs/api): every route.
