@lukoweb/apitogo 0.1.77 → 0.1.79

package/docs/cli/commands.md

@@ -0,0 +1,80 @@
+---
+title: CLI commands
+description: APItoGo CLI command catalog by category.
+sidebar_icon: wrench
+---
+
+Commands are exposed by the **`apitogo`** binary (`@lukoweb/apitogo`). Platform commands delegate to
+`@lukoweb/apitogo-mcp` (`apitogo-apply`, `apitogo-status`, `apitogo-teardown`).
+
+## Lifecycle (prefer these)
+
+| Command | Role |
+| ------- | ---- |
+| `init` | Scaffold portal locally (no platform calls) |
+| `config` / `make-config` | Write or update `apitogo.config.json` (interactive: OpenAPI, pages, plans) |
+| `dev` | Local preview server |
+| `build` | Production build (`--preview` to serve locally) |
+| `apply` | Publish config to platform (apihub + portal) |
+| `status` | Account, project, and live readiness |
+| `teardown --yes` | Delete the linked platform project |
+
+## Scaffold and config
+
+| Command | Role |
+| ------- | ---- |
+| `init [dir]` | Create `package.json`, stubs, and initial `apitogo.config.json` |
+| `config` | Merge pages nav, wire OpenAPI, patch site/theme/auth; `-i` wizard for OpenAPI, custom pages, plans |
+
+`npm create @lukoweb/apitogo@latest` is an interactive alternative to `init` for new folders.
+
+See [Make config (CLI)](../configuration/make-config.mdx) for all `config` flags.
+
+## Local development
+
+| Command | Role |
+| ------- | ---- |
+| `dev` | Run Vite dev server (`--port`, `--open`, `--ssr`) |
+| `build` | Production static build |
+| `build --preview` | Build then serve locally |
+
+## Platform (requires API credentials)
+
+| Command | Role |
+| ------- | ---- |
+| `apply` | Full publish — project, plans, apihub, portal backend/frontend |
+| `apply --only <resource>` | Limit to `apihub`, `portal-backend`, or `portal-frontend` |
+| `apply --force` | Redeploy selected resources even when healthy |
+| `apply --platform-plan` | Select Free / Starter / Professional hosting |
+| `apply --resume-from` | Resume interrupted publish |
+| `status` | Whoami + project + live verification |
+| `teardown --yes` | Delete platform project (confirmation required) |
+
+Env: `APITOGO_API_KEY_ID`, `APITOGO_API_SECRET`. Optional: `APITOGO_API_URL`, `APITOGO_MCP_PATH`.
+
+## Hand-edit exceptions
+
+| Change            | Where                                              |
+| ----------------- | -------------------------------------------------- |
+| Home page content | `landing/LandingPage.tsx`                          |
+| Site footer       | `apitogo.config.json` → `modules.landing.content.footer` |
+
+There is no CLI command for arbitrary home page content.
+
+## Removed commands
+
+These print a redirect message — use the replacement:
+
+| Removed | Use instead |
+| ------- | ----------- |
+| `deploy` | `apitogo apply` (optionally `--only portal-frontend`) |
+| `preview` | `apitogo build --preview` or `apitogo dev` |
+| `remove` | `apitogo teardown --yes` |
+| `configure-github-workflow` | `apitogo apply` |
+
+## Related
+
+- [Overview](./overview.md)
+- [Shape](./shape.md)
+- [Go live](./go-live.md)
+- [MCP tools](../mcp/tools.md) — agent tool catalog

package/docs/cli/go-live.md

