@lukoweb/apitogo 0.1.77 → 0.1.79

package/docs/configuration/manifest.md

@@ -57,8 +57,8 @@ metadata, with optional `.env` overrides for secrets and local tweaks.
 - **Site name / logo:** only `site.title` and `site.logo` (platform branding is derived at publish).
 - **OpenAPI path:** `backend.openApiPath` is derived from `apis[0].input`.
 - **Billing / account plans:** use `modules.userPanel.plans.enabled` and store the plan catalog in
-  `modules.userPanel.plans.items`. Legacy root `plans` is migrated on load. Legacy `pricing.enabled`
-  is migrated and stripped from site JSON; MCP/publish still receives derived `pricing.enabled`.
+  `modules.userPanel.plans.items`. Add plans with `apitogo config -i` or edit the manifest by hand.
+  See [Gateway plans](./plans.md). Legacy root `plans` is migrated on load.
 - **Docs / API keys:** configure under `modules.docs` and `modules.userPanel.apiKeys` only.
 
 ## Environment variables
@@ -90,6 +90,7 @@ APITOGO_CONFIG_AUTHENTICATION__STRIPE__WEBHOOK_SECRET=whsec_...
 
 ## Related
 
+- [Gateway plans](./plans.md)
 - [Authentication](./authentication.md)
 - [Overview](./overview.md)
 - [MCP overview](../mcp/overview.md)

package/docs/configuration/overview.md

@@ -160,6 +160,8 @@ Put navigation in `apitogo.config.json`, or keep large trees in a separate modul
 ## Related
 
 - [Manifest (`apitogo.config.json`)](./manifest.md)
-- [Make config (CLI)](./make-config.mdx)
+- [Make config (CLI)](./make-config.mdx) — interactive wizard (`apitogo config -i`)
+- [Gateway plans](./plans.md)
 - [Authentication](./authentication.md)
 - [MCP overview](../mcp/overview.md)
+- [Shape with CLI](../cli/shape.md)

package/docs/configuration/plans.md

@@ -0,0 +1,113 @@
+---
+title: Gateway plans
+sidebar_icon: tags
+description:
+  Configure end-user API plans in apitogo.config.json — pricing, rate limits, quotas, and publish
+  behavior.
+---
+
+**Gateway plans** (also called API plans) are what your **end users** subscribe to on `/pricing`.
+They are separate from **platform hosting** (Free / Starter / Professional on APItoGo), which you
+select with `apitogo apply --platform-plan`.
+
+Store the catalog under `modules.userPanel.plans.items` in `apitogo.config.json`.
+
+## Shape with the CLI
+
+`apitogo config -i` can add plans interactively (title, price, rate limit, monthly quota). You can
+also edit the manifest by hand or use MCP `update_dev_portal_manifest`.
+
+```bash
+npx apitogo config -i
+# loop: plan → enter title, price, policies → done
+```
+
+## Canonical shape
+
+```json
+{
+  "modules": {
+    "userPanel": {
+      "plans": {
+        "enabled": true,
+        "items": [
+          {
+            "sku": "free",
+            "displayName": "Free",
+            "priceAmount": 0,
+            "limitsJson": "{\"rateLimit\":{\"calls\":100,\"renewalPeriodSeconds\":60},\"quota\":{\"calls\":50000,\"renewalPeriodDays\":30}}"
+          },
+          {
+            "sku": "pro",
+            "displayName": "Pro",
+            "priceAmount": 29,
+            "priceCurrency": "usd",
+            "billingPeriod": "month",
+            "limitsJson": "{\"rateLimit\":{\"calls\":1000,\"renewalPeriodSeconds\":60},\"quota\":{\"calls\":500000,\"renewalPeriodDays\":30}}"
+          }
+        ]
+      }
+    }
+  }
+}
+```
+
+- **`sku`** — stable identifier (used in checkout URLs and gateway sync).
+- **`displayName`** — label on `/pricing`.
+- **`priceAmount`** — `0` for free tiers; greater than zero for paid plans (USD by default).
+- **`limitsJson`** — JSON string with rate limit and quota policies (see below).
+
+Enable the catalog with `modules.userPanel.plans.enabled: true`. Legacy root `plans` is migrated on
+load.
+
+## limitsJson schema
+
+```json
+{
+  "rateLimit": { "calls": 100, "renewalPeriodSeconds": 60 },
+  "quota": { "calls": 50000, "renewalPeriodDays": 30 }
+}
+```
+
+- **rateLimit** — maximum calls per renewal window (per minute when `renewalPeriodSeconds` is 60).
+- **quota** — longer-window cap (per 30 days when `renewalPeriodDays` is 30).
+
+After OpenAPI is deployed, you can scope plans to specific API operations with
+`includedActionKeys` (for example `get:/orders/{id}`). Edit those fields in
+`apitogo.config.json` — see [Manifest](./manifest.md).
+
+## Publish
+
+Gateway plans are applied when you run:
+
+```bash
+apitogo apply
+```
+
+`apitogo apply` syncs plans from the manifest to the platform gateway. Paid plans require Stripe
+secrets in `.env` before publish — see [Go live with CLI](../cli/go-live.md).
+
+## Platform hosting vs gateway plans
+
+| Kind | What it is | How |
+| ---- | ---------- | --- |
+| **Platform hosting** | APItoGo bill for hosting your portal + API hub | `apitogo apply --platform-plan` |
+| **Gateway / API plans** | What your customers pay for API access | `modules.userPanel.plans.items` |
+
+### Free platform limitations
+
+The **Free** platform plan cannot:
+
+- Publish **paid** gateway plans (`priceAmount > 0`)
+- Attach a **custom domain** to the dev portal
+
+Use **Starter** or **Professional** for paid API tiers, Stripe checkout, and custom domains. If your
+manifest has paid plans and you try `apitogo apply --platform-plan free`, apply is blocked until you
+upgrade or zero/remove those paid plans.
+
+## Related
+
+- [Manifest](./manifest.md)
+- [Make config (CLI)](./make-config.mdx)
+- [Authentication](./authentication.md)
+- [Go live with CLI](../cli/go-live.md)

