@vibiz/cli 0.3.19 → 0.3.21

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -10,7 +10,7 @@ import {
10
10
  deployFiles,
11
11
  oneKeyMessage,
12
12
  writeEnvFile
13
- } from "./chunk-ABEQTLK5.js";
13
+ } from "./chunk-EB6UCD3N.js";
14
14
 
15
15
  // packages/docs/src/generated/content.ts
16
16
  var PAGES = [
@@ -21,7 +21,7 @@ var PAGES = [
21
21
  "section": "Getting started",
22
22
  "order": 10,
23
23
  "topic": null,
24
- "body": "thelastapi is one API for everything a new business needs online: **hosting, a Postgres database, sign-in, email, AI, web data (scraping, search, competitor ads), payments and company formation**, with usage, limits and keys in one place. It is built for builders and the AI agents that work for them: Claude or ChatGPT with nothing installed, Claude Code, Codex, Cursor or your own. See the [Quickstart](/docs/quickstart) for both starts.\n\nYou ask for a capability; thelastapi provisions it, keeps its secrets, meters it and hands your app one key. Every service you call is a thelastapi service, under one name and one key, and it keeps getting better without breaking your app.\n\n```bash\nvibiz init \"Acme Bakery\" # https://acme-bakery.vibiz.app, with a database and sign-in\nvibiz dev # a development database, sign-in and AI key for local work\nvibiz deploy # live\n```\n\nTake all of it, or just one piece: every service works on its own for an app hosted anywhere, a plain site, a mobile app's backend or a script ([Use one service](/docs/use-one)).\n\n## What you get\n\n| Product | In one line |\n| --- | --- |\n| [Hosting](/docs/hosting) | Deploy a folder to `<slug>.vibiz.app`; previews, instant promote and rollback |\n| [Database](/docs/database) | Postgres per project, with an empty development branch for agents and laptops |\n| [Sign-in](/docs/sign-in) | Email and password, magic links, Google, GitHub and Vercel sign-in |\n| [Email](/docs/email) | Send from `<mailbox>@<slug>.vibiz.app` |\n| [AI](/docs/ai) | An OpenAI-compatible gateway: chat, embeddings, images, video, speech, transcription |\n| [Files](/docs/files) | A drive per project: every generated image, video and audio is kept there with a permanent link |\n| [Payments](/docs/payments) | One-time and recurring payments from the first call; thelastapi is the merchant |\n| [Company](/docs/company) | Form a US LLC or C-Corp, with the registered agent and the EIN |\n| [Analytics](/docs/analytics) | Cookieless web analytics and session replay |\n| [Web data](/docs/actions) | Scrape or crawl a site, search the web, competitor ads from the Meta Ad Library, Google Maps places, reviews, Instagram and TikTok, product prices |\n| [Domains](/docs/domains) | Buy a domain from credits and use it on any project with no DNS, or connect one you own; redirect an old one to a new one |\n| [Search](/docs/search) | New pages sent to IndexNow after every deploy; each site verified and read in your Google Search Console and Bing Webmaster |\n| [Mission Control](/docs/mission-control) | Every business on one board, checked about hourly, from its domain to its sales, with how to fix each problem |\n| [Phone](/docs/phone) | A US number for texts and calls, with a voice agent |\n| [Social](/docs/social) | Post and schedule to the business's own social accounts, and run its ad campaigns with the owner approving |\n| [Connectors](/docs/connectors) | Any HTTP API from a manifest or an OpenAPI spec, its key kept sealed |\n| [Usage and limits](/docs/usage) | What was spent, per tool, model, project, key or end user, and today's ceilings |\n\n## How you use it\n\n- **The console** at [thelastapi.dev](https://thelastapi.dev): projects, deploys, payments, company, spend and keys, for the person who owns the account.\n- **Claude or ChatGPT**: add `https://thelastapi.dev/mcp` as a custom connector and ask for a site; nothing to install. See [Agents](/docs/agents#chat-apps-claude-chatgpt).\n- **The CLI** (`vibiz`) and the **MCP server** (`vibiz mcp`): what coding agents and terminals use. See [Agents](/docs/agents).\n- **The HTTP API** at `https://thelastapi.dev/v1`: everything the CLI and console do. See the [API reference](/docs/api).\n- **`@vibiz/app`**: the client a running app uses, on one key. See [@vibiz/app](/docs/app-sdk).\n\n## The rule that shapes everything\n\nAn agent's key does what the person allowed when they approved its sign-in: **Full access** (the default) can do everything the owner can; **Limited** creates projects, deploys, sends email, uses AI and does everything in development, but **never holds a production secret or moves live money**. When a Limited key hits one of those it gets `403` with `details.next_step`: the link for the person to do it, and the one to give the key full access. See [Keys and environments](/docs/keys).\n\n## Status\n\nthelastapi is invite-only for now: [join the waitlist](https://thelastapi.dev/waitlist) to open an account. Everything the CLI, the MCP server and `@vibiz/app` do is the plain HTTP API, documented here. Prices that are not decided say so on their page. Guides, how-tos and comparisons are on the blog at `/blog` (each post also as markdown: add `.md`; feed at `/blog/rss.xml`)."
24
+ "body": "thelastapi is one API for everything a new business needs online: **hosting, a Postgres database, sign-in, email, AI, web data (scraping, search, competitor ads), payments and company formation**, with usage, limits and keys in one place. It is built for builders and the AI agents that work for them: Claude or ChatGPT with nothing installed, Claude Code, Codex, Cursor or your own. See the [Quickstart](/docs/quickstart) for both starts.\n\nYou ask for a capability; thelastapi provisions it, keeps its secrets, meters it and hands your app one key. Every service you call is a thelastapi service, under one name and one key, and it keeps getting better without breaking your app.\n\n```bash\nvibiz init \"Acme Bakery\" # https://acme-bakery.vibiz.app, with a database and sign-in\nvibiz dev # a development database, sign-in and AI key for local work\nvibiz deploy # live\n```\n\nTake all of it, or just one piece: every service works on its own for an app hosted anywhere, a plain site, a mobile app's backend or a script ([Use one service](/docs/use-one)).\n\n## What you get\n\n| Product | In one line |\n| --- | --- |\n| [Hosting](/docs/hosting) | Deploy a folder to `<slug>.vibiz.app`; previews, instant promote and rollback |\n| [Database](/docs/database) | Postgres per project, with an empty development branch for agents and laptops |\n| [Sign-in](/docs/sign-in) | Email and password, magic links, Google, GitHub and Vercel sign-in |\n| [Email](/docs/email) | Send from `<mailbox>@<slug>.vibiz.app` |\n| [AI](/docs/ai) | An OpenAI-compatible gateway: chat, embeddings, images, video, speech, transcription |\n| [Files](/docs/files) | A drive per project: every generated image, video and audio is kept there with a permanent link |\n| [Payments](/docs/payments) | One-time and recurring payments from the first call; thelastapi is the merchant |\n| [Company](/docs/company) | Form a US LLC or C-Corp, with the registered agent and the EIN |\n| [Analytics](/docs/analytics) | Cookieless web analytics and session replay |\n| [Web data](/docs/actions) | Scrape or crawl a site, search the web, competitor ads from the Meta Ad Library, Google Maps places, reviews, Instagram and TikTok, product prices |\n| [Domains](/docs/domains) | Buy a domain from credits and use it on any project with no DNS, or connect one you own; redirect an old one to a new one |\n| [Search](/docs/search) | New pages sent to IndexNow after every deploy; each site verified and read in your Google Search Console and Bing Webmaster |\n| [Mission Control](/docs/mission-control) | Every business on one board, checked about hourly, from its domain to its sales, with how to fix each problem |\n| [Phone](/docs/phone) | A US number for texts and calls, with a voice agent |\n| [Social](/docs/social) | Post and schedule to the business's own social accounts, and run its ad campaigns with the owner approving |\n| [Connectors](/docs/connectors) | Any HTTP API from a manifest or an OpenAPI spec, its key kept sealed |\n| [Usage and limits](/docs/usage) | What was spent, per tool, model, project, key or end user, and today's ceilings |\n\n## How you use it\n\n- **The console** at [thelastapi.dev](https://thelastapi.dev): projects, deploys, payments, company, spend and keys, for the person who owns the account.\n- **Claude or ChatGPT**: add `https://thelastapi.dev/mcp` as a custom connector and ask for a site; nothing to install. See [Agents](/docs/agents#chat-apps-claude-chatgpt).\n- **The CLI** (`vibiz`) and the **MCP server** (`vibiz mcp`): what coding agents and terminals use. See [Agents](/docs/agents).\n- **The HTTP API** at `https://thelastapi.dev/v1`: everything the CLI and console do. See the [API reference](/docs/api).\n- **`@vibiz/app`**: the client a running app uses, on one key. See [@vibiz/app](/docs/app-sdk).\n\n## The rule that shapes everything\n\nAn agent's key does what the person allowed when they approved its sign-in: **Full access** (the default) can do everything the owner can; **Limited** creates projects, deploys, sends email, uses AI and does everything in development, but **never holds a production secret or moves live money**. When a Limited key hits one of those it gets `403` with `details.next_step`: the link for the person to do it, and the one to give the key full access. See [Keys and environments](/docs/keys).\n\n## Status\n\nCreate your account at [thelastapi.dev/start](https://thelastapi.dev/start). Everything the CLI, the MCP server and `@vibiz/app` do is the plain HTTP API, documented here. Prices that are not decided say so on their page. Guides, how-tos and comparisons are on the blog at `/blog` (each post also as markdown: add `.md`; feed at `/blog/rss.xml`)."
25
25
  },
26
26
  {
27
27
  "slug": "quickstart",
@@ -30,7 +30,7 @@ var PAGES = [
30
30
  "section": "Getting started",
31
31
  "order": 20,
32
32
  "topic": null,
33
- "body": 'There are two ways in, on the same account, projects and code:\n\n| | Best for |\n| --- | --- |\n| **In Claude or ChatGPT**, nothing to install | a simple site, a landing page, a small app, trying thelastapi from any device |\n| **On your computer**, in Claude Code, Codex, Cursor\u2026 | real apps, existing code, anything big |\n\nA 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.\n\n## Start in Claude or ChatGPT\n\nAdd thelastapi once as a custom connector with this URL:\n\n```text\nhttps://thelastapi.dev/mcp\n```\n\n- **Claude** (claude.ai, desktop or mobile): **Settings \u25B8 Connectors \u25B8 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.\n- **ChatGPT**: turn on **Developer mode** (Settings \u25B8 Apps \u25B8 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.\n\nThen, in a new chat:\n\n```text\nUse thelastapi to build and publish a landing page for my bakery, Acme Bakery, with a contact form.\n```\n\nIt 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](/docs/hosting#from-a-chat-nothing-installed).\n\n## Start from your coding agent\n\nOpen 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):\n\n```text\nSet up thelastapi for me: follow https://thelastapi.dev/get-started.md\n```\n\nThe 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](/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 were invited and 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? thelastapi is invite-only for now: [join the waitlist](https://thelastapi.dev/waitlist) first.\n\nThen, in an empty folder, ask for what you want:\n\n```text\nUse thelastapi to build and deploy a website for my bakery, Acme Bakery, with sign-in and a $15/month plan.\n```\n\nThe agent creates the project, builds the app and deploys it. Anything with live money or a real company filing waits for you.\n\nPrefer to connect it yourself? The MCP server needs nothing installed:\n\n```bash\nclaude mcp add --transport http vibiz --scope user https://thelastapi.dev/mcp\n```\n\nThe 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](/docs/agents)).\n\nThe rest of this page is the same thing by hand.\n\n## 1. Open an account\n\nthelastapi is invite-only for now. [Join the waitlist](https://thelastapi.dev/waitlist) and we email you a sign-in link when your spot opens. Once invited, sign in at [thelastapi.dev](https://thelastapi.dev) with your thelastapi account, using the invited email, and create a thelastapi account, or let `vibiz login` (next step) open one for you.\n\nWhen the CLI or an agent signs in, you approve it and choose what its key (`vz_sk_\u2026`) 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](/docs/keys).\n\n## 2. Log in the CLI\n\nThe CLI is the `@vibiz/cli` package on npm (the command is `vibiz`): `npx @vibiz/cli \u2026` (Node 20+), or `npm install -g @vibiz/cli` once. Every command maps to the HTTP API, so `curl` works everywhere instead.\n\n```bash\nvibiz login # prints a link: open it and click Authorize\n```\n\nThe CLI saves its own new key, named after your computer. Already have a key? `vibiz login --key vz_sk_\u2026`. `VIBIZ_API_KEY` and `VIBIZ_API_URL` in the environment override the saved login (`~/.vibiz/config.json`).\n\n## 3. Create a project\n\n```bash\nmkdir acme && cd acme\nvibiz init "Acme Bakery" # hosting, database, sign-in, analytics and session replay\nvibiz init "Acme Bakery" --template nextjs-saas # or start from the Next.js starter app\n```\n\n`vibiz init` writes `./vibiz.json` with the project id; agents read it instead of asking you. Over HTTP:\n\n```bash\ncurl https://thelastapi.dev/v1/projects \\\n -H "Authorization: Bearer $VIBIZ_API_KEY" -H \'content-type: application/json\' \\\n -d \'{"name":"Acme Bakery"}\'\n# \u2192 202 { "project": { "id": "prj_\u2026", "slug": "acme-bakery", "resources": [ \u2026 "status": "pending" ] }, "operations": [ \u2026 ] }\n```\n\nResources are provisioned in the background: each goes `pending \u2192 provisioning \u2192 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](/docs/use-one).\n\n## 4. Work locally\n\n```bash\nvibiz dev # writes .env.development.local: dev database, sign-in, AI key\nnpm run dev\n```\n\nThe 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.\n\n## 5. Deploy\n\n```bash\nvibiz deploy # live at https://acme-bakery.vibiz.app\nvibiz deploy --preview # or a separate URL to check first, then: vibiz promote <id>\nvibiz rollback # instantly back to the previous production deployment\n```\n\n## 6. Give it to your agent\n\n```bash\nvibiz mcp add --clients "Claude Code" # remote MCP: Codex, Cursor, "VS Code with Copilot"\u2026 too\nvibiz skills add --global # the agent skills, for the agent this runs in\nclaude mcp add vibiz -- npx -y @vibiz/cli mcp # or the local MCP server, with the CLI\'s login\n```\n\nOr hand it all to your agent: `Set up thelastapi for me: follow https://thelastapi.dev/get-started.md`. [Agents](/docs/agents) has Codex and Cursor too.\n\n## Next\n\n- [Payments](/docs/payments): sell a plan with a checkout link.\n- [Sign-in](/docs/sign-in): turn on Google or magic links.\n- [Web data](/docs/actions): scrape a site, search the web, pull a competitor\'s ads from the Meta Ad Library: `vibiz ads "Nike" --country US`.\n- [API reference](/docs/api): every route.'
33
+ "body": 'There are two ways in, on the same account, projects and code:\n\n| | Best for |\n| --- | --- |\n| **In Claude or ChatGPT**, nothing to install | a simple site, a landing page, a small app, trying thelastapi from any device |\n| **On your computer**, in Claude Code, Codex, Cursor\u2026 | real apps, existing code, anything big |\n\nA 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.\n\n## Start in Claude or ChatGPT\n\nAdd thelastapi once as a custom connector with this URL:\n\n```text\nhttps://thelastapi.dev/mcp\n```\n\n- **Claude** (claude.ai, desktop or mobile): **Settings \u25B8 Connectors \u25B8 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.\n- **ChatGPT**: turn on **Developer mode** (Settings \u25B8 Apps \u25B8 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.\n\nThen, in a new chat:\n\n```text\nUse thelastapi to build and publish a landing page for my bakery, Acme Bakery, with a contact form.\n```\n\nIt 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](/docs/hosting#from-a-chat-nothing-installed).\n\n## Start from your coding agent\n\nOpen 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):\n\n```text\nSet up thelastapi for me: follow https://thelastapi.dev/get-started.md\n```\n\nThe 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](/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).\n\nThen, in an empty folder, ask for what you want:\n\n```text\nUse thelastapi to build and deploy a website for my bakery, Acme Bakery, with sign-in and a $15/month plan.\n```\n\nThe agent creates the project, builds the app and deploys it. Anything with live money or a real company filing waits for you.\n\nPrefer to connect it yourself? The MCP server needs nothing installed:\n\n```bash\nclaude mcp add --transport http vibiz --scope user https://thelastapi.dev/mcp\n```\n\nThe 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](/docs/agents)).\n\nThe rest of this page is the same thing by hand.\n\n## 1. Open an account\n\nCreate 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.\n\nWhen the CLI or an agent signs in, you approve it and choose what its key (`vz_sk_\u2026`) 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](/docs/keys).\n\n## 2. Log in the CLI\n\nThe CLI is the `@vibiz/cli` package on npm (the command is `vibiz`): `npx @vibiz/cli \u2026` (Node 20+), or `npm install -g @vibiz/cli` once. Every command maps to the HTTP API, so `curl` works everywhere instead.\n\n```bash\nvibiz login # prints a link: open it and click Authorize\n```\n\nThe CLI saves its own new key, named after your computer. Already have a key? `vibiz login --key vz_sk_\u2026`. `VIBIZ_API_KEY` and `VIBIZ_API_URL` in the environment override the saved login (`~/.vibiz/config.json`).\n\n## 3. Create a project\n\n```bash\nmkdir acme && cd acme\nvibiz init "Acme Bakery" # hosting, database, sign-in, analytics and session replay\nvibiz init "Acme Bakery" --template nextjs-saas # or start from the Next.js starter app\n```\n\n`vibiz init` writes `./vibiz.json` with the project id; agents read it instead of asking you. Over HTTP:\n\n```bash\ncurl https://thelastapi.dev/v1/projects \\\n -H "Authorization: Bearer $VIBIZ_API_KEY" -H \'content-type: application/json\' \\\n -d \'{"name":"Acme Bakery"}\'\n# \u2192 202 { "project": { "id": "prj_\u2026", "slug": "acme-bakery", "resources": [ \u2026 "status": "pending" ] }, "operations": [ \u2026 ] }\n```\n\nResources are provisioned in the background: each goes `pending \u2192 provisioning \u2192 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](/docs/use-one).\n\n## 4. Work locally\n\n```bash\nvibiz dev # writes .env.development.local: dev database, sign-in, AI key\nnpm run dev\n```\n\nThe 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.\n\n## 5. Deploy\n\n```bash\nvibiz deploy # live at https://acme-bakery.vibiz.app\nvibiz deploy --preview # or a separate URL to check first, then: vibiz promote <id>\nvibiz rollback # instantly back to the previous production deployment\n```\n\n## 6. Give it to your agent\n\n```bash\nvibiz mcp add --clients "Claude Code" # remote MCP: Codex, Cursor, "VS Code with Copilot"\u2026 too\nvibiz skills add --global # the agent skills, for the agent this runs in\nclaude mcp add vibiz -- npx -y @vibiz/cli mcp # or the local MCP server, with the CLI\'s login\n```\n\nOr hand it all to your agent: `Set up thelastapi for me: follow https://thelastapi.dev/get-started.md`. [Agents](/docs/agents) has Codex and Cursor too.\n\n## Next\n\n- [Payments](/docs/payments): sell a plan with a checkout link.\n- [Sign-in](/docs/sign-in): turn on Google or magic links.\n- [Web data](/docs/actions): scrape a site, search the web, pull a competitor\'s ads from the Meta Ad Library: `vibiz ads "Nike" --country US`.\n- [API reference](/docs/api): every route.'
34
34
  },
35
35
  {
36
36
  "slug": "use-one",
@@ -39,7 +39,7 @@ var PAGES = [
39
39
  "section": "Getting started",
40
40
  "order": 25,
41
41
  "topic": null,
42
- "body": "Every thelastapi service works on its own. The app doesn't have to be deployed on thelastapi: it can run on another host, be a plain HTML site, a mobile app's backend, a cron job or a script. A project is just the services you pick, and none of them needs `hosting`.\n\n## Three steps\n\n1. **Create a project with only what you need.** `vibiz init <name> --resources <one>` (MCP: `vibiz_create_project { name, resources: [\"auth\"] }`). Payments, files, web data, social, company and connectors need no resource: `--resources none` (or naming them, `--resources payments`, makes the same empty project).\n2. **Add the app's domain as running elsewhere**: `vibiz domains add app.example.com --elsewhere`. From a Limited key, analytics counts it at once and sign-in trusts it once its TXT record (`trust_record`, `_vibiz.app.example.com`) is in and `vibiz domains verify app.example.com` finds it, or the owner confirms it in the console. Sign-in trusts it, analytics counts visits from it, and payment events may be sent to it. Not needed for a script or a server with no web address.\n3. **Give the app its key: one key = everything.** One secret, `VIBIZ_APP_KEY`, reaches everything the project has: database, sign-in, email and inbox, AI models, files, payments, analytics with session replays, web data, social, phone and connectors. An owner copies it from the console and puts it in the host. An agent (or `vibiz app-key`, `vibiz connect`) gives them the exact link that opens it ready to copy (`app_key_console_url` from `vibiz_project_env`), never directions, in these words:\n\n > Add one key to Vercel and your app can use everything on thelastapi (database, sign-in, email and inbox, AI models, files, payments, analytics with session replays, web data, social, phone and connectors): copy VIBIZ_APP_KEY here: https://thelastapi.dev/projects/prj_\u2026/settings?key=production , paste it into Vercel's production environment variables, and redeploy. Or connect Vercel once (`vibiz hosts add vercel <app>`) and thelastapi keeps every variable in sync.\n\n The app loads the rest at boot:\n\n```ts\nimport { vibiz } from '@vibiz/app';\nawait vibiz.loadEnv(); // DATABASE_URL, VIBIZ_AUTH_*, VIBIZ_WEBHOOK_SECRET\u2026 into process.env\n```\n\nAny language: `npx @vibiz/cli run -- <start command>`. A build step or CI: `npx @vibiz/cli env pull --format dotenv -o .env.production`. A connected host (`vibiz hosts add <host> <app>`) gets the values written for it instead. For local work, `vibiz dev` writes the development copy (its own key, no production data) to `.env.development.local`.\n\n## Every website gets the SDK\n\nAn agent working on a website or web app that belongs to a thelastapi project (a `vibiz.json` in its folder, or one it made with `vibiz init`) always installs `@vibiz/app` pinned exactly (`npm install --save-exact @vibiz/app@0.3.19`), calls `await vibiz.loadEnv()` where the server starts, and adds the analytics tag with session replays on, unasked, and says it did. Secrets such as a host's token are never asked for in a chat: the agent hands over the command (`vibiz hosts add vercel <app>`), and a person types the value in their own terminal.\n\n## Per service\n\n| Service | Create with | Domain needed | The app uses it with |\n| --- | --- | --- | --- |\n| Database | `--resources database` | no | `DATABASE_URL`, plain Postgres over the internet |\n| Sign-in | `--resources auth` (brings the database) | yes, the app's web address | `VIBIZ_AUTH_*` from the env ([Sign-in](/docs/sign-in)) |\n| Payments | `--resources none` | for webhooks | `vibiz.payments.checkout(\u2026)` with any `https` `success_url` and `cancel_url`; events at the webhook URL the owner sets (`vibiz payments webhook <url>`) |\n| Email | `--resources email` | no | `vibiz.email.send(\u2026)` from `<mailbox>@<slug>.vibiz.app` |\n| Email at your own domain | `--resources none` | its own DNS | `vibiz email forward hello@example.com <inbox>` (owner), no app code |\n| AI | `--resources ai` | no | `new OpenAI(vibiz.ai)`: OpenAI-compatible, metered per call |\n| Analytics | `--resources analytics` (add `replay` too, unless the person doesn't want recordings) | yes | the tag from `vibiz analytics snippet` before `</head>`; server events with `vibiz.track(\u2026)` |\n| Session replay | `--resources replay` (brings analytics) | yes | the same tag: it records by itself (`require_consent: true` if visitors must agree first, then `vibiz('replay', 'start')`) |\n| Files | `--resources none` | no | `vibiz.files.upload(bytes, { name })` returns a permanent link |\n| Web data | `--resources none` | no | `vibiz.actions.run('web.scrape', { url })` and every other action |\n| Design | `--resources none`, or no project at all | no | `vibiz design <url> --tailwind`, or `vibiz.actions.run('web.design', { url })`: the theme and brief work in any stack |\n| Connectors | `--resources none` | no | `vibiz connectors add \u2026`; the app calls them through thelastapi with its key |\n| Social | `--resources none` | no | the owner connects accounts once (`vibiz social connect <platform>`); posts from the CLI, the console or an agent |\n| Company formation | `--resources none` | no | `vibiz company draft`, the owner files |\n\nWithout the package, every call above is an HTTP route under `/v1/app` with `Authorization: Bearer $VIBIZ_APP_KEY` ([@vibiz/app](/docs/app-sdk)).\n\n## Examples\n\nA Next.js app on another host that only takes payments:\n\n```bash\nvibiz init shop --resources none\nvibiz domains add shop.example.com --elsewhere # Limited key: then its TXT record + verify\nvibiz payments products add Pro --amount 900 --interval month --lookup-key pro-monthly\nvibiz payments webhook https://shop.example.com/api/vibiz/webhook # full-access key (production); Limited keys set development\n```\n\nOnce the domain is trusted, the live webhook defaults to `https://shop.example.com/api/vibiz/webhook` anyway; a Limited key can set a live URL on one of the project's domains with `PATCH /v1/projects/<id>/payments?env=production`.\n\n```ts\nimport { vibiz } from '@vibiz/app';\n\nconst { url } = await vibiz.payments.checkout({\n lookup_key: 'pro-monthly',\n user: session.userId,\n success_url: 'https://shop.example.com/thanks',\n cancel_url: 'https://shop.example.com/pricing',\n});\n// redirect the buyer to url; await vibiz.webhooks.receive(req) in the webhook route (only the app key needed)\n```\n\nA script that sends a daily report by email:\n\n```bash\nvibiz init reports --resources email\nVIBIZ_APP_KEY=vz_app_\u2026 node report.mjs\n```\n\n```js\nimport { vibiz } from '@vibiz/app';\nawait vibiz.email.send({ to: 'team@example.com', subject: 'Daily report', text: body });\n```\n\nA plain HTML site with analytics and session replay (replay comes with analytics): `vibiz init mysite --resources analytics`, `vibiz domains add mysite.com --elsewhere`, then paste `vibiz analytics snippet` before `</head>` ([Analytics](/docs/analytics)).\n\n## Limits\n\nThe app runs under the account's caps wherever it is hosted: $5 daily spend per account, $1 AI budget per project per day, 50 app emails per project per day, and the rest in [Usage \u25B8 Limits](/docs/usage#limits). The owner raises them in the console (Billing \u25B8 Daily safety cap, the project \u25B8 AI \u25B8 Daily AI budget) or with `PATCH /v1/billing {\"daily_spend_limit_usd\": 50}` and `PATCH /v1/projects/<id>/ai {\"daily_budget_usd\": 10}`. thelastapi emails the owners at 80 % and 100 % of each cap and shows a banner with a link that raises it ([Limit alerts](/docs/usage#limit-alerts)). Agents building the app: tell the owner the caps and the expected daily cost, set the project budget to fit the traffic, and keep any cap the app adds under the platform's, telling the owner when it's hit.\n\n## Good to know\n\n- **The app key is a server secret.** `@vibiz/app` refuses to run in a browser. A plain site or a mobile app calls its own backend (or a small function) that holds the key; only the analytics tag's site key is public.\n- **Add every domain the app answers on.** Sign-in and analytics refuse other origins (`www.` comes with the domain). An agent may add one; sign-in trusts it once its TXT record proves it (or the owner confirms it).\n- **Payment webhooks have no default without hosting.** On thelastapi hosting events go to `https://<slug>.vibiz.app/api/vibiz/webhook` by themselves; elsewhere the owner sets the URL, or an agent sets one on a domain the owner already added. Setting it puts `VIBIZ_WEBHOOK_SECRET` in the env.\n- **Rotations follow on the next boot.** Values loaded with the key are read fresh each start; pasted values don't follow a rotation.\n- **What needs thelastapi hosting:** deploys, previews and rollback; buying a domain (it is served there at once: connect one bought elsewhere with `--elsewhere` instead); and the code in an [export](/docs/export) (the database and the env guide export without it).\n- **Add hosting later** with `vibiz add hosting`: every key is then pushed to the host by itself."
42
+ "body": "Every thelastapi service works on its own. The app doesn't have to be deployed on thelastapi: it can run on another host, be a plain HTML site, a mobile app's backend, a cron job or a script. A project is just the services you pick, and none of them needs `hosting`.\n\n## Three steps\n\n1. **Create a project with only what you need.** `vibiz init <name> --resources <one>` (MCP: `vibiz_create_project { name, resources: [\"auth\"] }`). Payments, files, web data, social, company and connectors need no resource: `--resources none` (or naming them, `--resources payments`, makes the same empty project).\n2. **Add the app's domain as running elsewhere**: `vibiz domains add app.example.com --elsewhere`. From a Limited key, analytics counts it at once and sign-in trusts it once its TXT record (`trust_record`, `_vibiz.app.example.com`) is in and `vibiz domains verify app.example.com` finds it, or the owner confirms it in the console. Sign-in trusts it, analytics counts visits from it, and payment events may be sent to it. Not needed for a script or a server with no web address.\n3. **Give the app its key: one key = everything.** One secret, `VIBIZ_APP_KEY`, reaches everything the project has: database, sign-in, email and inbox, AI models, files, payments, analytics with session replays, web data, social, phone and connectors. An owner copies it from the console and puts it in the host. An agent (or `vibiz app-key`, `vibiz connect`) gives them the exact link that opens it ready to copy (`app_key_console_url` from `vibiz_project_env`), never directions, in these words:\n\n > Add one key to Vercel and your app can use everything on thelastapi (database, sign-in, email and inbox, AI models, files, payments, analytics with session replays, web data, social, phone and connectors): copy VIBIZ_APP_KEY here: https://thelastapi.dev/projects/prj_\u2026/settings?key=production , paste it into Vercel's production environment variables, and redeploy. Or connect Vercel once (`vibiz hosts add vercel <app>`) and thelastapi keeps every variable in sync.\n\n The app loads the rest at boot:\n\n```ts\nimport { vibiz } from '@vibiz/app';\nawait vibiz.loadEnv(); // DATABASE_URL, VIBIZ_AUTH_*, VIBIZ_WEBHOOK_SECRET\u2026 into process.env\n```\n\nAny language: `npx @vibiz/cli run -- <start command>`. A build step or CI: `npx @vibiz/cli env pull --format dotenv -o .env.production`. A connected host (`vibiz hosts add <host> <app>`) gets the values written for it instead. For local work, `vibiz dev` writes the development copy (its own key, no production data) to `.env.development.local`.\n\n## Every website gets the SDK\n\nAn agent working on a website or web app that belongs to a thelastapi project (a `vibiz.json` in its folder, or one it made with `vibiz init`) always installs `@vibiz/app` pinned exactly (`npm install --save-exact @vibiz/app@0.3.21`), calls `await vibiz.loadEnv()` where the server starts, and adds the analytics tag with session replays on, unasked, and says it did. Secrets such as a host's token are never asked for in a chat: the agent hands over the command (`vibiz hosts add vercel <app>`), and a person types the value in their own terminal.\n\n## Per service\n\n| Service | Create with | Domain needed | The app uses it with |\n| --- | --- | --- | --- |\n| Database | `--resources database` | no | `DATABASE_URL`, plain Postgres over the internet |\n| Sign-in | `--resources auth` (brings the database) | yes, the app's web address | `VIBIZ_AUTH_*` from the env ([Sign-in](/docs/sign-in)) |\n| Payments | `--resources none` | for webhooks | `vibiz.payments.checkout(\u2026)` with any `https` `success_url` and `cancel_url`; events at the webhook URL the owner sets (`vibiz payments webhook <url>`) |\n| Email | `--resources email` | no | `vibiz.email.send(\u2026)` from `<mailbox>@<slug>.vibiz.app` |\n| Email at your own domain | `--resources none` | its own DNS | `vibiz email forward hello@example.com <inbox>` (owner), no app code |\n| AI | `--resources ai` | no | `new OpenAI(vibiz.ai)`: OpenAI-compatible, metered per call |\n| Analytics | `--resources analytics` (add `replay` too, unless the person doesn't want recordings) | yes | the tag from `vibiz analytics snippet` before `</head>`; server events with `vibiz.track(\u2026)` |\n| Session replay | `--resources replay` (brings analytics) | yes | the same tag: it records by itself (`require_consent: true` if visitors must agree first, then `vibiz('replay', 'start')`) |\n| Files | `--resources none` | no | `vibiz.files.upload(bytes, { name })` returns a permanent link |\n| Web data | `--resources none` | no | `vibiz.actions.run('web.scrape', { url })` and every other action |\n| Design | `--resources none`, or no project at all | no | `vibiz design <url> --tailwind`, or `vibiz.actions.run('web.design', { url })`: the theme and brief work in any stack |\n| Connectors | `--resources none` | no | `vibiz connectors add \u2026`; the app calls them through thelastapi with its key |\n| Social | `--resources none` | no | the owner connects accounts once (`vibiz social connect <platform>`); posts from the CLI, the console or an agent |\n| Company formation | `--resources none` | no | `vibiz company draft`, the owner files |\n\nWithout the package, every call above is an HTTP route under `/v1/app` with `Authorization: Bearer $VIBIZ_APP_KEY` ([@vibiz/app](/docs/app-sdk)).\n\n## Examples\n\nA Next.js app on another host that only takes payments:\n\n```bash\nvibiz init shop --resources none\nvibiz domains add shop.example.com --elsewhere # Limited key: then its TXT record + verify\nvibiz payments products add Pro --amount 900 --interval month --lookup-key pro-monthly\nvibiz payments webhook https://shop.example.com/api/vibiz/webhook # full-access key (production); Limited keys set development\n```\n\nOnce the domain is trusted, the live webhook defaults to `https://shop.example.com/api/vibiz/webhook` anyway; a Limited key can set a live URL on one of the project's domains with `PATCH /v1/projects/<id>/payments?env=production`.\n\n```ts\nimport { vibiz } from '@vibiz/app';\n\nconst { url } = await vibiz.payments.checkout({\n lookup_key: 'pro-monthly',\n user: session.userId,\n success_url: 'https://shop.example.com/thanks',\n cancel_url: 'https://shop.example.com/pricing',\n});\n// redirect the buyer to url; await vibiz.webhooks.receive(req) in the webhook route (only the app key needed)\n```\n\nA script that sends a daily report by email:\n\n```bash\nvibiz init reports --resources email\nVIBIZ_APP_KEY=vz_app_\u2026 node report.mjs\n```\n\n```js\nimport { vibiz } from '@vibiz/app';\nawait vibiz.email.send({ to: 'team@example.com', subject: 'Daily report', text: body });\n```\n\nA plain HTML site with analytics and session replay (replay comes with analytics): `vibiz init mysite --resources analytics`, `vibiz domains add mysite.com --elsewhere`, then paste `vibiz analytics snippet` before `</head>` ([Analytics](/docs/analytics)).\n\n## Limits\n\nThe app runs under the account's caps wherever it is hosted: $5 daily spend per account, $1 AI budget per project per day, 50 app emails per project per day, and the rest in [Usage \u25B8 Limits](/docs/usage#limits). The owner raises them in the console (Billing \u25B8 Daily safety cap, the project \u25B8 AI \u25B8 Daily AI budget) or with `PATCH /v1/billing {\"daily_spend_limit_usd\": 50}` and `PATCH /v1/projects/<id>/ai {\"daily_budget_usd\": 10}`. thelastapi emails the owners at 80 % and 100 % of each cap and shows a banner with a link that raises it ([Limit alerts](/docs/usage#limit-alerts)). Agents building the app: tell the owner the caps and the expected daily cost, set the project budget to fit the traffic, and keep any cap the app adds under the platform's, telling the owner when it's hit.\n\n## Good to know\n\n- **The app key is a server secret.** `@vibiz/app` refuses to run in a browser. A plain site or a mobile app calls its own backend (or a small function) that holds the key; only the analytics tag's site key is public.\n- **Add every domain the app answers on.** Sign-in and analytics refuse other origins (`www.` comes with the domain). An agent may add one; sign-in trusts it once its TXT record proves it (or the owner confirms it).\n- **Payment webhooks have no default without hosting.** On thelastapi hosting events go to `https://<slug>.vibiz.app/api/vibiz/webhook` by themselves; elsewhere the owner sets the URL, or an agent sets one on a domain the owner already added. Setting it puts `VIBIZ_WEBHOOK_SECRET` in the env.\n- **Rotations follow on the next boot.** Values loaded with the key are read fresh each start; pasted values don't follow a rotation.\n- **What needs thelastapi hosting:** deploys, previews and rollback; buying a domain (it is served there at once: connect one bought elsewhere with `--elsewhere` instead); and the code in an [export](/docs/export) (the database and the env guide export without it).\n- **Add hosting later** with `vibiz add hosting`: every key is then pushed to the host by itself."
43
43
  },
44
44
  {
45
45
  "slug": "keys",
@@ -48,7 +48,7 @@ var PAGES = [
48
48
  "section": "Getting started",
49
49
  "order": 30,
50
50
  "topic": null,
51
- "body": '**A key can do everything the owner can, unless the person chose Limited.** Signing in (`vibiz login`, or Authorize for an MCP client) asks which: **Full access** is pre-selected; **Limited** builds and runs but never holds a production secret nor moves live money. A Limited key works against a separate development environment that holds none of production\'s data, and gets a link for the person whenever something needs more. The owner can change any key between Full and Limited on the Keys page.\n\n## The keys\n\n| Key | Looks like | Held by | Can |\n| --- | --- | --- | --- |\n| **Full-access key** (default) | `vz_sk_\u2026`, `access: owner` | the CLI, the MCP server, CI, a person | everything the owner can: projects, deploys, actions, email, AI, usage, the production env, keys, domains, connecting hosts, live refunds and withdrawals, deleting |\n| **Limited key** | `vz_sk_\u2026`, `access: agent` | an agent the person chose to limit | create projects, deploy, promote, run actions, send email, use AI, read usage, get the development env, everything in development. Never the production env, keys, removing a domain or live money |\n| **Console session** | a cookie | a person signed in at thelastapi.dev | the access of their account: whoever opened the account is its owner |\n| **App key** | `vz_app_\u2026` (`VIBIZ_APP_KEY`) | the running app | its own project and environment only: env, AI, actions, email, events, payments for its users |\n| **Project AI key** | `vz_ai_\u2026` | the app (`VIBIZ_AI_API_KEY`) | the AI gateway, billed to the project |\n\nNew keys have full access unless the owner picks Limited (creating, changing and revoking keys needs a full-access key):\n\n```bash\nvibiz keys create ci # full access, shown once\nvibiz keys create growth-agent --limited # a Limited key\nvibiz keys access key_\u2026 limited # change it afterwards (full | read | limited)\nvibiz keys revoke key_\u2026\n```\n\n```bash\ncurl https://thelastapi.dev/v1/api-keys -H "Authorization: Bearer $OWNER_KEY" \\\n -H \'content-type: application/json\' -d \'{"name":"growth-agent","access":"agent"}\'\n# \u2192 201 { "id": "key_\u2026", "secret": "vz_sk_\u2026", "access": "agent", \u2026 } the secret is returned once\ncurl -X PATCH https://thelastapi.dev/v1/api-keys/key_\u2026 -H "Authorization: Bearer $OWNER_KEY" \\\n -H \'content-type: application/json\' -d \'{"access":"owner"}\'\n# \u2192 200 { "id": "key_\u2026", "access": "owner", \u2026 } a key never changes its own access\n```\n\nKeys made before full access became the default keep the access they had.\n\nName a key per person or agent: usage breaks down by key (`vibiz usage --by api_key`).\n\n## Keys and environments\n\n- **Full-access key** (`vz_sk_\u2026`, access `owner`): what the MCP server and the CLI hold by default, since signing in pre-selects Full access. It can do everything the owner can: projects, deploys, actions, AI, usage, production secrets, live money, keys, domains, connecting hosts, deleting.\n- **Limited key** (access `agent`): what the person gets by choosing Limited when they sign in (or set later on the Keys page). Builds and runs: projects, deploys, actions, AI, usage, the development env, everything in development. Never a production secret, never live money: production refunds, cancels, withdrawals, payment settings, keys, removing domains and connecting hosts answer `403 owner_only`. The fix for `owner_only` is a person, not a retry: give them `details.console_url` to do it themselves, or `details.key_url` to give this key full access (or they sign in again choosing Full access).\n- **App key** (`vz_app_\u2026`, `VIBIZ_APP_KEY`): the running app\'s one secret, per environment.\n\n**Development env** (`vibiz_dev_env`, `vibiz dev`): its own database branch with the app\'s tables and no production rows, its own sign-in (trusts `http://localhost:3000`), its own AI key, and `VIBIZ_WEBHOOK_SECRET` once a development webhook is set. `write_to` puts the values in an env file without showing them.\n\n**The project id**: `./vibiz.json` `{ "project_id": "prj_\u2026" }` in a linked app folder, or `vibiz_project_status` for the list. Read it instead of asking the user.\n\n## Environments\n\nEvery project has two environments. `env` (or `--dev` in the CLI) picks one; it defaults to **production for full-access keys and development for Limited keys**.\n\n| | production | development |\n| --- | --- | --- |\n| Database | the real one | a branch with the same tables and **no rows** |\n| Sign-in | real users; trusts the live domains | its own users; trusts `http://localhost:3000` |\n| AI | the project\'s key | a second key, billed to the project |\n| Payments | live money, 7-day hold | test mode, test cards, no hold, `simulate` |\n| Company | a real filing, real fees | nothing filed, nothing charged, `simulate` |\n| Who | full access for secrets and money | anyone on the account, Limited keys included |\n\nHosting, analytics, replay and email have no development copy (a local run shouldn\'t count as visits or send mail from the live address).\n\n```bash\nvibiz dev # create it once and write .env.development.local (names printed, values not)\nvibiz dev -- npm run dev # pass the values to a command, no file\nvibiz dev --reset # throw the copy away; the next `vibiz dev` branches again\n```\n\nOver HTTP: `POST /v1/projects/:id/dev` (create, `202`), `GET /v1/projects/:id/dev` (`status: none | provisioning | ready | failed`), `GET /v1/projects/:id/dev/env` (the values, `409` until ready), `DELETE /v1/projects/:id/dev`.\n\n## Getting the production env to the app\n\n1. **thelastapi hosting**: automatic. Every key is pushed to the host and kept in sync.\n2. **A connected host**: the owner connects Vercel, Netlify, Render, Railway, Fly.io, Heroku, Cloudflare Workers or Pages, or GitHub Actions once (`vibiz hosts add <host> <app>`); thelastapi writes the env there whenever it changes, rotations included. Vercel is verified live; the others are in beta.\n3. **One key, any host**: put only `VIBIZ_APP_KEY` in the host and load the rest at boot.\n\n```ts\nimport { vibiz } from \'@vibiz/app\';\nawait vibiz.loadEnv(); // the app\'s env into process.env\n```\n\n```bash\neval "$(curl -fsS -H "Authorization: Bearer $VIBIZ_APP_KEY" \\\n https://thelastapi.dev/v1/app/env?format=shell)" && exec node server.js\n```\n\n`GET /v1/app/env?format=json|dotenv|shell|docker`. Before any of these, the app\'s domain is added (`vibiz domains add app.example.com --elsewhere`; a Limited key may, and sign-in then trusts it once its TXT record proves it or the owner confirms it) so sign-in and analytics accept it. The project needs no thelastapi hosting at all: any one service works alone ([Use one service](/docs/use-one)).\n\n## The app key\n\n- One per project **and** environment, put in that environment\'s env with `VIBIZ_API_URL`. A development key reads only the development env, and its events are not recorded.\n- It works only for its own project: account routes answer `401`.\n- Rotate with `vibiz app-key rotate` (production needs an owner). The new key is pushed to thelastapi hosting and every connected host; the old one keeps working for a day by default (`--grace <seconds>`, `0` ends it now). The new secret is never printed.\n\n## What a Limited key can and can\'t do\n\n| | Limited key | Full-access key |\n| --- | --- | --- |\n| Projects, deploys, actions, AI, email, usage | yes | yes |\n| Development env values | yes | yes |\n| Production env values (`GET /projects/:id/env`) | names only (`?names=1`) | yes |\n| Add the app\'s domains | yes (sign-in trusts one once its TXT record proves it) | yes |\n| Create, change or revoke keys, remove domains, connect hosts | no | yes |\n| Live refunds, cancels, withdrawals, payment settings | no | yes |\n| Rotate the production app key | no | yes |\n\nA Limited key hitting an owner route gets `403 forbidden` with `details.reason: "owner_only"`, `details.permission` (what it lacks), `details.grant_url` (`/keys/<id>/allow?permission=\u2026`: a page for this key to allow just that, read everything, or everything), `details.console_url` (where the person does it), `details.key_url` (the Keys page with this key highlighted, `/keys?key=<id>`) and `details.next_step` naming them. Retrying with the same key works only once the permission is allowed.\n\n## Permissions: Read everything, or one at a time\n\nA Limited key can be given more without full access:\n\n- **Read everything** (`preset: "read_all"`): reads all of it, production data and settings included (the production database, production variables, live payment details, a company\'s full details, exports), and changes nothing live.\n- **Single permissions** (`grants`): exactly the ones it needs, e.g. only `database.production:read`.\n\n| Permission | Group | What it allows |\n| --- | --- | --- |\n| `database.production:read` | Database | read the production database (the app\'s users\' data) |\n| `app_users:write` | Database | sign out one of the app\'s users |\n| `env.production:read` | Production settings | read production variables |\n| `env.production:write` | Production settings | set and remove production variables |\n| `app_key.production:read` | Production settings | see the production app key |\n| `app_key.production:write` | Production settings | rotate the production app key |\n| `auth.production:write` | Production settings | change production sign-in settings |\n| `exports.production:read` | Production settings | export production data and download secret values |\n| `projects:write` | Projects | turn the public live page on or off |\n| `domains:write` | Domains & hosting | remove domains |\n| `hosting:write` | Domains & hosting | connect and disconnect hosts |\n| `payments.live:read` | Payments | see live payment details and webhook secrets |\n| `payments.live:write` | Payments | refund, cancel, change live products and webhooks, withdraw, connect your own payment account |\n| `billing:write` | Billing & keys | change billing settings and the card |\n| `keys:write` | Billing & keys | create, revoke and change API keys |\n| `ai_keys:write` | Billing & keys | set, change and remove AI provider keys |\n| `company:read` | Company | see a company\'s full details and documents |\n| `company:write` | Company | send tax ids, sign, answer, pay for and submit filings |\n| `connectors.live:write` | Connectors | change live connectors and approve their calls |\n| `email.marketing:write` | Email | change marketing email settings |\n| `social.live:write` | Social | approve, publish, cancel live posts and ad changes |\n| `phone:write` | Phone | buy and release phone numbers |\n| `search:write` | Search | connect Google and Bing and change search settings |\n\nWhen a Limited key is refused, the error names the permission and links to it: `details.permission` (`*` when only full access will do), `details.grant_url` (a page for this one key: what it asked for, when it was last used, and **Allow just this**, **Read everything**, **Full access** or **Choose exactly**), `details.key_id`, and `details.console_url` (where a person does it by hand). An agent gives the user `grant_url`, then retries once it is allowed. The CLI prints it as "Allow it for this key: \u2026" and opens it when a person is at the terminal.\n\n```bash\nvibiz keys access # what this key may do, and the link to change it\nvibiz keys access key_\u2026 read # Read everything (full | read | limited)\nvibiz keys access key_\u2026 allow database.production:read\nvibiz keys permissions # every permission, in plain words\nvibiz keys create reporter --read-all\n```\n\n```bash\ncurl -X PATCH https://thelastapi.dev/v1/api-keys/key_\u2026 -H "Authorization: Bearer $OWNER_KEY" \\\n -H \'content-type: application/json\' -d \'{"grants":["database.production:read"]}\'\n```\n\n`PATCH /v1/api-keys/:id` takes `{"access"}`, `{"preset": "full" | "read_all" | "limited"}` or `{"grants": [...]}` (`GET /v1/api-keys/permissions` lists them). It needs `keys:write`; a Limited key never gives more than it has, and never changes its own access. Signing in (`vibiz login`, an MCP client\'s Authorize) offers Full access, Read everything or Limited.\n\n\nWhatever the access, a few things are the person\'s own in the browser, not a key permission: verifying their identity to withdraw, connecting their own Stripe account, and approving a sign-in. Nobody can read card numbers.\n\n## Secrets by link\n\nA secret never passes through a chat. When an app needs one (a third-party API key, a host token), the agent asks thelastapi for a link and gives it to the person, who pastes the value there:\n\n```text\nPaste STRIPE_SECRET_KEY here: https://thelastapi.dev/projects/prj_\u2026/secrets/new?name=STRIPE_SECRET_KEY&env=production&kind=env . It goes straight to thelastapi, never through this chat.\n```\n\n- From an agent: `vibiz_request_secret { project_id, name, env?, kind? }` returns that `console_url` and the sentence to pass on. Over HTTP: `POST /v1/projects/:id/secret-link { name, environment?, kind? }`.\n- `kind`: `env` (default) is one of the app\'s own variables; `connector` a [connector](/docs/connectors)\'s key (name = its variable); `ai` the project\'s own lab key (name `google`); `host` a host token, so thelastapi keeps that host\'s env in sync (name `vercel`, `netlify`\u2026).\n- **The app\'s own variables** are write-only: names are listed (`vibiz env vars`, `GET /v1/projects/:id/env/vars`), a value is never returned to any key. They are in the env the app loads (`await vibiz.loadEnv()`, `vibiz env pull`) as `process.env.NAME`, and in every connected host. Setting a production one needs full access (a Limited key gets the link instead). In a terminal: `vibiz env set <NAME>` asks for the value hidden; `vibiz env link <NAME>` prints the link; `vibiz env unset <NAME>` removes it.\n\n## Errors\n\n| Code | Status | When | Next step |\n| --- | --- | --- | --- |\n| `unauthorized` | 401 | missing, unknown or revoked key; an app key on an account route | check `VIBIZ_API_KEY` / `VIBIZ_APP_KEY` |\n| `forbidden` + `owner_only` | 403 | a Limited key without the permission (`details.permission`) | give the person `details.grant_url` (allows it for this key), or `details.console_url` to do it themselves |\n| `dependency_not_ready` | 409 | the development copy isn\'t ready yet | poll `GET /projects/:id/dev` |\n| `not_found` | 404 | the project isn\'t on this account | check `./vibiz.json` |'
51
+ "body": '**A key can do everything the owner can, unless the person chose Limited.** Signing in (`vibiz login`, or Authorize for an MCP client) asks which: **Full access** is pre-selected; **Limited** builds and runs but never holds a production secret nor moves live money. A Limited key works against a separate development environment that holds none of production\'s data, and gets a link for the person whenever something needs more. The owner can change any key between Full and Limited on the Keys page.\n\n## The keys\n\n| Key | Looks like | Held by | Can |\n| --- | --- | --- | --- |\n| **Full-access key** (default) | `vz_sk_\u2026`, `access: owner` | the CLI, the MCP server, CI, a person | everything the owner can: projects, deploys, actions, email, AI, usage, the production env, keys, domains, connecting hosts, live refunds and withdrawals, deleting |\n| **Limited key** | `vz_sk_\u2026`, `access: agent` | an agent the person chose to limit | create projects, deploy, promote, run actions, send email, use AI, read usage, get the development env, everything in development. Never the production env, keys, removing a domain or live money |\n| **Console session** | a cookie | a person signed in at thelastapi.dev | the access of their account: whoever opened the account is its owner |\n| **App key** | `vz_app_\u2026` (`VIBIZ_APP_KEY`) | the running app | its own project and environment only: env, AI, actions, email, events, payments for its users |\n| **Project AI key** | `vz_ai_\u2026` | the app (`VIBIZ_AI_API_KEY`) | the AI gateway, billed to the project |\n\nNew keys have full access unless the owner picks Limited (creating, changing and revoking keys needs a full-access key):\n\n```bash\nvibiz keys create ci # full access, shown once\nvibiz keys create growth-agent --limited # a Limited key\nvibiz keys access key_\u2026 limited # change it afterwards (full | read | limited)\nvibiz keys revoke key_\u2026\n```\n\n```bash\ncurl https://thelastapi.dev/v1/api-keys -H "Authorization: Bearer $OWNER_KEY" \\\n -H \'content-type: application/json\' -d \'{"name":"growth-agent","access":"agent"}\'\n# \u2192 201 { "id": "key_\u2026", "secret": "vz_sk_\u2026", "access": "agent", \u2026 } the secret is returned once\ncurl -X PATCH https://thelastapi.dev/v1/api-keys/key_\u2026 -H "Authorization: Bearer $OWNER_KEY" \\\n -H \'content-type: application/json\' -d \'{"access":"owner"}\'\n# \u2192 200 { "id": "key_\u2026", "access": "owner", \u2026 } a key never changes its own access\n```\n\nKeys made before full access became the default keep the access they had.\n\nName a key per person or agent: usage breaks down by key (`vibiz usage --by api_key`).\n\n## Keys and environments\n\n- **Full-access key** (`vz_sk_\u2026`, access `owner`): what the MCP server and the CLI hold by default, since signing in pre-selects Full access. It can do everything the owner can: projects, deploys, actions, AI, usage, production secrets, live money, keys, domains, connecting hosts, deleting.\n- **Limited key** (access `agent`): what the person gets by choosing Limited when they sign in (or set later on the Keys page). Builds and runs: projects, deploys, actions, AI, usage, the development env, everything in development. Never a production secret, never live money: production refunds, cancels, withdrawals, payment settings, keys, removing domains and connecting hosts answer `403 owner_only`. The fix for `owner_only` is a person, not a retry: give them `details.console_url` to do it themselves, or `details.key_url` to give this key full access (or they sign in again choosing Full access).\n- **App key** (`vz_app_\u2026`, `VIBIZ_APP_KEY`): the running app\'s one secret, per environment.\n\n**Development env** (`vibiz_dev_env`, `vibiz dev`): its own database branch with the app\'s tables and no production rows, its own sign-in (trusts `http://localhost:3000`), its own AI key, and `VIBIZ_WEBHOOK_SECRET` once a development webhook is set. `write_to` puts the values in an env file without showing them.\n\n**The project id**: `./vibiz.json` `{ "project_id": "prj_\u2026" }` in a linked app folder, or `vibiz_project_status` for the list. Read it instead of asking the user.\n\n## Environments\n\nEvery project has two environments. `env` (or `--dev` in the CLI) picks one; it defaults to **production for full-access keys and development for Limited keys**.\n\n| | production | development |\n| --- | --- | --- |\n| Database | the real one | a branch with the same tables and **no rows** |\n| Sign-in | real users; trusts the live domains | its own users; trusts `http://localhost:3000` |\n| AI | the project\'s key | a second key, billed to the project |\n| Payments | live money, 7-day hold | test mode, test cards, no hold, `simulate` |\n| Company | a real filing, real fees | nothing filed, nothing charged, `simulate` |\n| Who | full access for secrets and money | anyone on the account, Limited keys included |\n\nHosting, analytics, replay and email have no development copy (a local run shouldn\'t count as visits or send mail from the live address).\n\n```bash\nvibiz dev # create it once and write .env.development.local (names printed, values not)\nvibiz dev -- npm run dev # pass the values to a command, no file\nvibiz dev --reset # throw the copy away; the next `vibiz dev` branches again\n```\n\nOver HTTP: `POST /v1/projects/:id/dev` (create, `202`), `GET /v1/projects/:id/dev` (`status: none | provisioning | ready | failed`), `GET /v1/projects/:id/dev/env` (the values, `409` until ready), `DELETE /v1/projects/:id/dev`.\n\n## Getting the production env to the app\n\n1. **thelastapi hosting**: automatic. Every key is pushed to the host and kept in sync.\n2. **A connected host**: the owner connects Vercel, Netlify, Render, Railway, Fly.io, Heroku, Cloudflare Workers or Pages, or GitHub Actions once (`vibiz hosts add <host> <app>`); thelastapi writes the env there whenever it changes, rotations included. Vercel is verified live; the others are in beta.\n3. **One key, any host**: put only `VIBIZ_APP_KEY` in the host and load the rest at boot.\n\n```ts\nimport { vibiz } from \'@vibiz/app\';\nawait vibiz.loadEnv(); // the app\'s env into process.env\n```\n\n```bash\neval "$(curl -fsS -H "Authorization: Bearer $VIBIZ_APP_KEY" \\\n https://thelastapi.dev/v1/app/env?format=shell)" && exec node server.js\n```\n\n`GET /v1/app/env?format=json|dotenv|shell|docker`. Before any of these, the app\'s domain is added (`vibiz domains add app.example.com --elsewhere`; a Limited key may, and sign-in then trusts it once its TXT record proves it or the owner confirms it) so sign-in and analytics accept it. The project needs no thelastapi hosting at all: any one service works alone ([Use one service](/docs/use-one)).\n\n## The app key\n\n- One per project **and** environment, put in that environment\'s env with `VIBIZ_API_URL`. A development key reads only the development env, and its events are not recorded.\n- It works only for its own project: account routes answer `401`.\n- Rotate with `vibiz app-key rotate` (production needs an owner). The new key is pushed to thelastapi hosting and every connected host; the old one keeps working for a day by default (`--grace <seconds>`, `0` ends it now). The new secret is never printed.\n\n## What a Limited key can and can\'t do\n\n| | Limited key | Full-access key |\n| --- | --- | --- |\n| Projects, deploys, actions, AI, email, usage | yes | yes |\n| Development env values | yes | yes |\n| Production env values (`GET /projects/:id/env`) | names only (`?names=1`) | yes |\n| Add the app\'s domains | yes (sign-in trusts one once its TXT record proves it) | yes |\n| Create, change or revoke keys, remove domains, connect hosts | no | yes |\n| Live refunds, cancels, withdrawals, payment settings | no | yes |\n| Rotate the production app key | no | yes |\n\nA Limited key hitting an owner route gets `403 forbidden` with `details.reason: "owner_only"`, `details.permission` (what it lacks), `details.grant_url` (`/keys/<id>/allow?permission=\u2026`: a page for this key to allow just that, read everything, or everything), `details.console_url` (where the person does it), `details.key_url` (the Keys page with this key highlighted, `/keys?key=<id>`) and `details.next_step` naming them. Retrying with the same key works only once the permission is allowed.\n\n## Permissions: Read everything, or one at a time\n\nA Limited key can be given more without full access:\n\n- **Read everything** (`preset: "read_all"`): reads all of it, production data and settings included (the production database, production variables, live payment details, a company\'s full details, exports), and changes nothing live.\n- **Single permissions** (`grants`): exactly the ones it needs, e.g. only `database.production:read`.\n\n| Permission | Group | What it allows |\n| --- | --- | --- |\n| `database.production:read` | Database | read the production database (the app\'s users\' data) |\n| `app_users:write` | Database | sign out one of the app\'s users |\n| `env.production:read` | Production settings | read production variables |\n| `env.production:write` | Production settings | set and remove production variables |\n| `app_key.production:read` | Production settings | see the production app key |\n| `app_key.production:write` | Production settings | rotate the production app key |\n| `auth.production:write` | Production settings | change production sign-in settings |\n| `exports.production:read` | Production settings | export production data and download secret values |\n| `projects:write` | Projects | turn the public live page on or off |\n| `domains:write` | Domains & hosting | remove domains |\n| `domains.registration:write` | Domains & hosting | see and change a bought domain\'s owner details, auto-renew and transfer code, and move it between projects |\n| `dns:write` | Domains & hosting | change a domain\'s DNS records |\n| `hosting:write` | Domains & hosting | connect and disconnect hosts |\n| `payments.live:read` | Payments | see live payment details and webhook secrets |\n| `payments.live:write` | Payments | refund, cancel, change live products and webhooks, withdraw, connect your own payment account |\n| `billing:write` | Billing & keys | change billing settings and the card |\n| `keys:write` | Billing & keys | create, revoke and change API keys |\n| `ai_keys:write` | Billing & keys | set, change and remove AI provider keys |\n| `company:read` | Company | see a company\'s full details and documents |\n| `company:write` | Company | send tax ids, sign, answer, pay for and submit filings |\n| `connectors.live:write` | Connectors | change live connectors and approve their calls |\n| `email.marketing:write` | Email | change marketing email settings |\n| `email.inbox:write` | Email | add, change and delete mailboxes and forwarding, and move a domain\'s mail |\n| `social.live:write` | Social | approve, publish, cancel live posts and ad changes |\n| `phone:write` | Phone | buy and release phone numbers |\n| `search:write` | Search | connect Google and Bing and change search settings |\n\nWhen a Limited key is refused, the error names the permission and links to it: `details.permission` (`*` when only full access will do), `details.grant_url` (a page for this one key: what it asked for, when it was last used, and **Allow just this**, **Read everything**, **Full access** or **Choose exactly**), `details.key_id`, and `details.console_url` (where a person does it by hand). An agent gives the user `grant_url`, then retries once it is allowed. The CLI prints it as "Allow it for this key: \u2026" and opens it when a person is at the terminal.\n\n```bash\nvibiz keys access # what this key may do, and the link to change it\nvibiz keys access key_\u2026 read # Read everything (full | read | limited)\nvibiz keys access key_\u2026 allow database.production:read\nvibiz keys permissions # every permission, in plain words\nvibiz keys create reporter --read-all\n```\n\n```bash\ncurl -X PATCH https://thelastapi.dev/v1/api-keys/key_\u2026 -H "Authorization: Bearer $OWNER_KEY" \\\n -H \'content-type: application/json\' -d \'{"grants":["database.production:read"]}\'\n```\n\n`PATCH /v1/api-keys/:id` takes `{"access"}`, `{"preset": "full" | "read_all" | "limited"}` or `{"grants": [...]}` (`GET /v1/api-keys/permissions` lists them). It needs `keys:write`; a Limited key never gives more than it has, and never changes its own access. Signing in (`vibiz login`, an MCP client\'s Authorize) offers Full access, Read everything or Limited.\n\n\nWhatever the access, a few things are the person\'s own in the browser, not a key permission: verifying their identity to withdraw, connecting their own Stripe account, and approving a sign-in. Nobody can read card numbers.\n\n## Secrets by link\n\nA secret never passes through a chat. When an app needs one (a third-party API key, a host token), the agent asks thelastapi for a link and gives it to the person, who pastes the value there:\n\n```text\nPaste STRIPE_SECRET_KEY here: https://thelastapi.dev/projects/prj_\u2026/secrets/new?name=STRIPE_SECRET_KEY&env=production&kind=env . It goes straight to thelastapi, never through this chat.\n```\n\n- From an agent: `vibiz_request_secret { project_id, name, env?, kind? }` returns that `console_url` and the sentence to pass on. Over HTTP: `POST /v1/projects/:id/secret-link { name, environment?, kind? }`.\n- `kind`: `env` (default) is one of the app\'s own variables; `connector` a [connector](/docs/connectors)\'s key (name = its variable); `ai` the project\'s own lab key (name `google`); `host` a host token, so thelastapi keeps that host\'s env in sync (name `vercel`, `netlify`\u2026).\n- **The app\'s own variables** are write-only: names are listed (`vibiz env vars`, `GET /v1/projects/:id/env/vars`), a value is never returned to any key. They are in the env the app loads (`await vibiz.loadEnv()`, `vibiz env pull`) as `process.env.NAME`, and in every connected host. Setting a production one needs full access (a Limited key gets the link instead). In a terminal: `vibiz env set <NAME>` asks for the value hidden; `vibiz env link <NAME>` prints the link; `vibiz env unset <NAME>` removes it.\n\n## Errors\n\n| Code | Status | When | Next step |\n| --- | --- | --- | --- |\n| `unauthorized` | 401 | missing, unknown or revoked key; an app key on an account route | check `VIBIZ_API_KEY` / `VIBIZ_APP_KEY` |\n| `forbidden` + `owner_only` | 403 | a Limited key without the permission (`details.permission`) | give the person `details.grant_url` (allows it for this key), or `details.console_url` to do it themselves |\n| `dependency_not_ready` | 409 | the development copy isn\'t ready yet | poll `GET /projects/:id/dev` |\n| `not_found` | 404 | the project isn\'t on this account | check `./vibiz.json` |'
52
52
  },
53
53
  {
54
54
  "slug": "billing",
@@ -201,7 +201,16 @@ var PAGES = [
201
201
  "section": "Products",
202
202
  "order": 87,
203
203
  "topic": null,
204
- "body": 'Every account can claim a username and get a public page at `https://thelastapi.dev/<username>`: who you are, the businesses you list, and only the numbers you choose to share, with a chart over time. Each listed business also gets its own page at `https://thelastapi.dev/<username>/<project-slug>`. Set it up in the console \u25B8 **Settings \u25B8 Public profile**, with `vibiz profile`, the `vibiz_profile` MCP tool or `PATCH /v1/profile`.\n\n## Private by default\n\nNothing is public until you say so, at every level:\n\n| Level | Default | Turn it on |\n| --- | --- | --- |\n| The profile | private: the page answers **not found**, the same as a username nobody has | `public: true` (needs a username) |\n| Each business | not listed | `listed: true` on that business |\n| Each number of a business | hidden | `show_revenue`, `show_mrr`, `show_visitors` on that business |\n| Activity | hidden | `show_activity`, and `show_activity_stats` for streaks |\n\nA number that is off is left out of the page, its JSON and the totals altogether. Totals add up only the values shared: if one business shares revenue and another doesn\'t, the total revenue is the first one\'s. Turning something off takes effect on the next page load; copies cached by browsers and caches can live up to 5 minutes.\n\n## What a page shows\n\n- **You**: display name, `@username`, bio, picture (prefilled from your sign-in picture; clear it to show your initial), an optional X handle, website and country, and a Share button that copies the link.\n- **Totals**: total revenue, MRR, visitors (30 days) and how many businesses, each only when at least one business shares it.\n- **A chart** of revenue, MRR or visitors combined, over 30 days, 12 months or all time. The choice is in the address (`?period=12m&metric=revenue`), so a link opens it.\n- **Activity** (when on): a grid of the last 52 weeks, one square per day, shaded by what you did: each production deploy counts 3, each project created 5, and calls made with your account\'s own keys (CLI, MCP, API) count by their order of magnitude (`ceil(log2(calls + 1))`), so a deploy always shows. Only daily totals: never what was called, never which business. Optional streaks: current, longest, most active day.\n- **A card per listed business**: logo (yours, else the live site\'s icon, else its initial), name, tagline, a Visit link to its site, the month it was founded (its creation day unless you set another), and its shared numbers with a small sparkline.\n\nThe numbers come from thelastapi: **revenue** is all-time live sales through thelastapi payments, net of refunds, in US dollars; **MRR** is the monthly value of active subscriptions sold through thelastapi payments (yearly plans count a twelfth); **visitors** are distinct visitors in the last 30 days from thelastapi analytics. Test mode never counts.\n\n## Usernames\n\n3 to 30 characters: lowercase letters, digits, `-` and `_`, starting with a letter or digit. A username is unique whatever the case (`Alice` is `alice`; `/Alice` redirects). Names the site already uses (`docs`, `blog`, `settings`, `projects`, `v1`, `mcp`\u2026) and a few others (`admin`, `api`, `pricing`, `login`, `thelastapi`\u2026) are reserved. Check one with `vibiz profile check <name>` or `GET /v1/profile/username?u=<name>`. Changing your username breaks links to the old one.\n\n## From an agent\n\n```bash\nvibiz profile # the profile and every business\'s switches\nvibiz profile set username=alice name="Alice" bio="I build small things."\nvibiz profile business sunny-shop listed=on tagline="Sunny things" revenue=on visitors=on\nvibiz profile set public=on activity=on # publish it\nvibiz profile businesses listed=on # list every business at once (numbers stay hidden)\nvibiz profile businesses shop,blog visitors=on # the same switch on a few, by slug or id\n```\n\nMany at once: `PATCH /v1/profile/businesses { "projects": ["shop", "prj_\u2026"], "listed": true, "show_visitors": true }` (leave `projects` out for every active project; only the switches you send change). SDK `vibiz.profile.businesses(\u2026)`, MCP `vibiz_profile` action `businesses`. In the console, Settings \u25B8 Public profile lists every business in one table with a search, a Listed / Not listed view, and "List all", "Show all" and "Hide all" for what is in view; showing a number on many businesses asks once more.\n\nChanging the profile takes a full-access key (or a Limited key allowed `profile:write`). Agents should never publish a profile, list a business or share a number unless the person asked: revenue is private business data.\n\nThe public data is also JSON: `GET /v1/profiles/<username>` (and `/v1/profiles/<username>/<slug>`), no key needed, with the same fields the page shows and nothing more.'
204
+ "body": 'Every account can claim a username and get a public page at `https://thelastapi.dev/<username>`: who you are, the businesses you list, and only the numbers you choose to share, with a chart over time. Each listed business also gets its own page at `https://thelastapi.dev/<username>/<project-slug>`. Set it up in the console \u25B8 **Settings \u25B8 Public profile**, with `vibiz profile`, the `vibiz_profile` MCP tool or `PATCH /v1/profile`.\n\n## Private by default\n\nNothing is public until you say so, at every level:\n\n| Level | Default | Turn it on |\n| --- | --- | --- |\n| The profile | private: the page answers **not found**, the same as a username nobody has | `public: true` (needs a username) |\n| Each business | not listed | `listed: true` on that business |\n| Each number of a business | hidden | `show_revenue`, `show_mrr`, `show_visitors` on that business |\n| Activity | hidden | `show_activity`, and `show_activity_stats` for streaks |\n\nA number that is off is left out of the page, its JSON and the totals altogether. Totals add up only the values shared: if one business shares revenue and another doesn\'t, the total revenue is the first one\'s. Turning something off takes effect on the next page load; copies cached by browsers and caches can live up to 5 minutes.\n\n## What a page shows\n\n- **You**: display name, `@username`, bio, picture (prefilled from your sign-in picture; clear it to show your initial), an optional X handle, website and country, and a Share button that copies the link.\n- **Totals**: total revenue, MRR, visitors (30 days) and how many businesses, each only when at least one business shares it.\n- **A chart** of revenue, MRR or visitors combined, over 30 days, 12 months or all time. The choice is in the address (`?period=12m&metric=revenue`), so a link opens it.\n- **Activity** (when on): a grid of the last 52 weeks, one square per day, shaded by what you did: each production deploy counts 3, each project created 5, and calls made with your account\'s own keys (CLI, MCP, API) count by their order of magnitude (`ceil(log2(calls + 1))`), so a deploy always shows. Only daily totals: never what was called, never which business. Optional streaks: current, longest, most active day.\n- **A card per listed business**: logo (yours, else the live site\'s icon, else its initial), name, tagline, a Visit link to its site, the month it was founded (its creation day unless you set another), and its shared numbers with a small sparkline.\n\n- **A share picture**: when someone posts the link (X, LinkedIn, WhatsApp, iMessage, Slack\u2026), it shows a large card made from the public page only: your picture, name and bio, the shared totals that are above 0, the last 30 days as bars (the shared number with the most days that have something, else your activity when it is on) and up to 8 business logos. A business link gets its own card with its numbers. The picture is at `<page>/og.png` and is redrawn at most every 5 minutes; apps keep their own copy of a shared link\'s picture, and a new one is offered to them every day.\n\nThe numbers come from thelastapi: **revenue** is all-time live sales through thelastapi payments, net of refunds, in US dollars; **MRR** is the monthly value of active subscriptions sold through thelastapi payments (yearly plans count a twelfth); **visitors** are distinct visitors in the last 30 days from thelastapi analytics. Test mode never counts.\n\n## Usernames\n\n3 to 30 characters: lowercase letters, digits, `-` and `_`, starting with a letter or digit. A username is unique whatever the case (`Alice` is `alice`; `/Alice` redirects). Names the site already uses (`docs`, `blog`, `settings`, `projects`, `v1`, `mcp`\u2026) and a few others (`admin`, `api`, `pricing`, `login`, `thelastapi`\u2026) are reserved. Check one with `vibiz profile check <name>` or `GET /v1/profile/username?u=<name>`. Changing your username breaks links to the old one.\n\n## From an agent\n\n```bash\nvibiz profile # the profile and every business\'s switches\nvibiz profile set username=alice name="Alice" bio="I build small things."\nvibiz profile business sunny-shop listed=on tagline="Sunny things" revenue=on visitors=on\nvibiz profile set public=on activity=on # publish it\nvibiz profile businesses listed=on # list every business at once (numbers stay hidden)\nvibiz profile businesses shop,blog visitors=on # the same switch on a few, by slug or id\n```\n\nMany at once: `PATCH /v1/profile/businesses { "projects": ["shop", "prj_\u2026"], "listed": true, "show_visitors": true }` (leave `projects` out for every active project; only the switches you send change). SDK `vibiz.profile.businesses(\u2026)`, MCP `vibiz_profile` action `businesses`. In the console, Settings \u25B8 Public profile lists every business in one table with a search, a Listed / Not listed view, and "List all", "Show all" and "Hide all" for what is in view; showing a number on many businesses asks once more.\n\nChanging the profile takes a full-access key (or a Limited key allowed `profile:write`). Agents should never publish a profile, list a business or share a number unless the person asked: revenue is private business data.\n\nThe public data is also JSON: `GET /v1/profiles/<username>` (and `/v1/profiles/<username>/<slug>`), no key needed, with the same fields the page shows and nothing more.'
205
+ },
206
+ {
207
+ "slug": "dashboards",
208
+ "title": "Dashboards",
209
+ "description": "Your own dashboards of live numbers from every product, for one business or across all of them, built from a list of metrics, never SQL.",
210
+ "section": "Products",
211
+ "order": 88,
212
+ "topic": null,
213
+ "body": 'A dashboard is a grid of **widgets** fed by live data from everything thelastapi runs for you: payments, analytics, session replay, sign-in, AI and spend, email, hosting, phone, social and connectors. Build a churn dashboard, a traffic dashboard, an AI-cost dashboard, or a portfolio of every business side by side. Each widget is a **type** (a number, a chart, a table\u2026) plus a **metric** picked from a catalogue, plus its options. Nobody writes a query.\n\nDashboards live at two levels:\n\n| Level | Where | Reads |\n| --- | --- | --- |\n| **Project** | console \u25B8 a project \u25B8 **Dashboards**, `project_id` set | that business |\n| **Account** | console \u25B8 **Dashboards**, no `project_id` | every business, or the ones in `project_ids`; any widget can break down by business |\n\nPeople make them in the console; agents make them with `vibiz dashboards`, the `vibiz_dashboards` tool, the SDK or `POST /v1/dashboards`. Every answer has a `console_url` that opens the dashboard with its range.\n\n## Templates\n\nOne call makes a whole dashboard you can then change:\n\n| Template | Level | What is on it |\n| --- | --- | --- |\n| `churn` | project | revenue, MRR, active subscribers, churn rate, MRR and revenue over time, new and churned subscriptions, a retention grid by month, revenue per customer, refunds, latest payments |\n| `traffic` | project | visitors, pageviews, custom events, sessions with errors, visitors by day, sources, top pages, countries, devices, sessions with problems to watch |\n| `ai_cost` | project | AI spend and calls, spend on every product, AI spend by day and model, spend by model and by product |\n| `growth` | project | sign-ups, active users, users, visitors, sign-ups by day, latest sign-ups |\n| `portfolio` | account | revenue, MRR, visitors and AI spend across businesses, a row per business, revenue and visitors by business, AI spend and errors by business |\n\n```bash\nvibiz dashboards create --template churn # in the app\'s folder: this project\nvibiz dashboards create --template portfolio # the account, every business\n```\n\n## Widget types\n\nThe grid has 12 columns; each widget has a `layout` `{ x, y, w, h }` (rows of 64 px). Leave `layout` out and it goes in the first free spot. On a phone, widgets stack top to bottom.\n\n| Type | Shows | Metric shape |\n| --- | --- | --- |\n| `stat` | one number for the range, with its change against the period before (red when a rise is bad: churn, errors, spend) | scalar |\n| `line` | a number over time; with a breakdown, one line per value | timeseries |\n| `area` | the same, filled; with a breakdown, stacked | timeseries |\n| `bar` | columns over time (stacked by the breakdown), or bars for a breakdown like countries | timeseries or table |\n| `table` | a breakdown as rows (value and share) | table |\n| `list` | the latest items: payments, sign-ups, deploys, sessions with problems, each with its console link | table |\n| `funnel` | visitors who reached each step in order, and the drop between steps | funnel |\n| `cohort` | retention by month of start | cohort |\n| `text` | a heading or a note in markdown (`#`, `-`, `**bold**`) | none |\n\n## Options\n\n| Option | Meaning |\n| --- | --- |\n| `range` | `24h`, `7d`, `30d`, `90d`, `12m`: this widget\'s own range (a request\'s range wins) |\n| `bucket` | `hour`, `day`, `week`, `month` for charts; by default it fits the range |\n| `breakdown` | one of the metric\'s breakdowns (`project` at the account level, `source`, `country`, `model`\u2026) |\n| `filters` | equality filters the metric lists: `{ "country": "US" }`, `{ "source": "Google" }`, `{ "environment": "development" }` |\n| `limit` | rows of a table or list, or series of a chart (the rest are summed as Other); 1 to 50 |\n| `steps` | a funnel\'s steps in order: a page (`/pricing`) or an event name (`Signup`) |\n\n## The metric catalogue\n\n`GET /v1/dashboards/metrics` (or `vibiz dashboards metrics`) lists every metric with its levels, shapes, breakdowns, filters, unit and the permission a Limited key needs. Money is in US cents (`usd_cents`); AI and product spend in millionths of a dollar (`usd_micro`). Every metric works at both levels unless it says otherwise, and every one that can be split takes `project` as a breakdown at the account level.\n\n| Metric | What it is | Breakdowns | Unit |\n| --- | --- | --- | --- |\n| `payments.revenue` | sales net of refunds (other currencies as they settled), by the day of the sale | currency | usd_cents |\n| `payments.sales` | payments that went through | currency | count |\n| `payments.refunds` | refunded of the sales in the range | | usd_cents |\n| `payments.mrr` | monthly recurring revenue of paying subscriptions; over time, at the end of each period | | usd_cents |\n| `payments.active_subscribers` | active, trialing and past due subscriptions | | count |\n| `payments.new_subscriptions` | subscriptions started | | count |\n| `payments.churned_subscriptions` | subscriptions canceled | | count |\n| `payments.churn_rate` | canceled in the period over active at its start | | percent |\n| `payments.arpu` | revenue over the customers who paid | | usd_cents |\n| `payments.latest` | the newest payments (customers\' emails masked for a Limited key without live payment details) | | list |\n| `payments.subscription_retention` | cohorts by month of start, share still paying each month after (at least the last 6 months) | | percent |\n| `analytics.visitors` | unique visitors (a visitor counts once a day) | source, country, device, page | count |\n| `analytics.pageviews` | pages viewed | source, country, device, page | count |\n| `analytics.events` | custom and server-side events | event, page, country | count |\n| `analytics.funnel` | visitors through `steps`, same visitor, same day | | funnel |\n| `replay.sessions` | recorded sessions | device, country | count |\n| `replay.error_sessions` | sessions with a JavaScript error | device, country | count |\n| `replay.errors` | JavaScript errors | device, country | count |\n| `replay.rage_clicks` | rage clicks | device, country | count |\n| `replay.dead_clicks` | dead clicks | device, country | count |\n| `replay.problem_sessions` | the latest sessions with problems, each with a link to watch it | | list |\n| `sign_in.signups` | accounts created in the app | | count |\n| `sign_in.active_users` | users who signed in | | count |\n| `sign_in.users` | every account, now | | count |\n| `sign_in.latest_signups` | the newest accounts | | list |\n| `ai.spend` | what AI calls cost | model, kind | usd_micro |\n| `ai.calls` | AI calls | model, kind | count |\n| `usage.spend` | what every product cost | product, tool | usd_micro |\n| `email.sent` | emails the app sent | | count |\n| `email.received` | messages in the business\'s inbox | | count |\n| `email.newsletter_sends` | broadcast and automation emails sent | kind, status | count |\n| `email.opens` | newsletter emails opened by a person | kind | count |\n| `email.bounces` | newsletter emails that bounced | kind | count |\n| `email.new_contacts` | contacts added to the list | status | count |\n| `hosting.deploys` | deployments started | status, target | count |\n| `hosting.latest_deploys` | the newest deployments | | list |\n| `phone.calls` | calls made and received | direction, status | count |\n| `phone.messages` | texts sent and received | direction | count |\n| `social.posts_published` | social posts that went out | | count |\n| `connectors.calls` | calls to your own APIs through connectors | status, risk | count |\n| `portfolio.projects` | account only: one row per business with visitors, revenue, sales, MRR, AI spend, sessions with errors and deploys | | table |\n\nPayments metrics read production unless `filters.environment` is `development`.\n\n## Who can see what\n\nAny key can make and change dashboards: they are views. What a widget **reads** keeps the permission of reading it directly ([Keys](/docs/keys)):\n\n- **Sign-in** metrics read the app\'s own production database: a Limited key needs `database.production:read`. Without it, that widget alone answers `forbidden` with the permission and a `grant_url` (the page where the owner allows it); the rest of the dashboard still loads. Set the widget\'s `filters.environment` to `development` to read the development database instead.\n- **Latest payments** shows customers\' emails masked unless the key has `payments.live:read`, as the payments list does. Totals (revenue, MRR, churn) are readable by any key, as `GET /v1/projects/:id/payments/revenue` is.\n- Every dashboard and every business is the account\'s own: another account\'s dashboard or project is `404`.\n\n## Errors that say what to fix\n\nA spec with problems is refused with every problem named by its field, why, and what would work:\n\n```json\n{\n "error": {\n "code": "invalid_request",\n "message": "widgets.0.metric: \\"payments.mrrr\\" isn\'t a metric (did you mean payments.mrr?); widgets.1.type: a funnel widget can\'t show payments.revenue (it answers scalar, timeseries, table).",\n "details": {\n "field": "widgets.0.metric",\n "problems": [\n { "field": "widgets.0.metric", "message": "widgets.0.metric: \\"payments.mrrr\\" isn\'t a metric (did you mean payments.mrr?)" },\n { "field": "widgets.1.type", "message": "widgets.1.type: a funnel widget can\'t show payments.revenue (it answers scalar, timeseries, table)" }\n ],\n "next_step": "Pick one from GET /v1/dashboards/metrics (vibiz dashboards metrics)."\n }\n }\n}\n```\n\nWhen reading data, each widget fails on its own: `widgets[].error` has `code`, `message` and `details.next_step`, and the console shows it in the widget with the link to fix it.\n\n## In the console\n\n- **Dashboards** in the sidebar is the account\'s; a project\'s sidebar has its own **Dashboards**.\n- **New dashboard**: a template or blank. **Edit** shows each widget\'s controls: move (arrows), narrower and wider, shorter and taller, rename and remove; whatever a widget is moved onto slides down. **Add widget** browses the metrics by product, shows the types each fits and a live preview before adding it.\n- The range (`?range=30d`, or `?from=2026-10-01&to=2026-10-31`), the business picked on an account dashboard (`?projects=<id>`) and edit mode (`?edit=1`) are in the URL, so a link opens the same view.\n- Numbers are kept a minute; the refresh button reads them again now.\n\n## From an agent\n\n```bash\nvibiz dashboards # this project\'s dashboards (--level account: the account\'s)\nvibiz dashboards metrics --product payments # the catalogue\nvibiz dashboards create --template traffic --open\nvibiz dashboards create "Weekly numbers" --level account\nvibiz dashboards add-widget dsh_\u2026 --type table --metric analytics.visitors --breakdown country --limit 8\nvibiz dashboards add-widget dsh_\u2026 --type funnel --metric analytics.funnel --steps /,/pricing,Signup\nvibiz dashboards show dsh_\u2026 --range 7d # every widget\'s numbers, and the link\nvibiz dashboards rm-widget dsh_\u2026 w_\u2026 | rm dsh_\u2026 | open dsh_\u2026\n```\n\nMCP: `vibiz_dashboards { action: "metrics" | "list" | "create" | "get" | "data" | "update" | "delete" | "add_widget" | "update_widget" | "remove_widget" | "query", \u2026 }`. `query` reads one unsaved widget, to try a metric before adding it.\n\nSDK:\n\n```ts\nconst d = await vibiz.dashboards.create({ template: \'churn\', project_id: \'prj_\u2026\' });\nawait vibiz.dashboards.addWidget(d.id, {\n type: \'line\',\n metric: \'analytics.visitors\',\n options: { breakdown: \'source\', limit: 5 },\n});\nconst data = await vibiz.dashboards.data(d.id, { range: \'90d\' });\nfor (const w of data.widgets) console.log(w.title, w.error?.message ?? w.data);\n```\n\n## API\n\n| Route | Does |\n| --- | --- |\n| `GET /v1/dashboards/metrics` | the catalogue: metrics, widget types, ranges, buckets, templates |\n| `GET /v1/dashboards` | the dashboards; `?project_id=` one project\'s, `?level=account` the account\'s |\n| `POST /v1/dashboards` | `{ name, project_id?, project_ids?, range?, widgets?, template? }` \u2192 `201` |\n| `GET /v1/dashboards/:id` | one dashboard and its widgets |\n| `PATCH /v1/dashboards/:id` | `{ name?, description?, range?, project_ids?, widgets? }`; `widgets` replaces the list |\n| `DELETE /v1/dashboards/:id` | delete it (the data stays) |\n| `POST /v1/dashboards/:id/widgets` | add one widget |\n| `PATCH /v1/dashboards/:id/widgets/:widgetId` | change one widget |\n| `DELETE /v1/dashboards/:id/widgets/:widgetId` | remove one widget |\n| `GET /v1/dashboards/:id/data` | every widget\'s data: `?range=` or `?from=&to=`, `?project_ids=a,b`, `?widget=`, `?refresh=1` |\n| `POST /v1/dashboards/query` | one unsaved widget\'s data |\n\nA widget\'s data, by shape:\n\n```json\n{ "shape": "scalar", "unit": "usd_cents", "value": 482300, "previous": 401200, "change_pct": 20 }\n{ "shape": "timeseries", "unit": "count", "bucket": "day", "keys": ["2026-11-11", "\u2026"],\n "series": [{ "key": "Google", "label": "Google", "values": [12, 15], "total": 27 }] }\n{ "shape": "table", "unit": "count", "columns": [{ "key": "label", "label": "Source" }, { "key": "value", "label": "Visitors" }],\n "rows": [{ "key": "Google", "label": "Google", "value": 27, "share": 61.4 }] }\n{ "shape": "funnel", "unit": "count", "steps": [{ "step": "/pricing", "visitors": 120, "rate_from_start": 100, "rate_from_previous": null }] }\n{ "shape": "cohort", "unit": "percent", "periods": 6, "cohorts": [{ "key": "2026-06", "label": "Jun 2026", "size": 40, "values": [100, 92.5, 85] }] }\n```'
205
214
  },
206
215
  {
207
216
  "slug": "actions",
@@ -255,7 +264,7 @@ var PAGES = [
255
264
  "section": "Agents",
256
265
  "order": 10,
257
266
  "topic": null,
258
- "body": 'thelastapi is built to be driven by agents. When you approve an agent\'s sign-in you choose what its key may do: **Full access** (pre-selected) can do everything you can, live payments, refunds and withdrawals, secrets, domains and deleting included; **Limited** creates projects, deploys, sends email, uses AI and does everything in development, but never reads a production secret or moves live money. A Limited key that hits something only you may do gets `403 owner_only` with `details.next_step`: the link to do it yourself, and the Keys page link to give that key full access. You can change any key between Full and Limited on the Keys page.\n\nThere are four ways in, and they share one API:\n\n| | For | |\n| --- | --- | --- |\n| **Remote MCP server** (`https://thelastapi.dev/mcp`) | Claude and ChatGPT (custom connector), Claude Code, Codex, Cursor, any MCP client with OAuth | the same tools, nothing to install; sign in on first use |\n| **MCP server** (`vibiz mcp`) | Claude Code, Codex, Cursor, any MCP client | tools for every product, plus `vibiz_docs`, and local folders and files |\n| **CLI** (`vibiz`) | terminals, scripts, agents with a shell | [CLI reference](/docs/cli) |\n| **Agent skills** | Claude Code, Codex, Cursor | [installable SKILL.md bundles](/skills) that teach the workflows |\n| **HTTP** | anything | [API reference](/docs/api) |\n\n## Paste to your agent\n\nSet up once, from one line. Paste this into Claude Code, Codex or Cursor (or press **Paste to your agent** at [thelastapi.dev/get-started](https://thelastapi.dev/get-started)):\n\n```text\nSet up thelastapi for me: follow https://thelastapi.dev/get-started.md\n```\n\n[`/get-started.md`](https://thelastapi.dev/get-started.md) is a playbook for the agent: install the CLI and log in, add the skills (`vibiz skills add --global`), connect the MCP server (`vibiz mcp add --clients "<client>"`, with a manual route per client), check the connection with `vibiz_docs` and `vibiz_project_status`, and report what is set up. It pauses only for your sign-in.\n\nThen ask for what you want, in an empty folder:\n\n```text\nUse thelastapi (https://thelastapi.dev/llms.txt) to build and deploy <what you want>.\n```\n\n**Already set up somewhere else?** One prompt also works on its own: add "Log in with `npx @vibiz/cli login` and show me the link."\n\n**Logging in.** `npx @vibiz/cli login` prints a link and a code. The person opens the link, signs in with their thelastapi account and clicks **Authorize** (Full access unless they pick Limited); a thelastapi account is opened on the way if they were invited and have none. New accounts are invite-only for now: someone without an invite gets `reason: signup_closed` with `waitlist_url`, so stop and give them that link instead of retrying. The CLI then holds its own key (`cli \xB7 <computer name>`). If the shell times out first, run `vibiz login` again: it keeps waiting on the same code. Never ask the person to paste a key into the chat. A tool that answers `unauthorized` with `reason: not_logged_in` means exactly this step.\n\n## Remote MCP: nothing to install\n\n```bash\nclaude mcp add --transport http vibiz https://thelastapi.dev/mcp\n```\n\nYour client finds the sign-in on its own (OAuth 2.1 with PKCE): the first time it calls a tool, it opens the browser on the same **Authorize** page. The person picks its access there too (Full access, or Limited). The connection gets its own key with that access, named after the client ("Claude Code"), listed on the API keys page, where its access can be changed and revoking it disconnects the client. Tokens refresh on their own and keep the access.\n\n- **Any of them, from the CLI**: `vibiz mcp add --clients "Claude Code"` (or `Codex`, `Cursor`, `"VS Code with Copilot"`, `Windsurf`, `"Gemini CLI"`, `OpenCode`; several, comma-separated). It runs the client\'s own CLI where there is one and otherwise merges only the `vibiz` entry into its user config.\n- **Cursor**: `.cursor/mcp.json` \u2192 `{ "mcpServers": { "vibiz": { "url": "https://thelastapi.dev/mcp" } } }`\n- **Codex**: `codex mcp add vibiz --url https://thelastapi.dev/mcp`, then `codex mcp login vibiz`\n- **Headless** (CI): send a key instead, `--header "Authorization: Bearer $VIBIZ_API_KEY"`.\n\nThe remote server has every tool of the local one. `vibiz_deploy` takes the site\'s files themselves (`files: [{ path, content }]`); its `path` (a folder on your machine) and `vibiz_speech_transcribe` of a local file answer with the CLI command to run instead (`npx @vibiz/cli deploy --project <id>`), and `write_to` isn\'t available: use the local server or the CLI for those.\n\n## Chat apps (Claude, ChatGPT)\n\nClaude (claude.ai, desktop, mobile) and ChatGPT reach the same remote server as a custom connector, with nothing installed:\n\n```text\nhttps://thelastapi.dev/mcp\n```\n\n- **Claude**: **Settings \u25B8 Connectors \u25B8 Add custom connector**, name `Vibiz`, that URL, **Add**, then **Connect**, sign in and **Authorize**. On Free (one custom connector), Pro, Max, Team and Enterprise; on Team and Enterprise an Owner adds it.\n- **ChatGPT**: turn on **Developer mode** (Settings \u25B8 Apps \u25B8 Advanced settings), then create an app with the same URL and OAuth sign-in. Menu names vary by plan; it needs a plan that allows custom connectors.\n\nThe sign-in is the same **Authorize** page (Full access, or Limited), and the connection gets its own key on the API keys page. What works from a chat:\n\n- **Build and publish a site**: `vibiz_create_project`, then `vibiz_deploy { project_id, files }` with every file. It\'s live at `<slug>.vibiz.app`.\n- **Edit it later**: `vibiz_code` reads the live files (they are the project\'s code), then `vibiz_deploy` sends only the changed ones; `vibiz_rollback` undoes a deploy.\n- **Secrets**: `vibiz_request_secret` gives the person a console link to paste a key; it never goes through the chat.\n- Every other tool (database, sign-in, email, payments, analytics, AI, web data) works as it does anywhere.\n\nLimits: one deploy carries up to 300 files, 3 MiB per file and 4 MiB in all. A bigger app or an existing codebase belongs on your computer, with the CLI or a coding agent. Both share the account and the code: `vibiz pull` brings a site started in a chat into a folder, and a chat can edit anything deployed from a computer. Details in [Hosting](/docs/hosting#from-a-chat-nothing-installed).\n\n## Install\n\nThe CLI and the MCP server are one npm package, `@vibiz/cli` (Node 20+): `npx @vibiz/cli \u2026` runs the CLI and `npx -y @vibiz/cli mcp` the MCP server, with nothing to install first. Apps install `@vibiz/app`; scripts and servers that drive the API itself use `@vibiz/sdk`. An app that can\'t add a dependency calls the same HTTP routes with `fetch`: see [@vibiz/app](/docs/app-sdk#without-the-package).\n\nThe local MCP server reads `VIBIZ_API_KEY` and `VIBIZ_API_URL` from its environment, or the CLI\'s saved login (`vibiz login`). Leave `VIBIZ_API_URL` out for production (`https://thelastapi.dev`). Without a key it still starts, and every tool answers `unauthorized` with `details.next_step`: run `npx @vibiz/cli login` and show the person the link.\n\n## Claude Code\n\n```bash\nclaude mcp add --transport http vibiz https://thelastapi.dev/mcp # remote, sign in on first use\nclaude mcp add vibiz -- npx -y @vibiz/cli mcp # local, uses `vibiz login`\n```\n\nOr commit a project `.mcp.json` without the key (`${VIBIZ_API_KEY}` is read from your shell):\n\n```json\n{\n "mcpServers": {\n "vibiz": {\n "command": "npx",\n "args": ["-y", "@vibiz/cli", "mcp"],\n "env": { "VIBIZ_API_KEY": "${VIBIZ_API_KEY}" }\n }\n }\n}\n```\n\n## Codex\n\n```bash\ncodex mcp add vibiz --env VIBIZ_API_KEY=vz_sk_\u2026 -- npx -y @vibiz/cli mcp\n```\n\nOr in `~/.codex/config.toml`:\n\n```toml\n[mcp_servers.vibiz]\ncommand = "npx"\nargs = ["-y", "@vibiz/cli", "mcp"]\nenv = { VIBIZ_API_KEY = "vz_sk_\u2026" }\n```\n\n`codex exec` (non-interactive) refuses tools it can\'t ask you to approve; add `-c mcp_servers.vibiz.default_tools_approval_mode="approve"` to let it call them.\n\n## Cursor\n\n`.cursor/mcp.json` in the project, or `~/.cursor/mcp.json` for every project:\n\n```json\n{\n "mcpServers": {\n "vibiz": {\n "command": "npx",\n "args": ["-y", "@vibiz/cli", "mcp"],\n "env": { "VIBIZ_API_KEY": "${env:VIBIZ_API_KEY}" }\n }\n }\n}\n```\n\n## The tools\n\n| Tool | Does |\n| --- | --- |\n| `vibiz_docs` | **Read first.** The facts and code agents otherwise guess: `payments`, `app-payments`, `webhooks`, `company`, `keys`, `usage`, `connectors`, `social`, `console-urls`. Also MCP resources `vibiz://docs/<topic>` |\n| `vibiz_usage` | **Check before spending.** What was spent and today\'s limits |\n| `vibiz_billing` | the account\'s credits: balance, status, a top-up link for a person, history |\n| `vibiz_capabilities` | resource types, actions, defaults |\n| `vibiz_create_project`, `vibiz_add_resources`, `vibiz_project_status` | projects and resources; waits until ready |\n| `vibiz_project_env` | the production env\'s variable **names** (never values) |\n| `vibiz_dev_env` | the development env; `write_to` merges it into an env file without showing values |\n| `vibiz_hosts` | connected hosts; `sync: true` pushes the env again |\n| `vibiz_domains`, `vibiz_buy_domain`, `vibiz_dns_records` | the app\'s own domains (add, verify, DNS records); search, quote and buy a domain, and use a bought one (or `app.<domain>`) on any project with no DNS, or move it; a bought domain\'s DNS records (list, add, remove) |\n| `vibiz_export` | the project\'s code, database and env guide as download links |\n| `vibiz_files` | the project\'s Files: generated media and uploads, with permanent links |\n| `vibiz_deploy`, `vibiz_promote`, `vibiz_rollback` | hosting: a local folder (`path`), or the files themselves from a chat (`files`); over a live site, only the changed files. Always pass a short `message`. `vibiz_rollback` goes back to any version; the database is not rolled back, so ask first |\n| `vibiz_code` | the project\'s code, which is its live deployment\'s files: `list`, or `read` up to 20 at a time; `history` lists every version, `diff` shows what changed |\n| `vibiz_request_secret` | a console link where the person pastes a secret, so it never passes through the chat |\n| `vibiz_database` | the development database: tables, or one read-only statement |\n| `vibiz_auth_settings` | sign-in settings, development copy |\n| `vibiz_send_email`, `vibiz_run_action` | email and actions: web data (scrape, crawl, search, screenshot, places, reviews, social, products) |\n| `vibiz_inbox_threads`, `vibiz_inbox_read`, `vibiz_inbox_reply`, `vibiz_inbox_send`, `vibiz_inbox_mark`, `vibiz_inbox_setup`, `vibiz_email_forwarding` | the business\'s own inbox at its domain, and forwarding to an inbox it already uses |\n| `vibiz_email_contacts`, `vibiz_email_broadcasts`, `vibiz_email_automations`, `vibiz_email_settings` | contacts and imports, drafts, reviews, tests to the owner; sending and activating are the owner\'s unless they set a monthly allowance ([Email](/docs/email#newsletters-announcements-and-automations)) |\n| `vibiz_ads_library`, `vibiz_action_runs` | competitor ads from the Meta Ad Library; past web data runs, with their output |\n| `vibiz_seo` | SEO data: who ranks for a keyword, keyword volume and ideas, a site\'s search traffic and backlinks, a page audit, mentions in ChatGPT and Google AI answers |\n| `vibiz_web_design` | a site\'s design system (tokens, components, layout) with Tailwind, shadcn/ui and CSS exports |\n| `vibiz_payments` | payments: `get`, `products`, `create_product`, `add_price`, `checkout`, `payments`, `subscriptions`, `ledger`, `withdrawals`, `deliveries`, `connect_own_account` (a link for the owner); in development `webhook`, `simulate`, `refund`, `cancel`, `withdraw` |\n| `vibiz_social` | the business\'s social and ad accounts: connect, post, schedule, analytics, campaigns |\n| `vibiz_connectors`, `vibiz_call` | the user\'s own APIs, added from an OpenAPI spec or a manifest, called with the key kept by thelastapi |\n| `vibiz_company` | company formation: `catalog`, `draft`, `get`; in development `submit`, `simulate` |\n| `vibiz_ai_chat`, `vibiz_image_generate`, `vibiz_speech_create`, `vibiz_speech_transcribe` | AI, metered; media as links, `write_to` saves files |\n| `vibiz_ai_models`, `vibiz_ai_keys` | every model you can call, with prices; the account\'s own AI provider key status (never a secret) |\n| `vibiz_analytics`, `vibiz_replay_insights`, `vibiz_list_replays`, `vibiz_replay_detail`, `vibiz_replay_frames`, `vibiz_replay_share_link` | analytics and replay |\n| `vibiz_delete_project`, `vibiz_restore_project` | offline now, data kept 7 days |\n\nTools default to the **development** environment (`vibiz_files` reads production unless `env` says otherwise). The project id is in `./vibiz.json` in a linked app folder, or `vibiz_project_status` lists them. Set `VIBIZ_USER` in the server\'s env to attribute an agent\'s calls to an end user.\n\n## The docs tool\n\n`vibiz_docs` (and `vibiz docs <topic>` in the CLI) serves the [agent guides](/docs/guides/payments): short pages written from what real Claude Code and Codex runs got wrong (the 7-day hold, the fee example ($100 \u2192 $94.80 with the default 2% thelastapi fee), wiring webhooks, the `@vibiz/app` calls, company fees in cents). They are the same text as on this site and in `/llms-full.txt`, generated from one source.\n\n## For agents reading this site\n\n- [/llms.txt](/llms.txt): the index of every page, as markdown links.\n- [/llms-full.txt](/llms-full.txt): every page in one file.\n- Any page as markdown: add `.md` to its URL (`/docs/payments.md`).\n\n## What agents can and can\'t do\n\n| Agents may | Only a person may |\n| --- | --- |\n| create projects, deploy, promote, roll back, delete and restore | read the production env, create or revoke keys, remove domains, connect hosts |\n| everything in development, including test payments and test company filings | live refunds, cancels, withdrawals and payment settings |\n| create products, prices and checkout links, live too | submit a real company filing, sign, send an SSN or ITIN |\n| send email, run actions, use AI (metered) | verify identity and add a bank to get paid |\n| add contacts, draft broadcasts and automations, send tests to the owner | send a broadcast or turn an automation on (beyond the owner\'s monthly allowance), set the postal address |\n\nNever paste a full-access key into an agent\'s environment: an agent with a shell can read what the owner\'s machine can.'
267
+ "body": 'thelastapi is built to be driven by agents. When you approve an agent\'s sign-in you choose what its key may do: **Full access** (pre-selected) can do everything you can, live payments, refunds and withdrawals, secrets, domains and deleting included; **Limited** creates projects, deploys, sends email, uses AI and does everything in development, but never reads a production secret or moves live money. A Limited key that hits something only you may do gets `403 owner_only` with `details.next_step`: the link to do it yourself, and the Keys page link to give that key full access. You can change any key between Full and Limited on the Keys page.\n\nThere are four ways in, and they share one API:\n\n| | For | |\n| --- | --- | --- |\n| **Remote MCP server** (`https://thelastapi.dev/mcp`) | Claude and ChatGPT (custom connector), Claude Code, Codex, Cursor, any MCP client with OAuth | the same tools, nothing to install; sign in on first use |\n| **MCP server** (`vibiz mcp`) | Claude Code, Codex, Cursor, any MCP client | tools for every product, plus `vibiz_docs`, and local folders and files |\n| **CLI** (`vibiz`) | terminals, scripts, agents with a shell | [CLI reference](/docs/cli) |\n| **Agent skills** | Claude Code, Codex, Cursor | [installable SKILL.md bundles](/skills) that teach the workflows |\n| **HTTP** | anything | [API reference](/docs/api) |\n\n## Paste to your agent\n\nSet up once, from one line. Paste this into Claude Code, Codex or Cursor (or press **Paste to your agent** at [thelastapi.dev/get-started](https://thelastapi.dev/get-started)):\n\n```text\nSet up thelastapi for me: follow https://thelastapi.dev/get-started.md\n```\n\n[`/get-started.md`](https://thelastapi.dev/get-started.md) is a playbook for the agent: install the CLI and log in, add the skills (`vibiz skills add --global`), connect the MCP server (`vibiz mcp add --clients "<client>"`, with a manual route per client), check the connection with `vibiz_docs` and `vibiz_project_status`, and report what is set up. It pauses only for your sign-in.\n\nThen ask for what you want, in an empty folder:\n\n```text\nUse thelastapi (https://thelastapi.dev/llms.txt) to build and deploy <what you want>.\n```\n\n**Already set up somewhere else?** One prompt also works on its own: add "Log in with `npx @vibiz/cli login` and show me the link."\n\n**Logging in.** `npx @vibiz/cli login` prints a link and a code. The person opens the link, signs in with their thelastapi account and clicks **Authorize** (Full access unless they pick Limited); a thelastapi account is opened on the way if they have none. If their email can\'t open a new account yet, the login answers `reason: signup_closed` with `waitlist_url`, so stop and give them that link instead of retrying. The CLI then holds its own key (`cli \xB7 <computer name>`). If the shell times out first, run `vibiz login` again: it keeps waiting on the same code. Never ask the person to paste a key into the chat. A tool that answers `unauthorized` with `reason: not_logged_in` means exactly this step.\n\n## Remote MCP: nothing to install\n\n```bash\nclaude mcp add --transport http vibiz https://thelastapi.dev/mcp\n```\n\nYour client finds the sign-in on its own (OAuth 2.1 with PKCE): the first time it calls a tool, it opens the browser on the same **Authorize** page. The person picks its access there too (Full access, or Limited). The connection gets its own key with that access, named after the client ("Claude Code"), listed on the API keys page, where its access can be changed and revoking it disconnects the client. Tokens refresh on their own and keep the access.\n\n- **Any of them, from the CLI**: `vibiz mcp add --clients "Claude Code"` (or `Codex`, `Cursor`, `"VS Code with Copilot"`, `Windsurf`, `"Gemini CLI"`, `OpenCode`; several, comma-separated). It runs the client\'s own CLI where there is one and otherwise merges only the `vibiz` entry into its user config.\n- **Cursor**: `.cursor/mcp.json` \u2192 `{ "mcpServers": { "vibiz": { "url": "https://thelastapi.dev/mcp" } } }`\n- **Codex**: `codex mcp add vibiz --url https://thelastapi.dev/mcp`, then `codex mcp login vibiz`\n- **Headless** (CI): send a key instead, `--header "Authorization: Bearer $VIBIZ_API_KEY"`.\n\nThe remote server has every tool of the local one. `vibiz_deploy` takes the site\'s files themselves (`files: [{ path, content }]`); its `path` (a folder on your machine) and `vibiz_speech_transcribe` of a local file answer with the CLI command to run instead (`npx @vibiz/cli deploy --project <id>`), and `write_to` isn\'t available: use the local server or the CLI for those.\n\n## Chat apps (Claude, ChatGPT)\n\nClaude (claude.ai, desktop, mobile) and ChatGPT reach the same remote server as a custom connector, with nothing installed:\n\n```text\nhttps://thelastapi.dev/mcp\n```\n\n- **Claude**: **Settings \u25B8 Connectors \u25B8 Add custom connector**, name `Vibiz`, that URL, **Add**, then **Connect**, sign in and **Authorize**. On Free (one custom connector), Pro, Max, Team and Enterprise; on Team and Enterprise an Owner adds it.\n- **ChatGPT**: turn on **Developer mode** (Settings \u25B8 Apps \u25B8 Advanced settings), then create an app with the same URL and OAuth sign-in. Menu names vary by plan; it needs a plan that allows custom connectors.\n\nThe sign-in is the same **Authorize** page (Full access, or Limited), and the connection gets its own key on the API keys page. What works from a chat:\n\n- **Build and publish a site**: `vibiz_create_project`, then `vibiz_deploy { project_id, files }` with every file. It\'s live at `<slug>.vibiz.app`.\n- **Edit it later**: `vibiz_code` reads the live files (they are the project\'s code), then `vibiz_deploy` sends only the changed ones; `vibiz_rollback` undoes a deploy.\n- **Secrets**: `vibiz_request_secret` gives the person a console link to paste a key; it never goes through the chat.\n- Every other tool (database, sign-in, email, payments, analytics, AI, web data) works as it does anywhere.\n\nLimits: one deploy carries up to 300 files, 3 MiB per file and 4 MiB in all. A bigger app or an existing codebase belongs on your computer, with the CLI or a coding agent. Both share the account and the code: `vibiz pull` brings a site started in a chat into a folder, and a chat can edit anything deployed from a computer. Details in [Hosting](/docs/hosting#from-a-chat-nothing-installed).\n\n## Install\n\nThe CLI and the MCP server are one npm package, `@vibiz/cli` (Node 20+): `npx @vibiz/cli \u2026` runs the CLI and `npx -y @vibiz/cli mcp` the MCP server, with nothing to install first. Apps install `@vibiz/app`; scripts and servers that drive the API itself use `@vibiz/sdk`. An app that can\'t add a dependency calls the same HTTP routes with `fetch`: see [@vibiz/app](/docs/app-sdk#without-the-package).\n\nThe local MCP server reads `VIBIZ_API_KEY` and `VIBIZ_API_URL` from its environment, or the CLI\'s saved login (`vibiz login`). Leave `VIBIZ_API_URL` out for production (`https://thelastapi.dev`). Without a key it still starts, and every tool answers `unauthorized` with `details.next_step`: run `npx @vibiz/cli login` and show the person the link.\n\n## Claude Code\n\n```bash\nclaude mcp add --transport http vibiz https://thelastapi.dev/mcp # remote, sign in on first use\nclaude mcp add vibiz -- npx -y @vibiz/cli mcp # local, uses `vibiz login`\n```\n\nOr commit a project `.mcp.json` without the key (`${VIBIZ_API_KEY}` is read from your shell):\n\n```json\n{\n "mcpServers": {\n "vibiz": {\n "command": "npx",\n "args": ["-y", "@vibiz/cli", "mcp"],\n "env": { "VIBIZ_API_KEY": "${VIBIZ_API_KEY}" }\n }\n }\n}\n```\n\n## Codex\n\n```bash\ncodex mcp add vibiz --env VIBIZ_API_KEY=vz_sk_\u2026 -- npx -y @vibiz/cli mcp\n```\n\nOr in `~/.codex/config.toml`:\n\n```toml\n[mcp_servers.vibiz]\ncommand = "npx"\nargs = ["-y", "@vibiz/cli", "mcp"]\nenv = { VIBIZ_API_KEY = "vz_sk_\u2026" }\n```\n\n`codex exec` (non-interactive) refuses tools it can\'t ask you to approve; add `-c mcp_servers.vibiz.default_tools_approval_mode="approve"` to let it call them.\n\n## Cursor\n\n`.cursor/mcp.json` in the project, or `~/.cursor/mcp.json` for every project:\n\n```json\n{\n "mcpServers": {\n "vibiz": {\n "command": "npx",\n "args": ["-y", "@vibiz/cli", "mcp"],\n "env": { "VIBIZ_API_KEY": "${env:VIBIZ_API_KEY}" }\n }\n }\n}\n```\n\n## The tools\n\n| Tool | Does |\n| --- | --- |\n| `vibiz_docs` | **Read first.** The facts and code agents otherwise guess: `payments`, `app-payments`, `webhooks`, `company`, `keys`, `usage`, `connectors`, `social`, `console-urls`. Also MCP resources `vibiz://docs/<topic>` |\n| `vibiz_usage` | **Check before spending.** What was spent and today\'s limits |\n| `vibiz_billing` | the account\'s credits: balance, status, a top-up link for a person, history |\n| `vibiz_capabilities` | resource types, actions, defaults |\n| `vibiz_create_project`, `vibiz_add_resources`, `vibiz_project_status` | projects and resources; waits until ready |\n| `vibiz_project_env` | the production env\'s variable **names** (never values) |\n| `vibiz_dev_env` | the development env; `write_to` merges it into an env file without showing values |\n| `vibiz_hosts` | connected hosts; `sync: true` pushes the env again |\n| `vibiz_domains`, `vibiz_buy_domain`, `vibiz_dns_records` | the app\'s own domains (add, verify, DNS records); search, quote and buy a domain, and use a bought one (or `app.<domain>`) on any project with no DNS, or move it; a bought domain\'s DNS records (list, add, remove) |\n| `vibiz_export` | the project\'s code, database and env guide as download links |\n| `vibiz_files` | the project\'s Files: generated media and uploads, with permanent links |\n| `vibiz_deploy`, `vibiz_promote`, `vibiz_rollback` | hosting: a local folder (`path`), or the files themselves from a chat (`files`); over a live site, only the changed files. Always pass a short `message`. `vibiz_rollback` goes back to any version; the database is not rolled back, so ask first |\n| `vibiz_code` | the project\'s code, which is its live deployment\'s files: `list`, or `read` up to 20 at a time; `history` lists every version, `diff` shows what changed |\n| `vibiz_request_secret` | a console link where the person pastes a secret, so it never passes through the chat |\n| `vibiz_database` | the development database: tables, or one read-only statement |\n| `vibiz_auth_settings` | sign-in settings, development copy |\n| `vibiz_send_email`, `vibiz_run_action` | email and actions: web data (scrape, crawl, search, screenshot, places, reviews, social, products) |\n| `vibiz_inbox_threads`, `vibiz_inbox_read`, `vibiz_inbox_reply`, `vibiz_inbox_send`, `vibiz_inbox_mark`, `vibiz_inbox_setup`, `vibiz_email_forwarding` | the business\'s own inbox at its domain, and forwarding to an inbox it already uses |\n| `vibiz_email_contacts`, `vibiz_email_broadcasts`, `vibiz_email_automations`, `vibiz_email_settings` | contacts and imports, drafts, reviews, tests to the owner; sending and activating are the owner\'s unless they set a monthly allowance ([Email](/docs/email#newsletters-announcements-and-automations)) |\n| `vibiz_ads_library`, `vibiz_action_runs` | competitor ads from the Meta Ad Library; past web data runs, with their output |\n| `vibiz_seo` | SEO data: who ranks for a keyword, keyword volume and ideas, a site\'s search traffic and backlinks, a page audit, mentions in ChatGPT and Google AI answers |\n| `vibiz_web_design` | a site\'s design system (tokens, components, layout) with Tailwind, shadcn/ui and CSS exports |\n| `vibiz_payments` | payments: `get`, `products`, `create_product`, `add_price`, `checkout`, `payments`, `subscriptions`, `ledger`, `withdrawals`, `deliveries`, `connect_own_account` (a link for the owner); in development `webhook`, `simulate`, `refund`, `cancel`, `withdraw` |\n| `vibiz_social` | the business\'s social and ad accounts: connect, post, schedule, analytics, campaigns |\n| `vibiz_connectors`, `vibiz_call` | the user\'s own APIs, added from an OpenAPI spec or a manifest, called with the key kept by thelastapi |\n| `vibiz_company` | company formation: `catalog`, `draft`, `get`; in development `submit`, `simulate` |\n| `vibiz_ai_chat`, `vibiz_image_generate`, `vibiz_speech_create`, `vibiz_speech_transcribe` | AI, metered; media as links, `write_to` saves files |\n| `vibiz_ai_models`, `vibiz_ai_keys` | every model you can call, with prices; the account\'s own AI provider key status (never a secret) |\n| `vibiz_analytics`, `vibiz_replay_insights`, `vibiz_list_replays`, `vibiz_replay_detail`, `vibiz_replay_frames`, `vibiz_replay_share_link` | analytics and replay |\n| `vibiz_delete_project`, `vibiz_restore_project` | offline now, data kept 7 days |\n\nTools default to the **development** environment (`vibiz_files` reads production unless `env` says otherwise). The project id is in `./vibiz.json` in a linked app folder, or `vibiz_project_status` lists them. Set `VIBIZ_USER` in the server\'s env to attribute an agent\'s calls to an end user.\n\n## The docs tool\n\n`vibiz_docs` (and `vibiz docs <topic>` in the CLI) serves the [agent guides](/docs/guides/payments): short pages written from what real Claude Code and Codex runs got wrong (the 7-day hold, the fee example ($100 \u2192 $94.80 with the default 2% thelastapi fee), wiring webhooks, the `@vibiz/app` calls, company fees in cents). They are the same text as on this site and in `/llms-full.txt`, generated from one source.\n\n## For agents reading this site\n\n- [/llms.txt](/llms.txt): the index of every page, as markdown links.\n- [/llms-full.txt](/llms-full.txt): every page in one file.\n- Any page as markdown: add `.md` to its URL (`/docs/payments.md`).\n\n## What agents can and can\'t do\n\n| Agents may | Only a person may |\n| --- | --- |\n| create projects, deploy, promote, roll back, delete and restore | read the production env, create or revoke keys, remove domains, connect hosts |\n| everything in development, including test payments and test company filings | live refunds, cancels, withdrawals and payment settings |\n| create products, prices and checkout links, live too | submit a real company filing, sign, send an SSN or ITIN |\n| send email, run actions, use AI (metered) | verify identity and add a bank to get paid |\n| add contacts, draft broadcasts and automations, send tests to the owner | send a broadcast or turn an automation on (beyond the owner\'s monthly allowance), set the postal address |\n\nNever paste a full-access key into an agent\'s environment: an agent with a shell can read what the owner\'s machine can.'
259
268
  },
260
269
  {
261
270
  "slug": "cli",
@@ -272,7 +281,7 @@ vibiz whoami # the account and key this machine uses
272
281
  vibiz <command> --help # one command's help
273
282
  \`\`\`
274
283
 
275
- \`vibiz login\` opens the link in your browser (\`--no-browser\` only prints it) and waits up to 10 minutes. You sign in with your thelastapi account, check the code and the machine, and click **Authorize**; if you were invited and don't have a thelastapi account yet, it is opened on the way (new accounts are invite-only for now: without an invite, the page and the CLI point you to the [waitlist](https://thelastapi.dev/waitlist)). The CLI then gets its own **Limited key**, named \`cli \xB7 <your computer's name>\`, which you can revoke on the API keys page. An agent can run it for you: it shows you the link, and running \`vibiz login\` again keeps waiting on the same code. Already have a key? \`vibiz login --key vz_sk_\u2026\`. \`vibiz logout\` forgets the key (and revokes it, if \`vibiz login\` made it).
284
+ \`vibiz login\` opens the link in your browser (\`--no-browser\` only prints it) and waits up to 10 minutes. You sign in with your thelastapi account, check the code and the machine, and click **Authorize**; if you don't have a thelastapi account yet, it is opened on the way (if this email can't open one yet, the page and the CLI say so and point you to [thelastapi.dev/start](https://thelastapi.dev/start)). The CLI then gets its own **Limited key**, named \`cli \xB7 <your computer's name>\`, which you can revoke on the API keys page. An agent can run it for you: it shows you the link, and running \`vibiz login\` again keeps waiting on the same code. Already have a key? \`vibiz login --key vz_sk_\u2026\`. \`vibiz logout\` forgets the key (and revokes it, if \`vibiz login\` made it).
276
285
 
277
286
  - \`VIBIZ_API_KEY\` and \`VIBIZ_API_URL\` override the saved login (\`~/.vibiz/config.json\`).
278
287
  - A linked folder has \`./vibiz.json\` with the project id; commands that act on a project read it.
@@ -290,8 +299,8 @@ vibiz \u2014 website, database and sign-in for a new business, in one command
290
299
  Authorize (Full access by default, or Limited),
291
300
  and the new key is saved here
292
301
  [--key <vz_sk_\u2026>] [--api <url>] [--no-browser] or save a key you already have
293
- vibiz signup the same as login: invited, with no account yet? one
294
- is opened for you on the way
302
+ vibiz signup the same as login: no account yet? one is opened
303
+ for you on the way
295
304
  vibiz whoami the account and key this machine uses
296
305
  vibiz logout forget this machine's key (a browser login's key is
297
306
  revoked too)
@@ -522,6 +531,20 @@ vibiz \u2014 website, database and sign-in for a new business, in one command
522
531
  to fix, and the console page
523
532
  vibiz health run [<project>] check again now (every business, or one); checks
524
533
  also run every hour on their own
534
+ vibiz dashboards [--level account] [--json] this project's dashboards (or the account's, across
535
+ businesses), each with its console link
536
+ vibiz dashboards metrics [--product payments] the metric catalogue: what each widget can show,
537
+ its breakdowns, filters and the permission it needs
538
+ vibiz dashboards create --template churn|traffic|ai_cost|growth|portfolio [--name n] [--open]
539
+ a whole dashboard in one call (portfolio: the account)
540
+ vibiz dashboards create "<name>" [--level account] an empty one to add widgets to
541
+ vibiz dashboards show <id> [--range 7d|30d|90d|12m] [--from YYYY-MM-DD --to \u2026] [--json]
542
+ every widget's numbers, and the link with the range
543
+ vibiz dashboards add-widget <id> --type stat|line|area|bar|table|list|funnel|cohort|text
544
+ --metric <id> [--breakdown source] [--filter key=value]\u2026 [--limit n] [--bucket week]
545
+ [--steps /,/pricing,Signup] [--title t] [--text "## Note"]
546
+ add one, placed in the first free spot
547
+ vibiz dashboards rm-widget <id> <widget> | rm <id> | open <id>
525
548
  vibiz search [--json] where this project's pages go to search engines:
526
549
  new and changed pages go to IndexNow after every
527
550
  production deploy (own domain only)
@@ -749,7 +772,7 @@ vibiz \u2014 website, database and sign-in for a new business, in one command
749
772
  "section": "Agents",
750
773
  "order": 30,
751
774
  "topic": null,
752
- "body": "Agent skills are folders with a `SKILL.md` (a name, a description that says when to use it, and instructions) plus reference pages. Claude Code, Codex and Cursor load a skill when a task matches its description, so the agent gets the right workflow (and the facts it would otherwise guess) only when it needs it. The [skills page](/skills) has the same list with copy buttons.\n\nThe quickest way in is the CLI: `vibiz skills add --global` installs every skill for the agent it runs in (`--agent claude|codex|cursor` to choose, a skill name to take only that one, no `--global` for this project only), and `vibiz skills list` shows which are installed.\n\nEach skill is served as a `.tar.gz` that unpacks to `<name>/SKILL.md` and `<name>/references/`; the files are also served one by one under `/skills/<name>/`. The references are the pages of this site, generated from the same source, so a skill never says something these docs don't.\n\n### vibiz\n\nStart here for thelastapi - what it can do (hosting, Postgres, sign-in, email and a business inbox, newsletters, AI models, files, payments, analytics with session replay, web data and design, social, connectors, company formation, domains), which skill covers each, how to log in or connect the MCP server, the one-key model (VIBIZ_APP_KEY), credits and spend limits, and the rules every thelastapi task follows (console links, owner-only steps). Use when starting with thelastapi, when someone asks what thelastapi can do or which service fits, or when no other vibiz-* skill matches.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz/SKILL.md), [references/introduction.md](/skills/vibiz/references/introduction.md), [references/agents.md](/skills/vibiz/references/agents.md), [references/billing.md](/skills/vibiz/references/billing.md), [references/usage.md](/skills/vibiz/references/usage.md), [references/keys.md](/skills/vibiz/references/keys.md), [references/console-urls.md](/skills/vibiz/references/console-urls.md), [references/mission-control.md](/skills/vibiz/references/mission-control.md), [references/profiles.md](/skills/vibiz/references/profiles.md).\n\n### vibiz-ai\n\nUse AI models through thelastapi - chat with GPT, Claude, Gemini, Kimi, DeepSeek and every major lab's models by id, generate images (Nano Banana, GPT Image) or edit a photo (image_url), make videos (or animate a photo), run any image or video model by its id on credit (Kling, Seedance, Veo, face swap, lip sync, upscalers), text to speech and transcription, from an agent (MCP tools, CLI) or from an app with one key (OpenAI-compatible, new OpenAI(vibiz.ai)) - with per-call prices, the daily spend ceiling, project budgets and the account's own Google or fal key. Use when an app needs an LLM, images, video or voice, when you need to generate or edit an image, a video or audio for a project, when someone asks for a specific image/video model, or someone asks what a model costs or which models they can call.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-ai.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-ai.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-ai.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-ai/SKILL.md), [references/ai.md](/skills/vibiz-ai/references/ai.md), [references/usage.md](/skills/vibiz-ai/references/usage.md).\n\n### vibiz-analytics\n\nSet up and read a thelastapi project's visitor analytics (cookieless pageviews, sources, countries, devices, custom and server-side events) together with session replay (masked recordings of what went wrong for visitors - JS errors, rage and dead clicks, abandoned forms - with insights and private links to watch a session), on thelastapi hosting or any other site. Use when someone wants analytics, to track visits or events, asks how their site is doing, where visitors come from, or what is going wrong for users - and always set up replays along with analytics.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-analytics.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-analytics.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-analytics.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-analytics/SKILL.md), [references/analytics.md](/skills/vibiz-analytics/references/analytics.md), [references/console-urls.md](/skills/vibiz-analytics/references/console-urls.md), [references/mission-control.md](/skills/vibiz-analytics/references/mission-control.md).\n\n### vibiz-auth\n\nSet up and change sign-in for a thelastapi project - email and password, verification, magic links, Google, GitHub or Vercel sign-in, allowed email domains, and the callback URLs to register. Use when a thelastapi project's users need to sign in or its sign-in settings need changing.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-auth.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-auth.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-auth.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-auth/SKILL.md), [references/sign-in.md](/skills/vibiz-auth/references/sign-in.md), [references/keys.md](/skills/vibiz-auth/references/keys.md).\n\n### vibiz-broadcasts\n\nEmail a thelastapi project's users and subscribers - contacts from the app at signup, safe CSV imports, newsletters and announcements (broadcasts) with a review step, and automations such as onboarding sequences and trial reminders - with one-click unsubscribe, sending pace and spam protection built in. Use when a business wants to email its users about its software, send a newsletter or product update, or set up an onboarding or re-engagement sequence.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-broadcasts.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-broadcasts.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-broadcasts.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-broadcasts/SKILL.md), [references/email.md](/skills/vibiz-broadcasts/references/email.md).\n\n### vibiz-company\n\nForm the US company behind a thelastapi project (LLC or C-Corp, any state) - read the fee catalog in cents, quote the total, draft the filing and fix its problems, and hand the real submission to the owner. Use when someone asks what forming an LLC or corporation costs through thelastapi, or wants to incorporate the business behind their app.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-company.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-company.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-company.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-company/SKILL.md), [references/company.md](/skills/vibiz-company/references/company.md), [references/guide-company.md](/skills/vibiz-company/references/guide-company.md).\n\n### vibiz-connectors\n\nConnect a thelastapi project to any outside HTTP API (a CRM, a weather or shipping API, an internal service) as a custom connector - import its OpenAPI spec or write a short manifest, set its key per environment, and call it through thelastapi with approvals for risky operations. Use when a thelastapi app or agent needs a third-party API that thelastapi doesn't provide itself.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-connectors.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-connectors.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-connectors.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-connectors/SKILL.md), [references/connectors.md](/skills/vibiz-connectors/references/connectors.md), [references/guide-connectors.md](/skills/vibiz-connectors/references/guide-connectors.md).\n\n### vibiz-database\n\nWork with a thelastapi project's Postgres database - get the development DATABASE_URL, run migrations, inspect tables and run read-only queries, without ever touching production rows. Use when a thelastapi project needs schema changes, queries, seed data or a look at its data.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-database.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-database.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-database.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-database/SKILL.md), [references/database.md](/skills/vibiz-database/references/database.md), [references/keys.md](/skills/vibiz-database/references/keys.md).\n\n### vibiz-deploy\n\nCreate a thelastapi project and deploy it - vibiz init, the development env for local work, deploy to <slug>.vibiz.app (a folder, or the files themselves from a chat), edit a live site by reading its code and deploying only the changed files, previews, promote and instant rollback, run the app on another host with one key, or export it (code, database, env guide) to take it elsewhere. Use when an app should go live on thelastapi or a thelastapi project needs a new deployment or a rollback.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-deploy.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-deploy.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-deploy.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-deploy/SKILL.md), [references/hosting.md](/skills/vibiz-deploy/references/hosting.md), [references/domains.md](/skills/vibiz-deploy/references/domains.md), [references/quickstart.md](/skills/vibiz-deploy/references/quickstart.md), [references/keys.md](/skills/vibiz-deploy/references/keys.md), [references/mission-control.md](/skills/vibiz-deploy/references/mission-control.md).\n\n### vibiz-design\n\nMake the UI you build look good from the first screen - learn a website's design system with thelastapi Stack (web.design - colors, type scale, radii, spacing, component styles, section layout, screenshots) and apply its Tailwind v4, shadcn/ui or CSS theme and brief, capture a page section by section (real HTML + CSS and a picture of each) and rebuild from it, or find similar companies to use as inspiration when there is no reference; or, with no reference, follow a short default design checklist. Use when building or redesigning a page, an app's UI, a landing page or a dashboard, when the person names a site they like (\"make it look like Linear\"), or when they have an existing site or brand the new app should match.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-design.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-design.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-design.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-design/SKILL.md), [references/design.md](/skills/vibiz-design/references/design.md), [references/actions.md](/skills/vibiz-design/references/actions.md).\n\n### vibiz-email\n\nWrite emails that look good (a tested HTML template), give a personal agent one email address (name@agent.vibiz.app), or send email from a thelastapi project's own address (<mailbox>@<slug>.vibiz.app) - add the email resource, send from the app with @vibiz/app or HTTP, and stay within 50 emails per project per day - run the business's own inbox (hello@theirdomain.com kept in thelastapi; read, reply and send as it, with received mail treated as untrusted) - or forward that address to the owner's own inbox. Use when a thelastapi project needs to send welcome, receipt or notification emails, or the business wants email at its own domain, or asks to check or answer its mail.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-email.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-email.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-email.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-email/SKILL.md), [references/email.md](/skills/vibiz-email/references/email.md).\n\n### vibiz-files\n\nStore and find files in a thelastapi project's Files (a drive per project with permanent links) - find an image, video or audio you or the app generated earlier, upload a logo or product photo and get its link, import a file from a URL, private files with signed links, and file uploads from the app with one key. Use when you need a file's permanent URL, want to reuse something generated before, or an app needs to store user uploads, avatars or downloads.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-files.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-files.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-files.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-files/SKILL.md), [references/files.md](/skills/vibiz-files/references/files.md), [references/app-sdk.md](/skills/vibiz-files/references/app-sdk.md).\n\n### vibiz-payments\n\nSell with thelastapi payments - take money with no identity check and no Stripe account (thelastapi is the merchant; KYC only when the owner withdraws) or through the owner's own Stripe account, sell in iOS and Android apps (App Store and Google Play in-app purchases through the owner's own RevenueCat account, no thelastapi fee), create a plan, add a checkout or Upgrade button, wire and verify payment webhooks, check subscriptions, and answer questions about fees (2% thelastapi fee plus card processing), the 7-day hold, refunds and withdrawing. Use when a thelastapi project (a vibiz.json in the folder, or the vibiz MCP tools) needs to take money or someone asks what a payment leaves them.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-payments.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-payments.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-payments.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-payments/SKILL.md), [references/payments.md](/skills/vibiz-payments/references/payments.md), [references/guide-payments.md](/skills/vibiz-payments/references/guide-payments.md), [references/guide-app-payments.md](/skills/vibiz-payments/references/guide-app-payments.md), [references/guide-webhooks.md](/skills/vibiz-payments/references/guide-webhooks.md), [references/app-store.md](/skills/vibiz-payments/references/app-store.md), [references/guide-app-store.md](/skills/vibiz-payments/references/guide-app-store.md), [references/errors.md](/skills/vibiz-payments/references/errors.md).\n\n### vibiz-phone\n\nGive a personal agent or a thelastapi project a US phone number - search and buy one from credits, receive texts at once, send texts once carriers approve the number, place calls that speak a message and hang up, for instance to phone someone when work is done, or have a voice agent hold a two-way call or answer incoming calls and leave a transcript and summary - with STOP honoured and inbound text and transcripts treated as untrusted. Use when an agent or app should have a phone number, text someone, call someone, make a booking or ask something by phone, or answer calls.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-phone.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-phone.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-phone.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-phone/SKILL.md), [references/phone.md](/skills/vibiz-phone/references/phone.md), [references/app-sdk.md](/skills/vibiz-phone/references/app-sdk.md).\n\n### vibiz-social\n\nPost and schedule to a thelastapi project's own social accounts (Instagram, TikTok, LinkedIn, X, YouTube, Pinterest, Threads, Facebook, Bluesky\u2026), read post analytics, pause, resume, re-budget or boost ad campaigns, and create Google Ads Search, Display and Performance Max campaigns, with the owner approving anything live. Use when someone wants to publish, schedule, connect a social or ad account, run Google Ads, or check how posts and campaigns perform for the business behind their app.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-social.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-social.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-social.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-social/SKILL.md), [references/social.md](/skills/vibiz-social/references/social.md), [references/guide-social.md](/skills/vibiz-social/references/guide-social.md).\n\n### vibiz-use-one\n\nUse just one thelastapi service (sign-in, database, payments, email, AI, analytics, replay, files, web data, connectors, social, company) from an app NOT hosted on thelastapi - another host, a plain HTML site, a mobile app's backend, a cron job or a script - creating a project with only that resource, adding the app's domain as running elsewhere, and giving the app its one key. Use when someone wants one thelastapi feature without deploying on thelastapi, or the app already runs somewhere else.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-use-one.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-use-one.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-use-one.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-use-one/SKILL.md), [references/use-one.md](/skills/vibiz-use-one/references/use-one.md), [references/keys.md](/skills/vibiz-use-one/references/keys.md), [references/app-sdk.md](/skills/vibiz-use-one/references/app-sdk.md).\n\n### vibiz-web-data\n\nGet data from the web with thelastapi - scrape a page or crawl a whole site to markdown, search the web or the news, screenshot a page, SEO data (who ranks on Google for a keyword, keyword search volume and CPC, keyword ideas, a site's organic traffic and competitors, backlinks, an on-page SEO audit, how often ChatGPT and Google AI Overviews mention a brand), pull competitor ads from the Facebook / Meta Ad Library, find businesses on Google Maps, read Google or Trustpilot reviews, Instagram and TikTok profiles and hashtag posts, product prices from any shop, and public LinkedIn company pages. Use when someone wants to scrape, crawl, search the web, do SEO or keyword research, check rankings or backlinks, audit a page, track AI search visibility, research competitors or their ads, find leads or places, collect reviews, check product prices, or look at an Instagram/TikTok profile, and the vibiz CLI or MCP tools are available.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-web-data.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-web-data.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-web-data.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-web-data/SKILL.md), [references/actions.md](/skills/vibiz-web-data/references/actions.md), [references/errors.md](/skills/vibiz-web-data/references/errors.md).\n\n## Where each agent looks\n\n| Agent | Personal (every project) | One project |\n| --- | --- | --- |\n| Claude Code | `~/.claude/skills/<name>/SKILL.md` | `.claude/skills/<name>/SKILL.md` |\n| Codex | `~/.agents/skills/<name>/SKILL.md` | `.agents/skills/<name>/SKILL.md` (from the folder you start in up to the repository root) |\n| Cursor | `~/.cursor/skills/<name>/SKILL.md` | `.cursor/skills/<name>/SKILL.md` (it also reads `.agents/skills` and `.claude/skills`) |\n\nClaude Code and Codex pick up a new skill without a restart; if one doesn't show up, restart the session. Skills work best with the [MCP server](/docs/agents) connected, since most steps call its tools."
775
+ "body": "Agent skills are folders with a `SKILL.md` (a name, a description that says when to use it, and instructions) plus reference pages. Claude Code, Codex and Cursor load a skill when a task matches its description, so the agent gets the right workflow (and the facts it would otherwise guess) only when it needs it. The [skills page](/skills) has the same list with copy buttons.\n\nThe quickest way in is the CLI: `vibiz skills add --global` installs every skill for the agent it runs in (`--agent claude|codex|cursor` to choose, a skill name to take only that one, no `--global` for this project only), and `vibiz skills list` shows which are installed.\n\nEach skill is served as a `.tar.gz` that unpacks to `<name>/SKILL.md` and `<name>/references/`; the files are also served one by one under `/skills/<name>/`. The references are the pages of this site, generated from the same source, so a skill never says something these docs don't.\n\n### vibiz\n\nStart here for thelastapi - what it can do (hosting, Postgres, sign-in, email and a business inbox, newsletters, AI models, files, payments, analytics with session replay, web data and design, social, connectors, company formation, domains), which skill covers each, how to log in or connect the MCP server, the one-key model (VIBIZ_APP_KEY), credits and spend limits, and the rules every thelastapi task follows (console links, owner-only steps). Use when starting with thelastapi, when someone asks what thelastapi can do or which service fits, or when no other vibiz-* skill matches.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz/SKILL.md), [references/introduction.md](/skills/vibiz/references/introduction.md), [references/agents.md](/skills/vibiz/references/agents.md), [references/billing.md](/skills/vibiz/references/billing.md), [references/usage.md](/skills/vibiz/references/usage.md), [references/keys.md](/skills/vibiz/references/keys.md), [references/console-urls.md](/skills/vibiz/references/console-urls.md), [references/mission-control.md](/skills/vibiz/references/mission-control.md), [references/dashboards.md](/skills/vibiz/references/dashboards.md), [references/profiles.md](/skills/vibiz/references/profiles.md).\n\n### vibiz-ai\n\nUse AI models through thelastapi - chat with GPT, Claude, Gemini, Kimi, DeepSeek and every major lab's models by id, generate images (Nano Banana, GPT Image) or edit a photo (image_url), make videos (or animate a photo), run any image or video model by its id on credit (Kling, Seedance, Veo, face swap, lip sync, upscalers), text to speech and transcription, from an agent (MCP tools, CLI) or from an app with one key (OpenAI-compatible, new OpenAI(vibiz.ai)) - with per-call prices, the daily spend ceiling, project budgets and the account's own Google or fal key. Use when an app needs an LLM, images, video or voice, when you need to generate or edit an image, a video or audio for a project, when someone asks for a specific image/video model, or someone asks what a model costs or which models they can call.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-ai.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-ai.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-ai.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-ai/SKILL.md), [references/ai.md](/skills/vibiz-ai/references/ai.md), [references/usage.md](/skills/vibiz-ai/references/usage.md).\n\n### vibiz-analytics\n\nSet up and read a thelastapi project's visitor analytics (cookieless pageviews, sources, countries, devices, custom and server-side events) together with session replay (masked recordings of what went wrong for visitors - JS errors, rage and dead clicks, abandoned forms - with insights and private links to watch a session), on thelastapi hosting or any other site. Use when someone wants analytics, to track visits or events, asks how their site is doing, where visitors come from, or what is going wrong for users - and always set up replays along with analytics.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-analytics.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-analytics.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-analytics.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-analytics/SKILL.md), [references/analytics.md](/skills/vibiz-analytics/references/analytics.md), [references/console-urls.md](/skills/vibiz-analytics/references/console-urls.md), [references/mission-control.md](/skills/vibiz-analytics/references/mission-control.md), [references/dashboards.md](/skills/vibiz-analytics/references/dashboards.md).\n\n### vibiz-auth\n\nSet up and change sign-in for a thelastapi project - email and password, verification, magic links, Google, GitHub or Vercel sign-in, allowed email domains, and the callback URLs to register. Use when a thelastapi project's users need to sign in or its sign-in settings need changing.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-auth.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-auth.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-auth.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-auth/SKILL.md), [references/sign-in.md](/skills/vibiz-auth/references/sign-in.md), [references/keys.md](/skills/vibiz-auth/references/keys.md).\n\n### vibiz-broadcasts\n\nEmail a thelastapi project's users and subscribers - contacts from the app at signup, safe CSV imports, newsletters and announcements (broadcasts) with a review step, and automations such as onboarding sequences and trial reminders - with one-click unsubscribe, sending pace and spam protection built in. Use when a business wants to email its users about its software, send a newsletter or product update, or set up an onboarding or re-engagement sequence.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-broadcasts.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-broadcasts.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-broadcasts.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-broadcasts/SKILL.md), [references/email.md](/skills/vibiz-broadcasts/references/email.md).\n\n### vibiz-company\n\nForm the US company behind a thelastapi project (LLC or C-Corp, any state) - read the fee catalog in cents, quote the total, draft the filing and fix its problems, and hand the real submission to the owner. Use when someone asks what forming an LLC or corporation costs through thelastapi, or wants to incorporate the business behind their app.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-company.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-company.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-company.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-company/SKILL.md), [references/company.md](/skills/vibiz-company/references/company.md), [references/guide-company.md](/skills/vibiz-company/references/guide-company.md).\n\n### vibiz-connectors\n\nConnect a thelastapi project to any outside HTTP API (a CRM, a weather or shipping API, an internal service) as a custom connector - import its OpenAPI spec or write a short manifest, set its key per environment, and call it through thelastapi with approvals for risky operations. Use when a thelastapi app or agent needs a third-party API that thelastapi doesn't provide itself.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-connectors.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-connectors.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-connectors.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-connectors/SKILL.md), [references/connectors.md](/skills/vibiz-connectors/references/connectors.md), [references/guide-connectors.md](/skills/vibiz-connectors/references/guide-connectors.md).\n\n### vibiz-database\n\nWork with a thelastapi project's Postgres database - get the development DATABASE_URL, run migrations, inspect tables and run read-only queries, without ever touching production rows. Use when a thelastapi project needs schema changes, queries, seed data or a look at its data.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-database.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-database.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-database.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-database/SKILL.md), [references/database.md](/skills/vibiz-database/references/database.md), [references/keys.md](/skills/vibiz-database/references/keys.md).\n\n### vibiz-deploy\n\nCreate a thelastapi project and deploy it - vibiz init, the development env for local work, deploy to <slug>.vibiz.app (a folder, or the files themselves from a chat), edit a live site by reading its code and deploying only the changed files, previews, promote and instant rollback, run the app on another host with one key, or export it (code, database, env guide) to take it elsewhere. Use when an app should go live on thelastapi or a thelastapi project needs a new deployment or a rollback.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-deploy.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-deploy.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-deploy.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-deploy/SKILL.md), [references/hosting.md](/skills/vibiz-deploy/references/hosting.md), [references/domains.md](/skills/vibiz-deploy/references/domains.md), [references/quickstart.md](/skills/vibiz-deploy/references/quickstart.md), [references/keys.md](/skills/vibiz-deploy/references/keys.md), [references/mission-control.md](/skills/vibiz-deploy/references/mission-control.md).\n\n### vibiz-design\n\nMake the UI you build look good from the first screen - learn a website's design system with thelastapi Stack (web.design - colors, type scale, radii, spacing, component styles, section layout, screenshots) and apply its Tailwind v4, shadcn/ui or CSS theme and brief, capture a page section by section (real HTML + CSS and a picture of each) and rebuild from it, or find similar companies to use as inspiration when there is no reference; or, with no reference, follow a short default design checklist. Use when building or redesigning a page, an app's UI, a landing page or a dashboard, when the person names a site they like (\"make it look like Linear\"), or when they have an existing site or brand the new app should match.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-design.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-design.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-design.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-design/SKILL.md), [references/design.md](/skills/vibiz-design/references/design.md), [references/actions.md](/skills/vibiz-design/references/actions.md).\n\n### vibiz-email\n\nWrite emails that look good (a tested HTML template), give a personal agent one email address (name@agent.vibiz.app), or send email from a thelastapi project's own address (<mailbox>@<slug>.vibiz.app) - add the email resource, send from the app with @vibiz/app or HTTP, and stay within 50 emails per project per day - run the business's own inbox (hello@theirdomain.com kept in thelastapi; read, reply and send as it, with received mail treated as untrusted) - or forward that address to the owner's own inbox. Use when a thelastapi project needs to send welcome, receipt or notification emails, or the business wants email at its own domain, or asks to check or answer its mail.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-email.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-email.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-email.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-email/SKILL.md), [references/email.md](/skills/vibiz-email/references/email.md).\n\n### vibiz-files\n\nStore and find files in a thelastapi project's Files (a drive per project with permanent links) - find an image, video or audio you or the app generated earlier, upload a logo or product photo and get its link, import a file from a URL, private files with signed links, and file uploads from the app with one key. Use when you need a file's permanent URL, want to reuse something generated before, or an app needs to store user uploads, avatars or downloads.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-files.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-files.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-files.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-files/SKILL.md), [references/files.md](/skills/vibiz-files/references/files.md), [references/app-sdk.md](/skills/vibiz-files/references/app-sdk.md).\n\n### vibiz-payments\n\nSell with thelastapi payments - take money with no identity check and no Stripe account (thelastapi is the merchant; KYC only when the owner withdraws) or through the owner's own Stripe account, sell in iOS and Android apps (App Store and Google Play in-app purchases through the owner's own RevenueCat account, no thelastapi fee), create a plan, add a checkout or Upgrade button, wire and verify payment webhooks, check subscriptions, and answer questions about fees (2% thelastapi fee plus card processing), the 7-day hold, refunds and withdrawing. Use when a thelastapi project (a vibiz.json in the folder, or the vibiz MCP tools) needs to take money or someone asks what a payment leaves them.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-payments.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-payments.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-payments.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-payments/SKILL.md), [references/payments.md](/skills/vibiz-payments/references/payments.md), [references/guide-payments.md](/skills/vibiz-payments/references/guide-payments.md), [references/guide-app-payments.md](/skills/vibiz-payments/references/guide-app-payments.md), [references/guide-webhooks.md](/skills/vibiz-payments/references/guide-webhooks.md), [references/app-store.md](/skills/vibiz-payments/references/app-store.md), [references/guide-app-store.md](/skills/vibiz-payments/references/guide-app-store.md), [references/errors.md](/skills/vibiz-payments/references/errors.md), [references/dashboards.md](/skills/vibiz-payments/references/dashboards.md).\n\n### vibiz-phone\n\nGive a personal agent or a thelastapi project a US phone number - search and buy one from credits, receive texts at once, send texts once carriers approve the number, place calls that speak a message and hang up, for instance to phone someone when work is done, or have a voice agent hold a two-way call or answer incoming calls and leave a transcript and summary - with STOP honoured and inbound text and transcripts treated as untrusted. Use when an agent or app should have a phone number, text someone, call someone, make a booking or ask something by phone, or answer calls.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-phone.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-phone.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-phone.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-phone/SKILL.md), [references/phone.md](/skills/vibiz-phone/references/phone.md), [references/app-sdk.md](/skills/vibiz-phone/references/app-sdk.md).\n\n### vibiz-social\n\nPost and schedule to a thelastapi project's own social accounts (Instagram, TikTok, LinkedIn, X, YouTube, Pinterest, Threads, Facebook, Bluesky\u2026), read post analytics, pause, resume, re-budget or boost ad campaigns, and create Google Ads Search, Display and Performance Max campaigns, with the owner approving anything live. Use when someone wants to publish, schedule, connect a social or ad account, run Google Ads, or check how posts and campaigns perform for the business behind their app.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-social.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-social.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-social.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-social/SKILL.md), [references/social.md](/skills/vibiz-social/references/social.md), [references/guide-social.md](/skills/vibiz-social/references/guide-social.md).\n\n### vibiz-use-one\n\nUse just one thelastapi service (sign-in, database, payments, email, AI, analytics, replay, files, web data, connectors, social, company) from an app NOT hosted on thelastapi - another host, a plain HTML site, a mobile app's backend, a cron job or a script - creating a project with only that resource, adding the app's domain as running elsewhere, and giving the app its one key. Use when someone wants one thelastapi feature without deploying on thelastapi, or the app already runs somewhere else.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-use-one.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-use-one.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-use-one.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-use-one/SKILL.md), [references/use-one.md](/skills/vibiz-use-one/references/use-one.md), [references/keys.md](/skills/vibiz-use-one/references/keys.md), [references/app-sdk.md](/skills/vibiz-use-one/references/app-sdk.md).\n\n### vibiz-web-data\n\nGet data from the web with thelastapi - scrape a page or crawl a whole site to markdown, search the web or the news, screenshot a page, SEO data (who ranks on Google for a keyword, keyword search volume and CPC, keyword ideas, a site's organic traffic and competitors, backlinks, an on-page SEO audit, how often ChatGPT and Google AI Overviews mention a brand), pull competitor ads from the Facebook / Meta Ad Library, find businesses on Google Maps, read Google or Trustpilot reviews, Instagram and TikTok profiles and hashtag posts, product prices from any shop, and public LinkedIn company pages. Use when someone wants to scrape, crawl, search the web, do SEO or keyword research, check rankings or backlinks, audit a page, track AI search visibility, research competitors or their ads, find leads or places, collect reviews, check product prices, or look at an Instagram/TikTok profile, and the vibiz CLI or MCP tools are available.\n\nClaude Code:\n\n```bash\nmkdir -p ~/.claude/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-web-data.tar.gz | tar -xz -C ~/.claude/skills\n```\n\nCodex:\n\n```bash\nmkdir -p ~/.agents/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-web-data.tar.gz | tar -xz -C ~/.agents/skills\n```\n\nCursor:\n\n```bash\nmkdir -p .cursor/skills && curl -fsSL https://thelastapi.dev/skills/vibiz-web-data.tar.gz | tar -xz -C .cursor/skills\n```\n\nFiles: [SKILL.md](/skills/vibiz-web-data/SKILL.md), [references/actions.md](/skills/vibiz-web-data/references/actions.md), [references/errors.md](/skills/vibiz-web-data/references/errors.md).\n\n## Where each agent looks\n\n| Agent | Personal (every project) | One project |\n| --- | --- | --- |\n| Claude Code | `~/.claude/skills/<name>/SKILL.md` | `.claude/skills/<name>/SKILL.md` |\n| Codex | `~/.agents/skills/<name>/SKILL.md` | `.agents/skills/<name>/SKILL.md` (from the folder you start in up to the repository root) |\n| Cursor | `~/.cursor/skills/<name>/SKILL.md` | `.cursor/skills/<name>/SKILL.md` (it also reads `.agents/skills` and `.claude/skills`) |\n\nClaude Code and Codex pick up a new skill without a restart; if one doesn't show up, restart the session. Skills work best with the [MCP server](/docs/agents) connected, since most steps call its tools."
753
776
  },
754
777
  {
755
778
  "slug": "console-urls",
@@ -767,7 +790,7 @@ vibiz \u2014 website, database and sign-in for a new business, in one command
767
790
  "section": "Reference",
768
791
  "order": 10,
769
792
  "topic": null,
770
- "body": "Base URL: `https://thelastapi.dev/v1`. Authenticate with `Authorization: Bearer <key>`. Request and response bodies are JSON unless a route says otherwise; every response has an `X-Request-Id`.\n\n```bash\ncurl https://thelastapi.dev/v1/projects -H \"Authorization: Bearer $VIBIZ_API_KEY\"\n```\n\n- **Keys**: an account key (`vz_sk_\u2026`, agent or owner access), the app key (`vz_app_\u2026`) on `/v1/app/*` and `/v1/ai/*`, or a project AI key (`vz_ai_\u2026`) on `/v1/ai/*`. See [Keys and environments](/docs/keys).\n- **Environments**: project routes for payments, company, sign-in and the database take `?env=production|development`; the default is production for full-access keys and development for Limited keys.\n- **Idempotency**: any `POST` takes `Idempotency-Key` (24 hours).\n- **Errors**: `{ \"error\": { \"code\", \"message\", \"details\"? } }`. See [Errors](/docs/errors).\n- **Lists**: `{ \"object\": \"list\", \"data\": [...] }`; payments lists add `has_more` and `next_cursor`.\n- **Async work**: creating a project, adding a resource and deploying answer `202` with the queued operations; poll the object.\n\nAuth below: *account key* is any account key; *full-access key* refuses Limited keys with `403 owner_only`; *owner on production* means a Limited key may do it in development only.\n\n## Projects\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/health` | account key | Mission Control: every active project with its health, worst first: `status` (`fail`, `warn`, `ok`, `unknown`), `checked_at`, `counts`, `top` (the 3 worst problems, each with `detail`, `fix`, `link`, `since`), `metrics` (`visitors_7d`, `pageviews_24h`, `sales_30d`, `errors_24h`) and `console_url`; with `totals`. `?status=fail` (or `fail,warn`), `?q=`. Without credentials it is the liveness probe: `{ ok: true }`. |\n| `POST /v1/health/run` | account key | Check every project again now, in the background \u2192 `202` `{ queued }`. Twice per 10 minutes; checks also run hourly. |\n| `GET /v1/projects/:id/health` | account key | One project's health checks, worst first (site up, last deploy, resources, errors, traffic, sitemap & pages, payments, limits, domain), each with `detail`, `fix`, `link` and `since`. Checked on this read if it never was. |\n| `POST /v1/projects/:id/health/run` | account key | Check one project now \u2192 its checks. 5 a minute per project. |\n| `GET /v1/mission-control` | account key | Mission Control's board in one call: every active project as a row of `steps` (domain, deploy, pages, traffic, experience, payments, sales, limits; each with `status`, `set_up`, `value`, `line`, `link`; the pages step's `value` is how many pages the sitemap lists), its `metrics` (30 days of `pageviews_30d`/`visitors_30d`, `visitors_7d` and `visitors_prev_7d` with `visitors_change_pct`, sales and revenue 30 days and today, `errors_24h`, `sitemap_pages`, `indexed_pages` and `search_clicks_7d` (Google Search Console; null until the site is verified there), `ai_spend_today_usd_micro`, `top_sources_7d`, `top_pages_7d`, `last_deploy`, `latest_problem_replay`), worst first; plus `insights` (`today`, `movers`, `new_problems`, `top_sources_7d`) and the `layout`. Figures kept a minute (`metrics_at`), health fresh. |\n| `GET /v1/projects/:id/search` | account key | Where the project's pages go to search engines and what they say: `indexnow` with the `host` sent (its own domain, or the free address when turned on), `pages_sent`, `last_sent_at`, `last_sent_count`, `key_url` and a `note` when the last run sent nothing; `google` (the account's own Search Console) with `connected`, `property`, `verify_method`, `verified_at`, `sitemap_submitted_at`, `last_sync_at`, `note` (what failed, why, how to fix), `totals` (`pages_known`, `indexed`, `not_indexed`, `not_inspected`), `clicks_28d`, `impressions_28d`, `position_28d`, `daily`, `top_queries`, `top_pages`, `push` (`enabled`, `pushed_today`, `pushed_total`, `indexed_after_push`, `note`); `bing` with `connected`, `site_added_at`, `verified_at`, `indexed`, `crawled_28d`, `crawl_errors`, `submitted_today`, `submitted_total`, `quota_left`, `clicks_28d`, `impressions_28d`, `note`. |\n| `GET /v1/projects/:id/search/pages` | account key | The sitemap's pages as Google sees them (URL Inspection, up to 200 a day): `state` `indexed`, `not_indexed` or `all` (default), `limit` (\u2264 200), `offset`. Each has `indexed`, `verdict`, `coverage_state` (Google's words), `last_crawl_time`, canonicals and `google_inspect_url`, where the owner clicks Request indexing. |\n| `POST /v1/projects/:id/search/sync` | account key | Set the site up in Google and Bing and read them now instead of waiting for the daily sync \u2192 the project search. 3 per 10 minutes per project. |\n| `GET /v1/search/connections` | account key | The account's own search engine accounts: Google Search Console (`account_email`, `sites` of `site_limit` 1,000, `status`, `error`) and Bing Webmaster. `google_available`: whether this Stack can connect Google. Tokens and keys are never returned. |\n| `POST /v1/search/google/connect` | full-access key | Connect a Google account's Search Console \u2192 `{ url }`, Google's consent page; open it in a browser. Several Google accounts can be connected (Google allows 1,000 sites each). `not_configured` when this Stack has no Google client. |\n| `GET /v1/search/overview` | account key | Every project with its own domain (or the free address, when sent) at a glance, most clicks first: `host`, Google `property`, `verified_at`, `sitemap_submitted_at`, `pages` (`pages_known`, `indexed`, `not_indexed`, `not_inspected`), `clicks_28d`, `impressions_28d`, `ctr_28d`, `position_28d`, `note`, `bing`; plus `totals` (with `pushed_today` and `bing_submitted_today`). |\n| `POST /v1/search/google/key` | account key | Owner: add a Google service-account key (`key`: the JSON file as text or an object) so every project goes into Search Console without anyone signing in; `owner_email` is added as an owner of every site. Checked with Google first (an API that's off is named with its link); stored sealed, never shown. \u2192 the connections. |\n| `POST /v1/search/bing` | full-access key | `{ api_key }`: the Bing Webmaster API key (Bing Webmaster Tools \u25B8 Settings \u25B8 API access), checked with Bing, then used for every project; replaces the previous one. |\n| `PATCH /v1/search/settings` | full-access key | `{ google_push }`: push pages Google hasn't crawled yet to Google (its Indexing API), up to 200 a day per Google Cloud project, on every Google connection of the account. Off by default; Google says the API is meant for job-posting and livestream pages and may ignore other pages or withdraw access. \u2192 the connections, with `google_push` and each Google connection's `push` (`enabled`, `pushed_today`, `paused_until`, `note`). |\n| `DELETE /v1/search/connections/:id` | full-access key | Disconnect a Google account (its access is revoked at Google) or the Bing key. Projects on that Google account move to another connected one on the next sync. |\n| `PATCH /v1/projects/:id/search` | account key | `{ submit_free_address }`: also send the free vibiz.app address while there is no own domain (off by default). |\n| `POST /v1/projects/:id/search/submit` | account key | Send the pages that are new or changed in the sitemap to IndexNow now; `run` has `sent` and `host`, or `note` saying why nothing went. |\n| `GET /v1/mission-control/layout` | account key | The account's pinned rows and row order on the board: `rows` of `{ project_id, pinned, position }`. |\n| `PUT /v1/mission-control/layout` | account key | Pin or order rows: `{ rows: [{ project_id, pinned, position }], replace? }`; `replace: true` drops every row not listed (Tidy up). Each project once; another account's project is `404`. |\n| `POST /v1/projects` | account key | Create a project `{ name, slug?, resources? }`. Default resources: hosting, database, auth, analytics. \u2192 `202 { project, operations }`. |\n| `GET /v1/projects` | account key | List projects, each with `url`, `primary_url` and `custom_domains`. |\n| `GET /v1/projects/metrics` | account key | Every project's revenue (30 days, net of refunds, `usd_cents` plus `by_currency` as charged) and visitors (7 days) in one call, with the account's `totals`. `?env=production\\|development` (default production). \u2192 `list` of `project_metrics`. |\n| `GET /v1/projects/:id` | account key | One project with its resources, `url` (the vibiz.app address), `primary_url` (a live own domain that does not redirect, else `url`) `custom_domains` (`{ domain, hosting, live, redirects_to }`, live first; a domain that redirects is never the primary) and `public_live`. |\n| `PATCH /v1/projects/:id` | full-access key | Change a project's settings: `{ public_live: true\\|false }` shows it on the public live page or takes it off at once. \u2192 the project. |\n| `GET /v1/projects/:id/icon` | account key | The live site's favicon as a data URI (`icon`, null without one), fetched by thelastapi. |\n| `DELETE /v1/projects/:id` | account key | Site offline now; data destroyed after 7 days. `409 payments_held` while it holds live money. \u2192 `202` with `delete_after`. |\n| `POST /v1/projects/:id/restore` | account key | Undo a delete within the 7 days; what was live is rebuilt. \u2192 `202`. |\n| `POST /v1/projects/:id/resources` | account key | Add a resource `{ type }` (`hosting`, `database`, `auth`, `email`, `analytics`, `replay`, `ai`); dependencies are added. \u2192 `202`. |\n| `PATCH /v1/projects/:id/resources/:type` | account key | Change a resource's settings `{ config }` (only `replay` has settings). |\n| `GET /v1/projects/:id/env` | full-access key | The production env values. `?names=1` lists only the names, for any key. |\n| `GET /v1/projects/:id/env/vars` | account key | The app's own variables: `data[]` with `name`, `environment` and `updated_at`, never a value. |\n| `PUT /v1/projects/:id/env/:name` | owner on production \xB7 any key on development | Set one of the app's own variables `{ value, environment? }` (`production` by default): write-only, sealed, added to the env the app loads and to connected hosts. `NAME`: capitals, digits and `_`; a name thelastapi sets answers `409`. |\n| `DELETE /v1/projects/:id/env/:name` | owner on production \xB7 any key on development | Remove one of the app's own variables (`?environment=development` for the development one). |\n| `POST /v1/projects/:id/secret-link` | account key | The console link where a person types one secret `{ name, environment?, kind? }` (`env`, `connector`, `ai`, `host`): what an agent hands over instead of asking for the value in a chat. \u2192 `{ console_url }`. |\n| `GET /v1/projects/:id/domains` | account key | The free `address` and the owner's own domains: `data[]` with `status` (`pending_dns`, `verifying`, `active`, `error`, `external`), `https` and the `records_to_set` (`type`, `name`, `value`); `domains` lists the names. |\n| `POST /v1/projects/:id/domains` | account key | Connect a domain `{ domain, hosting? }` (`vibiz`: served here with HTTPS, the default with hosting; `elsewhere`: only trusted). At most 10; `409 domain_taken` if another project has it. \u2192 `201` with `domain`. |\n| `POST /v1/projects/:id/domains/:domain/verify` | account key | Check DNS and ownership again now. \u2192 the domain. |\n| `PATCH /v1/projects/:id/domains/:domain` | full-access key | Move to a new address: `{ redirect_to: \"<another domain of the project>\" }` makes every URL on this domain answer a permanent redirect (308) to the same path there, so search engines carry its pages over; `{ redirect_to: null }` stops it. The target must be live and never redirect itself; a redirecting domain is never `primary_url`. \u2192 the domain, with `redirect_to`. |\n| `DELETE /v1/projects/:id/domains/:domain` | full-access key | Disconnect a domain (and its `www` redirect). |\n| `POST /v1/projects/:id/domains/buy` | full-access key | Buy a domain from credits for this project `{ domain, years?, expected_price_cents, confirm_premium?, contact?, save_contact?, additional? }`: registered to the saved owner details, served here at once. \u2192 `202` the owned domain. `402` short of credits, `409 price_changed` with a new quote; agents get `owner_only` with the console link. |\n| `POST /v1/domains/buy` | full-access key | Buy a domain for the account `{ domain, project_id?, years?, expected_price_cents, \u2026 }` (as the project route): on `project_id` once registered, or none to use later. \u2192 `202` the owned domain. |\n| `POST /v1/domains/:domain/use` | account key | Use a bought domain, or a name under it, on any of the account's projects `{ project_id (id or slug), name?, hosting?, points_to? }`: no DNS to set, trusted for sign-in at once. `409 in_use` (with `used_on` and the move) when another project has it. \u2192 `domain_use`. |\n| `POST /v1/domains/:domain/move` | full-access key | Move a name of a bought domain to another project `{ to_project_id, name?, from_project_id?, hosting?, points_to? }`: the old project lets go of it (and its `www`). \u2192 `domain_use` with `moved_from`. |\n| `POST /v1/domains/:domain/point` | account key | A bought name used by an app on another host: point it there `{ name?, points_to, project_id? }` (`null` clears it); we write the record in its DNS. \u2192 `domain_use`. |\n| `GET /v1/domains/search` | account key | Domains for a name `?q=` across endings, with `price_cents` and `renewal_price_cents` (USD) and a `buy_url`. |\n| `GET /v1/domains/quote` | account key | One domain `?domain=&years=&project_id=`: the price, the balance after, the owner details it still needs (`fields_needed`) and `buy_url` for the owner. |\n| `GET /v1/domains` | account key | Domains the account bought: `status`, `expires_at`, `auto_renew`, `renewal_price_cents`, `registered_to`, `used_on` (every project and name using it), `contact_verification` (`status`, `verify_by`, `can_confirm`), `last_order`. |\n| `GET /v1/domains/:domain` | account key | One bought domain. |\n| `PATCH /v1/domains/:domain` | full-access key | Turn auto-renew (from credits, ~30 days before expiry) on or off `{ auto_renew }`. |\n| `POST /v1/domains/:domain/renew` | full-access key | Renew now from credits `{ years?, expected_price_cents }` \u2192 `202`. |\n| `GET /v1/domains/:domain/records` | account key | A bought domain's DNS records: `id`, `type`, `name` (relative, `''` the domain itself), `value`, `ttl`, `priority` (MX), and `managed` / `managed_by` (`hosting`, `email`, `default`) for the ones thelastapi keeps. |\n| `POST /v1/domains/:domain/records` | full-access key | Add a record `{ type: A\\|AAAA\\|CNAME\\|MX\\|TXT\\|CAA, name, value, ttl?, priority? }` \u2192 `201` the record (`200` with `created: false` when the same one is already there). |\n| `DELETE /v1/domains/:domain/records/:id` | full-access key | Remove a record. A `managed` one answers `409 managed_record` with what to run instead, unless `?force=1`. |\n| `POST /v1/domains/:domain/contact-verification/confirm` | full-access key | Confirm the owner's contact details for a new domain (ICANN asks within 15 days) when `contact_verification.can_confirm`. \u2192 the owned domain. |\n| `POST /v1/domains/:domain/contact-verification/check` | account key | Check now whether the owner's contact details are confirmed. \u2192 the owned domain. |\n| `POST /v1/domains/:domain/auth-code` | full-access key | The transfer code another registrar asks for. |\n| `GET /v1/domains/owner` | full-access key | The domain owner details (the registrant every new domain is registered to). |\n| `PUT /v1/domains/owner` | full-access key | Save the domain owner details `{ contact }`; they apply to domains bought from then on. |\n\n## Development environment\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/dev` | account key | `{ status: none\\|provisioning\\|ready\\|failed, resources }`. |\n| `POST /v1/projects/:id/dev` | account key | Create the development copies (idempotent). \u2192 `202`. |\n| `GET /v1/projects/:id/dev/env` | account key | The development env values; `409` until ready. |\n| `DELETE /v1/projects/:id/dev` | account key | Throw the development copies away. \u2192 `202`. |\n\n## Keys and hosts\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/waitlist` | public | Join the waitlist for a new account: `{ email, source? }` \u2192 `200 { object: \"waitlist_signup\", listed: true }`, the same answer whether or not the email was already listed. 20 per address per hour. |\n| `POST /v1/cli/login` | public | Start a browser login (`vibiz login`): `{ hostname?, os?, cli_version? }` \u2192 `201 { device_code, user_code, verification_uri, verification_uri_complete, expires_in, interval }`. The person opens the link and clicks Authorize. 10 per address per 10 minutes. |\n| `POST /v1/cli/login/token` | public | Poll a browser login `{ device_code }` every `interval` seconds: `400 { error }` with `authorization_pending`, `slow_down`, `expired_token`, `access_denied` or `invalid_grant` (`authorization_pending` with `reason: signup_closed` and `waitlist_url` when the person who opened the link is not invited: stop and pass on `error_description`); once approved, `200 { api_key, key, account, api_url }`, exactly once. The key is a new Limited key named `cli \xB7 <hostname>`. |\n| `GET /v1/whoami` | account key | The account and key this request acts as: `{ account, key: { id, name, prefix, kind, access }, role }`. |\n| `POST /v1/cli/logout` | account key | The calling key revokes itself (`vibiz logout` for a key a browser login made). |\n| `GET /v1/api-keys` | account key | Named keys, no secrets, with `access`, `preset` (full, read_all, custom, limited) and a Limited key's `grants`. |\n| `GET /v1/api-keys/permissions` | account key | Every permission a Limited key can be given (`id`, `area`, `label`), and the presets. |\n| `POST /v1/api-keys` | full-access key | Create a key `{ name, access?: owner\\|agent, preset?: full\\|read_all\\|limited, grants?: [...] }` (default Full access; needs `keys:write`; never more than the caller has). The secret is returned once. \u2192 `201`. |\n| `PATCH /v1/api-keys/:id` | full-access key | Change a key's access `{ access }`, `{ preset: full\\|read_all\\|limited }` or `{ grants: [...] }` (Limited with those permissions). Needs `keys:write`; never beyond the caller's own, and a key can't change its own. |\n| `DELETE /v1/api-keys/:id` | full-access key | Revoke a key (a key can't revoke itself). |\n| `GET /v1/projects/:id/app-keys` | account key | App key prefixes and last use, per environment, each with the `console_url` that opens it ready to copy. |\n| `GET /v1/projects/:id/app-keys/:environment` | owner on production \xB7 any key on development | The app key itself, to paste into a host thelastapi can't connect to. A Limited key gets `owner_only` with the `console_url` to hand over. |\n| `POST /v1/projects/:id/app-keys/rotate` | owner on production \xB7 any key on development | Rotate an app key `{ environment, grace_seconds }`; the new key is pushed everywhere, never shown. |\n| `GET /v1/hosts` | account key | The hosts thelastapi can connect to and what each asks for. |\n| `GET /v1/projects/:id/hosts` | account key | Connected hosts: status and the variable names written. |\n| `POST /v1/projects/:id/hosts` | full-access key | Connect a host `{ kind, token, project?, team_id?, environments? }`; the token is checked first. \u2192 `201`. |\n| `POST /v1/projects/:id/hosts/sync` | account key | Push the env to every connected host now. \u2192 `202`. |\n| `DELETE /v1/projects/:id/hosts/:target` | full-access key | Disconnect; `?keep_values=1` leaves the values in place. |\n\n## Hosting\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/files/missing` | account key | Which of `{ shas }` (SHA-1, up to 10,000) still need uploading. |\n| `PUT /v1/files/:sha` | account key | Upload one file (raw bytes, up to 50 MB); must match its SHA-1. \u2192 `204`. |\n| `POST /v1/projects/:id/deployments` | account key | Build `{ files: [{ path, sha, size }], target? }` (`production` by default, or `preview`). \u2192 `202 { deployment, operation }`. |\n| `GET /v1/projects/:id/deployments` | account key | The latest 50 deployments. |\n| `GET /v1/deployments/:id` | account key | `status`: `queued \u2192 building \u2192 ready` or `failed`. |\n| `GET /v1/deployments/:id/files` | account key | The deployment's code as deployed: `data[]` with every file's `path`, `sha` and `size`. |\n| `GET /v1/deployments/:id/files/*` | account key | One file's bytes by its path (`/files/src/app.js`), with `x-vibiz-sha`. `404` for a path the deployment doesn't have. |\n| `GET /v1/projects/:id/versions` | account key | Version history, newest first: `data[]` with `message`, `summary`, `who`, `created_at`, `target`, `status`, `live` and `files` added, updated and deleted against the version before. `?limit=`, `?cursor=`. |\n| `GET /v1/projects/:id/versions/diff` | account key | What changed between two versions: `?to=` (default the live one) against `?from=` (default the one before). `files[]` with a unified `diff` for text and sizes for binary files; `unavailable[]` names files no longer stored, with why. |\n| `POST /v1/projects/:id/versions/:version/restore` | account key | Put a version live again: `:version` is an id or `previous`. Instant for a production version (`200`), rebuilt for a preview or a build the host no longer keeps (`202`). The database is not rolled back: the answer has a `warning` saying so. |\n| `POST /v1/deployments/:id/promote` | account key | Make it live: a production deployment switches instantly (`200`, how rollback works); a preview is rebuilt as production (`202`). |\n\n## Database and users\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/database` | owner on production \xB7 any key on development | The app database's schemas and tables. `?env=`. |\n| `GET /v1/projects/:id/database/tables/:schema/:table` | owner on production \xB7 any key on development | One table's rows, read-only. `limit` (\u2264 200), `offset`. |\n| `POST /v1/projects/:id/database/query` | owner on production \xB7 any key on development | One read-only statement `{ sql, env? }` (SELECT, WITH, TABLE, VALUES, EXPLAIN, SHOW). |\n| `GET /v1/projects/:id/users` | owner on production \xB7 any key on development | The app's signed-up users. `limit` (\u2264 100), `offset`, `search`. |\n| `POST /v1/projects/:id/users/:user/sign-out` | full-access key | End one user's sessions. |\n\n## Sign-in\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/auth/settings` | owner on production \xB7 any key on development | Sign-in settings for `?env=`: email and password, magic link, providers with callback URLs, localhost, allowed domains, sender. |\n| `PATCH /v1/projects/:id/auth/settings` | owner on production \xB7 any key on development | Change sign-in settings (partial). |\n| `PUT /v1/projects/:id/auth/providers/:provider` | owner on production \xB7 any key on development | `google`, `github`, `vercel`: `{ credentials: \"shared\" }` (Google only) or `{ credentials: \"own\", client_id, client_secret }`. |\n| `DELETE /v1/projects/:id/auth/providers/:provider` | owner on production \xB7 any key on development | Turn a provider off. |\n| `POST /v1/projects/:id/auth/test-email` | full-access key | A test message `{ to }` through the SMTP sender that is set. |\n\n## Email\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/email` | account key | The project's mail domain, status, today's sends and recent activity. |\n| `GET /v1/forwarding` | account key | Email forwarding on every domain of the account: `data[]` as `GET /v1/domains/:domain/forwarding`. |\n| `GET /v1/domains/:domain/forwarding` | account key | Email forwarding for a domain: `status` (`off`, `needs_dns`, `verifying`, `active`, `failed`), `managed_dns`, the `records` it needs, `mx` (whose mail servers it points at, with a warning when they are another provider's), `rules[]` (`address`, `to[]` with each inbox's `status`: `pending` until it confirms, `confirmed`, `disabled`), `forwarded_today`, `daily_cap`, `next_step`. |\n| `PUT /v1/domains/:domain/forwarding` | full-access key | Set every rule `{ rules: [{ address: \"hello\" \\| \"*\", to: [\"me@example.com\"] }], replace_mx? }` (up to 5 inboxes each; `*` is any other address). Domains bought through thelastapi get their records set; `replace_mx: true` confirms taking the domain's mail from the provider it uses today. New inboxes get a confirmation email. Agents get `owner_only` with a `console_url` that has their proposal filled in. |\n| `DELETE /v1/domains/:domain/forwarding` | full-access key | Turn email forwarding off for the domain and remove the records thelastapi set. |\n| `POST /v1/domains/:domain/forwarding/verify-dns` | account key | Check the domain's records again now. \u2192 the forwarding. |\n| `GET /v1/domains/:domain/forwarding/log` | account key | Recent messages to the domain's forwarding addresses (`?limit=`, \u2264 200; kept 30 days): `at`, `from`, `to`, `destination`, `subject`, `status` (`sent`, `unconfirmed`, `spam`, `virus`, `dmarc`, `loop`, `no_rule`, `daily_cap`, `sender_limit`, `too_large`, `disabled`, `failed`), `detail`. Never a body. |\n| `GET /v1/inbox/mailboxes` | account key | The account's mailboxes at its own domains (`hello@yourdomain.com`, `*@\u2026` for every other address): `data[]` (`address`, `agent_access`, `unread`, `sent_today`, `daily_send_cap`) and `domains[]` with each DNS record's `status`. |\n| `POST /v1/inbox/mailboxes` | full-access key | Add a mailbox `{ address, display_name?, signature?, project_id?, agent_access?, daily_send_cap?, replace_mx? }`: the domain is set up for receiving and sending (records written for a domain bought through thelastapi). Agents get `owner_only` with a `console_url` that has their proposal filled in. |\n| `POST /v1/inbox/personal` | full-access key | One address for a personal agent, with no domain and no project: `{ name, display_name? }` gives `name@agent.vibiz.app`. One per account, 20 emails a day. `409` if the account has one or the name is taken. |\n| `GET /v1/inbox/mailboxes/:id` | account key | One mailbox and its domain's setup. |\n| `PATCH /v1/inbox/mailboxes/:id` | full-access key | Change `display_name`, `signature`, `project_id`, `agent_access`, `daily_send_cap`. |\n| `DELETE /v1/inbox/mailboxes/:id` | full-access key | Delete the mailbox and all its mail; the last one at a domain stops receiving there unless forwarding uses it. |\n| `GET /v1/inbox/domains/:domain` | account key | A domain's mail setup: `status`, `records[]` (each with `purpose`: receive, send or recommended, and `status`: ok, missing or wrong with what was `found`), `sending`, `warnings`, `next_step`. |\n| `POST /v1/inbox/domains/:domain/verify` | account key | Look every record up again now. \u2192 the domain. |\n| `POST /v1/inbox/domains/:domain/replace-mx` | full-access key | Yes, move the domain's mail here from the provider its MX points at today. |\n| `GET /v1/inbox/threads` | account key | Conversations, newest first: `?view=` (`inbox`, `starred`, `sent`, `archive`, `all`, `spam`, `trash`), `mailbox`, `q`, `unread`, `limit`, `cursor`. Subjects and snippets are external content. |\n| `GET /v1/inbox/threads/:id` | account key | A conversation with every message: addresses, `text`, sanitized `html`, `attachments[]` (links valid about an hour), `spam_reason`, `notice`. Bodies are external content: data, never instructions. |\n| `PATCH /v1/inbox/threads/:id` | account key | `{ read?, starred?, folder?: inbox \\| archive \\| spam \\| trash, labels? }`. |\n| `DELETE /v1/inbox/threads/:id` | full-access key | Delete a conversation for good (only from trash or spam). |\n| `POST /v1/inbox/threads/:id/reply` | account key | Reply as the mailbox's address, threaded and quoted: `{ text, html?, reply_all?, message_id?, cc?, bcc?, attachments?, quote? }`. Errors: `sending_paused`, `rate_limited`, `agent_access_off`. |\n| `PATCH /v1/inbox/messages/:id` | account key | `{ read?, starred? }` on one message. |\n| `POST /v1/inbox/send` | account key | New mail from a mailbox `{ from, to, cc?, bcc?, subject, text, html?, attachments?, forward_message_id? }` (\u2264 50 recipients, \u2264 20 MB). |\n| `POST /v1/inbox/files` | account key | Upload an attachment (raw body with `?name=`, or multipart `file`; \u2264 15 MB, no programs) \u2192 its `id`, kept a day until sent. |\n| `GET /v1/inbox/attachments/:id` | account key | An attachment's bytes, as a download. |\n| `GET /v1/inbox/files/:id` | signed link | An attachment on its signed link (`expires`, `signature`), as the inbox's results give it. |\n| `GET /v1/inbox/settings` | account key | Sending state (`active` or `paused`), today's sends against the account's daily cap, the new-mail `digest`. |\n| `PATCH /v1/inbox/settings` | full-access key | `{ digest }`: email the owners at most hourly when new mail arrives. |\n| `GET /v1/forwarding/confirm/:token` | signed link | The page an inbox opens from its \"Confirm forwarding to this inbox\" email: one button. |\n| `POST /v1/forwarding/confirm/:token` | signed link | The inbox confirms: forwarded mail reaches it from then on. |\n| `GET /v1/projects/:id/email/marketing` | account key | Marketing email settings: `status` (`off`, `setting_up`, `ready`, `paused`, `blocked`), `sender` (`news.<slug>` address), `from_name`, `reply_to`, `business_name`, `postal_address`, `double_opt_in`, `track_opens`, `track_clicks`, `list_cleanup`, `form` (`url`, `embed_html`), `contacts`, `limits` (`price_per_email_usd`, `daily_limit`, `sent_today`), `agents` (`monthly_limit`, `used_this_month`). |\n| `PATCH /v1/projects/:id/email/marketing` | account key | Change settings. `postal_address`, `agent_monthly_limit` and turning `double_opt_in` off are the owner's. |\n| `POST /v1/projects/:id/email/marketing/setup` | account key | Set up sending (adds the email resource if needed): `202`, `status: setting_up` until the address verifies, then `ready`. |\n| `GET /v1/projects/:id/email/lists` | account key | Lists with their `subscribed` counts. |\n| `POST /v1/projects/:id/email/lists` | account key | `{ name, description?, public? }` \u2192 the list. `public` lists show on the preference page. |\n| `PATCH /v1/projects/:id/email/lists/:list` | account key | Rename or describe a list (id or name). |\n| `DELETE /v1/projects/:id/email/lists/:list` | account key | Delete a list (its contacts stay). |\n| `GET /v1/projects/:id/email/contacts/export` | account key | Contacts as CSV (`?status=`, `?list=`), with consent and properties. |\n| `GET /v1/projects/:id/email/contacts/imports` | account key | Past imports with their reports. |\n| `POST /v1/projects/:id/email/contacts/import` | account key | Import a CSV `{ csv, dry_run?, consent, lists?, fix_typos?, include_role?, update_existing? }` \u2192 a report: `new_contacts`, `updated_contacts`, `skipped` by reason, `samples`, `typo_suggestions`. `consent: true` is required to import. |\n| `GET /v1/projects/:id/email/contacts` | account key | Contacts, newest first: `?q=`, `?status=`, `?list=`, `?segment=`, `?cursor=`, `?limit=` (\u2264 200); `total`. |\n| `POST /v1/projects/:id/email/contacts` | account key | Add or update one by email `{ email, first_name?, last_name?, properties?, lists?, subscribed?, double_opt_in?, consent? }`. Never re-subscribes someone who left: they get a confirmation email (`pending`). |\n| `GET /v1/projects/:id/email/contacts/:contact` | account key | One contact (id or email) with its lists and last 20 events. |\n| `PATCH /v1/projects/:id/email/contacts/:contact` | account key | `{ first_name?, last_name?, properties?, status?: subscribed \\| unsubscribed, add_lists?, remove_lists? }`. Subscribing again by hand is the owner's. |\n| `DELETE /v1/projects/:id/email/contacts/:contact` | account key | Forget a contact. An address that unsubscribed, bounced or complained stays suppressed. |\n| `POST /v1/projects/:id/email/events` | account key | `{ email, event, properties? }`: something a contact did. Starts event automations and ends runs whose exit event it is. |\n| `GET /v1/projects/:id/email/segments` | account key | Saved segments with their `contacts` counts. |\n| `POST /v1/projects/:id/email/segments/preview` | account key | `{ filter }` \u2192 `contacts` and a sample, without saving. |\n| `POST /v1/projects/:id/email/segments` | account key | `{ name, filter: { match: all \\| any, conditions[] } }`: properties, fields, lists, events, engagement. |\n| `PATCH /v1/projects/:id/email/segments/:segment` | account key | Rename it or change its filter. |\n| `DELETE /v1/projects/:id/email/segments/:segment` | account key | Delete a segment. |\n| `POST /v1/projects/:id/email/render` | account key | Render a draft `{ subject, preview_text?, format, body, contact_id? }` as a contact gets it: `html`, `text`, `size_bytes`, `merge_tags`. |\n| `GET /v1/projects/:id/email/broadcasts` | account key | Broadcasts, newest first (`?status=`), with their stats. |\n| `POST /v1/projects/:id/email/broadcasts` | account key | A draft `{ name?, subject, preview_text?, from_local?, from_name?, reply_to?, format: markdown \\| html, body, audience: { list_id?, segment_id? } }`. |\n| `GET /v1/projects/:id/email/broadcasts/:broadcast` | account key | One broadcast: `status`, `waiting`, `recipients`, `charged_cents`, `stats` (sent, delivered, opened, clicked, bounced, complained, unsubscribed, rates, `by_mailbox`). |\n| `PATCH /v1/projects/:id/email/broadcasts/:broadcast` | account key | Edit a draft, a scheduled or a waiting-for-approval broadcast. |\n| `DELETE /v1/projects/:id/email/broadcasts/:broadcast` | account key | Delete a draft or canceled broadcast. |\n| `GET /v1/projects/:id/email/broadcasts/:broadcast/review` | account key | The checklist before sending: `ready`, `checks[]` (`ok`, `warning`, `error`), `audience`, `cost` (`total_cents`, `balance_cents`, `enough_credits`), `sending`, `preview`, `console_url`. |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/test` | account key | Send a free `[Test]` copy `{ to? }` (agents: to the owners only; 20 a day). |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/send` | account key | Send now or `{ scheduled_at }`. An agent sends only within the owner's monthly allowance; otherwise `403 owner_only` with the review link. |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/cancel` | account key | Stop it; nothing more goes out and the held credits are released. |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/resume` | full-access key | Go on after a pause. |\n| `GET /v1/projects/:id/email/broadcasts/:broadcast/recipients` | account key | Who got it: `?status=` (`sent`, `delivered`, `opened`, `clicked`, `bounced`, `complained`, `unsubscribed`, `failed`), `?mailbox=`, `?cursor=`. |\n| `GET /v1/projects/:id/email/automations` | account key | Automations with their run counts. |\n| `POST /v1/projects/:id/email/automations` | account key | `{ name, trigger, steps[], exit_event? }`: triggers `contact_added`, `event`, `date`; steps `wait`, `email`, `condition` (`yes[]`, `no[]`), `exit`. |\n| `GET /v1/projects/:id/email/automations/:automation` | account key | One automation with `enrollments` counts and emails sent, opened, clicked. |\n| `PATCH /v1/projects/:id/email/automations/:automation` | account key | Edit. While active only email wording changes; pause it to change the trigger, waits or branches. |\n| `DELETE /v1/projects/:id/email/automations/:automation` | account key | Delete it (archived if it sent email). |\n| `POST /v1/projects/:id/email/automations/:automation/activate` | account key | Turn it on. An agent needs the owner's monthly allowance; otherwise `403 owner_only` with the console link. |\n| `POST /v1/projects/:id/email/automations/:automation/pause` | account key | Pause it; runs wait where they are. |\n| `GET /v1/projects/:id/email/automations/:automation/enrollments` | account key | Runs: `?status=` (`active`, `completed`, `exited`, `failed`), each with its `step_id`, `next_run_at`, `history`. |\n| `POST /v1/projects/:id/email/automations/:automation/test` | account key | Send one email step as a free test `{ step_id, to? }`. |\n| `GET /v1/email/u/:token` | signed link | The unsubscribe page a contact opens from an email (`?view=preferences`: lists to keep). GET changes nothing. |\n| `POST /v1/email/u/:token` | signed link | One-click unsubscribe (`List-Unsubscribe=One-Click`, RFC 8058), or the page's form: unsubscribe, subscribe again, save lists, never from anyone. |\n| `GET /v1/email/confirm/:token` | signed link | The double opt-in page: one button. |\n| `POST /v1/email/confirm/:token` | signed link | The contact confirms: `subscribed`. |\n| `GET /v1/email/k/:token` | signed link | \"Keep sending\" page from the list-cleanup email. |\n| `POST /v1/email/k/:token` | signed link | The contact keeps getting emails. |\n| `GET /v1/email/o/:token` | signed link | Open tracking pixel. |\n| `GET /v1/email/c/:token` | signed link | Click tracking: redirects to the signed destination. |\n| `GET /v1/email/f/:form` | public | The hosted signup form. |\n| `POST /v1/email/f/:form` | public | A signup from the form, a pasted snippet or JSON from any site `{ email, first_name? }`: honeypot, rate limits, double opt-in. |\n| `OPTIONS /v1/email/f/:form` | public | CORS preflight for the signup API. |\n\n## AI\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/ai/chat/completions` | account, project AI or app key | OpenAI chat completions, streaming (SSE) or not. `model` defaults to `vibiz/fast`. |\n| `POST /v1/ai/embeddings` | account, project AI or app key | Embeddings. |\n| `POST /v1/ai/images/generations` | account, project AI or app key | Images: `b64_json` (default) or `url` (24 h). Edit a photo with `image_url` (or `image_urls`, up to 8). Any image model from `GET /v1/ai/media-models` by its id, with its own parameters in `model_input`. |\n| `POST /v1/ai/audio/speech` | account, project AI or app key | Text to speech; streams `mp3` or `pcm`. |\n| `POST /v1/ai/audio/transcriptions` | account, project AI or app key | Speech to text, multipart `file` (\u2264 25 MB). |\n| `POST /v1/ai/jobs` | account, project AI or app key | Async image or video `{ type, model?, input }`: any model from `GET /v1/ai/media-models` by its id, with its own parameters in `input.model_input`. \u2192 `202`. |\n| `GET /v1/ai/jobs/:id` | account, project AI or app key | A job and, once done, its output. |\n| `POST /v1/ai/jobs/:id/cancel` | account, project AI or app key | Cancel a job. |\n| `GET /v1/ai/models` | public | The thelastapi models, each with the lab model it runs, and the lab models, with prices. `?all=1` every model, `?q=` search. |\n| `GET /v1/ai/media-models` | account, project AI or app key | Every image and video model that runs by its id (Kling, face swap, upscalers\u2026), with its live price. `?q=`, `?category=`, `?limit=`. |\n| `GET /v1/ai/health` | public | Per capability `ok`/`degraded`/`down`. |\n| `GET /v1/ai/media/:token` | signed link | Generated media; the token in the link is the credential (24 h). |\n| `GET /v1/projects/:id/ai` | account key | A project's AI key status, budgets, limits and today's spend. |\n| `PATCH /v1/projects/:id/ai` | account key | `{ daily_budget_usd?, end_user_daily_budget_usd?, log_content?, rpm?, tpm?, concurrency? }`. |\n| `POST /v1/projects/:id/ai/keys/rotate` | full-access key | A new project AI key `{ grace_seconds? }` (default 3600), written to the app env. |\n| `POST /v1/projects/:id/ai/keys/revoke` | account key | Every AI key of the project stops now; rotate to get a new one. |\n| `GET /v1/ai-keys` | account key | Your own AI provider keys, the account's: status per provider (never a secret) and calls they served in 30 days. |\n| `GET /v1/ai-keys/:provider` | account key | One key: `has_key`, last 4, last used, last error, and per thelastapi model whether `your_key` or `vibiz` serves (and pays for) it. |\n| `PUT /v1/ai-keys/:provider` | full-access key | Set your own key. provider `\"google\"`: `{ type: \"gemini_api_key\", api_key }` or `{ type: \"vertex\", service_account, project_id?, region? }`; provider `\"fal\"`: `{ type: \"fal_key\", api_key }`; `use_for?`. Checked with a free call first. |\n| `PATCH /v1/ai-keys/:provider` | full-access key | `{ use_for: [capability\u2026] }`: what the key serves; the rest runs on thelastapi. |\n| `DELETE /v1/ai-keys/:provider` | full-access key | Remove the key; calls go back to thelastapi (jobs promised to it fail). |\n| `POST /v1/ai-keys/:provider/test` | account key | Re-check the stored key with the same free call; records the result. |\n| `GET /v1/projects/:id/ai-keys` | account key | Your own AI provider keys, a project's override (else it inherits the account's): status per provider (never a secret) and calls they served in 30 days. |\n| `GET /v1/projects/:id/ai-keys/:provider` | account key | One key: `has_key`, last 4, last used, last error, and per thelastapi model whether `your_key` or `vibiz` serves (and pays for) it. |\n| `PUT /v1/projects/:id/ai-keys/:provider` | full-access key | Set your own key (`google`): `{ type: \"gemini_api_key\", api_key }` or `{ type: \"vertex\", service_account, project_id?, region? }`, `use_for?`. Checked with a free call first. |\n| `PATCH /v1/projects/:id/ai-keys/:provider` | full-access key | `{ use_for: [capability\u2026] }`: what the key serves; the rest runs on thelastapi. |\n| `DELETE /v1/projects/:id/ai-keys/:provider` | full-access key | Remove the key; calls go back to thelastapi (jobs promised to it fail). |\n| `POST /v1/projects/:id/ai-keys/:provider/test` | account key | Re-check the stored key with the same free call; records the result. |\n| `GET /v1/projects/:id/ai/calls` | account key | The project's recent AI calls: model, tokens, cost, outcome (no content). |\n| `POST /v1/actions/ai.chat` | account key | `{ input: { prompt \\| messages, system?, model?, max_tokens?, json? } }` \u2192 `{ output: { text, model, usage }, cost_micro_usd }`. |\n| `POST /v1/projects/:id/actions/ai.chat` | account key | The same, billed to the project. |\n| `POST /v1/actions/image.generate` | account key | `{ input: { prompt, size?, n?, model? } }` \u2192 image links (24 h). |\n| `POST /v1/projects/:id/actions/image.generate` | account key | The same, billed to the project. |\n| `POST /v1/actions/speech.create` | account key | `{ input: { text, voice?, format?, model? } }` \u2192 an audio link. |\n| `POST /v1/projects/:id/actions/speech.create` | account key | The same, billed to the project. |\n| `POST /v1/actions/speech.transcribe` | account key | `{ input: { audio_base64, filename?, language?, model? } }` \u2192 `{ text, language, duration_seconds }`. |\n| `POST /v1/projects/:id/actions/speech.transcribe` | account key | The same, billed to the project. |\n\n## Files\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/files` | account key | The project's files, newest first (`env`, `type`, `source`, `q`, `since`, `until`, `model`, `tag`, `folder`, `limit`, `cursor`), with `total_files` and `total_bytes`. |\n| `POST /v1/projects/:id/files` | account key | Upload a file (raw body with `?name=`, or multipart `file`), up to 50 MB \u2192 the file with its permanent `url`. |\n| `POST /v1/projects/:id/files/import` | account key | Save what a public URL serves `{ url, name?, folder?, private? }`. |\n| `GET /v1/projects/:id/files/latest` | account key | The newest file matching `type`, `source`, `model`, `tag`: what an agent just made. |\n| `GET /v1/projects/:id/files/:fileId` | account key | One file: its link, type, size, dimensions and, for AI media, the model, prompt and cost. |\n| `GET /v1/projects/:id/files/:fileId/content` | account key | The file's bytes, private or not. |\n| `PATCH /v1/projects/:id/files/:fileId` | account key | Rename, move, tag, annotate or make private `{ name?, folder?, tags?, note?, private? }`. |\n| `DELETE /v1/projects/:id/files/:fileId` | account key | Delete a file: its link stops working. |\n\n## Export\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/projects/:id/exports` | owner on production \xB7 any key on development | Pack the project to take it elsewhere `{ include?: [code, database, database_csv, env_guide], env?, deployment_id? }` \u2192 `202` and the export, `queued`. The code is the source of the live deployment (or `deployment_id`) with `VIBIZ-EXPORT.md` and `.env.example`; the database is plain SQL that `psql` restores, CSV optional. A production database is an owner's; one export at a time, 10 a day. |\n| `GET /v1/projects/:id/exports` | account key | The last 20 exports, newest first. |\n| `GET /v1/projects/:id/exports/:exportId` | account key | One export: `status` (`queued`, `running`, `ready`, `failed`, `expired`), `step`, `progress`, and `files` with signed download links until `expires_at` (a day). Agents get no link to production data. |\n| `GET /v1/projects/:id/exports/:exportId/env` | full-access key | The export environment's secret values as a `.env` file, with `confirm=1`. Never cached, never in the zip. |\n\n## Actions\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/actions/:name` | account key | Run an account action `{ input }`: web data (`web.scrape`, `web.search`, `web.crawl`, `web.screenshot`, `web.design`, `ads.library`, `places.search`, `reviews`, `social.profile`, `social.posts`, `ecommerce.product`, `linkedin.company`; SEO data: `seo.serp`, `seo.keywords`, `seo.keyword_ideas`, `seo.domain`, `seo.backlinks`, `seo.audit`, `seo.ai_mentions`) \u2192 `{ output, cost_micro_usd, run_id, console_url }`. `web.design` with `sections: true` captures a page section by section; with `section: <n>` it reads one, free from the saved capture. |\n| `GET /v1/actions` | account key | The web data actions: name, title, one line, slow or not, a hint per field, an example and the input as JSON Schema. |\n| `GET /v1/actions/runs` | account key | Past web data runs, newest first (input, status, cost, no output). `?project=<id>\\|none`, `?action=`, `?since=<iso>`, `?cursor=`, `?limit=` (25, \u2264 100). With `console_url`. |\n| `GET /v1/actions/runs/:id` | account key | One run with its output (cut to 1 MB: `truncated`), error and cost, with `console_url`. |\n| `POST /v1/projects/:id/actions/:name` | account key | Run an action as the project (`email.send`, or any action billed to it) \u2192 `{ project_id, output, cost_micro_usd, usage }`; web data also `run_id`, `console_url`, and a screenshot is saved to the project's Files. |\n\n## Payments\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/payments` | account key | The payments account: where sales go (`account.mode`: `vibiz` or `own`), balance, payouts status, `fees` (with `hold_days` and a $100 example), webhook. |\n| `PATCH /v1/projects/:id/payments` | owner on production \xB7 any key on development | `{ statement_descriptor_suffix?, webhook_url?, webhook_events?, brand? }`. `brand` (`{ name?, logo_url?, icon_url?, background_color?, button_color?, font?, border_style? }`) is the checkout page's look for every checkout, merged field by field (a field set to null goes; `brand: null` clears it). |\n| `POST /v1/projects/:id/payments/webhook-secret` | owner on production \xB7 any key on development | Rotate the webhook secret; shown once and written to the app env as `VIBIZ_WEBHOOK_SECRET`. |\n| `GET /v1/projects/:id/payments/deliveries` | account key | The last 50 webhook deliveries and their status codes. |\n| `GET /v1/projects/:id/payments/products` | account key | The catalog for `?env=`. |\n| `POST /v1/projects/:id/payments/products` | account key | Create `{ name, description?, price?: { unit_amount_cents, currency?, type, interval?, interval_count?, lookup_key? } }` (`currency`: ISO 4217, default `usd`; amounts in its smallest unit). |\n| `GET /v1/projects/:id/payments/products/:productId` | account key | One product with its prices. |\n| `PATCH /v1/projects/:id/payments/products/:productId` | account key | Rename, describe, activate or deactivate. |\n| `DELETE /v1/projects/:id/payments/products/:productId` | owner on production \xB7 any key on development | Archive a product. |\n| `POST /v1/projects/:id/payments/products/:productId/prices` | account key | Add a price `{ unit_amount_cents, currency?, type, interval?, interval_count?, lookup_key? }`. Prices are immutable. |\n| `PATCH /v1/projects/:id/payments/prices/:priceId` | account key | `{ active?, lookup_key? }`. |\n| `POST /v1/projects/:id/payments/checkout` | account key | A hosted checkout `{ price_id \\| lookup_key \\| amount_cents+name(+currency), user?, success_url, cancel_url, brand?, \u2026 }` \u2192 `{ url, expires_at }` (1 h, one buyer). |\n| `GET /v1/projects/:id/payments/payments` | account key | Payments, newest first (`cursor`, `limit`); emails masked for agents on production. |\n| `GET /v1/projects/:id/payments/payments/:paymentId` | account key | One payment. |\n| `POST /v1/projects/:id/payments/payments/:paymentId/refund` | owner on production \xB7 any key on development | `{ amount_cents?, reason? }`; `409 insufficient_balance` when the balance can't cover it. |\n| `GET /v1/projects/:id/payments/subscriptions` | account key | Subscriptions, `?user=&status=`, each with its price. |\n| `POST /v1/projects/:id/payments/subscriptions/:subId/cancel` | owner on production \xB7 any key on development | `{ at_period_end? = true }`. |\n| `GET /v1/projects/:id/payments/ledger` | account key | Every money movement, newest first. |\n| `POST /v1/projects/:id/payments/payouts/session` | owner on production \xB7 any key on development | A session for the embedded identity, bank and payouts UI (Get paid). |\n| `POST /v1/projects/:id/payments/withdraw` | owner on production \xB7 any key on development | `{ amount_cents? }` (default everything available) \u2192 a withdrawal; `409` when payouts are not ready or nothing is available. |\n| `GET /v1/projects/:id/payments/withdrawals` | account key | Withdrawals and their status. |\n| `GET /v1/projects/:id/payments/revenue` | account key | What sales brought in over the last `days` (default 30, up to 365) and the period before, net of refunds: `usd_cents` and `by_currency`. Reads only. |\n| `POST /v1/projects/:id/payments/refresh` | account key | Re-read the account and recent charges now. |\n| `POST /v1/projects/:id/payments/simulate` | account key | Development only: `{ event: payment \\| dispute \\| refund \\| release_hold, \u2026 }` runs a real test-mode charge through the ledger and webhooks. |\n| `POST /v1/projects/:id/payments/own-account/link` | account key | A link for the owner to connect their own Stripe account instead (`?env=`, default production) \u2192 `{ url, console_url, expires_at }`. Give `url` to the owner: only they can complete it. `503` when it isn't available. |\n| `DELETE /v1/projects/:id/payments/own-account` | full-access key | Disconnect the owner\u2019s own Stripe account (or opt the project out of the Stripe account for every project): new sales go through thelastapi again, and \"Apply to all projects\" leaves it alone. |\n| `POST /v1/projects/:id/payments/own-account/use-account` | owner on production \xB7 any key on development | Put the project on the Stripe account connected once for every project (Settings \u25B8 Payments), after opting out or instead of its own. `409 account_stripe_not_connected` until it is connected. |\n| `GET /v1/payments/own-account` | account key | The owner\u2019s Stripe connected once for every project: per environment (`environments.production\\|development`), `use_for_all_projects`, and how each project uses it (`account`, `other_account`, `vibiz`, `opted_out`, `not_started`). |\n| `POST /v1/payments/own-account` | full-access key | `{ use_for_all_projects }`: when on, every new project\u2019s payments start on the owner\u2019s Stripe account (in each environment where it is connected). |\n| `POST /v1/payments/own-account/link` | account key | A link for the owner to connect their Stripe account once for every project (`?env=`, default production) \u2192 `{ url, console_url, expires_at }`. Give `url` to the owner: only they can complete it. |\n| `POST /v1/payments/own-account/apply` | owner on production \xB7 any key on development | `{ env?, dry_run?, include_opted_out? }`: switch existing projects to the owner\u2019s Stripe account for new sales \u2192 `{ changed, unchanged, skipped }` (frozen, being deleted, on another Stripe account, opted out). Balances stay to withdraw; subscriptions sold through thelastapi keep billing there. `dry_run` lists without changing (any key). |\n| `DELETE /v1/payments/own-account` | full-access key | Disconnect the owner\u2019s Stripe account for every project (`?env=`): projects that used it sell through thelastapi again for new sales (`moved`); projects that connected the same Stripe account themselves keep it (`kept`). The connection is let go only when nothing uses it. |\n| `GET /v1/payments/app-store` | account key | The owner's own RevenueCat account: the projects there its keys reach (never a key), and which projects use them. |\n| `POST /v1/payments/app-store/link` | account key | A link for the owner to connect their RevenueCat account \u2192 `{ url, expires_at }`. They paste a V2 secret key on that page (never in a chat); only they can complete it. |\n| `DELETE /v1/payments/app-store/connections/:connectionId` | full-access key | Forget a RevenueCat key; the projects set up with it stop taking new store purchases (recorded ones stay). |\n| `GET /v1/projects/:id/payments/app-store` | account key | App Store and Google Play for the project (`?env=`): connected, the app set up (public SDK keys, store product ids, webhook), and `next` steps. |\n| `POST /v1/projects/:id/payments/app-store/setup` | account key | `{ ios_bundle_id?, android_package?, store_project_id? }`: create (or find) the app in the owner's RevenueCat account, mirror the catalog (a product per price with a lookup key, an entitlement per plan, a default offering), register the webhook \u2192 the public SDK key, the App Store product ids to create, and `next`. Safe to re-run. |\n| `GET /v1/projects/:id/payments/app-store/subscriptions` | account key | App Store and Google Play purchases recorded (`?env=&user=`), newest first. |\n| `GET /v1/projects/:id/payments/app-store/webhook-secret` | full-access key | The Authorization header value to paste in the RevenueCat dashboard when the webhook could not be registered for you. |\n\n## Company\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/company/catalog` | account key | States with their fees per entity type (cents), endings, industries, thelastapi fees, disclaimer. |\n| `GET /v1/projects/:id/company` | account key | The company, with `problems` and `quote` while a draft; `404` none yet. |\n| `PUT /v1/projects/:id/company` | account key | Create or replace the draft. |\n| `PATCH /v1/projects/:id/company` | account key | Change the draft (top-level keys replace). |\n| `DELETE /v1/projects/:id/company` | account key | Delete a draft (or a failed or cancelled one). |\n| `POST /v1/projects/:id/company/submit` | owner on production \xB7 any key on development | File it. Production: `{ confirm, accept_terms, expected_total_cents, expected_updated_at }`, paid from the credits (`402 payment_required` when they fall short); development: `{ accept_terms }`. |\n| `POST /v1/projects/:id/company/checkout` | full-access key | Pay a live filing by card instead: the submit body \u2192 a `billing_checkout` for exactly `quote.total_cents`; filed when the payment arrives. |\n| `POST /v1/projects/:id/company/signatures/:document` | owner on production \xB7 any key on development | A fresh signing link (`ss4`, `form_8821`). |\n| `POST /v1/projects/:id/company/actions/:actionId` | owner on production \xB7 any key on development | Answer an action: `{ names }` or `{ address }`. |\n| `GET /v1/projects/:id/company/documents/:docId` | owner on production \xB7 any key on development | A short-lived download link. |\n| `POST /v1/projects/:id/company/refresh` | account key | Re-read it from the filing partner now. |\n| `POST /v1/projects/:id/company/simulate` | account key | Development only: `{ step: formation \\| ein }`. |\n\n## Social\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/social` | account key | Overview: platforms with their limits, connected accounts, posts waiting, scheduled and failed, ad changes waiting. |\n| `GET /v1/projects/:id/social/accounts` | account key | Connected social and ad accounts (`kind`, `platform` filters). |\n| `POST /v1/projects/:id/social/connect` | account key | `{ platform, ads? }` \u2192 a link (1 h) for the owner to open: they approve it in the console, then sign in to the platform. Production unless `env=development`, which makes a test account at once and returns it. |\n| `POST /v1/projects/:id/social/accounts/refresh` | account key | Read the accounts again from the platforms. |\n| `DELETE /v1/projects/:id/social/accounts/:accountId` | owner on production \xB7 any key on development | Disconnect an account. |\n| `GET /v1/projects/:id/social/accounts/:accountId/analytics` | account key | Followers, totals and a daily series (`from`, `to`; 30 days by default). |\n| `POST /v1/projects/:id/social/media` | account key | Upload a file (raw body, its `content-type`, `?filename=`; up to 512 MB) \u2192 a URL to post with. |\n| `GET /v1/projects/:id/social/posts` | account key | Posts, newest first (`status`, `account`, `platform`, `from`, `to`, `cursor`, `limit`). |\n| `POST /v1/projects/:id/social/posts` | account key | Publish now, schedule (`schedule_at`) or draft. Production: owners send `confirm: true`; an agent's post waits for the owner (`pending_approval`). |\n| `GET /v1/projects/:id/social/posts/:postId` | account key | One post, with each account's status, link and error. |\n| `DELETE /v1/projects/:id/social/posts/:postId` | account key | Cancel a draft, a waiting or a scheduled post (a live scheduled one: owner). Published posts stay on the platforms. |\n| `POST /v1/projects/:id/social/posts/:postId/publish` | account key | Publish or schedule a draft (same rules as creating one). |\n| `POST /v1/projects/:id/social/posts/:postId/approve` | full-access key | Approve a waiting post: it goes out now or at its time (`schedule_at` to change it). |\n| `POST /v1/projects/:id/social/posts/:postId/reject` | full-access key | Reject a waiting post. |\n| `POST /v1/projects/:id/social/posts/:postId/retry` | owner on production \xB7 any key on development | Publish the failed accounts again (production: `confirm: true`). |\n| `POST /v1/projects/:id/social/posts/:postId/refresh` | account key | Read its status again from the platforms. |\n| `GET /v1/projects/:id/social/posts/:postId/analytics` | account key | Impressions, reach, likes, comments, shares, saves, clicks per account. |\n| `GET /v1/projects/:id/social/ads/campaigns` | account key | Campaigns of an ad account with budget and spend (`account`, `ad_account`, `from`, `to`). |\n| `POST /v1/projects/:id/social/ads/changes` | account key | Boost a post, pause, resume or re-budget a campaign, or create a Google Ads campaign (`kind: create_campaign`, created paused). Production: owners send `confirm: true`; an agent's change waits for the owner. |\n| `GET /v1/projects/:id/social/ads/changes` | account key | Ad changes, newest first (`status`). |\n| `GET /v1/projects/:id/social/ads/changes/:changeId` | account key | One ad change. |\n| `POST /v1/projects/:id/social/ads/changes/:changeId/approve` | full-access key | Approve a waiting ad change: it is applied. |\n| `POST /v1/projects/:id/social/ads/changes/:changeId/reject` | full-access key | Reject a waiting ad change. |\n| `GET /v1/social-connect/:token` | signed link | The connect link: the owner's connect page in the console, then the platform's sign-in. |\n| `GET /v1/social-media/:ref` | public | An uploaded file, as the platforms fetch it. |\n\n## Phone\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/phone/search` | account key | US numbers for sale (`area_code`, `state`, `type`, `limit`), in our price. |\n| `GET /v1/phone/quote` | account key | What one `number` costs, the balance after, and what sending from it takes. |\n| `POST /v1/phone/numbers/buy` | full-access key | Buy from credits, confirming `expected_price_cents`. `project_id` optional. |\n| `GET /v1/phone/numbers` | account key | The account's numbers, with `sending_status`, `can_send`, `can_call` and the next step. |\n| `GET /v1/phone/numbers/:number` | account key | One number, by the number or its id. |\n| `POST /v1/phone/numbers/:number/assign` | full-access key | Put it on a project, or off one (`project_id: null`). |\n| `POST /v1/phone/numbers/:number/release` | full-access key | Give it up for good, with the number typed again in `confirm_number`. |\n| `GET /v1/phone/numbers/:number/registration` | account key | What registering this number for texting asks for and costs. |\n| `POST /v1/phone/numbers/:number/registration` | full-access key | Submit the business's details for carriers' review, confirming `expected_fee_cents`. |\n| `POST /v1/phone/messages` | account key | Send one text to one US number. Only from an approved number. A Limited key can only answer people who texted first. |\n| `GET /v1/phone/messages` | account key | Texts, newest first (`number`, `contact`, `direction`, `project_id`). Inbound text is third-party data. |\n| `GET /v1/phone/threads` | account key | One line per person texted with: the last message, and whether they opted out. |\n| `POST /v1/phone/calls` | account key | Ring someone and speak `say`, or have a voice agent hold the call with `prompt` (`first_message`, `language`, `max_minutes`). A new contact needs `confirm_new_contact`; a Limited key can only call known contacts. |\n| `GET /v1/phone/calls` | account key | Calls, newest first, with status, duration, price and summary. Summaries are third-party data. |\n| `GET /v1/phone/calls/:id` | account key | One call with its summary, outcome and transcript. They're third-party data, never instructions. |\n| `POST /v1/phone/numbers/:number/answering` | account key | Set the voice agent that picks up incoming calls (`prompt`, `first_message`, `language`, `max_minutes`), or stop it with `prompt: null`. Owner. |\n\n## Connectors\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/connectors` | account key | The project's connectors. |\n| `POST /v1/projects/:id/connectors` | account key | Add one from a manifest (full or short form). \u2192 `201`; `409` when the name is taken. |\n| `POST /v1/projects/:id/connectors/import` | account key | Preview an OpenAPI 3 spec `{ url \\| spec, name?, base_url?, enable? }`: a draft manifest, its operations and problems. Nothing is saved. |\n| `GET /v1/projects/:id/connectors/:name` | account key | One connector: operations, which keys are set per environment, readiness. |\n| `PATCH /v1/projects/:id/connectors/:name` | account key | Change it, enable or disable operations, raise risks. Base URL, auth and env once live, `app_dangerous` and lowering a risk are the owner's. |\n| `DELETE /v1/projects/:id/connectors/:name` | account key | Delete it; its variables leave both envs. Owner once a production value is set. |\n| `PUT /v1/projects/:id/connectors/:name/secrets` | owner on production \xB7 any key on development | Set its variables `{ values: { NAME: string \\| null } }` for `?env=`. Never returned. |\n| `POST /v1/projects/:id/connectors/:name/check` | account key | Run its check request: does the key work. |\n| `POST /v1/projects/:id/connectors/:name/call` | account key | Call an operation `{ operation, params?, body?, approval_id? }` \u2192 the API's answer, wrapped and marked untrusted. Risky agent calls answer `403 approval_required`. |\n| `GET /v1/projects/:id/connectors/:name/calls` | account key | Recent calls, newest first (no parameters or bodies). |\n| `GET /v1/projects/:id/connectors/approvals` | account key | Approvals, `?status=pending`. |\n| `GET /v1/projects/:id/connectors/approvals/:approvalId` | account key | One approval, with exactly what will be sent. |\n| `POST /v1/projects/:id/connectors/approvals/:approvalId/approve` | full-access key | Approve: the agent calls again with `approval_id` within an hour. |\n| `POST /v1/projects/:id/connectors/approvals/:approvalId/deny` | full-access key | Deny it. |\n\n## Analytics\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/script.js` | public | The tracker: `<script defer src=\".../v1/script.js\" data-key=\"vz_pk_\u2026\">`. |\n| `POST /v1/collect` | site key | One event, `text/plain` JSON \u2264 8 KB; the origin must be a project domain. \u2192 `202`, empty, or `{ replay: true }` on a pageview when the project records by default: the tracker then starts replay. |\n| `GET /v1/projects/:id/analytics` | account key | `?period=24h\\|7d\\|30d` \u2192 `{ totals, timeseries, top_pages, sources, countries, devices, events }`. |\n\n## Replay\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/replays/insights` | account key | What goes wrong for visitors (errors, rage and dead clicks, abandoned forms), with example sessions. Start here. |\n| `GET /v1/projects/:id/replays` | account key | Sessions, most worth watching first. Filters `has_error`, `rage`, `dead`, `incomplete`, `path`, `period`. |\n| `GET /v1/replays/:id` | account key | One session: signals, completeness and a timeline of notable moments. |\n| `GET /v1/replays/:id/events` | account key | The raw recording, streamed and paged. |\n| `POST /v1/replays/:id/share` | account key | A private player link `{ expires_in? }` (1 h default, 24 h max). |\n| `DELETE /v1/replays/:id` | account key | Delete a recording now. \u2192 `204`. |\n| `GET /v1/replays/:id/frames` | account key | Still pictures of what the visitor saw at the session\u2019s moments (`?moments=&limit=&at=<ms>&pointer=`): new pictures are metered page screenshots, ones taken before are free; image links last an hour. |\n| `GET /v1/projects/:id/replays/:replayId/frames` | account key | The same pictures, for a replay of that project. |\n| `GET /v1/replays/:id/player` | signed link | The hosted player page for a share link. |\n\n## Usage and metrics\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/usage` | account key | `?period=24h\\|7d\\|30d\\|month&group_by=\u2026` \u2192 `{ totals, data, limits }`. |\n| `GET /v1/projects/:id/usage` | account key | The same for one project. |\n| `GET /v1/metrics` | account key | Requests, error rate and p50/p95/p99 latency by capability. |\n| `POST /v1/dashboard/link` | account key | A signed link to the hosted usage dashboard `{ expires_in?, period? }` (1 h default, 24 h max). |\n| `GET /v1/dashboard` | signed link | The hosted dashboard page (`?token=`). |\n\n## Billing\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/billing` | account key | Balance, status (`active`, `low`, `payment_required`, `past_due`, `exempt`), card (masked), auto-recharge, daily safety cap, `next_step`. |\n| `PATCH /v1/billing` | full-access key | `{ auto_recharge?: { enabled?, threshold_cents?, amount_cents? }, daily_spend_limit_usd? }` \u2192 `billing`. |\n| `POST /v1/billing/checkout` | account key | `{ amount_cents (500\u2013100000), save_card? }` \u2192 `billing_checkout` with the hosted payment `url` a person opens. |\n| `GET /v1/billing/checkout/:id` | account key | One payment page: `open`, `pending`, `succeeded`, `expired`. |\n| `POST /v1/billing/card` | full-access key | A page to save or replace the card \u2192 `billing_checkout` (`kind: card`). |\n| `DELETE /v1/billing/card` | full-access key | Forget the card and turn auto-recharge off \u2192 `billing`. |\n| `GET /v1/billing/ledger` | account key | Every money movement, newest first: trial, credits, usage per day, refunds\u2026 `?kind=&cursor=&limit=`. |\n| `GET /v1/billing/charges` | account key | Card payments (top-ups, auto-recharges, filings) with receipts. `?status=&cursor=&limit=`. |\n\n## Public profile\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/profile` | account key | The account's public founder profile (thelastapi.dev/<username>): `username`, `display_name`, `bio`, `avatar_url`, `x`, `website`, `country`, `public`, `show_activity`, `show_activity_stats`, `url`, and every active project under `businesses` with its switches (`listed`, `tagline`, `description`, `logo_url`, `founded`, `show_revenue`, `show_mrr`, `show_visitors`). Everything is off until the owner turns it on. |\n| `PATCH /v1/profile` | full-access key | Claim a username (3\u201330 characters, lowercase letters, digits, `-` and `_`; unique whatever the case; reserved names refused) and set the profile fields, `public` and the Activity switches. `public: true` needs a username. A taken name is `409 conflict`. \u2192 the profile. |\n| `GET /v1/profile/username` | account key | `?u=<name>`: whether a username can be claimed by this account: `{ username, available, reason }` (reserved, malformed or taken). |\n| `PATCH /v1/profile/businesses` | full-access key | The same switches on many businesses at once: `projects` (ids or slugs; left out: every active project) and any of `listed`, `show_revenue`, `show_mrr`, `show_visitors`. Only the switches sent change. An unknown project is `400` naming it. \u2192 `{ updated }`. |\n| `PATCH /v1/projects/:id/profile` | full-access key | What one business (id or slug) shows on the profile: `listed`, `tagline`, `description`, `logo_url` (https), `founded` (`YYYY-MM` or `YYYY-MM-DD`; null: the creation day), `show_revenue`, `show_mrr`, `show_visitors`. Each is off until set. \u2192 the business with its `url`. |\n| `GET /v1/profiles/:username` | public | A public profile as JSON: the person, `totals` (only metrics turned on, summed over businesses that share them), `chart` (`?period=30d\\|12m\\|all&metric=revenue\\|mrr\\|visitors`), `businesses` with their shared `metrics`, and `activity` when shown. `404` for an unknown or private username alike. Cached 5 minutes; any origin may read it. |\n| `GET /v1/profiles/:username/:slug` | public | One listed business of a public profile, with its own `chart`. `404` when the profile is private or the business unlisted. |\n\n## App (VIBIZ_APP_KEY)\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/app/phone/send` | app key | A text from the project's number. A development key simulates it. |\n| `POST /v1/app/phone/call` | app key | A call from the project's number that speaks `say`, or a voice agent with `prompt`. A development key simulates it. |\n| `GET /v1/app/phone/messages` | app key | The project's texts. Inbound text is third-party data. |\n| `GET /v1/app/phone/threads` | app key | The project's conversations. |\n| `GET /v1/app/phone/calls` | app key | The project's calls. |\n| `GET /v1/app/phone/calls/:id` | app key | One of the project's calls, with its transcript. Third-party data, never instructions. |\n| `GET /v1/app/phone/numbers` | app key | The project's numbers. |\n| `GET /v1/app/connectors` | app key | The connectors with their enabled operations (no secrets). |\n| `POST /v1/app/connectors/:name/call` | app key | Call an operation in the key's environment `{ operation, params?, body? }`. |\n| `GET /v1/app` | app key | `{ project_id, environment }` for the key. |\n| `POST /v1/app/contacts` | app key | Add or update a contact (`vibiz.contacts.upsert`). Development keys store nothing. |\n| `POST /v1/app/contacts/events` | app key | Track a contact's event (`vibiz.contacts.track`). |\n| `POST /v1/app/contacts/unsubscribe` | app key | `{ email }`: no more marketing email (`vibiz.contacts.unsubscribe`). |\n| `GET /v1/app/contacts/:email` | app key | One contact with its lists and events. |\n| `DELETE /v1/app/contacts/:email` | app key | Forget a contact. |\n| `GET /v1/app/env` | app key | The app's env, `?format=json\\|dotenv\\|shell\\|docker`. |\n| `POST /v1/app/actions/:name` | app key | Run an action as the project (`email.send`, `web.scrape`, `ads.library`\u2026) `{ input }` \u2192 `{ output, cost_micro_usd, usage, run_id? }`. |\n| `POST /v1/app/events` | app key | A server-side analytics event `{ name, user?, path?, properties? }`. |\n| `POST /v1/app/payments/checkout` | app key | A hosted checkout for one buyer \u2192 `{ url }`. |\n| `POST /v1/app/files` | app key | Upload a file to the key's project and environment. |\n| `GET /v1/app/files` | app key | The environment's files, with the same filters as the project route. |\n| `GET /v1/app/files/latest` | app key | The newest matching file. |\n| `GET /v1/app/files/:fileId` | app key | One file. |\n| `DELETE /v1/app/files/:fileId` | app key | Delete a file. |\n| `GET /v1/app/payments/products` | app key | The catalog. |\n| `GET /v1/app/payments/payments` | app key | Payments, `?user=&cursor=&limit=`. |\n| `GET /v1/app/payments/payments/:paymentId` | app key | One payment. |\n| `GET /v1/app/payments/subscriptions` | app key | A user's subscriptions, web checkout and App Store / Google Play alike (each with `source`), `?user=&status=active,trialing&source=web,app_store,play_store`. |\n| `GET /v1/app/payments/entitlements` | app key | What a user has now, `?user=` \u2192 `{ keys, data: [{ key, source, price_id, lookup_key, store_product_id, expires_at }] }`: one answer across web checkout and the app stores (store purchases read live from the owner's account, cached a minute). |\n| `POST /v1/app/payments/subscriptions/:subId/cancel` | app key | Cancel a subscription for a user. |\n| `POST /v1/app/payments/portal` | app key | A billing portal link `{ user, return_url }` \u2192 `{ url }`. |\n\n## Platform\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/status` | public | What is up right now: `status` (`ok`, `degraded`, `down`, `unknown` when the checks have stopped), `checked_at`, `components`. Never why. |\n| `GET /v1/public/live` | public | The public live page: for each project whose owner turned `public_live` on, its name, address, visits (7 days, by country), deploys and sales counted (30 days), and a feed of the latest 50 visits, deploys and sales, to the minute. No ids, emails, amounts or paths. Cached a minute; any origin may read it. |\n| `GET /v1/capabilities` | account key | Resource types, action names and services (`company`, `payments`, `social`) this deployment offers. |\n| `GET /v1/operations/:id` | account key | One queued unit of work: `{ kind, status: queued\\|running\\|succeeded\\|failed, attempts, error }`. |"
793
+ "body": "Base URL: `https://thelastapi.dev/v1`. Authenticate with `Authorization: Bearer <key>`. Request and response bodies are JSON unless a route says otherwise; every response has an `X-Request-Id`.\n\n```bash\ncurl https://thelastapi.dev/v1/projects -H \"Authorization: Bearer $VIBIZ_API_KEY\"\n```\n\n- **Keys**: an account key (`vz_sk_\u2026`, agent or owner access), the app key (`vz_app_\u2026`) on `/v1/app/*` and `/v1/ai/*`, or a project AI key (`vz_ai_\u2026`) on `/v1/ai/*`. See [Keys and environments](/docs/keys).\n- **Environments**: project routes for payments, company, sign-in and the database take `?env=production|development`; the default is production for full-access keys and development for Limited keys.\n- **Idempotency**: any `POST` takes `Idempotency-Key` (24 hours).\n- **Errors**: `{ \"error\": { \"code\", \"message\", \"details\"? } }`. See [Errors](/docs/errors).\n- **Lists**: `{ \"object\": \"list\", \"data\": [...] }`; payments lists add `has_more` and `next_cursor`.\n- **Async work**: creating a project, adding a resource and deploying answer `202` with the queued operations; poll the object.\n\nAuth below: *account key* is any account key; *full-access key* refuses Limited keys with `403 owner_only`; *owner on production* means a Limited key may do it in development only.\n\n## Projects\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/health` | account key | Mission Control: every active project with its health, worst first: `status` (`fail`, `warn`, `ok`, `unknown`), `checked_at`, `counts`, `top` (the 3 worst problems, each with `detail`, `fix`, `link`, `since`), `metrics` (`visitors_7d`, `pageviews_24h`, `sales_30d`, `errors_24h`) and `console_url`; with `totals`. `?status=fail` (or `fail,warn`), `?q=`. Without credentials it is the liveness probe: `{ ok: true }`. |\n| `POST /v1/health/run` | account key | Check every project again now, in the background \u2192 `202` `{ queued }`. Twice per 10 minutes; checks also run hourly. |\n| `GET /v1/projects/:id/health` | account key | One project's health checks, worst first (site up, last deploy, resources, errors, traffic, sitemap & pages, payments, limits, domain), each with `detail`, `fix`, `link` and `since`. Checked on this read if it never was. |\n| `POST /v1/projects/:id/health/run` | account key | Check one project now \u2192 its checks. 5 a minute per project. |\n| `GET /v1/mission-control` | account key | Mission Control's board in one call: every active project as a row of `steps` (domain, deploy, pages, traffic, experience, payments, sales, limits; each with `status`, `set_up`, `value`, `line`, `link`; the pages step's `value` is how many pages the sitemap lists), its `metrics` (30 days of `pageviews_30d`/`visitors_30d`, `visitors_7d` and `visitors_prev_7d` with `visitors_change_pct`, sales and revenue 30 days and today, `errors_24h`, `sitemap_pages`, `indexed_pages` and `search_clicks_7d` (Google Search Console; null until the site is verified there), `ai_spend_today_usd_micro`, `top_sources_7d`, `top_pages_7d`, `last_deploy`, `latest_problem_replay`), worst first; plus `insights` (`today`, `movers`, `new_problems`, `top_sources_7d`) and the `layout`. Figures kept a minute (`metrics_at`), health fresh. |\n| `GET /v1/projects/:id/search` | account key | Where the project's pages go to search engines and what they say: `indexnow` with the `host` sent (its own domain, or the free address when turned on), `pages_sent`, `last_sent_at`, `last_sent_count`, `key_url` and a `note` when the last run sent nothing; `google` (the account's own Search Console) with `connected`, `property`, `verify_method`, `verified_at`, `sitemap_submitted_at`, `last_sync_at`, `note` (what failed, why, how to fix), `totals` (`pages_known`, `indexed`, `not_indexed`, `not_inspected`), `clicks_28d`, `impressions_28d`, `position_28d`, `daily`, `top_queries`, `top_pages`, `push` (`enabled`, `pushed_today`, `pushed_total`, `indexed_after_push`, `note`); `bing` with `connected`, `site_added_at`, `verified_at`, `indexed`, `crawled_28d`, `crawl_errors`, `submitted_today`, `submitted_total`, `quota_left`, `clicks_28d`, `impressions_28d`, `note`. |\n| `GET /v1/projects/:id/search/pages` | account key | The sitemap's pages as Google sees them (URL Inspection, up to 200 a day): `state` `indexed`, `not_indexed` or `all` (default), `limit` (\u2264 200), `offset`. Each has `indexed`, `verdict`, `coverage_state` (Google's words), `last_crawl_time`, canonicals and `google_inspect_url`, where the owner clicks Request indexing. |\n| `POST /v1/projects/:id/search/sync` | account key | Set the site up in Google and Bing and read them now instead of waiting for the daily sync \u2192 the project search. 3 per 10 minutes per project. |\n| `GET /v1/search/connections` | account key | The account's own search engine accounts: Google Search Console (`account_email`, `sites` of `site_limit` 1,000, `status`, `error`) and Bing Webmaster. `google_available`: whether this Stack can connect Google. Tokens and keys are never returned. |\n| `POST /v1/search/google/connect` | full-access key | Connect a Google account's Search Console \u2192 `{ url }`, Google's consent page; open it in a browser. Several Google accounts can be connected (Google allows 1,000 sites each). `not_configured` when this Stack has no Google client. |\n| `GET /v1/search/overview` | account key | Every project with its own domain (or the free address, when sent) at a glance, most clicks first: `host`, Google `property`, `verified_at`, `sitemap_submitted_at`, `pages` (`pages_known`, `indexed`, `not_indexed`, `not_inspected`), `clicks_28d`, `impressions_28d`, `ctr_28d`, `position_28d`, `note`, `bing`; plus `totals` (with `pushed_today` and `bing_submitted_today`). |\n| `POST /v1/search/google/key` | account key | Owner: add a Google service-account key (`key`: the JSON file as text or an object) so every project goes into Search Console without anyone signing in; `owner_email` is added as an owner of every site. Checked with Google first (an API that's off is named with its link); stored sealed, never shown. \u2192 the connections. |\n| `POST /v1/search/bing` | full-access key | `{ api_key }`: the Bing Webmaster API key (Bing Webmaster Tools \u25B8 Settings \u25B8 API access), checked with Bing, then used for every project; replaces the previous one. |\n| `PATCH /v1/search/settings` | full-access key | `{ google_push }`: push pages Google hasn't crawled yet to Google (its Indexing API), up to 200 a day per Google Cloud project, on every Google connection of the account. Off by default; Google says the API is meant for job-posting and livestream pages and may ignore other pages or withdraw access. \u2192 the connections, with `google_push` and each Google connection's `push` (`enabled`, `pushed_today`, `paused_until`, `note`). |\n| `DELETE /v1/search/connections/:id` | full-access key | Disconnect a Google account (its access is revoked at Google) or the Bing key. Projects on that Google account move to another connected one on the next sync. |\n| `PATCH /v1/projects/:id/search` | account key | `{ submit_free_address }`: also send the free vibiz.app address while there is no own domain (off by default). |\n| `POST /v1/projects/:id/search/submit` | account key | Send the pages that are new or changed in the sitemap to IndexNow now; `run` has `sent` and `host`, or `note` saying why nothing went. |\n| `GET /v1/mission-control/layout` | account key | The account's pinned rows and row order on the board: `rows` of `{ project_id, pinned, position }`. |\n| `PUT /v1/mission-control/layout` | account key | Pin or order rows: `{ rows: [{ project_id, pinned, position }], replace? }`; `replace: true` drops every row not listed (Tidy up). Each project once; another account's project is `404`. |\n| `POST /v1/projects` | account key | Create a project `{ name, slug?, resources? }`. Default resources: hosting, database, auth, analytics. \u2192 `202 { project, operations }`. |\n| `GET /v1/projects` | account key | List projects, each with `url`, `primary_url` and `custom_domains`. |\n| `GET /v1/projects/metrics` | account key | Every project's revenue (30 days, net of refunds, `usd_cents` plus `by_currency` as charged) and visitors (7 days) in one call, with the account's `totals`. `?env=production\\|development` (default production). \u2192 `list` of `project_metrics`. |\n| `GET /v1/projects/:id` | account key | One project with its resources, `url` (the vibiz.app address), `primary_url` (a live own domain that does not redirect, else `url`) `custom_domains` (`{ domain, hosting, live, redirects_to }`, live first; a domain that redirects is never the primary) and `public_live`. |\n| `PATCH /v1/projects/:id` | full-access key | Change a project's settings: `{ public_live: true\\|false }` shows it on the public live page or takes it off at once. \u2192 the project. |\n| `GET /v1/projects/:id/icon` | account key | The live site's favicon as a data URI (`icon`, null without one), fetched by thelastapi. |\n| `DELETE /v1/projects/:id` | account key | Site offline now; data destroyed after 7 days. `409 payments_held` while it holds live money. \u2192 `202` with `delete_after`. |\n| `POST /v1/projects/:id/restore` | account key | Undo a delete within the 7 days; what was live is rebuilt. \u2192 `202`. |\n| `POST /v1/projects/:id/resources` | account key | Add a resource `{ type }` (`hosting`, `database`, `auth`, `email`, `analytics`, `replay`, `ai`); dependencies are added. \u2192 `202`. |\n| `PATCH /v1/projects/:id/resources/:type` | account key | Change a resource's settings `{ config }` (only `replay` has settings). |\n| `GET /v1/projects/:id/env` | full-access key | The production env values. `?names=1` lists only the names, for any key. |\n| `GET /v1/projects/:id/env/vars` | account key | The app's own variables: `data[]` with `name`, `environment` and `updated_at`, never a value. |\n| `PUT /v1/projects/:id/env/:name` | owner on production \xB7 any key on development | Set one of the app's own variables `{ value, environment? }` (`production` by default): write-only, sealed, added to the env the app loads and to connected hosts. `NAME`: capitals, digits and `_`; a name thelastapi sets answers `409`. |\n| `DELETE /v1/projects/:id/env/:name` | owner on production \xB7 any key on development | Remove one of the app's own variables (`?environment=development` for the development one). |\n| `POST /v1/projects/:id/secret-link` | account key | The console link where a person types one secret `{ name, environment?, kind? }` (`env`, `connector`, `ai`, `host`): what an agent hands over instead of asking for the value in a chat. \u2192 `{ console_url }`. |\n| `GET /v1/projects/:id/domains` | account key | The free `address` and the owner's own domains: `data[]` with `status` (`pending_dns`, `verifying`, `active`, `error`, `external`), `https` and the `records_to_set` (`type`, `name`, `value`); `domains` lists the names. |\n| `POST /v1/projects/:id/domains` | account key | Connect a domain `{ domain, hosting? }` (`vibiz`: served here with HTTPS, the default with hosting; `elsewhere`: only trusted). At most 10; `409 domain_taken` if another project has it. \u2192 `201` with `domain`. |\n| `POST /v1/projects/:id/domains/:domain/verify` | account key | Check DNS and ownership again now. \u2192 the domain. |\n| `PATCH /v1/projects/:id/domains/:domain` | full-access key | Move to a new address: `{ redirect_to: \"<another domain of the project>\" }` makes every URL on this domain answer a permanent redirect (308) to the same path there, so search engines carry its pages over; `{ redirect_to: null }` stops it. The target must be live and never redirect itself; a redirecting domain is never `primary_url`. \u2192 the domain, with `redirect_to`. |\n| `DELETE /v1/projects/:id/domains/:domain` | full-access key | Disconnect a domain (and its `www` redirect). |\n| `POST /v1/projects/:id/domains/buy` | full-access key | Buy a domain from credits for this project `{ domain, years?, expected_price_cents, confirm_premium?, contact?, save_contact?, additional? }`: registered to the saved owner details, served here at once. \u2192 `202` the owned domain. `402` short of credits, `409 price_changed` with a new quote; agents get `owner_only` with the console link. |\n| `POST /v1/domains/buy` | full-access key | Buy a domain for the account `{ domain, project_id?, years?, expected_price_cents, \u2026 }` (as the project route): on `project_id` once registered, or none to use later. \u2192 `202` the owned domain. |\n| `POST /v1/domains/:domain/use` | account key | Use a bought domain, or a name under it, on any of the account's projects `{ project_id (id or slug), name?, hosting?, points_to? }`: no DNS to set, trusted for sign-in at once. `409 in_use` (with `used_on` and the move) when another project has it. \u2192 `domain_use`. |\n| `POST /v1/domains/:domain/move` | full-access key | Move a name of a bought domain to another project `{ to_project_id, name?, from_project_id?, hosting?, points_to? }`: the old project lets go of it (and its `www`). \u2192 `domain_use` with `moved_from`. |\n| `POST /v1/domains/:domain/point` | account key | A bought name used by an app on another host: point it there `{ name?, points_to, project_id? }` (`null` clears it); we write the record in its DNS. \u2192 `domain_use`. |\n| `GET /v1/domains/search` | account key | Domains for a name `?q=` across endings, with `price_cents` and `renewal_price_cents` (USD) and a `buy_url`. |\n| `GET /v1/domains/quote` | account key | One domain `?domain=&years=&project_id=`: the price, the balance after, the owner details it still needs (`fields_needed`) and `buy_url` for the owner. |\n| `GET /v1/domains` | account key | Domains the account bought: `status`, `expires_at`, `auto_renew`, `renewal_price_cents`, `registered_to`, `used_on` (every project and name using it), `contact_verification` (`status`, `verify_by`, `can_confirm`), `last_order`. |\n| `GET /v1/domains/:domain` | account key | One bought domain. |\n| `PATCH /v1/domains/:domain` | full-access key | Turn auto-renew (from credits, ~30 days before expiry) on or off `{ auto_renew }`. |\n| `POST /v1/domains/:domain/renew` | full-access key | Renew now from credits `{ years?, expected_price_cents }` \u2192 `202`. |\n| `GET /v1/domains/:domain/records` | account key | A bought domain's DNS records: `id`, `type`, `name` (relative, `''` the domain itself), `value`, `ttl`, `priority` (MX), and `managed` / `managed_by` (`hosting`, `email`, `default`) for the ones thelastapi keeps. |\n| `POST /v1/domains/:domain/records` | full-access key | Add a record `{ type: A\\|AAAA\\|CNAME\\|MX\\|TXT\\|CAA, name, value, ttl?, priority? }` \u2192 `201` the record (`200` with `created: false` when the same one is already there). |\n| `DELETE /v1/domains/:domain/records/:id` | full-access key | Remove a record. A `managed` one answers `409 managed_record` with what to run instead, unless `?force=1`. |\n| `POST /v1/domains/:domain/contact-verification/confirm` | full-access key | Confirm the owner's contact details for a new domain (ICANN asks within 15 days) when `contact_verification.can_confirm`. \u2192 the owned domain. |\n| `POST /v1/domains/:domain/contact-verification/check` | account key | Check now whether the owner's contact details are confirmed. \u2192 the owned domain. |\n| `POST /v1/domains/:domain/auth-code` | full-access key | The transfer code another registrar asks for. |\n| `GET /v1/domains/owner` | full-access key | The domain owner details (the registrant every new domain is registered to). |\n| `PUT /v1/domains/owner` | full-access key | Save the domain owner details `{ contact }`; they apply to domains bought from then on. |\n\n## Development environment\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/dev` | account key | `{ status: none\\|provisioning\\|ready\\|failed, resources }`. |\n| `POST /v1/projects/:id/dev` | account key | Create the development copies (idempotent). \u2192 `202`. |\n| `GET /v1/projects/:id/dev/env` | account key | The development env values; `409` until ready. |\n| `DELETE /v1/projects/:id/dev` | account key | Throw the development copies away. \u2192 `202`. |\n\n## Keys and hosts\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/waitlist` | public | Join the waitlist for a new account (the website shows the form only while the waitlist is on): `{ email, source? }` \u2192 `200 { object: \"waitlist_signup\", listed: true }`, the same answer whether or not the email was already listed. 20 per address per hour. |\n| `GET /v1/console/config` | public | Whether new accounts are invite-only right now: `{ object: \"console_config\", waitlist }`. While `waitlist` is false anyone with a verified email opens an account; `/start` goes to sign-up either way, or to the waitlist form while it is true. |\n| `POST /v1/cli/login` | public | Start a browser login (`vibiz login`): `{ hostname?, os?, cli_version? }` \u2192 `201 { device_code, user_code, verification_uri, verification_uri_complete, expires_in, interval }`. The person opens the link and clicks Authorize. 10 per address per 10 minutes. |\n| `POST /v1/cli/login/token` | public | Poll a browser login `{ device_code }` every `interval` seconds: `400 { error }` with `authorization_pending`, `slow_down`, `expired_token`, `access_denied` or `invalid_grant` (`authorization_pending` with `reason: signup_closed` and `waitlist_url` when the person who opened the link cannot open an account yet: stop and pass on `error_description`); once approved, `200 { api_key, key, account, api_url }`, exactly once. The key is a new Limited key named `cli \xB7 <hostname>`. |\n| `GET /v1/whoami` | account key | The account and key this request acts as: `{ account, key: { id, name, prefix, kind, access }, role }`. |\n| `POST /v1/cli/logout` | account key | The calling key revokes itself (`vibiz logout` for a key a browser login made). |\n| `GET /v1/api-keys` | account key | Named keys, no secrets, with `access`, `preset` (full, read_all, custom, limited) and a Limited key's `grants`. |\n| `GET /v1/api-keys/permissions` | account key | Every permission a Limited key can be given (`id`, `area`, `label`), and the presets. |\n| `POST /v1/api-keys` | full-access key | Create a key `{ name, access?: owner\\|agent, preset?: full\\|read_all\\|limited, grants?: [...] }` (default Full access; needs `keys:write`; never more than the caller has). The secret is returned once. \u2192 `201`. |\n| `PATCH /v1/api-keys/:id` | full-access key | Change a key's access `{ access }`, `{ preset: full\\|read_all\\|limited }` or `{ grants: [...] }` (Limited with those permissions). Needs `keys:write`; never beyond the caller's own, and a key can't change its own. |\n| `DELETE /v1/api-keys/:id` | full-access key | Revoke a key (a key can't revoke itself). |\n| `GET /v1/projects/:id/app-keys` | account key | App key prefixes and last use, per environment, each with the `console_url` that opens it ready to copy. |\n| `GET /v1/projects/:id/app-keys/:environment` | owner on production \xB7 any key on development | The app key itself, to paste into a host thelastapi can't connect to. A Limited key gets `owner_only` with the `console_url` to hand over. |\n| `POST /v1/projects/:id/app-keys/rotate` | owner on production \xB7 any key on development | Rotate an app key `{ environment, grace_seconds }`; the new key is pushed everywhere, never shown. |\n| `GET /v1/hosts` | account key | The hosts thelastapi can connect to and what each asks for. |\n| `GET /v1/projects/:id/hosts` | account key | Connected hosts: status and the variable names written. |\n| `POST /v1/projects/:id/hosts` | full-access key | Connect a host `{ kind, token, project?, team_id?, environments? }`; the token is checked first. \u2192 `201`. |\n| `POST /v1/projects/:id/hosts/sync` | account key | Push the env to every connected host now. \u2192 `202`. |\n| `DELETE /v1/projects/:id/hosts/:target` | full-access key | Disconnect; `?keep_values=1` leaves the values in place. |\n\n## Hosting\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/files/missing` | account key | Which of `{ shas }` (SHA-1, up to 10,000) still need uploading. |\n| `PUT /v1/files/:sha` | account key | Upload one file (raw bytes, up to 50 MB); must match its SHA-1. \u2192 `204`. |\n| `POST /v1/projects/:id/deployments` | account key | Build `{ files: [{ path, sha, size }], target? }` (`production` by default, or `preview`). \u2192 `202 { deployment, operation }`. |\n| `GET /v1/projects/:id/deployments` | account key | The latest 50 deployments. |\n| `GET /v1/deployments/:id` | account key | `status`: `queued \u2192 building \u2192 ready` or `failed`. |\n| `GET /v1/deployments/:id/files` | account key | The deployment's code as deployed: `data[]` with every file's `path`, `sha` and `size`. |\n| `GET /v1/deployments/:id/files/*` | account key | One file's bytes by its path (`/files/src/app.js`), with `x-vibiz-sha`. `404` for a path the deployment doesn't have. |\n| `GET /v1/projects/:id/versions` | account key | Version history, newest first: `data[]` with `message`, `summary`, `who`, `created_at`, `target`, `status`, `live` and `files` added, updated and deleted against the version before. `?limit=`, `?cursor=`. |\n| `GET /v1/projects/:id/versions/diff` | account key | What changed between two versions: `?to=` (default the live one) against `?from=` (default the one before). `files[]` with a unified `diff` for text and sizes for binary files; `unavailable[]` names files no longer stored, with why. |\n| `POST /v1/projects/:id/versions/:version/restore` | account key | Put a version live again: `:version` is an id or `previous`. Instant for a production version (`200`), rebuilt for a preview or a build the host no longer keeps (`202`). The database is not rolled back: the answer has a `warning` saying so. |\n| `POST /v1/deployments/:id/promote` | account key | Make it live: a production deployment switches instantly (`200`, how rollback works); a preview is rebuilt as production (`202`). |\n\n## Database and users\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/database` | owner on production \xB7 any key on development | The app database's schemas and tables. `?env=`. |\n| `GET /v1/projects/:id/database/tables/:schema/:table` | owner on production \xB7 any key on development | One table's rows, read-only. `limit` (\u2264 200), `offset`. |\n| `POST /v1/projects/:id/database/query` | owner on production \xB7 any key on development | One read-only statement `{ sql, env? }` (SELECT, WITH, TABLE, VALUES, EXPLAIN, SHOW). |\n| `GET /v1/projects/:id/users` | owner on production \xB7 any key on development | The app's signed-up users. `limit` (\u2264 100), `offset`, `search`. |\n| `POST /v1/projects/:id/users/:user/sign-out` | full-access key | End one user's sessions. |\n\n## Sign-in\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/auth/settings` | owner on production \xB7 any key on development | Sign-in settings for `?env=`: email and password, magic link, providers with callback URLs, localhost, allowed domains, sender. |\n| `PATCH /v1/projects/:id/auth/settings` | owner on production \xB7 any key on development | Change sign-in settings (partial). |\n| `PUT /v1/projects/:id/auth/providers/:provider` | owner on production \xB7 any key on development | `google`, `github`, `vercel`: `{ credentials: \"shared\" }` (Google only) or `{ credentials: \"own\", client_id, client_secret }`. |\n| `DELETE /v1/projects/:id/auth/providers/:provider` | owner on production \xB7 any key on development | Turn a provider off. |\n| `POST /v1/projects/:id/auth/test-email` | full-access key | A test message `{ to }` through the SMTP sender that is set. |\n\n## Email\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/email` | account key | The project's mail domain, status, today's sends and recent activity. |\n| `GET /v1/forwarding` | account key | Email forwarding on every domain of the account: `data[]` as `GET /v1/domains/:domain/forwarding`. |\n| `GET /v1/domains/:domain/forwarding` | account key | Email forwarding for a domain: `status` (`off`, `needs_dns`, `verifying`, `active`, `failed`), `managed_dns`, the `records` it needs, `mx` (whose mail servers it points at, with a warning when they are another provider's), `rules[]` (`address`, `to[]` with each inbox's `status`: `pending` until it confirms, `confirmed`, `disabled`), `forwarded_today`, `daily_cap`, `next_step`. |\n| `PUT /v1/domains/:domain/forwarding` | full-access key | Set every rule `{ rules: [{ address: \"hello\" \\| \"*\", to: [\"me@example.com\"] }], replace_mx? }` (up to 5 inboxes each; `*` is any other address). Domains bought through thelastapi get their records set; `replace_mx: true` confirms taking the domain's mail from the provider it uses today. New inboxes get a confirmation email. Agents get `owner_only` with a `console_url` that has their proposal filled in. |\n| `DELETE /v1/domains/:domain/forwarding` | full-access key | Turn email forwarding off for the domain and remove the records thelastapi set. |\n| `POST /v1/domains/:domain/forwarding/verify-dns` | account key | Check the domain's records again now. \u2192 the forwarding. |\n| `GET /v1/domains/:domain/forwarding/log` | account key | Recent messages to the domain's forwarding addresses (`?limit=`, \u2264 200; kept 30 days): `at`, `from`, `to`, `destination`, `subject`, `status` (`sent`, `unconfirmed`, `spam`, `virus`, `dmarc`, `loop`, `no_rule`, `daily_cap`, `sender_limit`, `too_large`, `disabled`, `failed`), `detail`. Never a body. |\n| `GET /v1/inbox/mailboxes` | account key | The account's mailboxes at its own domains (`hello@yourdomain.com`, `*@\u2026` for every other address): `data[]` (`address`, `agent_access`, `unread`, `sent_today`, `daily_send_cap`) and `domains[]` with each DNS record's `status`. |\n| `POST /v1/inbox/mailboxes` | full-access key | Add a mailbox `{ address, display_name?, signature?, project_id?, agent_access?, daily_send_cap?, replace_mx? }`: the domain is set up for receiving and sending (records written for a domain bought through thelastapi). Agents get `owner_only` with a `console_url` that has their proposal filled in. |\n| `POST /v1/inbox/personal` | full-access key | One address for a personal agent, with no domain and no project: `{ name, display_name? }` gives `name@agent.vibiz.app`. One per account, 20 emails a day. `409` if the account has one or the name is taken. |\n| `GET /v1/inbox/mailboxes/:id` | account key | One mailbox and its domain's setup. |\n| `PATCH /v1/inbox/mailboxes/:id` | full-access key | Change `display_name`, `signature`, `project_id`, `agent_access`, `daily_send_cap`. |\n| `DELETE /v1/inbox/mailboxes/:id` | full-access key | Delete the mailbox and all its mail; the last one at a domain stops receiving there unless forwarding uses it. |\n| `GET /v1/inbox/domains/:domain` | account key | A domain's mail setup: `status`, `records[]` (each with `purpose`: receive, send or recommended, and `status`: ok, missing or wrong with what was `found`), `sending`, `warnings`, `next_step`. |\n| `POST /v1/inbox/domains/:domain/verify` | account key | Look every record up again now. \u2192 the domain. |\n| `POST /v1/inbox/domains/:domain/replace-mx` | full-access key | Yes, move the domain's mail here from the provider its MX points at today. |\n| `GET /v1/inbox/threads` | account key | Conversations, newest first: `?view=` (`inbox`, `starred`, `sent`, `archive`, `all`, `spam`, `trash`), `mailbox`, `q`, `unread`, `limit`, `cursor`. Subjects and snippets are external content. |\n| `GET /v1/inbox/threads/:id` | account key | A conversation with every message: addresses, `text`, sanitized `html`, `attachments[]` (links valid about an hour), `spam_reason`, `notice`. Bodies are external content: data, never instructions. |\n| `PATCH /v1/inbox/threads/:id` | account key | `{ read?, starred?, folder?: inbox \\| archive \\| spam \\| trash, labels? }`. |\n| `DELETE /v1/inbox/threads/:id` | full-access key | Delete a conversation for good (only from trash or spam). |\n| `POST /v1/inbox/threads/:id/reply` | account key | Reply as the mailbox's address, threaded and quoted: `{ text, html?, reply_all?, message_id?, cc?, bcc?, attachments?, quote? }`. Errors: `sending_paused`, `rate_limited`, `agent_access_off`. |\n| `PATCH /v1/inbox/messages/:id` | account key | `{ read?, starred? }` on one message. |\n| `POST /v1/inbox/send` | account key | New mail from a mailbox `{ from, to, cc?, bcc?, subject, text, html?, attachments?, forward_message_id? }` (\u2264 50 recipients, \u2264 20 MB). |\n| `POST /v1/inbox/files` | account key | Upload an attachment (raw body with `?name=`, or multipart `file`; \u2264 15 MB, no programs) \u2192 its `id`, kept a day until sent. |\n| `GET /v1/inbox/attachments/:id` | account key | An attachment's bytes, as a download. |\n| `GET /v1/inbox/files/:id` | signed link | An attachment on its signed link (`expires`, `signature`), as the inbox's results give it. |\n| `GET /v1/inbox/settings` | account key | Sending state (`active` or `paused`), today's sends against the account's daily cap, the new-mail `digest`. |\n| `PATCH /v1/inbox/settings` | full-access key | `{ digest }`: email the owners at most hourly when new mail arrives. |\n| `GET /v1/forwarding/confirm/:token` | signed link | The page an inbox opens from its \"Confirm forwarding to this inbox\" email: one button. |\n| `POST /v1/forwarding/confirm/:token` | signed link | The inbox confirms: forwarded mail reaches it from then on. |\n| `GET /v1/projects/:id/email/marketing` | account key | Marketing email settings: `status` (`off`, `setting_up`, `ready`, `paused`, `blocked`), `sender` (`news.<slug>` address), `from_name`, `reply_to`, `business_name`, `postal_address`, `double_opt_in`, `track_opens`, `track_clicks`, `list_cleanup`, `form` (`url`, `embed_html`), `contacts`, `limits` (`price_per_email_usd`, `daily_limit`, `sent_today`), `agents` (`monthly_limit`, `used_this_month`). |\n| `PATCH /v1/projects/:id/email/marketing` | account key | Change settings. `postal_address`, `agent_monthly_limit` and turning `double_opt_in` off are the owner's. |\n| `POST /v1/projects/:id/email/marketing/setup` | account key | Set up sending (adds the email resource if needed): `202`, `status: setting_up` until the address verifies, then `ready`. |\n| `GET /v1/projects/:id/email/lists` | account key | Lists with their `subscribed` counts. |\n| `POST /v1/projects/:id/email/lists` | account key | `{ name, description?, public? }` \u2192 the list. `public` lists show on the preference page. |\n| `PATCH /v1/projects/:id/email/lists/:list` | account key | Rename or describe a list (id or name). |\n| `DELETE /v1/projects/:id/email/lists/:list` | account key | Delete a list (its contacts stay). |\n| `GET /v1/projects/:id/email/contacts/export` | account key | Contacts as CSV (`?status=`, `?list=`), with consent and properties. |\n| `GET /v1/projects/:id/email/contacts/imports` | account key | Past imports with their reports. |\n| `POST /v1/projects/:id/email/contacts/import` | account key | Import a CSV `{ csv, dry_run?, consent, lists?, fix_typos?, include_role?, update_existing? }` \u2192 a report: `new_contacts`, `updated_contacts`, `skipped` by reason, `samples`, `typo_suggestions`. `consent: true` is required to import. |\n| `GET /v1/projects/:id/email/contacts` | account key | Contacts, newest first: `?q=`, `?status=`, `?list=`, `?segment=`, `?cursor=`, `?limit=` (\u2264 200); `total`. |\n| `POST /v1/projects/:id/email/contacts` | account key | Add or update one by email `{ email, first_name?, last_name?, properties?, lists?, subscribed?, double_opt_in?, consent? }`. Never re-subscribes someone who left: they get a confirmation email (`pending`). |\n| `GET /v1/projects/:id/email/contacts/:contact` | account key | One contact (id or email) with its lists and last 20 events. |\n| `PATCH /v1/projects/:id/email/contacts/:contact` | account key | `{ first_name?, last_name?, properties?, status?: subscribed \\| unsubscribed, add_lists?, remove_lists? }`. Subscribing again by hand is the owner's. |\n| `DELETE /v1/projects/:id/email/contacts/:contact` | account key | Forget a contact. An address that unsubscribed, bounced or complained stays suppressed. |\n| `POST /v1/projects/:id/email/events` | account key | `{ email, event, properties? }`: something a contact did. Starts event automations and ends runs whose exit event it is. |\n| `GET /v1/projects/:id/email/segments` | account key | Saved segments with their `contacts` counts. |\n| `POST /v1/projects/:id/email/segments/preview` | account key | `{ filter }` \u2192 `contacts` and a sample, without saving. |\n| `POST /v1/projects/:id/email/segments` | account key | `{ name, filter: { match: all \\| any, conditions[] } }`: properties, fields, lists, events, engagement. |\n| `PATCH /v1/projects/:id/email/segments/:segment` | account key | Rename it or change its filter. |\n| `DELETE /v1/projects/:id/email/segments/:segment` | account key | Delete a segment. |\n| `POST /v1/projects/:id/email/render` | account key | Render a draft `{ subject, preview_text?, format, body, contact_id? }` as a contact gets it: `html`, `text`, `size_bytes`, `merge_tags`. |\n| `GET /v1/projects/:id/email/broadcasts` | account key | Broadcasts, newest first (`?status=`), with their stats. |\n| `POST /v1/projects/:id/email/broadcasts` | account key | A draft `{ name?, subject, preview_text?, from_local?, from_name?, reply_to?, format: markdown \\| html, body, audience: { list_id?, segment_id? } }`. |\n| `GET /v1/projects/:id/email/broadcasts/:broadcast` | account key | One broadcast: `status`, `waiting`, `recipients`, `charged_cents`, `stats` (sent, delivered, opened, clicked, bounced, complained, unsubscribed, rates, `by_mailbox`). |\n| `PATCH /v1/projects/:id/email/broadcasts/:broadcast` | account key | Edit a draft, a scheduled or a waiting-for-approval broadcast. |\n| `DELETE /v1/projects/:id/email/broadcasts/:broadcast` | account key | Delete a draft or canceled broadcast. |\n| `GET /v1/projects/:id/email/broadcasts/:broadcast/review` | account key | The checklist before sending: `ready`, `checks[]` (`ok`, `warning`, `error`), `audience`, `cost` (`total_cents`, `balance_cents`, `enough_credits`), `sending`, `preview`, `console_url`. |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/test` | account key | Send a free `[Test]` copy `{ to? }` (agents: to the owners only; 20 a day). |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/send` | account key | Send now or `{ scheduled_at }`. An agent sends only within the owner's monthly allowance; otherwise `403 owner_only` with the review link. |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/cancel` | account key | Stop it; nothing more goes out and the held credits are released. |\n| `POST /v1/projects/:id/email/broadcasts/:broadcast/resume` | full-access key | Go on after a pause. |\n| `GET /v1/projects/:id/email/broadcasts/:broadcast/recipients` | account key | Who got it: `?status=` (`sent`, `delivered`, `opened`, `clicked`, `bounced`, `complained`, `unsubscribed`, `failed`), `?mailbox=`, `?cursor=`. |\n| `GET /v1/projects/:id/email/automations` | account key | Automations with their run counts. |\n| `POST /v1/projects/:id/email/automations` | account key | `{ name, trigger, steps[], exit_event? }`: triggers `contact_added`, `event`, `date`; steps `wait`, `email`, `condition` (`yes[]`, `no[]`), `exit`. |\n| `GET /v1/projects/:id/email/automations/:automation` | account key | One automation with `enrollments` counts and emails sent, opened, clicked. |\n| `PATCH /v1/projects/:id/email/automations/:automation` | account key | Edit. While active only email wording changes; pause it to change the trigger, waits or branches. |\n| `DELETE /v1/projects/:id/email/automations/:automation` | account key | Delete it (archived if it sent email). |\n| `POST /v1/projects/:id/email/automations/:automation/activate` | account key | Turn it on. An agent needs the owner's monthly allowance; otherwise `403 owner_only` with the console link. |\n| `POST /v1/projects/:id/email/automations/:automation/pause` | account key | Pause it; runs wait where they are. |\n| `GET /v1/projects/:id/email/automations/:automation/enrollments` | account key | Runs: `?status=` (`active`, `completed`, `exited`, `failed`), each with its `step_id`, `next_run_at`, `history`. |\n| `POST /v1/projects/:id/email/automations/:automation/test` | account key | Send one email step as a free test `{ step_id, to? }`. |\n| `GET /v1/email/u/:token` | signed link | The unsubscribe page a contact opens from an email (`?view=preferences`: lists to keep). GET changes nothing. |\n| `POST /v1/email/u/:token` | signed link | One-click unsubscribe (`List-Unsubscribe=One-Click`, RFC 8058), or the page's form: unsubscribe, subscribe again, save lists, never from anyone. |\n| `GET /v1/email/confirm/:token` | signed link | The double opt-in page: one button. |\n| `POST /v1/email/confirm/:token` | signed link | The contact confirms: `subscribed`. |\n| `GET /v1/email/k/:token` | signed link | \"Keep sending\" page from the list-cleanup email. |\n| `POST /v1/email/k/:token` | signed link | The contact keeps getting emails. |\n| `GET /v1/email/o/:token` | signed link | Open tracking pixel. |\n| `GET /v1/email/c/:token` | signed link | Click tracking: redirects to the signed destination. |\n| `GET /v1/email/f/:form` | public | The hosted signup form. |\n| `POST /v1/email/f/:form` | public | A signup from the form, a pasted snippet or JSON from any site `{ email, first_name? }`: honeypot, rate limits, double opt-in. |\n| `OPTIONS /v1/email/f/:form` | public | CORS preflight for the signup API. |\n\n## AI\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/ai/chat/completions` | account, project AI or app key | OpenAI chat completions, streaming (SSE) or not. `model` defaults to `vibiz/fast`. |\n| `POST /v1/ai/embeddings` | account, project AI or app key | Embeddings. |\n| `POST /v1/ai/images/generations` | account, project AI or app key | Images: `b64_json` (default) or `url` (24 h). Edit a photo with `image_url` (or `image_urls`, up to 8). Any image model from `GET /v1/ai/media-models` by its id, with its own parameters in `model_input`. |\n| `POST /v1/ai/audio/speech` | account, project AI or app key | Text to speech; streams `mp3` or `pcm`. |\n| `POST /v1/ai/audio/transcriptions` | account, project AI or app key | Speech to text, multipart `file` (\u2264 25 MB). |\n| `POST /v1/ai/jobs` | account, project AI or app key | Async image or video `{ type, model?, input }`: any model from `GET /v1/ai/media-models` by its id, with its own parameters in `input.model_input`. \u2192 `202`. |\n| `GET /v1/ai/jobs/:id` | account, project AI or app key | A job and, once done, its output. |\n| `POST /v1/ai/jobs/:id/cancel` | account, project AI or app key | Cancel a job. |\n| `GET /v1/ai/models` | public | The thelastapi models, each with the lab model it runs, and the lab models, with prices. `?all=1` every model, `?q=` search. |\n| `GET /v1/ai/media-models` | account, project AI or app key | Every image and video model that runs by its id (Kling, face swap, upscalers\u2026), with its live price. `?q=`, `?category=`, `?limit=`. |\n| `GET /v1/ai/health` | public | Per capability `ok`/`degraded`/`down`. |\n| `GET /v1/ai/media/:token` | signed link | Generated media; the token in the link is the credential (24 h). |\n| `GET /v1/projects/:id/ai` | account key | A project's AI key status, budgets, limits and today's spend. |\n| `PATCH /v1/projects/:id/ai` | account key | `{ daily_budget_usd?, end_user_daily_budget_usd?, log_content?, rpm?, tpm?, concurrency? }`. |\n| `POST /v1/projects/:id/ai/keys/rotate` | full-access key | A new project AI key `{ grace_seconds? }` (default 3600), written to the app env. |\n| `POST /v1/projects/:id/ai/keys/revoke` | account key | Every AI key of the project stops now; rotate to get a new one. |\n| `GET /v1/ai-keys` | account key | Your own AI provider keys, the account's: status per provider (never a secret) and calls they served in 30 days. |\n| `GET /v1/ai-keys/:provider` | account key | One key: `has_key`, last 4, last used, last error, and per thelastapi model whether `your_key` or `vibiz` serves (and pays for) it. |\n| `PUT /v1/ai-keys/:provider` | full-access key | Set your own key. provider `\"google\"`: `{ type: \"gemini_api_key\", api_key }` or `{ type: \"vertex\", service_account, project_id?, region? }`; provider `\"fal\"`: `{ type: \"fal_key\", api_key }`; `use_for?`. Checked with a free call first. |\n| `PATCH /v1/ai-keys/:provider` | full-access key | `{ use_for: [capability\u2026] }`: what the key serves; the rest runs on thelastapi. |\n| `DELETE /v1/ai-keys/:provider` | full-access key | Remove the key; calls go back to thelastapi (jobs promised to it fail). |\n| `POST /v1/ai-keys/:provider/test` | account key | Re-check the stored key with the same free call; records the result. |\n| `GET /v1/projects/:id/ai-keys` | account key | Your own AI provider keys, a project's override (else it inherits the account's): status per provider (never a secret) and calls they served in 30 days. |\n| `GET /v1/projects/:id/ai-keys/:provider` | account key | One key: `has_key`, last 4, last used, last error, and per thelastapi model whether `your_key` or `vibiz` serves (and pays for) it. |\n| `PUT /v1/projects/:id/ai-keys/:provider` | full-access key | Set your own key (`google`): `{ type: \"gemini_api_key\", api_key }` or `{ type: \"vertex\", service_account, project_id?, region? }`, `use_for?`. Checked with a free call first. |\n| `PATCH /v1/projects/:id/ai-keys/:provider` | full-access key | `{ use_for: [capability\u2026] }`: what the key serves; the rest runs on thelastapi. |\n| `DELETE /v1/projects/:id/ai-keys/:provider` | full-access key | Remove the key; calls go back to thelastapi (jobs promised to it fail). |\n| `POST /v1/projects/:id/ai-keys/:provider/test` | account key | Re-check the stored key with the same free call; records the result. |\n| `GET /v1/projects/:id/ai/calls` | account key | The project's recent AI calls: model, tokens, cost, outcome (no content). |\n| `POST /v1/actions/ai.chat` | account key | `{ input: { prompt \\| messages, system?, model?, max_tokens?, json? } }` \u2192 `{ output: { text, model, usage }, cost_micro_usd }`. |\n| `POST /v1/projects/:id/actions/ai.chat` | account key | The same, billed to the project. |\n| `POST /v1/actions/image.generate` | account key | `{ input: { prompt, size?, n?, model? } }` \u2192 image links (24 h). |\n| `POST /v1/projects/:id/actions/image.generate` | account key | The same, billed to the project. |\n| `POST /v1/actions/speech.create` | account key | `{ input: { text, voice?, format?, model? } }` \u2192 an audio link. |\n| `POST /v1/projects/:id/actions/speech.create` | account key | The same, billed to the project. |\n| `POST /v1/actions/speech.transcribe` | account key | `{ input: { audio_base64, filename?, language?, model? } }` \u2192 `{ text, language, duration_seconds }`. |\n| `POST /v1/projects/:id/actions/speech.transcribe` | account key | The same, billed to the project. |\n\n## Files\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/files` | account key | The project's files, newest first (`env`, `type`, `source`, `q`, `since`, `until`, `model`, `tag`, `folder`, `limit`, `cursor`), with `total_files` and `total_bytes`. |\n| `POST /v1/projects/:id/files` | account key | Upload a file (raw body with `?name=`, or multipart `file`), up to 50 MB \u2192 the file with its permanent `url`. |\n| `POST /v1/projects/:id/files/import` | account key | Save what a public URL serves `{ url, name?, folder?, private? }`. |\n| `GET /v1/projects/:id/files/latest` | account key | The newest file matching `type`, `source`, `model`, `tag`: what an agent just made. |\n| `GET /v1/projects/:id/files/:fileId` | account key | One file: its link, type, size, dimensions and, for AI media, the model, prompt and cost. |\n| `GET /v1/projects/:id/files/:fileId/content` | account key | The file's bytes, private or not. |\n| `PATCH /v1/projects/:id/files/:fileId` | account key | Rename, move, tag, annotate or make private `{ name?, folder?, tags?, note?, private? }`. |\n| `DELETE /v1/projects/:id/files/:fileId` | account key | Delete a file: its link stops working. |\n\n## Export\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/projects/:id/exports` | owner on production \xB7 any key on development | Pack the project to take it elsewhere `{ include?: [code, database, database_csv, env_guide], env?, deployment_id? }` \u2192 `202` and the export, `queued`. The code is the source of the live deployment (or `deployment_id`) with `VIBIZ-EXPORT.md` and `.env.example`; the database is plain SQL that `psql` restores, CSV optional. A production database is an owner's; one export at a time, 10 a day. |\n| `GET /v1/projects/:id/exports` | account key | The last 20 exports, newest first. |\n| `GET /v1/projects/:id/exports/:exportId` | account key | One export: `status` (`queued`, `running`, `ready`, `failed`, `expired`), `step`, `progress`, and `files` with signed download links until `expires_at` (a day). Agents get no link to production data. |\n| `GET /v1/projects/:id/exports/:exportId/env` | full-access key | The export environment's secret values as a `.env` file, with `confirm=1`. Never cached, never in the zip. |\n\n## Actions\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/actions/:name` | account key | Run an account action `{ input }`: web data (`web.scrape`, `web.search`, `web.crawl`, `web.screenshot`, `web.design`, `ads.library`, `places.search`, `reviews`, `social.profile`, `social.posts`, `ecommerce.product`, `linkedin.company`; SEO data: `seo.serp`, `seo.keywords`, `seo.keyword_ideas`, `seo.domain`, `seo.backlinks`, `seo.audit`, `seo.ai_mentions`) \u2192 `{ output, cost_micro_usd, run_id, console_url }`. `web.design` with `sections: true` captures a page section by section; with `section: <n>` it reads one, free from the saved capture. |\n| `GET /v1/actions` | account key | The web data actions: name, title, one line, slow or not, a hint per field, an example and the input as JSON Schema. |\n| `GET /v1/actions/runs` | account key | Past web data runs, newest first (input, status, cost, no output). `?project=<id>\\|none`, `?action=`, `?since=<iso>`, `?cursor=`, `?limit=` (25, \u2264 100). With `console_url`. |\n| `GET /v1/actions/runs/:id` | account key | One run with its output (cut to 1 MB: `truncated`), error and cost, with `console_url`. |\n| `POST /v1/projects/:id/actions/:name` | account key | Run an action as the project (`email.send`, or any action billed to it) \u2192 `{ project_id, output, cost_micro_usd, usage }`; web data also `run_id`, `console_url`, and a screenshot is saved to the project's Files. |\n\n## Payments\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/payments` | account key | The payments account: where sales go (`account.mode`: `vibiz` or `own`), balance, payouts status, `fees` (with `hold_days` and a $100 example), webhook. |\n| `PATCH /v1/projects/:id/payments` | owner on production \xB7 any key on development | `{ statement_descriptor_suffix?, webhook_url?, webhook_events?, brand? }`. `brand` (`{ name?, logo_url?, icon_url?, background_color?, button_color?, font?, border_style? }`) is the checkout page's look for every checkout, merged field by field (a field set to null goes; `brand: null` clears it). |\n| `POST /v1/projects/:id/payments/webhook-secret` | owner on production \xB7 any key on development | Rotate the webhook secret; shown once and written to the app env as `VIBIZ_WEBHOOK_SECRET`. |\n| `GET /v1/projects/:id/payments/deliveries` | account key | The last 50 webhook deliveries and their status codes. |\n| `GET /v1/projects/:id/payments/products` | account key | The catalog for `?env=`. |\n| `POST /v1/projects/:id/payments/products` | account key | Create `{ name, description?, price?: { unit_amount_cents, currency?, type, interval?, interval_count?, lookup_key? } }` (`currency`: ISO 4217, default `usd`; amounts in its smallest unit). |\n| `GET /v1/projects/:id/payments/products/:productId` | account key | One product with its prices. |\n| `PATCH /v1/projects/:id/payments/products/:productId` | account key | Rename, describe, activate or deactivate. |\n| `DELETE /v1/projects/:id/payments/products/:productId` | owner on production \xB7 any key on development | Archive a product. |\n| `POST /v1/projects/:id/payments/products/:productId/prices` | account key | Add a price `{ unit_amount_cents, currency?, type, interval?, interval_count?, lookup_key? }`. Prices are immutable. |\n| `PATCH /v1/projects/:id/payments/prices/:priceId` | account key | `{ active?, lookup_key? }`. |\n| `POST /v1/projects/:id/payments/checkout` | account key | A hosted checkout `{ price_id \\| lookup_key \\| amount_cents+name(+currency), user?, success_url, cancel_url, brand?, \u2026 }` \u2192 `{ url, expires_at }` (1 h, one buyer). |\n| `GET /v1/projects/:id/payments/payments` | account key | Payments, newest first (`cursor`, `limit`); emails masked for agents on production. |\n| `GET /v1/projects/:id/payments/payments/:paymentId` | account key | One payment. |\n| `POST /v1/projects/:id/payments/payments/:paymentId/refund` | owner on production \xB7 any key on development | `{ amount_cents?, reason? }`; `409 insufficient_balance` when the balance can't cover it. |\n| `GET /v1/projects/:id/payments/subscriptions` | account key | Subscriptions, `?user=&status=`, each with its price. |\n| `POST /v1/projects/:id/payments/subscriptions/:subId/cancel` | owner on production \xB7 any key on development | `{ at_period_end? = true }`. |\n| `GET /v1/projects/:id/payments/ledger` | account key | Every money movement, newest first. |\n| `POST /v1/projects/:id/payments/payouts/session` | owner on production \xB7 any key on development | A session for the embedded identity, bank and payouts UI (Get paid). |\n| `POST /v1/projects/:id/payments/withdraw` | owner on production \xB7 any key on development | `{ amount_cents? }` (default everything available) \u2192 a withdrawal; `409` when payouts are not ready or nothing is available. |\n| `GET /v1/projects/:id/payments/withdrawals` | account key | Withdrawals and their status. |\n| `GET /v1/projects/:id/payments/revenue` | account key | What sales brought in over the last `days` (default 30, up to 365) and the period before, net of refunds: `usd_cents` and `by_currency`. Reads only. |\n| `POST /v1/projects/:id/payments/refresh` | account key | Re-read the account and recent charges now. |\n| `POST /v1/projects/:id/payments/simulate` | account key | Development only: `{ event: payment \\| dispute \\| refund \\| release_hold, \u2026 }` runs a real test-mode charge through the ledger and webhooks. |\n| `POST /v1/projects/:id/payments/own-account/link` | account key | A link for the owner to connect their own Stripe account instead (`?env=`, default production) \u2192 `{ url, console_url, expires_at }`. Give `url` to the owner: only they can complete it. `503` when it isn't available. |\n| `DELETE /v1/projects/:id/payments/own-account` | full-access key | Disconnect the owner\u2019s own Stripe account (or opt the project out of the Stripe account for every project): new sales go through thelastapi again, and \"Apply to all projects\" leaves it alone. |\n| `POST /v1/projects/:id/payments/own-account/use-account` | owner on production \xB7 any key on development | Put the project on the Stripe account connected once for every project (Settings \u25B8 Payments), after opting out or instead of its own. `409 account_stripe_not_connected` until it is connected. |\n| `GET /v1/payments/own-account` | account key | The owner\u2019s Stripe connected once for every project: per environment (`environments.production\\|development`), `use_for_all_projects`, and how each project uses it (`account`, `other_account`, `vibiz`, `opted_out`, `not_started`). |\n| `POST /v1/payments/own-account` | full-access key | `{ use_for_all_projects }`: when on, every new project\u2019s payments start on the owner\u2019s Stripe account (in each environment where it is connected). |\n| `POST /v1/payments/own-account/link` | account key | A link for the owner to connect their Stripe account once for every project (`?env=`, default production) \u2192 `{ url, console_url, expires_at }`. Give `url` to the owner: only they can complete it. |\n| `POST /v1/payments/own-account/apply` | owner on production \xB7 any key on development | `{ env?, dry_run?, include_opted_out? }`: switch existing projects to the owner\u2019s Stripe account for new sales \u2192 `{ changed, unchanged, skipped }` (frozen, being deleted, on another Stripe account, opted out). Balances stay to withdraw; subscriptions sold through thelastapi keep billing there. `dry_run` lists without changing (any key). |\n| `DELETE /v1/payments/own-account` | full-access key | Disconnect the owner\u2019s Stripe account for every project (`?env=`): projects that used it sell through thelastapi again for new sales (`moved`); projects that connected the same Stripe account themselves keep it (`kept`). The connection is let go only when nothing uses it. |\n| `GET /v1/payments/app-store` | account key | The owner's own RevenueCat account: the projects there its keys reach (never a key), and which projects use them. |\n| `POST /v1/payments/app-store/link` | account key | A link for the owner to connect their RevenueCat account \u2192 `{ url, expires_at }`. They paste a V2 secret key on that page (never in a chat); only they can complete it. |\n| `DELETE /v1/payments/app-store/connections/:connectionId` | full-access key | Forget a RevenueCat key; the projects set up with it stop taking new store purchases (recorded ones stay). |\n| `GET /v1/projects/:id/payments/app-store` | account key | App Store and Google Play for the project (`?env=`): connected, the app set up (public SDK keys, store product ids, webhook), and `next` steps. |\n| `POST /v1/projects/:id/payments/app-store/setup` | account key | `{ ios_bundle_id?, android_package?, store_project_id? }`: create (or find) the app in the owner's RevenueCat account, mirror the catalog (a product per price with a lookup key, an entitlement per plan, a default offering), register the webhook \u2192 the public SDK key, the App Store product ids to create, and `next`. Safe to re-run. |\n| `GET /v1/projects/:id/payments/app-store/subscriptions` | account key | App Store and Google Play purchases recorded (`?env=&user=`), newest first. |\n| `GET /v1/projects/:id/payments/app-store/webhook-secret` | full-access key | The Authorization header value to paste in the RevenueCat dashboard when the webhook could not be registered for you. |\n\n## Company\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/company/catalog` | account key | States with their fees per entity type (cents), endings, industries, thelastapi fees, disclaimer. |\n| `GET /v1/projects/:id/company` | account key | The company, with `problems` and `quote` while a draft; `404` none yet. |\n| `PUT /v1/projects/:id/company` | account key | Create or replace the draft. |\n| `PATCH /v1/projects/:id/company` | account key | Change the draft (top-level keys replace). |\n| `DELETE /v1/projects/:id/company` | account key | Delete a draft (or a failed or cancelled one). |\n| `POST /v1/projects/:id/company/submit` | owner on production \xB7 any key on development | File it. Production: `{ confirm, accept_terms, expected_total_cents, expected_updated_at }`, paid from the credits (`402 payment_required` when they fall short); development: `{ accept_terms }`. |\n| `POST /v1/projects/:id/company/checkout` | full-access key | Pay a live filing by card instead: the submit body \u2192 a `billing_checkout` for exactly `quote.total_cents`; filed when the payment arrives. |\n| `POST /v1/projects/:id/company/signatures/:document` | owner on production \xB7 any key on development | A fresh signing link (`ss4`, `form_8821`). |\n| `POST /v1/projects/:id/company/actions/:actionId` | owner on production \xB7 any key on development | Answer an action: `{ names }` or `{ address }`. |\n| `GET /v1/projects/:id/company/documents/:docId` | owner on production \xB7 any key on development | A short-lived download link. |\n| `POST /v1/projects/:id/company/refresh` | account key | Re-read it from the filing partner now. |\n| `POST /v1/projects/:id/company/simulate` | account key | Development only: `{ step: formation \\| ein }`. |\n\n## Social\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/social` | account key | Overview: platforms with their limits, connected accounts, posts waiting, scheduled and failed, ad changes waiting. |\n| `GET /v1/projects/:id/social/accounts` | account key | Connected social and ad accounts (`kind`, `platform` filters). |\n| `POST /v1/projects/:id/social/connect` | account key | `{ platform, ads? }` \u2192 a link (1 h) for the owner to open: they approve it in the console, then sign in to the platform. Production unless `env=development`, which makes a test account at once and returns it. |\n| `POST /v1/projects/:id/social/accounts/refresh` | account key | Read the accounts again from the platforms. |\n| `DELETE /v1/projects/:id/social/accounts/:accountId` | owner on production \xB7 any key on development | Disconnect an account. |\n| `GET /v1/projects/:id/social/accounts/:accountId/analytics` | account key | Followers, totals and a daily series (`from`, `to`; 30 days by default). |\n| `POST /v1/projects/:id/social/media` | account key | Upload a file (raw body, its `content-type`, `?filename=`; up to 512 MB) \u2192 a URL to post with. |\n| `GET /v1/projects/:id/social/posts` | account key | Posts, newest first (`status`, `account`, `platform`, `from`, `to`, `cursor`, `limit`). |\n| `POST /v1/projects/:id/social/posts` | account key | Publish now, schedule (`schedule_at`) or draft. Production: owners send `confirm: true`; an agent's post waits for the owner (`pending_approval`). |\n| `GET /v1/projects/:id/social/posts/:postId` | account key | One post, with each account's status, link and error. |\n| `DELETE /v1/projects/:id/social/posts/:postId` | account key | Cancel a draft, a waiting or a scheduled post (a live scheduled one: owner). Published posts stay on the platforms. |\n| `POST /v1/projects/:id/social/posts/:postId/publish` | account key | Publish or schedule a draft (same rules as creating one). |\n| `POST /v1/projects/:id/social/posts/:postId/approve` | full-access key | Approve a waiting post: it goes out now or at its time (`schedule_at` to change it). |\n| `POST /v1/projects/:id/social/posts/:postId/reject` | full-access key | Reject a waiting post. |\n| `POST /v1/projects/:id/social/posts/:postId/retry` | owner on production \xB7 any key on development | Publish the failed accounts again (production: `confirm: true`). |\n| `POST /v1/projects/:id/social/posts/:postId/refresh` | account key | Read its status again from the platforms. |\n| `GET /v1/projects/:id/social/posts/:postId/analytics` | account key | Impressions, reach, likes, comments, shares, saves, clicks per account. |\n| `GET /v1/projects/:id/social/ads/campaigns` | account key | Campaigns of an ad account with budget and spend (`account`, `ad_account`, `from`, `to`). |\n| `POST /v1/projects/:id/social/ads/changes` | account key | Boost a post, pause, resume or re-budget a campaign, or create a Google Ads campaign (`kind: create_campaign`, created paused). Production: owners send `confirm: true`; an agent's change waits for the owner. |\n| `GET /v1/projects/:id/social/ads/changes` | account key | Ad changes, newest first (`status`). |\n| `GET /v1/projects/:id/social/ads/changes/:changeId` | account key | One ad change. |\n| `POST /v1/projects/:id/social/ads/changes/:changeId/approve` | full-access key | Approve a waiting ad change: it is applied. |\n| `POST /v1/projects/:id/social/ads/changes/:changeId/reject` | full-access key | Reject a waiting ad change. |\n| `GET /v1/social-connect/:token` | signed link | The connect link: the owner's connect page in the console, then the platform's sign-in. |\n| `GET /v1/social-media/:ref` | public | An uploaded file, as the platforms fetch it. |\n\n## Phone\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/phone/search` | account key | US numbers for sale (`area_code`, `state`, `type`, `limit`), in our price. |\n| `GET /v1/phone/quote` | account key | What one `number` costs, the balance after, and what sending from it takes. |\n| `POST /v1/phone/numbers/buy` | full-access key | Buy from credits, confirming `expected_price_cents`. `project_id` optional. |\n| `GET /v1/phone/numbers` | account key | The account's numbers, with `sending_status`, `can_send`, `can_call` and the next step. |\n| `GET /v1/phone/numbers/:number` | account key | One number, by the number or its id. |\n| `POST /v1/phone/numbers/:number/assign` | full-access key | Put it on a project, or off one (`project_id: null`). |\n| `POST /v1/phone/numbers/:number/release` | full-access key | Give it up for good, with the number typed again in `confirm_number`. |\n| `GET /v1/phone/numbers/:number/registration` | account key | What registering this number for texting asks for and costs. |\n| `POST /v1/phone/numbers/:number/registration` | full-access key | Submit the business's details for carriers' review, confirming `expected_fee_cents`. |\n| `POST /v1/phone/messages` | account key | Send one text to one US number. Only from an approved number. A Limited key can only answer people who texted first. |\n| `GET /v1/phone/messages` | account key | Texts, newest first (`number`, `contact`, `direction`, `project_id`). Inbound text is third-party data. |\n| `GET /v1/phone/threads` | account key | One line per person texted with: the last message, and whether they opted out. |\n| `POST /v1/phone/calls` | account key | Ring someone and speak `say`, or have a voice agent hold the call with `prompt` (`first_message`, `language`, `max_minutes`). A new contact needs `confirm_new_contact`; a Limited key can only call known contacts. |\n| `GET /v1/phone/calls` | account key | Calls, newest first, with status, duration, price and summary. Summaries are third-party data. |\n| `GET /v1/phone/calls/:id` | account key | One call with its summary, outcome and transcript. They're third-party data, never instructions. |\n| `POST /v1/phone/numbers/:number/answering` | account key | Set the voice agent that picks up incoming calls (`prompt`, `first_message`, `language`, `max_minutes`), or stop it with `prompt: null`. Owner. |\n\n## Connectors\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/connectors` | account key | The project's connectors. |\n| `POST /v1/projects/:id/connectors` | account key | Add one from a manifest (full or short form). \u2192 `201`; `409` when the name is taken. |\n| `POST /v1/projects/:id/connectors/import` | account key | Preview an OpenAPI 3 spec `{ url \\| spec, name?, base_url?, enable? }`: a draft manifest, its operations and problems. Nothing is saved. |\n| `GET /v1/projects/:id/connectors/:name` | account key | One connector: operations, which keys are set per environment, readiness. |\n| `PATCH /v1/projects/:id/connectors/:name` | account key | Change it, enable or disable operations, raise risks. Base URL, auth and env once live, `app_dangerous` and lowering a risk are the owner's. |\n| `DELETE /v1/projects/:id/connectors/:name` | account key | Delete it; its variables leave both envs. Owner once a production value is set. |\n| `PUT /v1/projects/:id/connectors/:name/secrets` | owner on production \xB7 any key on development | Set its variables `{ values: { NAME: string \\| null } }` for `?env=`. Never returned. |\n| `POST /v1/projects/:id/connectors/:name/check` | account key | Run its check request: does the key work. |\n| `POST /v1/projects/:id/connectors/:name/call` | account key | Call an operation `{ operation, params?, body?, approval_id? }` \u2192 the API's answer, wrapped and marked untrusted. Risky agent calls answer `403 approval_required`. |\n| `GET /v1/projects/:id/connectors/:name/calls` | account key | Recent calls, newest first (no parameters or bodies). |\n| `GET /v1/projects/:id/connectors/approvals` | account key | Approvals, `?status=pending`. |\n| `GET /v1/projects/:id/connectors/approvals/:approvalId` | account key | One approval, with exactly what will be sent. |\n| `POST /v1/projects/:id/connectors/approvals/:approvalId/approve` | full-access key | Approve: the agent calls again with `approval_id` within an hour. |\n| `POST /v1/projects/:id/connectors/approvals/:approvalId/deny` | full-access key | Deny it. |\n\n## Analytics\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/script.js` | public | The tracker: `<script defer src=\".../v1/script.js\" data-key=\"vz_pk_\u2026\">`. |\n| `POST /v1/collect` | site key | One event, `text/plain` JSON \u2264 8 KB; the origin must be a project domain. \u2192 `202`, empty, or `{ replay: true }` on a pageview when the project records by default: the tracker then starts replay. |\n| `GET /v1/projects/:id/analytics` | account key | `?period=24h\\|7d\\|30d` \u2192 `{ totals, timeseries, top_pages, sources, countries, devices, events }`. |\n\n## Replay\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/projects/:id/replays/insights` | account key | What goes wrong for visitors (errors, rage and dead clicks, abandoned forms), with example sessions. Start here. |\n| `GET /v1/projects/:id/replays` | account key | Sessions, most worth watching first. Filters `has_error`, `rage`, `dead`, `incomplete`, `path`, `period`. |\n| `GET /v1/replays/:id` | account key | One session: signals, completeness and a timeline of notable moments. |\n| `GET /v1/replays/:id/events` | account key | The raw recording, streamed and paged. |\n| `POST /v1/replays/:id/share` | account key | A private player link `{ expires_in? }` (1 h default, 24 h max). |\n| `DELETE /v1/replays/:id` | account key | Delete a recording now. \u2192 `204`. |\n| `GET /v1/replays/:id/frames` | account key | Still pictures of what the visitor saw at the session\u2019s moments (`?moments=&limit=&at=<ms>&pointer=`): new pictures are metered page screenshots, ones taken before are free; image links last an hour. |\n| `GET /v1/projects/:id/replays/:replayId/frames` | account key | The same pictures, for a replay of that project. |\n| `GET /v1/replays/:id/player` | signed link | The hosted player page for a share link. |\n\n## Usage and metrics\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/usage` | account key | `?period=24h\\|7d\\|30d\\|month&group_by=\u2026` \u2192 `{ totals, data, limits }`. |\n| `GET /v1/projects/:id/usage` | account key | The same for one project. |\n| `GET /v1/metrics` | account key | Requests, error rate and p50/p95/p99 latency by capability. |\n| `POST /v1/dashboard/link` | account key | A signed link to the hosted usage dashboard `{ expires_in?, period? }` (1 h default, 24 h max). |\n| `GET /v1/dashboard` | signed link | The hosted dashboard page (`?token=`). |\n\n## Dashboards\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/dashboards/metrics` | account key | The catalogue a dashboard is made from: `metrics` (each with `id`, `label`, `description`, `product`, `levels` (`project`, `account`), `shapes` (`scalar`, `timeseries`, `table`, `funnel`, `cohort`), `unit` (`count`, `usd_cents`, `usd_micro`, `percent`), `breakdowns`, `filters`, `permission` a Limited key needs and `widget_types` that show it), `widget_types` (`stat`, `line`, `area`, `bar`, `table`, `list`, `funnel`, `cohort`, `text`, each with its default `size`), `ranges`, `buckets` and `templates`. |\n| `GET /v1/dashboards` | account key | The account's dashboards, newest change first; `?project_id=` one project's, `?level=account` the account-level ones. Each with its `widgets` and `console_url`. |\n| `POST /v1/dashboards` | account key | `{ name, project_id?, project_ids?, range?, widgets?, template? }` \u2192 `201` the dashboard. With `project_id` it belongs to that project; without, to the account (`project_ids` picks businesses, none = all). `template` (`churn`, `traffic`, `ai_cost`, `growth` per project; `portfolio` for the account) fills name, range and widgets in one call. Widgets without `layout` are placed on the 12-column grid. Every problem names its field (`widgets.2.metric: \"payments.mrrr\" isn't a metric (did you mean payments.mrr?)`). |\n| `POST /v1/dashboards/query` | account key | An unsaved widget's data: `{ widget, project_id?, project_ids?, range? \\| from, to }` \u2192 `{ data, error, shape, range }`. Try a metric before saving it. |\n| `GET /v1/dashboards/:id` | account key | One dashboard: `name`, `level`, `project_id`, `project_ids`, `range`, `widgets` (`id`, `type`, `title`, `metric`, `text`, `options`, `layout` `{ x, y, w, h }`), `console_url`. |\n| `PATCH /v1/dashboards/:id` | account key | `{ name?, description?, range?, project_ids?, widgets? }`: `widgets` replaces the whole list (move and resize by sending layouts). |\n| `DELETE /v1/dashboards/:id` | account key | Delete a dashboard (its data stays: it is only a view). |\n| `POST /v1/dashboards/:id/widgets` | account key | Add one widget `{ type, metric?, title?, text?, options?, layout? }` \u2192 `201` the dashboard and the `widget`, placed in the first free spot when `layout` is left out. |\n| `PATCH /v1/dashboards/:id/widgets/:widgetId` | account key | Change one widget: any of `type`, `title`, `metric`, `text`, `options` (replaced whole), `layout`. |\n| `DELETE /v1/dashboards/:id/widgets/:widgetId` | account key | Remove one widget \u2192 the dashboard. |\n| `GET /v1/dashboards/:id/data` | account key | Every widget's data: `?range=` (`24h`, `7d`, `30d`, `90d`, `12m`; default the dashboard's) or `?from=&to=` (days, UTC), `?project_ids=a,b` (account level), `?widget=` one widget, `?refresh=1` skips the minute's cache. Each widget answers `data` (`scalar` with `value`, `previous`, `change_pct`; `timeseries` with `keys` and `series`; `table` with `columns` and `rows`; `funnel` with `steps`; `cohort` with `cohorts`) or its own `error` saying what failed, why and how to fix it (a Limited key without `database.production:read` gets `forbidden` on sign-in widgets with `grant_url`). Money is US cents (`usd_cents`), AI spend millionths of a dollar (`usd_micro`). |\n\n## Billing\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/billing` | account key | Balance, status (`active`, `low`, `payment_required`, `past_due`, `exempt`), card (masked), auto-recharge, daily safety cap, `next_step`. |\n| `PATCH /v1/billing` | full-access key | `{ auto_recharge?: { enabled?, threshold_cents?, amount_cents? }, daily_spend_limit_usd? }` \u2192 `billing`. |\n| `POST /v1/billing/checkout` | account key | `{ amount_cents (500\u2013100000), save_card? }` \u2192 `billing_checkout` with the hosted payment `url` a person opens. |\n| `GET /v1/billing/checkout/:id` | account key | One payment page: `open`, `pending`, `succeeded`, `expired`. |\n| `POST /v1/billing/card` | full-access key | A page to save or replace the card \u2192 `billing_checkout` (`kind: card`). |\n| `DELETE /v1/billing/card` | full-access key | Forget the card and turn auto-recharge off \u2192 `billing`. |\n| `GET /v1/billing/ledger` | account key | Every money movement, newest first: trial, credits, usage per day, refunds\u2026 `?kind=&cursor=&limit=`. |\n| `GET /v1/billing/charges` | account key | Card payments (top-ups, auto-recharges, filings) with receipts. `?status=&cursor=&limit=`. |\n\n## Public profile\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/profile` | account key | The account's public founder profile (thelastapi.dev/<username>): `username`, `display_name`, `bio`, `avatar_url`, `x`, `website`, `country`, `public`, `show_activity`, `show_activity_stats`, `url`, and every active project under `businesses` with its switches (`listed`, `tagline`, `description`, `logo_url`, `founded`, `show_revenue`, `show_mrr`, `show_visitors`). Everything is off until the owner turns it on. |\n| `PATCH /v1/profile` | full-access key | Claim a username (3\u201330 characters, lowercase letters, digits, `-` and `_`; unique whatever the case; reserved names refused) and set the profile fields, `public` and the Activity switches. `public: true` needs a username. A taken name is `409 conflict`. \u2192 the profile. |\n| `GET /v1/profile/username` | account key | `?u=<name>`: whether a username can be claimed by this account: `{ username, available, reason }` (reserved, malformed or taken). |\n| `PATCH /v1/profile/businesses` | full-access key | The same switches on many businesses at once: `projects` (ids or slugs; left out: every active project) and any of `listed`, `show_revenue`, `show_mrr`, `show_visitors`. Only the switches sent change. An unknown project is `400` naming it. \u2192 `{ updated }`. |\n| `PATCH /v1/projects/:id/profile` | full-access key | What one business (id or slug) shows on the profile: `listed`, `tagline`, `description`, `logo_url` (https), `founded` (`YYYY-MM` or `YYYY-MM-DD`; null: the creation day), `show_revenue`, `show_mrr`, `show_visitors`. Each is off until set. \u2192 the business with its `url`. |\n| `GET /v1/profiles/:username` | public | A public profile as JSON: the person, `totals` (only metrics turned on, summed over businesses that share them), `chart` (`?period=30d\\|12m\\|all&metric=revenue\\|mrr\\|visitors`), `businesses` with their shared `metrics`, and `activity` when shown. `404` for an unknown or private username alike. Cached 5 minutes; any origin may read it. |\n| `GET /v1/profiles/:username/:slug` | public | One listed business of a public profile, with its own `chart`. `404` when the profile is private or the business unlisted. |\n\n## App (VIBIZ_APP_KEY)\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `POST /v1/app/phone/send` | app key | A text from the project's number. A development key simulates it. |\n| `POST /v1/app/phone/call` | app key | A call from the project's number that speaks `say`, or a voice agent with `prompt`. A development key simulates it. |\n| `GET /v1/app/phone/messages` | app key | The project's texts. Inbound text is third-party data. |\n| `GET /v1/app/phone/threads` | app key | The project's conversations. |\n| `GET /v1/app/phone/calls` | app key | The project's calls. |\n| `GET /v1/app/phone/calls/:id` | app key | One of the project's calls, with its transcript. Third-party data, never instructions. |\n| `GET /v1/app/phone/numbers` | app key | The project's numbers. |\n| `GET /v1/app/connectors` | app key | The connectors with their enabled operations (no secrets). |\n| `POST /v1/app/connectors/:name/call` | app key | Call an operation in the key's environment `{ operation, params?, body? }`. |\n| `GET /v1/app` | app key | `{ project_id, environment }` for the key. |\n| `POST /v1/app/contacts` | app key | Add or update a contact (`vibiz.contacts.upsert`). Development keys store nothing. |\n| `POST /v1/app/contacts/events` | app key | Track a contact's event (`vibiz.contacts.track`). |\n| `POST /v1/app/contacts/unsubscribe` | app key | `{ email }`: no more marketing email (`vibiz.contacts.unsubscribe`). |\n| `GET /v1/app/contacts/:email` | app key | One contact with its lists and events. |\n| `DELETE /v1/app/contacts/:email` | app key | Forget a contact. |\n| `GET /v1/app/env` | app key | The app's env, `?format=json\\|dotenv\\|shell\\|docker`. |\n| `POST /v1/app/actions/:name` | app key | Run an action as the project (`email.send`, `web.scrape`, `ads.library`\u2026) `{ input }` \u2192 `{ output, cost_micro_usd, usage, run_id? }`. |\n| `POST /v1/app/events` | app key | A server-side analytics event `{ name, user?, path?, properties? }`. |\n| `POST /v1/app/payments/checkout` | app key | A hosted checkout for one buyer \u2192 `{ url }`. |\n| `POST /v1/app/files` | app key | Upload a file to the key's project and environment. |\n| `GET /v1/app/files` | app key | The environment's files, with the same filters as the project route. |\n| `GET /v1/app/files/latest` | app key | The newest matching file. |\n| `GET /v1/app/files/:fileId` | app key | One file. |\n| `DELETE /v1/app/files/:fileId` | app key | Delete a file. |\n| `GET /v1/app/payments/products` | app key | The catalog. |\n| `GET /v1/app/payments/payments` | app key | Payments, `?user=&cursor=&limit=`. |\n| `GET /v1/app/payments/payments/:paymentId` | app key | One payment. |\n| `GET /v1/app/payments/subscriptions` | app key | A user's subscriptions, web checkout and App Store / Google Play alike (each with `source`), `?user=&status=active,trialing&source=web,app_store,play_store`. |\n| `GET /v1/app/payments/entitlements` | app key | What a user has now, `?user=` \u2192 `{ keys, data: [{ key, source, price_id, lookup_key, store_product_id, expires_at }] }`: one answer across web checkout and the app stores (store purchases read live from the owner's account, cached a minute). |\n| `POST /v1/app/payments/subscriptions/:subId/cancel` | app key | Cancel a subscription for a user. |\n| `POST /v1/app/payments/portal` | app key | A billing portal link `{ user, return_url }` \u2192 `{ url }`. |\n\n## Platform\n\n| Route | Auth | Does |\n| --- | --- | --- |\n| `GET /v1/status` | public | What is up right now: `status` (`ok`, `degraded`, `down`, `unknown` when the checks have stopped), `checked_at`, `components`. Never why. |\n| `GET /v1/public/live` | public | The public live page: for each project whose owner turned `public_live` on, its name, address, visits (7 days, by country), deploys and sales counted (30 days), and a feed of the latest 50 visits, deploys and sales, to the minute. No ids, emails, amounts or paths. Cached a minute; any origin may read it. |\n| `GET /v1/capabilities` | account key | Resource types, action names and services (`company`, `payments`, `social`) this deployment offers. |\n| `GET /v1/operations/:id` | account key | One queued unit of work: `{ kind, status: queued\\|running\\|succeeded\\|failed, attempts, error }`. |"
771
794
  },
772
795
  {
773
796
  "slug": "errors",
@@ -979,6 +1002,7 @@ To learn what is going wrong for visitors: vibiz_replay_insights first, then vib
979
1002
  AI (metered, costs money per call): vibiz_ai_chat, vibiz_image_generate, vibiz_speech_create, vibiz_speech_transcribe. Each reports cost_usd; the account has a daily spend ceiling.
980
1003
  Files (vibiz_files): every image, video and audio you generate for a project is saved in the project's Files. Use the url in the response (it is permanent), or later vibiz_files latest / vibiz_files list with q set to words from the prompt. Uploads from a URL: vibiz_files import.
981
1004
  Export (vibiz_export): the project's code with a guide to running it anywhere, and its database as SQL, as download links for a day; never secret values, and production data only for owners.
1005
+ Dashboards (vibiz_dashboards): custom dashboards of widgets over live data from every product, per project or across the account; a template (churn, traffic, ai_cost, growth, portfolio) makes one in one call; action data reads every widget's numbers.
982
1006
  Before spending (AI, actions, many builds), call vibiz_usage: it shows what was spent, per tool, model, project, key or end user, and how much of today's ceiling, budgets and caps is left.
983
1007
  Errors come back as tool errors whose text is JSON: { "error": { "code", "message", "details"? } }; details.next_step, when present, is what to tell the user.
984
1008
  Links for the person: results carry console_url (a project, a deployment, a recorded session, a payment, a report, or a list with its filters). It opens that exact view in the web console after sign-in: give the person that link instead of describing where to click. Every console view takes its filters in the URL (vibiz_docs console-urls).`;
@@ -4553,6 +4577,160 @@ To rebuild a page from the real thing, capture it section by section: sections:
4553
4577
  });
4554
4578
  })
4555
4579
  );
4580
+ const widgetShape = z.object({
4581
+ id: z.string().optional(),
4582
+ type: z.enum(["stat", "line", "area", "bar", "table", "list", "funnel", "cohort", "text"]),
4583
+ title: z.string().optional(),
4584
+ metric: z.string().optional().describe("A metric id from action metrics, e.g. payments.mrr."),
4585
+ text: z.string().optional().describe("Markdown, for a text widget."),
4586
+ options: z.object({
4587
+ range: z.enum(["24h", "7d", "30d", "90d", "12m"]).optional(),
4588
+ bucket: z.enum(["hour", "day", "week", "month"]).optional(),
4589
+ breakdown: z.string().optional(),
4590
+ filters: z.record(z.string(), z.string()).optional(),
4591
+ limit: z.number().int().optional(),
4592
+ steps: z.array(z.string()).optional()
4593
+ }).optional(),
4594
+ layout: z.object({
4595
+ x: z.number().int(),
4596
+ y: z.number().int(),
4597
+ w: z.number().int(),
4598
+ h: z.number().int()
4599
+ }).optional()
4600
+ });
4601
+ define(
4602
+ "vibiz_dashboards",
4603
+ {
4604
+ title: "Dashboards: build and read them",
4605
+ description: "Custom dashboards made of widgets over live data from every product (payments, analytics, session replay, sign-in, AI and spend, email, hosting, phone, social, connectors), for one project (project_id) or the whole account across businesses (no project_id; project_ids picks some). Never SQL: a widget is a type (stat, line, area, bar, table, list, funnel, cohort, text) + a metric id from the catalogue + options (range, bucket, breakdown, filters, limit, steps). action metrics: the catalogue (each metric's levels, shapes, breakdowns, filters, unit, the permission a Limited key needs) and the templates. action list: the dashboards (project_id for one project's). action create: with template (churn, traffic, ai_cost, growth for a project; portfolio for the account) a whole dashboard in one call, or name + widgets. action get / data: the dashboard, or every widget's numbers (range 24h|7d|30d|90d|12m or from/to days; each widget has data or its own error saying why and how to fix it). action add_widget / update_widget / remove_widget / update (name, range, project_ids, widgets) / delete. action query: one unsaved widget's data, to try a metric before adding it. Money is US cents (usd_cents), AI spend millionths of a dollar (usd_micro). Give the person console_url (it opens the dashboard with the range).",
4606
+ inputSchema: {
4607
+ action: z.enum([
4608
+ "metrics",
4609
+ "list",
4610
+ "create",
4611
+ "get",
4612
+ "data",
4613
+ "update",
4614
+ "delete",
4615
+ "add_widget",
4616
+ "update_widget",
4617
+ "remove_widget",
4618
+ "query"
4619
+ ]).default("list"),
4620
+ dashboard_id: z.string().optional().describe("For get, data, update, delete and widget actions."),
4621
+ project_id: z.string().optional().describe("A project dashboard (create, list, query). Leave out for the account level."),
4622
+ project_ids: z.array(z.string()).optional().describe("Account level: the businesses it reads (default every one)."),
4623
+ template: z.string().optional().describe("create: churn, traffic, ai_cost, growth (project) or portfolio (account)."),
4624
+ name: z.string().optional(),
4625
+ range: z.enum(["24h", "7d", "30d", "90d", "12m"]).optional(),
4626
+ from: z.string().optional().describe("data/query: a custom range, YYYY-MM-DD."),
4627
+ to: z.string().optional().describe("data/query: the custom range\u2019s last day, YYYY-MM-DD."),
4628
+ widget_id: z.string().optional().describe("update_widget, remove_widget, or data for one widget."),
4629
+ widget: widgetShape.optional().describe("add_widget, update_widget (the fields to change) or query."),
4630
+ widgets: z.array(widgetShape).optional().describe("create or update: the whole list.")
4631
+ },
4632
+ annotations: { readOnlyHint: false, openWorldHint: true }
4633
+ },
4634
+ handle(async (vibiz, args) => {
4635
+ const need = (what, v, next) => {
4636
+ if (v === void 0 || v === null || v === "") {
4637
+ throw Object.assign(new Error(`${what} is required for action ${args.action}.`), {
4638
+ toolError: fail("invalid_request", `${what} is required for action ${args.action}.`, {
4639
+ field: what,
4640
+ next_step: next
4641
+ })
4642
+ });
4643
+ }
4644
+ };
4645
+ try {
4646
+ switch (args.action) {
4647
+ case "metrics":
4648
+ return ok(await vibiz.dashboards.metrics());
4649
+ case "list":
4650
+ return ok(
4651
+ await vibiz.dashboards.list(args.project_id ? { project_id: args.project_id } : {})
4652
+ );
4653
+ case "create":
4654
+ return ok(
4655
+ await vibiz.dashboards.create({
4656
+ ...args.name ? { name: args.name } : {},
4657
+ ...args.template ? { template: args.template } : {},
4658
+ ...args.project_id ? { project_id: args.project_id } : {},
4659
+ ...args.project_ids ? { project_ids: args.project_ids } : {},
4660
+ ...args.range ? { range: args.range } : {},
4661
+ ...args.widgets ? { widgets: args.widgets } : {}
4662
+ })
4663
+ );
4664
+ case "query":
4665
+ need("widget", args.widget, "Send widget: { type, metric, options }.");
4666
+ return ok(
4667
+ await vibiz.dashboards.query({
4668
+ widget: args.widget,
4669
+ ...args.project_id ? { project_id: args.project_id } : {},
4670
+ ...args.project_ids ? { project_ids: args.project_ids } : {},
4671
+ ...args.range ? { range: args.range } : {},
4672
+ ...args.from ? { from: args.from } : {},
4673
+ ...args.to ? { to: args.to } : {}
4674
+ })
4675
+ );
4676
+ }
4677
+ need(
4678
+ "dashboard_id",
4679
+ args.dashboard_id,
4680
+ "Call vibiz_dashboards with action list to find it."
4681
+ );
4682
+ const id = args.dashboard_id;
4683
+ switch (args.action) {
4684
+ case "get":
4685
+ return ok(await vibiz.dashboards.get(id));
4686
+ case "data":
4687
+ return ok(
4688
+ await vibiz.dashboards.data(id, {
4689
+ ...args.range ? { range: args.range } : {},
4690
+ ...args.from ? { from: args.from } : {},
4691
+ ...args.to ? { to: args.to } : {},
4692
+ ...args.project_ids ? { project_ids: args.project_ids } : {},
4693
+ ...args.widget_id ? { widget: args.widget_id } : {}
4694
+ })
4695
+ );
4696
+ case "update":
4697
+ return ok(
4698
+ await vibiz.dashboards.update(id, {
4699
+ ...args.name ? { name: args.name } : {},
4700
+ ...args.range ? { range: args.range } : {},
4701
+ ...args.project_ids ? { project_ids: args.project_ids } : {},
4702
+ ...args.widgets ? { widgets: args.widgets } : {}
4703
+ })
4704
+ );
4705
+ case "delete":
4706
+ return ok(await vibiz.dashboards.delete(id));
4707
+ case "add_widget":
4708
+ need("widget", args.widget, "Send widget: { type, metric, options }.");
4709
+ return ok(
4710
+ await vibiz.dashboards.addWidget(id, args.widget)
4711
+ );
4712
+ case "update_widget":
4713
+ need("widget_id", args.widget_id, "Call action get to see the widget ids.");
4714
+ need("widget", args.widget, "Send widget with the fields to change.");
4715
+ return ok(
4716
+ await vibiz.dashboards.updateWidget(
4717
+ id,
4718
+ args.widget_id,
4719
+ args.widget
4720
+ )
4721
+ );
4722
+ case "remove_widget":
4723
+ need("widget_id", args.widget_id, "Call action get to see the widget ids.");
4724
+ return ok(await vibiz.dashboards.removeWidget(id, args.widget_id));
4725
+ }
4726
+ return fail("invalid_request", `Unknown action ${args.action}.`);
4727
+ } catch (e) {
4728
+ const te = e.toolError;
4729
+ if (te) return te;
4730
+ throw e;
4731
+ }
4732
+ })
4733
+ );
4556
4734
  define(
4557
4735
  "vibiz_search",
4558
4736
  {