@@ -0,0 +1,122 @@
+---
+title: Go live with CLI
+description:
+  Publish an APIToGo developer portal with apitogo apply — platform plans, secrets, and status.
+sidebar_icon: rocket
+---
+
+**Go live** publishes your shaped portal to APItoGo hosting, optionally deploys the backend, upserts
+gateway plans, and verifies the live site. `apitogo apply` uses the same engine as MCP
+`publish_dev_portal`.
+
+## Before you publish
+
+1. Confirm **gateway / API plans** in `apitogo.config.json`. Do not invent Free + Pro unless you
+   chose them.
+2. Save secrets in the site **`.env`** (never commit or paste into tickets):
+
+   ```sh
+   APITOGO_CONFIG_AUTHENTICATION__OIDC__AUTHORITY=https://login.example.com
+   APITOGO_CONFIG_AUTHENTICATION__OIDC__CLIENT_ID=your-client-id
+   APITOGO_CONFIG_AUTHENTICATION__OIDC__CLIENT_SECRET=your-client-secret
+   # Only when you have paid project plans:
+   APITOGO_CONFIG_AUTHENTICATION__STRIPE__SECRET_KEY=sk_test_...
+   APITOGO_CONFIG_AUTHENTICATION__STRIPE__WEBHOOK_SECRET=whsec_...
+   ```
+
+3. Export platform credentials and choose a **platform hosting** plan: **Free**, **Starter**, or
+   **Professional**. Starter and Professional use Stripe checkout on the platform.
+
+   **Free** cannot publish **paid gateway plans** (`priceAmount > 0`) or attach a **custom domain**.
+   If your manifest has paid API tiers, use Starter or Professional — see
+   [Gateway plans](../configuration/plans.md).
+
+   ```bash
+   export APITOGO_API_KEY_ID=apk_...
+   export APITOGO_API_SECRET=...
+   ```
+
+## Happy path
+
+```bash
+cd ./my-portal
+apitogo apply --platform-plan free
+apitogo status
+```
+
+`apitogo apply`:
+
+- Creates or links the platform project
+- Provisions modules and syncs gateway plans
+- Deploys the API hub (when configured)
+- Updates the portal backend (including auth API URL in `.env`) and builds + deploys the portal frontend
+
+If apply is blocked, fix the reported checklist (missing secrets, plan, OpenAPI). Do not invent
+credentials.
+
+After success, register **`manualSteps.oidcRedirectUri`** in your IdP. When Stripe is required for
+paid gateway plans, create a webhook at `manualSteps.stripeWebhookUrl` for the listed events.
+
+Do not treat warm-pool URLs as live until apply and status succeed.
+
+## Target specific resources
+
+```bash
+apitogo apply --only apihub
+apitogo apply --only portal-backend
+apitogo apply --only portal-frontend
+apitogo apply --only apihub,portal-frontend
+apitogo apply --only portal-frontend --force
+```
+
+| Resource         | What it updates                                      |
+| ---------------- | ---------------------------------------------------- |
+| `apihub`         | Gateway plans/baseline, API hub package + deploy     |
+| `portal-backend` | Dev-portal module settings and plan catalog        |
+| `portal-frontend` | Site build + Static Web App deploy                  |
+
+Omit `--only` to apply all three. Use `--force` to redeploy even when hashes match.
+
+## Other apply flags
+
+| Flag | Purpose |
+| ---- | ------- |
+| `--project-id` | Override project GUID |
+| `--project-name` | Display name when creating a project |
+| `--platform-plan` | `free` \| `starter` \| `professional` |
+| `--resume-from` | Resume publish ledger from step id |
+| `--no-wait` | Do not wait for long-running jobs |
+| `--json` | Print raw JSON result only |
+
+Resume state is stored in `.apitogo/publish-state.json`.
+
+## After publish
+
+```bash
+apitogo status              # account + project + live checks
+apitogo status --skip-live  # skip live health probes
+apitogo teardown --yes      # delete the platform project
+```
+
+## Platform plan vs API plans
+
+| Kind             | Meaning                                     | How                    |
+| ---------------- | ------------------------------------------- | ---------------------- |
+| Platform hosting | Free / Starter / Professional on APItoGo    | `--platform-plan`      |
+| Gateway / API    | End-user SKUs and rate limits on `/pricing` | `apitogo.config.json` — [Gateway plans](../configuration/plans.md) |
+
+## CLI apply vs MCP publish
+
+| Path                    | Use when                                           |
+| ----------------------- | -------------------------------------------------- |
+| `apitogo apply`         | Terminal, CI, scripts — full product go-live       |
+| MCP `publish_dev_portal` | Agent-driven go-live with the same engine         |
+
+## Related
+
+- [Shape](./shape.md)
+- [Commands](./commands.md)
+- [Authentication](../configuration/authentication.md)
+- [Manifest](../configuration/manifest.md)
+- [Gateway plans](../configuration/plans.md)
+- [MCP go live](../mcp/go-live.md)