package/docs/deploy/apitogo.md

@@ -1,145 +1,17 @@
----
-title: Deploy with APIToGo CLI
----
+# Deploy with APIToGo CLI
 
-[APIToGo](https://apitogo.com) hosts your documentation site. This page covers the **CLI** path
-(`apitogo deploy` with a deployment token).
+Platform publish is **`apitogo apply`** — the same engine as MCP `publish_dev_portal`.
 
-For a full API product (plans, `dev-portal` auth, gateway, platform Free / Starter / Professional),
-use MCP **`publish_dev_portal`** / `apply_product_intent` mode `goLive` — see
-[MCP go-live](../mcp/go-live.md).
+Full walkthrough (prerequisites, secrets, `--only`, status, teardown):
 
-| Path                     | When                                              |
-| ------------------------ | ------------------------------------------------- |
-| MCP `publish_dev_portal` | Connected portal + plans + hosting go-live        |
-| CLI `apitogo deploy`     | Build and upload a site with a deployment token   |
+→ **[Go live with CLI](../cli/go-live.md)**
 
-## Before you deploy
+Quick reference:
 
 ```bash
-npm run dev
+export APITOGO_API_KEY_ID=apk_...
+export APITOGO_API_SECRET=...
+cd ./my-portal
+apitogo apply --platform-plan free
+apitogo status
 ```
-
-## Deploy with the CLI
-
-To publish a site with a deployment token:
-
-1. Sign in to [apitogo.com](https://apitogo.com)
-2. Create a new project or open an existing one
-3. Navigate to Project settings and copy the deployment token
-4. Run the following command:
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --env=<environment-name>
-```
-
-The `--env` value is the **environment name** your deploy server uses. It must match what is
-configured for your project (see the APIToGo dashboard / deploy API).
-
-Common patterns:
-
-- **`production`** — main live site (default when `--env` is omitted)
-- **Named non-production environments** — any label your backend accepts, for example `staging`,
-  `dev`, or `preview`
-- **Multiple preview slots** — separate previews such as `preview-a` and `preview-b` when your
-  `/deploy` endpoint supports them:
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --env=preview-a
-apitogo deploy --deployment-token=<TOKEN> --env=preview-b
-```
-
-If you do not provide `--env`, APIToGo deploys to `production` by default:
-
-```bash
-apitogo deploy --deployment-token=<TOKEN>
-```
-
-### JSON-only mode (`--json-only`)
-
-Use `--json-only` when you want **machine-readable output** from the whole command (for example
-piping to `jq` in CI).
-
-- **Standard output** is a **single JSON value**: on success, the parsed deploy API response (the
-  same payload the server returns with `?jsonOnly=true`). On failure (including build errors),
-  stdout is `{"error":"..."}` and the process exits with a non-zero code.
-- The CLI **suppresses** normal build and progress logs so they do not mix with that JSON.
-- The deploy request still includes `?jsonOnly=true` on the endpoint.
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --json-only
-```
-
-Combine with `--env` as usual (including named previews such as `preview-a`):
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --env=preview --json-only
-apitogo deploy --deployment-token=<TOKEN> --env=preview-a --json-only
-```
-
-## Deploy with GitHub Actions
-
-You can automate deploys from GitHub so every merge to `main` updates production and every pull
-request gets a **preview** URL.
-
-### 1. Generate the workflow
-
-From your documentation project root (the folder that contains `apitogo.config.json` and `package.json`),
-run:
-
-```bash
-apitogo configure-github-workflow
-```
-
-This creates `.github/workflows/apitogo-deploy.yml` with two jobs:
-
-- **Preview** — runs on pull requests targeting `main`. It deploys to an environment named like
-  `preview-pr-<number>` and exposes the preview URL on the GitHub Actions run.
-- **Production** — runs on pushes to `main`. It deploys with the default production environment.
-
-If the file already exists, pass `--force` to overwrite it.
-
-### 2. Add your deployment token as a GitHub secret
-
-1. In [APIToGo](https://apitogo.com), open your project and copy the **deployment token** from
-   project settings (the same token you use with `apitogo deploy`).
-2. On GitHub, open your repository → **Settings** → **Secrets and variables** → **Actions**.
-3. Create a new repository secret named **`APITOGO_TOKEN`** and paste the token.
-
-The generated workflow reads that secret as `${{ secrets.APITOGO_TOKEN }}`.
-
-### 3. Optional: GitHub environments
-
-The workflow references **`preview`** and **`production`**
-[environments](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment).
-If you use environment protection rules, create matching environments in the repo settings and
-attach reviewers or branch filters as needed. If you do not use environments, the jobs still run;
-you can simplify the workflow later to drop `environment:` blocks.
-
-### 4. Commit and ship
-
-Add the new workflow to version control, commit, and push:
-
-```bash
-git add .github/workflows/apitogo-deploy.yml
-git commit -m "Add APIToGo GitHub Actions deploy workflow"
-git push
-```
-
-After that, pushes and pull requests against `main` trigger deploys automatically. You can also run
-the workflow manually from the **Actions** tab (**workflow_dispatch**).
-
-## What to verify after deployment
-
-After your site is live, check the following:
-
-- Navigation load correctly
-- Static assets such as images and logos resolve correctly
-- OpenAPI references and API playground features load as expected
-- Any custom domain or redirects are working properly
-
-## Open APIToGo
-
-To get started, sign in here:
-
-- [APIToGo Dashboard](https://apitogo.com)

package/docs/deployment.md

@@ -1,22 +1,8 @@
----
-title: Deploying APIToGo
----
+# Deployment
 
-Choose how you publish:
+| Path | Docs |
+| --- | --- |
+| **CLI** (`apitogo apply`) | [Go live with CLI](./cli/go-live.md) |
+| **MCP / agents** | [Go live](./mcp/go-live.md) |
 
-| Path | Guide |
-| ---- | ----- |
-| **MCP go-live** (portal + plans + hosting) | [MCP go-live](./mcp/go-live.md) |
-| **CLI** (`apitogo deploy` + token) | [Deploy with APIToGo CLI](./deploy/apitogo.md) |
-| **Static host** (GitHub Pages, upload `dist`) | Below and sibling deploy guides |
-
-## Build locally
-
-Produce static HTML, JavaScript, and CSS for any host:
-
-```bash
-npm run build
-```
-
-Output is in `dist/`. Upload that folder, or use [direct upload](./deploy/direct-upload.md) /
-[GitHub Pages](./deploy/github-pages.md).
+Local-only builds: `apitogo build` (optional `--preview`). Platform publish is always `apitogo apply`.

package/docs/guides/custom-pages.md

@@ -11,6 +11,14 @@ components that APIToGo already has such as buttons, links and headers.
 
 Start by creating the page you want to add.
 
+## CLI scaffold
+
+`apitogo config -i` can create a starter page under `pages/` and wire it into navigation. Choose
+`page` in the wizard loop, then edit the generated `.tsx` file.
+
+Predefined UI components (Callout, Card, Button, Heading, and more) are documented under
+[/docs/components/](/docs/components/callout).
+
 ## Setup a custom page
 
 Each custom page is a page component of its own and lives in a `src` directory at the root of your

package/docs/guides/environment-variables.md

@@ -21,7 +21,7 @@ APIToGo uses Vite’s [env and mode](https://vite.dev/guide/env-and-mode) model,
 Nested overrides use `__` path segments (SCREAMING_SNAKE). See [Manifest](../configuration/manifest.md).
 
 **Never commit** OIDC client secrets or Stripe keys. MCP never puts secrets in chat — you write them
-to `.env` before [go-live](../mcp/go-live.md).
+to `.env` before [go-live](../mcp/go-live.md) or `apitogo apply` ([CLI go-live](../cli/go-live.md)).
 
 Example:
 
@@ -85,7 +85,8 @@ interface ImportMeta {
 
 | Variable | Purpose |
 | -------- | ------- |
-| `APITOGO_API_KEY_ID` / `APITOGO_API_SECRET` | Required for MCP |
+| `APITOGO_API_KEY_ID` / `APITOGO_API_SECRET` | Required for MCP and CLI apply/status/teardown |
 | `APITOGO_DOC_TOOL_PATH` | Optional local doc-tool for scaffold |
+| `APITOGO_MCP_PATH` | Optional local MCP checkout for CLI apply/status/teardown |
 
-See [MCP overview](../mcp/overview.md).
+See [MCP overview](../mcp/overview.md) and [CLI overview](../cli/overview.md).

package/docs/mcp/go-live.md

@@ -88,9 +88,9 @@ shape → deploy_backend → publish_dev_portal(skipBackendRedeploy: true)
 | Path                         | Use when                                              |
 | ---------------------------- | ----------------------------------------------------- |
 | MCP `publish_dev_portal`     | Full product go-live (plans, auth, hosting, verify)   |
-| CLI `apitogo deploy`         | Build + deploy a site with a deployment token only    |
+| CLI `apitogo apply`          | Publish config to platform (apihub + portal)          |
 
-See [Deploy with APIToGo CLI](../deploy/apitogo.md).
+See [Go live with CLI](../cli/go-live.md).
 
 ## Related
 

package/docs/mcp/overview.md

@@ -73,4 +73,4 @@ Details: [Manifest](../configuration/manifest.md).
 - [Configure MCP](./setup.md)
 - [Quickstart](../quickstart.md)
 - [Shape](./shape.md) · [Go live](./go-live.md) · [Tools](./tools.md)
-- CLI without an agent: see the footnote on [Quickstart](../quickstart.md#without-an-agent-cli)
+- CLI without an agent: [CLI overview](../cli/overview.md)

package/docs/quickstart.md

@@ -68,14 +68,6 @@ Build an API product (developer portal, plans, gateway, backend) with an AI agen
 
 ## Without an agent (CLI)
 
-If you prefer not to use MCP:
+Prefer the terminal? Use the **`apitogo`** CLI for the same config-first workflow:
 
-```bash
-npm create @lukoweb/apitogo@latest
-cd your-project-name
-npm run dev
-```
-
-For an existing `pages/` + OpenAPI folder: `apitogo make-config` (see
-[Make config](./configuration/make-config.mdx)). That command writes `apitogo.config.json`. Site-only
-deploy with a token: [Deploy with APIToGo CLI](./deploy/apitogo.md).
+→ **[Install the CLI](./cli/setup.md)** · [Shape](./cli/shape.md) · [Go live](./cli/go-live.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lukoweb/apitogo",
-  "version": "0.1.77",
+  "version": "0.1.79",
   "type": "module",
   "sideEffects": [
     "**/*.css",