thelastapi
Console
Agent guides

Keys and environments

Full-access, Limited and app keys, what each may do, the development environment, and where the project id is.

Open as .md
  • Full-access key (vz_sk_…, 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.
  • 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).
  • App key (vz_app_…, VIBIZ_APP_KEY): the running app's one secret, per environment.

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.

The project id: ./vibiz.json { "project_id": "prj_…" } in a linked app folder, or vibiz_project_status for the list. Read it instead of asking the user.