package/docs/cli/overview.md

@@ -0,0 +1,89 @@
+---
+title: CLI overview
+description:
+  Use the APItoGo CLI to scaffold, shape, preview, and publish API products without an AI agent.
+sidebar_icon: terminal
+---
+
+The **`apitogo`** CLI lets you manage developer portals from the terminal. You scaffold and shape
+local files, preview with `apitogo dev`, and publish to APItoGo hosting with `apitogo apply`.
+
+**First time?** Install and wire credentials → **[Install the CLI](./setup.md)**. Then follow
+[Shape](./shape.md) and [Go live](./go-live.md).
+
+## What you get
+
+- Scaffold a local portal site (`npm create @lukoweb/apitogo@latest` or `apitogo init`)
+- Shape OpenAPI, plans, docs pages, and site title via `apitogo config -i` and file edits
+- Preview locally (`apitogo dev`)
+- Publish to APItoGo hosting (`apitogo apply`) with platform plans **Free**, **Starter**, or
+  **Professional**
+- Check live status (`apitogo status`) and tear down (`apitogo teardown --yes`)
+
+## Prerequisites
+
+### Shell environment (for apply / status / teardown)
+
+| Variable                | Required | Purpose           |
+| ----------------------- | -------- | ----------------- |
+| `APITOGO_API_KEY_ID`    | Yes      | Platform API auth |
+| `APITOGO_API_SECRET`    | Yes      | Platform API auth |
+
+### Local machine
+
+- Node.js 20+ (scaffold, build, preview)
+- Network access to the npm registry during install/build
+- OIDC credentials at publish time (site `.env` only — never in shell history for sharing)
+- Stripe secrets at publish only when you have **paid** project plans
+
+## Changing your site
+
+| Approach | When it helps |
+| -------- | ------------- |
+| **`apitogo config`** | Wire OpenAPI, custom pages, gateway plans, and site title from the terminal. See [Make config](../configuration/make-config.mdx). |
+| **Edit files directly** | Full control — `apitogo.config.json`, `pages/**`, `landing/LandingPage.tsx`, etc. |
+
+Common CLI shape tasks:
+
+| Change                              | How                                              |
+| ----------------------------------- | ------------------------------------------------ |
+| OpenAPI + API Reference nav         | `apitogo config` or `apitogo config -i` (openapi) |
+| Custom docs pages                   | `apitogo config -i` (page) or add under `pages/` |
+| Gateway / API plans                 | `apitogo config -i` (plan) or edit manifest      |
+| Site title                          | `apitogo config -i` or `--title`                 |
+| Theme, fonts, branding, projectId   | Edit `apitogo.config.json`                       |
+
+Home page content often lives in `landing/LandingPage.tsx`. Site footer can live under
+`modules.landing.content.footer` in `apitogo.config.json`.
+
+## Config model (local site)
+
+| File                  | Role                                  |
+| --------------------- | ------------------------------------- |
+| `apitogo.config.json` | Site, modules, plans, auth type, apis |
+| `.env`                | `VITE_*` + `APITOGO_CONFIG_*` secrets |
+
+Details: [Manifest](../configuration/manifest.md).
+
+## CLI vs MCP
+
+Both paths use the same config-first model. `apitogo apply` runs the same engine as MCP
+`publish_dev_portal`.
+
+| Task              | CLI                              | MCP (agent)                    |
+| ----------------- | -------------------------------- | ------------------------------ |
+| Scaffold          | `npm create` / `apitogo init`    | `create_dev_portal`            |
+| Shape config      | `apitogo config` + file edits    | `apply_product_intent` (shape) |
+| Preview           | `apitogo dev`                    | `npm run dev` / preview tool   |
+| Publish           | `apitogo apply`                  | `publish_dev_portal`           |
+| Status / teardown | `apitogo status` / `teardown`    | `verify_dev_portal_live` / `teardown_project` |
+
+Prefer MCP when an agent should drive changes. Prefer CLI for CI, scripts, or terminal-only
+workflows.
+
+## Next
+
+- [Install the CLI](./setup.md)
+- [Shape](./shape.md) · [Go live](./go-live.md) · [Commands](./commands.md)
+- [MCP overview](../mcp/overview.md) — agent-driven workflow
+- [Manifest](../configuration/manifest.md)

package/docs/cli/setup.md

@@ -0,0 +1,112 @@
+---
+title: Install the CLI
+description:
+  Install and invoke the APItoGo CLI to scaffold, configure, preview, and publish developer portals.
+sidebar_icon: terminal
+---
+
+Use the **`apitogo`** CLI (`@lukoweb/apitogo`) to scaffold a local portal, shape `apitogo.config.json`,
+preview with `apitogo dev`, and publish with `apitogo apply`. Platform commands (`apply`, `status`,
+`teardown`) use the same engine as MCP `publish_dev_portal`.
+
+## Prerequisites
+
+- **Node.js 20+**
+- Platform API credentials from [apitogo.com](https://apitogo.com) when you run `apitogo apply`
+  (API key id + secret)
+
+## Install
+
+The CLI is the npm package **`@lukoweb/apitogo`**. It exposes the **`apitogo`** binary. You do not
+need a global install — scaffold commands add it to your project and `npm install` puts it on
+`node_modules/.bin`.
+
+### New project (recommended)
+
+`npm create` scaffolds the site **and** installs `@lukoweb/apitogo` locally:
+
+```bash
+npm create @lukoweb/apitogo@latest
+cd your-project-name
+npx apitogo config -i    # interactive: title, OpenAPI, pages, plans
+npm run dev
+```
+
+Also works with `pnpm create @lukoweb/apitogo`, `yarn create @lukoweb/apitogo`, or
+`bunx @lukoweb/create-apitogo`.
+
+Non-interactive example:
+
+```bash
+npm create @lukoweb/apitogo@latest my-portal -- --yes --typescript
+cd my-portal
+npx apitogo config -i
+```
+
+### Scaffold into an existing folder
+
+`apitogo init` writes `package.json` with `@lukoweb/apitogo` as a dependency. Run **`npm install`**
+before other `apitogo` commands:
+
+```bash
+npx @lukoweb/apitogo init ./dev-portal
+cd ./dev-portal
+npm install
+npx apitogo config -i
+npm run dev
+```
+
+`apitogo init` is local only — it does not call the platform. After `config -i`, run `npm run dev`
+to preview, then `apitogo apply` when ready to go live.
+
+### How to run `apitogo`
+
+| Situation | Command |
+| --------- | ------- |
+| After `npm create` or `npm install` in the project | `npx apitogo <command>` (e.g. `npx apitogo config -i`) |
+| Same, if `node_modules/.bin` is on your PATH | `apitogo <command>` |
+| One-off, no project yet | `npx @lukoweb/apitogo <command>` |
+| Optional global install | `npm install -g @lukoweb/apitogo` then `apitogo <command>` anywhere |
+
+`npm run dev` / `npm run build` use the project-local CLI via `package.json` scripts — no global
+install required.
+
+## Platform credentials
+
+Export these before `apitogo apply`, `apitogo status`, or `apitogo teardown`:
+
+| Variable             | Required | Purpose           |
+| -------------------- | -------- | ----------------- |
+| `APITOGO_API_KEY_ID` | Yes      | Platform API auth |
+| `APITOGO_API_SECRET` | Yes      | Platform API auth |
+
+Optional:
+
+| Variable           | Purpose                                              |
+| ------------------ | ---------------------------------------------------- |
+| `APITOGO_API_URL`  | Override platform API base URL                       |
+| `APITOGO_MCP_PATH` | Local `@lukoweb/apitogo-mcp` checkout for apply/status/teardown |
+
+Never commit secrets. Site auth secrets (OIDC, Stripe) belong in the portal **`.env`** as
+`APITOGO_CONFIG_AUTHENTICATION__*` — see [Go live](./go-live.md).
+
+## Verify
+
+```bash
+npx apitogo --help
+```
+
+You should see `init`, `config`, `dev`, `build`, `apply`, `status`, and `teardown`.
+
+With credentials set:
+
+```bash
+apitogo status
+```
+
+## Next
+
+- [CLI overview](./overview.md)
+- [Shape](./shape.md) — scaffold and local preview
+- [Go live](./go-live.md) — `apitogo apply`
+- [Commands](./commands.md) — full catalog

package/docs/cli/shape.md

@@ -0,0 +1,121 @@
+---
+title: Shape with CLI
+description:
+  Scaffold and customize a developer portal locally with apitogo init, apitogo config, and apitogo dev.
+sidebar_icon: pencil-ruler
+---
+
+**Shape** means: create or update a local portal site (OpenAPI, plans, docs pages, auth)
+without publishing. You preview with `apitogo dev` or `npm run dev`.
+
+Requires the **`apitogo`** CLI (`@lukoweb/apitogo`). If you have not installed it yet, see
+[Install the CLI](./setup.md).
+
+## Happy path
+
+`npm create` installs `@lukoweb/apitogo` into the new project. Then run config via `npx`:
+
+```bash
+npm create @lukoweb/apitogo@latest my-portal -- --yes
+cd my-portal
+npx apitogo config -i      # title, OpenAPI, pages, plans
+npm run dev                # http://localhost:3000
+```
+
+Or scaffold into an existing folder (`npm install` is required after `init`):
+
+```bash
+npx @lukoweb/apitogo init ./dev-portal --name "Books API"
+cd ./dev-portal
+npm install
+npx apitogo config -i
+npm run dev
+```
+
+`apitogo init` does **not** call the platform. Run `apitogo apply` when you are ready to go live.
+
+## Interactive config (`apitogo config -i`)
+
+After **site title**, the wizard loops until you type `done`:
+
+| Choice | What it does |
+| ------ | ------------ |
+| `openapi` | Link an OpenAPI file by **relative path** in `apitogo.config.json` |
+| `page` | Create `pages/<slug>.tsx` and wire it in navigation |
+| `plan` | Add a gateway plan (title, price, rate limit, monthly quota) |
+
+Authentication is **on by default** — the wizard does not ask for an auth API URL. `apitogo apply`
+fills `VITE_APITOGO_AUTHENTICATION_API_BASE_URL` after the portal backend exists.
+
+Fonts and colors are **not** prompted — edit `apitogo.config.json` or see
+[Colors & theme](../customization/colors-theme.mdx).
+
+**Paid plans:** if any plan has `priceAmount > 0`, you need **Starter** or **Professional** platform
+hosting on apply. **Free** cannot publish paid gateway plans or custom domains.
+
+Full reference: [Make config (CLI)](../configuration/make-config.mdx) · [Gateway plans](../configuration/plans.md)
+
+## Configure with flags
+
+Writes or updates **`apitogo.config.json`**. Can create `package.json`, `tsconfig.json`, and portal
+stubs when missing. Scans `pages/` for navigation and wires OpenAPI when a spec is found.
+
+```bash
+npx apitogo config
+npx apitogo config --title "Books API"
+npx apitogo config --theme '{"light":{"primary":"#111111"}}'
+npx apitogo config -i
+```
+
+Common flags:
+
+| Flag | Purpose |
+| ---- | ------- |
+| `--interactive` / `-i` | Wizard: title, OpenAPI, custom pages, plans |
+| `--title` | Set `site.title` |
+| `--theme`, `--site`, `--authentication` | Deep-merge JSON into config |
+| `--pages-dir` | Folder to scan (default: `pages`) |
+| `--force` | Rebuild Documentation nav from disk |
+
+## Shape by editing files
+
+After `apitogo config`, edit the manifest and site files directly:
+
+- **Plans, branding, backend, projectId** — `apitogo.config.json`
+- **Docs pages** — `pages/**/*.mdx` or `.tsx`
+- **Home page** — `landing/LandingPage.tsx`
+- **Footer** — `modules.landing.content.footer` in `apitogo.config.json`
+
+Never put OIDC or Stripe secrets in `apitogo.config.json`. Use `.env` with
+`APITOGO_CONFIG_AUTHENTICATION__*` before publish.
+
+## Preview locally
+
+```bash
+apitogo dev
+apitogo dev --port 4000 --open
+```
+
+Production build check:
+
+```bash
+apitogo build
+apitogo build --preview
+```
+
+Shape-phase edits hot-reload when the dev server is running.
+
+## Existing docs + OpenAPI folder
+
+If you already have `pages/` and an OpenAPI spec:
+
+```bash
+npx @lukoweb/apitogo init .
+npm install
+npx apitogo config -i
+npm run dev
+```
+
+## Next
+
+When the site looks right, [go live](./go-live.md) with `apitogo apply`.

package/docs/configuration/authentication.md

@@ -11,7 +11,7 @@ For docs-only sites that embed a SPA identity provider directly in the browser,
 
 ## Dev portal (recommended)
 
-Set authentication in `apitogo.config.json`:
+Set authentication in `apitogo.config.json` (enabled by default on new scaffolds):
 
 ```json
 {
@@ -24,13 +24,14 @@ Set authentication in `apitogo.config.json`:
 }
 ```
 
-Backend API URL (MCP writes this at scaffold/publish):
+Backend API URL (`apitogo apply` writes this to `.env` after the portal backend is provisioned):
 
 ```bash
 VITE_APITOGO_AUTHENTICATION_API_BASE_URL=https://your-dev-portal-api.example.com
 ```
 
-Or `authentication.apiBaseUrl` in JSON / `APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` in `.env`.
+You do not need to enter this URL in `apitogo config -i`. Or set `authentication.apiBaseUrl` in JSON /
+`APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` in `.env` manually.
 
 ### Local demo mode
 

package/docs/configuration/make-config.mdx

@@ -3,24 +3,34 @@ title: Make config (CLI)
 navigation_label: Make config
 sidebar_icon: file-cog
 description:
-  Create or update apitogo.config.json from your pages folder, OpenAPI, and optional site, theme, and
-  authentication settings.
+  Create or update apitogo.config.json from your pages folder, OpenAPI, gateway plans, and optional
+  site settings.
 ---
 
-The **`apitogo make-config`** command writes **`apitogo.config.json`**. It can scaffold a portal
+The **`apitogo config`** (alias: `make-config`) command writes **`apitogo.config.json`**. It can scaffold a portal
 project (package.json, tsconfig, landing and user-panel stubs, thin `apitogo.config.tsx`) when those
-files are missing, merge **site / theme / authentication** from flags or an interactive wizard, scan
-`pages/` for navigation, and wire OpenAPI plus an **API Reference** link.
+files are missing, merge **site / theme / authentication** from flags, run an **interactive wizard**
+with `-i`, scan `pages/` for navigation, and wire OpenAPI plus an **API Reference** link.
 
-Landing and user panel are **always enabled** on new configs. The command does **not** change
-`modules` from the CLI and **never edits `redirects`**.
+Landing and user panel are **always enabled** on new configs. **Authentication is enabled by default**
+on new scaffolds. The command does **not** change `redirects`.
+
+## Prerequisites
+
+Install the CLI first — see [Install the CLI](../cli/setup.md). In short:
+
+- **New site:** `npm create @lukoweb/apitogo@latest` (installs `@lukoweb/apitogo` into the project)
+- **Existing folder:** `npx @lukoweb/apitogo init .` then `npm install`
+
+Run config from the project root with `npx apitogo config` (or `apitogo config` if
+`node_modules/.bin` is on your PATH).
 
 ## What it does
 
 1. **Ensures npm scripts** — Creates **`package.json`** (dev / build / preview) and **`tsconfig.json`**
    when missing, including `@lukoweb/apitogo`, landing, user-panel, and billing packages.
 2. **Creates `apitogo.config.json`** when missing, using the current portal template (`site`,
-   `theme`, `authentication`, `modules.docs`, **landing on**, **user panel on**). Creates a thin
+   `theme`, `authentication` **enabled**, `modules.docs`, **landing on**, **user panel on**). Creates a thin
    **`apitogo.config.tsx`** wrapper only if that file does not already exist (existing TSX is left
    alone).
 3. **Patches site, theme, and auth** from `--site`, `--theme`, `--authentication`, `--title`, or
@@ -30,16 +40,41 @@ Landing and user panel are **always enabled** on new configs. The command does *
    portal-only sites) — existing navigation is left alone. Other nav items are kept. Use
    **`--force`** to rebuild Documentation items from disk when pages are present (API Reference is
    still kept when OpenAPI is wired).
-5. **Wires OpenAPI** when a spec is found (or confirmed in interactive mode):
+5. **Wires OpenAPI** when a spec is found (non-interactive) or when you enter a path in `-i`:
    `apis: [{ type: "file", input, path: "api" }]` and a top-level **API Reference** link to `/api` if
-   that link is missing.
+   that link is missing. Interactive mode stores a **relative file path** in `apis[0].input` (for
+   example `./openapi.yaml` or `../api/openapi.yaml`).
+6. **Interactive only** — can scaffold **custom pages** under `pages/` and append **gateway plans**
+   to `modules.userPanel.plans.items`.
+
+## Interactive wizard (`-i`)
+
+```bash
+npx apitogo config -i
+```
+
+1. **Site title**
+2. **Loop** until you type `done`:
+   - **`openapi`** — path to your OpenAPI file (relative link in config; empty skips)
+   - **`page`** — page title + URL path (writes `pages/<slug>.tsx` and wires navigation)
+   - **`plan`** — plan title, price (USD/month), rate limit (calls/min), monthly quota
+3. **Wrap-up** — links to [docs.apitogo.com](https://docs.apitogo.com) for further configuration
+
+The wizard does **not** ask for fonts, colors, logo alt text, or the auth API base URL. Authentication
+stays **enabled**; `apitogo apply` writes `VITE_APITOGO_AUTHENTICATION_API_BASE_URL` to `.env` after
+the portal backend is provisioned.
+
+If you add a **paid** plan (`priceAmount > 0`), the CLI warns that **Free platform hosting cannot
+publish paid gateway plans or custom domains** — use Starter or Professional on apply.
+
+See [Gateway plans](./plans.md) and [Shape with CLI](../cli/shape.md).
 
 ## Usage
 
 Run from your project root (where `apitogo.config.json` and `package.json` live):
 
 ```bash
-apitogo make-config
+npx apitogo config
 ```
 
 ### Options
@@ -48,7 +83,7 @@ apitogo make-config
 | ------------------------- | --------------------------------------------------------------------------- |
 | `--pages-dir <dir>`       | Folder to scan for `.md` / `.mdx` / `.tsx` (default: `pages`)               |
 | `--dir <path>`            | Project root (default: current directory)                                   |
-| `--interactive` / `-i`    | Prompt for title, logo alt, auth, fonts, primary colors, and OpenAPI        |
+| `--interactive` / `-i`    | Wizard: site title, OpenAPI path, custom pages, gateway plans                 |
 | `--title <string>`        | Set `site.title`                                                            |
 | `--site <json>`           | Deep-merge a JSON object into `site`                                        |
 | `--theme <json>`          | Deep-merge a JSON object into `theme`                                       |
@@ -58,20 +93,25 @@ apitogo make-config
 Examples:
 
 ```bash
-apitogo make-config --title "Books API"
-apitogo make-config --theme '{"light":{"primary":"#111111"}}'
-apitogo make-config --interactive
+npx apitogo config --title "Books API"
+npx apitogo config --theme '{"light":{"primary":"#111111"}}'
+npx apitogo config -i
 ```
 
-There is **no `--modules` flag**. Edit `modules` in `apitogo.config.json` if you need to change
-landing or user panel later.
+Theme and fonts are edited in `apitogo.config.json` or via MCP — not in the interactive wizard. See
+[Colors & theme](../customization/colors-theme.mdx) and [Fonts](../customization/fonts.md).
+
+There is **no `--modules` flag** for landing or user-panel toggles. Interactive mode **does** update
+`modules.userPanel.plans` when you add plans.
 
 ## When not to use it
 
 - You need a fully custom navigation order — skip `--force` or maintain navigation by hand.
-- You want to change landing or user-panel module options — edit JSON (or use MCP), not this command.
+- You want to change landing module home content — edit `landing/LandingPage.tsx`.
 
 ## See also
 
 - [Manifest (`apitogo.config.json`)](./manifest.md)
+- [Gateway plans](./plans.md)
 - [Navigation](./navigation.md)
+- [Shape with CLI](../cli/shape.md)