@lukoweb/apitogo 0.1.121 → 0.1.127

package/docs/configuration/authentication.md

@@ -3,8 +3,8 @@ title: Authentication
 sidebar_icon: shield-check
 ---
 
-API products on APItoGo use **`dev-portal`** authentication: the static site delegates sign-in to the
-provisioned portal API; OIDC client secrets stay on the backend.
+API products on APItoGo use **`dev-portal`** authentication: the static site delegates sign-in to
+the provisioned portal API; OIDC client secrets stay on the backend.
 
 For docs-only sites that embed a SPA identity provider directly in the browser, see
 [SPA providers (advanced)](#spa-providers-advanced).
@@ -24,19 +24,20 @@ Set authentication in `apitogo.config.json` (enabled by default on new scaffolds
 }
 ```
 
-Backend API URL (`npx apitogo deploy` writes this to `.env` after the portal backend is provisioned):
+Backend API URL (`npx apitogo deploy` writes this to `.env` after the portal backend is
+provisioned):
 
 ```bash
 VITE_APITOGO_AUTHENTICATION_API_BASE_URL=https://your-dev-portal-api.example.com
 ```
 
-You do not need to enter this URL in `npx apitogo config`. Or set `authentication.apiBaseUrl` in JSON /
-`APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` in `.env` manually.
+You do not need to enter this URL in `npx apitogo config`. Or set `authentication.apiBaseUrl` in
+JSON / `APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` in `.env` manually.
 
 ### Local demo mode
 
-In development (`npx apitogo run`), `demoMode` is on by default when the user panel is enabled. You do
-not need a backend URL or OIDC to explore account pages. Sign in at `/login` with:
+In development (`npx apitogo run`), `demoMode` is on by default when the user panel is enabled. You
+do not need a backend URL or OIDC to explore account pages. Sign in at `/login` with:
 
 ```text
 demo@apitogo.local / password
@@ -51,10 +52,10 @@ unlocks after publish. Docs and API reference stay public. Plans on `/pricing` c
 
 ### Config files
 
-| Concern                                      | File                                                          |
-| -------------------------------------------- | ------------------------------------------------------------- |
-| Site, plans, modules, branding, backend      | `apitogo.config.json` (+ `.env` — [Manifest](./manifest.md))  |
-| OIDC and Stripe for publish                  | `.env` via `APITOGO_CONFIG_AUTHENTICATION__*`                 |
+| Concern                                 | File                                                         |
+| --------------------------------------- | ------------------------------------------------------------ |
+| Site, plans, modules, branding, backend | `apitogo.config.json` (+ `.env` — [Manifest](./manifest.md)) |
+| OIDC and Stripe for publish             | `.env` via `APITOGO_CONFIG_AUTHENTICATION__*`                |
 
 ### Production OIDC
 
@@ -72,7 +73,8 @@ APITOGO_CONFIG_AUTHENTICATION__STRIPE__SECRET_KEY=sk_test_...
 APITOGO_CONFIG_AUTHENTICATION__STRIPE__WEBHOOK_SECRET=whsec_...
 ```
 
-Stripe is required only when you have **paid** gateway plans. Full flow: [MCP go-live](../mcp/go-live.md).
+Stripe is required only when you have **paid** gateway plans. Full flow:
+[MCP go-live](../mcp/go-live.md).
 
 Auth mode for end users (`native` | `oidc` | `nativeAndOidc`) is shaped via MCP /
 `update_dev_portal_manifest`.
@@ -94,8 +96,8 @@ Or in TSX for custom authorization — see [Protected routes](./protected-routes
 :::caution{title="Portal products use dev-portal"}
 
 SPA providers (Auth0, Clerk, OpenID, Supabase, Azure B2C, Firebase, PingFederate) run the OAuth
-callback in the browser (`/oauth/callback`). Prefer **`dev-portal`** for APItoGo-hosted API products.
-Use SPA providers only for standalone docs sites that talk to the IdP directly.
+callback in the browser (`/oauth/callback`). Prefer **`dev-portal`** for APItoGo-hosted API
+products. Use SPA providers only for standalone docs sites that talk to the IdP directly.
 
 :::
 

package/docs/configuration/build-configuration.mdx

@@ -10,8 +10,8 @@ API schemas before they are used in the documentation.
 
 :::tip{title="Security Note"}
 
-Unlike your site config which runs in both client and server environments, `apitogo.build.ts`
-runs exclusively in Node.js during build time. This means:
+Unlike your site config which runs in both client and server environments, `apitogo.build.ts` runs
+exclusively in Node.js during build time. This means:
 
 - Sensitive operations (like API calls, file system access) can safely be performed
 - No build-time code or data is included in the final client bundle

package/docs/configuration/make-config.mdx

@@ -7,11 +7,11 @@ description:
   site settings.
 ---
 
-The **`npx apitogo 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, run an **interactive wizard** on a TTY (apply each change immediately), scan `pages/` for
-navigation, and wire OpenAPI plus an **API Reference** link.
+The **`npx apitogo 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, run an **interactive wizard**
+on a TTY (apply each change immediately), scan `pages/` for navigation, and wire OpenAPI plus an
+**API Reference** link.
 
 Landing and user panel are **always enabled** on new configs. **Authentication is enabled by
 default** on new scaffolds. The command does **not** change `redirects`.

package/docs/configuration/manifest.md

@@ -32,10 +32,7 @@ metadata, with optional `.env` overrides for secrets and local tweaks.
     "oidcMetadataUrl": "https://login.example.com/.well-known/openid-configuration",
     "publicRoutes": ["/health"],
     "cors": {
-      "allowedOrigins": [
-        "https://myapp.example.com",
-        "http://localhost:5173"
-      ]
+      "allowedOrigins": ["https://myapp.example.com", "http://localhost:5173"]
     }
   },
   "modules": {
@@ -80,21 +77,18 @@ when tenant apps or local frontends call the gateway:
 {
   "gateway": {
     "cors": {
-      "allowedOrigins": [
-        "https://myapp.example.com",
-        "http://localhost:5173"
-      ]
+      "allowedOrigins": ["https://myapp.example.com", "http://localhost:5173"]
     }
   }
 }
 ```
 
-| Rule | Detail |
-| ---- | ------ |
-| Portal origin | Always allowed by the platform (`https://{your-portal-host}`). Do not list it here. |
-| Extra origins | Absolute `http://` or `https://` origins only — no path, query, or fragment. |
-| Wildcard | `"*"` is allowed (replaces the list; credentials stay off). |
-| Empty / omitted | Portal playground still works; only extras are missing. |
+| Rule            | Detail                                                                              |
+| --------------- | ----------------------------------------------------------------------------------- |
+| Portal origin   | Always allowed by the platform (`https://{your-portal-host}`). Do not list it here. |
+| Extra origins   | Absolute `http://` or `https://` origins only — no path, query, or fragment.        |
+| Wildcard        | `"*"` is allowed (replaces the list; credentials stay off).                         |
+| Empty / omitted | Portal playground still works; only extras are missing.                             |
 
 Apply with `npx apitogo deploy` / `publish_dev_portal` so APIM policies pick up the change.
 

package/docs/configuration/navigation.mdx

@@ -59,13 +59,13 @@ one of several types. At the simplest level you may only have links and categori
 ## Generate navigation automatically
 
 Use the CLI command **`npx apitogo config`** to merge **`navigation`** from your pages folder into
-`apitogo.config.json`. See **[Make config (CLI)](./make-config.md)** for usage. The command does **not**
-change **`redirects`**.
+`apitogo.config.json`. See **[Make config (CLI)](./make-config.md)** for usage. The command does
+**not** change **`redirects`**.
 
 ::::caution
 
-Without `--force`, `npx apitogo config` only **adds missing** Documentation items. `--force` rebuilds
-Documentation items from disk but still keeps other nav entries such as API Reference.
+Without `--force`, `npx apitogo config` only **adds missing** Documentation items. `--force`
+rebuilds Documentation items from disk but still keeps other nav entries such as API Reference.
 
 ::::
 

package/docs/configuration/overview.md

@@ -1,8 +1,7 @@
 ---
 title: Configuration overview
 sidebar_icon: file-json-2
-description:
-  How APIToGo sites are configured — apitogo.config.json and .env overrides.
+description: How APIToGo sites are configured — apitogo.config.json and .env overrides.
 ---
 
 APIToGo sites are configured primarily with JSON and environment variables:
@@ -63,11 +62,11 @@ can change the site via MCP tools or by editing files — see [MCP overview](../
 
 Prefer `modules.*`:
 
-| Prefer                         | Legacy (still migrated on load) |
-| ------------------------------ | ------------------------------- |
-| `modules.docs`                 | root `docs`                     |
-| `modules.userPanel.apiKeys`    | root `apiKeys`                  |
-| `modules.userPanel.plans.*`    | root `plans` / `pricing.enabled` |
+| Prefer                      | Legacy (still migrated on load)  |
+| --------------------------- | -------------------------------- |
+| `modules.docs`              | root `docs`                      |
+| `modules.userPanel.apiKeys` | root `apiKeys`                   |
+| `modules.userPanel.plans.*` | root `plans` / `pricing.enabled` |
 
 ## Common options
 

package/docs/configuration/plans.md

@@ -8,7 +8,8 @@ description:
 
 **Gateway plans** (also called API plans) are what your **end users** subscribe to.
 
-- **`/pricing`** — public catalog. Visitors choose a plan before signup. Signed-in users still see this page; it must not redirect to `/account/plans`.
+- **`/pricing`** — public catalog. Visitors choose a plan before signup. Signed-in users still see
+  this page; it must not redirect to `/account/plans`.
 - **`/account/plans`** — authenticated billing. Sign-in required. Manage and change subscriptions.
 
 They are separate from **platform hosting** (Free / Starter / Professional on APItoGo), which you
@@ -18,8 +19,9 @@ Store the catalog under `modules.userPanel.plans.items` in `apitogo.config.json`
 
 ## Shape with the CLI
 
-`npx apitogo config` can add plans interactively (title, price, rate limit, monthly quota). Each plan is
-written immediately. You can also edit the manifest by hand or use MCP `update_dev_portal_manifest`.
+`npx apitogo config` can add plans interactively (title, price, rate limit, monthly quota). Each
+plan is written immediately. You can also edit the manifest by hand or use MCP
+`update_dev_portal_manifest`.
 
 ```bash
 npx apitogo config
@@ -65,7 +67,12 @@ npx apitogo config
 - **`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).
-- **`limits`** — rate limit and quota policies (see below). Encoded `limitsJson` strings are still accepted on load.
+- **`pricingModel`** — `fixed` (default) or `custom`. See
+  [Custom pricing](#custom-pricing-contact-sales).
+- **`priceLabel`** — optional text shown instead of the price, such as `"Let's talk"` (max 64
+  characters).
+- **`limits`** — rate limit and quota policies (see below). Encoded `limitsJson` strings are still
+  accepted on load.
 
 Enable the catalog with `modules.userPanel.plans.enabled: true`. Legacy root `plans` is migrated on
 load.
@@ -82,10 +89,32 @@ load.
 - **rateLimit** — maximum calls per renewal window (per minute when `renewalPeriodSeconds` is 60).
 - **quota** — longer-window cap (per 30 days when `renewalPeriodDays` is 30).
 
-New plans include **all** discovered OpenAPI operations unless you set `includedActionKeys`.
-After OpenAPI is deployed, you can scope a plan to specific operations with
-`includedActionKeys` (for example `get:/orders/{id}`). Edit those fields in
-`apitogo.config.json` — see [Manifest](./manifest.md).
+New plans include **all** discovered OpenAPI operations unless you set `includedActionKeys`. After
+OpenAPI is deployed, you can scope a plan to specific operations with `includedActionKeys` (for
+example `get:/orders/{id}`). Edit those fields in `apitogo.config.json` — see
+[Manifest](./manifest.md).
+
+## Custom pricing (contact sales)
+
+Set `pricingModel: "custom"` for plans with negotiated prices, such as an Enterprise tier. Leave
+`priceAmount` at `0` or omit it.
+
+```json
+{
+  "sku": "enterprise",
+  "displayName": "Enterprise",
+  "pricingModel": "custom",
+  "priceLabel": "Let's talk"
+}
+```
+
+On `/pricing`, custom plans show `priceLabel` (or **Custom**) and a **Contact sales** button. The
+button opens a public `/contact-sales` form instead of Stripe checkout or registration. Visitors
+don't need an account.
+
+Each submission is emailed to the project's **sales contact email**, or to the project owner's email
+when none is set. Custom plans can't be subscribed to through checkout. Custom plans are available
+on every platform plan, including Free.
 
 ## Publish
 
@@ -95,15 +124,15 @@ Gateway plans are applied when you run:
 npx apitogo deploy
 ```
 
-`npx apitogo deploy` 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).
+`npx apitogo deploy` 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 | `npx apitogo deploy --platform-plan` |
-| **Gateway / API plans** | What your customers pay for API access | `modules.userPanel.plans.items` |
+| Kind                    | What it is                                     | How                                  |
+| ----------------------- | ---------------------------------------------- | ------------------------------------ |
+| **Platform hosting**    | APItoGo bill for hosting your portal + API hub | `npx apitogo deploy --platform-plan` |
+| **Gateway / API plans** | What your customers pay for API access         | `modules.userPanel.plans.items`      |
 
 ### Free platform limitations
 
@@ -113,8 +142,8 @@ The **Free** platform plan cannot:
 - 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 `npx apitogo deploy --platform-plan free`, deploy is blocked until you
-upgrade or zero/remove those paid plans.
+manifest has paid plans and you try `npx apitogo deploy --platform-plan free`, deploy is blocked
+until you upgrade or zero/remove those paid plans.
 
 ## Related
 

package/docs/deploy/vercel.md

@@ -73,10 +73,9 @@ information.
 
 :::caution{title="Redirects"}
 
-If you have redirects in `apitogo.config.json`, you may also need matching entries in
-`vercel.json`. See the
-[Vercel Configuration](https://vercel.com/docs/projects/project-configuration#redirects) for more
-information.
+If you have redirects in `apitogo.config.json`, you may also need matching entries in `vercel.json`.
+See the [Vercel Configuration](https://vercel.com/docs/projects/project-configuration#redirects) for
+more information.
 
 This is a current limitation. See [#115](https://github.com/lukoweb/apitogo-doc-tool/issues/151).
 

package/docs/deployment.md

@@ -1,8 +1,9 @@
 # Deployment
 
-| Path | Docs |
-| --- | --- |
+| Path                           | Docs                                 |
+| ------------------------------ | ------------------------------------ |
 | **CLI** (`npx apitogo deploy`) | [Go live with CLI](./cli/go-live.md) |
-| **MCP / agents** | [Go live](./mcp/go-live.md) |
+| **MCP / agents**               | [Go live](./mcp/go-live.md)          |
 
-Local-only builds: `npx apitogo build` (optional `--preview`). Platform publish is always `npx apitogo deploy`.
+Local-only builds: `npx apitogo build` (optional `--preview`). Platform publish is always
+`npx apitogo deploy`.

package/docs/guides/custom-pages.md

@@ -13,8 +13,8 @@ Start by creating the page you want to add.
 
 ## CLI scaffold
 
-`npx apitogo config` can create a starter page under `pages/` and wire it into navigation immediately.
-Choose `page` in the wizard loop, then edit the generated `.tsx` file.
+`npx apitogo config` can create a starter page under `pages/` and wire it into navigation
+immediately. 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).

package/docs/guides/environment-variables.md

@@ -8,20 +8,22 @@ APIToGo uses Vite’s [env and mode](https://vite.dev/guide/env-and-mode) model,
 
 ## Portal / publish (`.env`)
 
-| Variable | Purpose |
-| -------- | ------- |
-| `VITE_APITOGO_AUTHENTICATION_API_BASE_URL` | Dev-portal API base URL (client) |
-| `APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` | Same, via config override |
-| `APITOGO_CONFIG_AUTHENTICATION__OIDC__*` | OIDC authority / client id / secret for publish |
-| `APITOGO_CONFIG_AUTHENTICATION__STRIPE__*` | Stripe secret + webhook (paid plans) |
-| `APITOGO_CONFIG_DEMO_MODE` | `false` to disable local demo sign-in |
-| `APITOGO_CONFIG_SITE__TITLE` | Override `site.title` |
-| `APITOGO_CONFIG_PROJECT_ID` | Local project id override |
-
-Nested overrides use `__` path segments (SCREAMING_SNAKE). See [Manifest](../configuration/manifest.md).
+| Variable                                      | Purpose                                         |
+| --------------------------------------------- | ----------------------------------------------- |
+| `VITE_APITOGO_AUTHENTICATION_API_BASE_URL`    | Dev-portal API base URL (client)                |
+| `APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` | Same, via config override                       |
+| `APITOGO_CONFIG_AUTHENTICATION__OIDC__*`      | OIDC authority / client id / secret for publish |
+| `APITOGO_CONFIG_AUTHENTICATION__STRIPE__*`    | Stripe secret + webhook (paid plans)            |
+| `APITOGO_CONFIG_DEMO_MODE`                    | `false` to disable local demo sign-in           |
+| `APITOGO_CONFIG_SITE__TITLE`                  | Override `site.title`                           |
+| `APITOGO_CONFIG_PROJECT_ID`                   | Local project id override                       |
+
+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) or `npx apitogo deploy` ([CLI go-live](../cli/go-live.md)).
+to `.env` before [go-live](../mcp/go-live.md) or `npx apitogo deploy`
+([CLI go-live](../cli/go-live.md)).
 
 Example:
 
@@ -83,10 +85,10 @@ interface ImportMeta {
 
 ## MCP host (agent machine)
 
-| Variable | Purpose |
-| -------- | ------- |
-| `APITOGO_API_KEY_ID` / `APITOGO_API_SECRET` | Required for MCP and CLI deploy/status/teardown |
-| `APITOGO_DOC_TOOL_PATH` | Optional local doc-tool for scaffold |
-| `APITOGO_CLI_PATH` | Optional local `@lukoweb/apitogo` / doc-tool checkout for MCP spawn |
+| Variable                                    | Purpose                                                             |
+| ------------------------------------------- | ------------------------------------------------------------------- |
+| `APITOGO_API_KEY_ID` / `APITOGO_API_SECRET` | Required for MCP and CLI deploy/status/teardown                     |
+| `APITOGO_DOC_TOOL_PATH`                     | Optional local doc-tool for scaffold                                |
+| `APITOGO_CLI_PATH`                          | Optional local `@lukoweb/apitogo` / doc-tool checkout for MCP spawn |
 
 See [MCP overview](../mcp/overview.md) and [CLI overview](../cli/overview.md).

package/docs/guides/managing-api-keys-and-identities.md

@@ -21,16 +21,15 @@ For developer portals, enable API keys under **`modules.userPanel.apiKeys`** in
 ```
 
 With MCP, prefer `update_dev_portal_manifest`. Subscription / gateway keys for provisioned portals
-are issued by the APItoGo platform after sign-in; see [Authentication](../configuration/authentication.md)
-and [MCP go-live](../mcp/go-live.md).
+are issued by the APItoGo platform after sign-in; see
+[Authentication](../configuration/authentication.md) and [MCP go-live](../mcp/go-live.md).
 
-Legacy root `apiKeys: { enabled: true }` is still migrated on load into
-`modules.userPanel.apiKeys`.
+Legacy root `apiKeys: { enabled: true }` is still migrated on load into `modules.userPanel.apiKeys`.
 
 ## Custom API key UI plugin
 
-APIToGo includes a UI plugin for managing API consumers and keys (create, view, update, delete).
-You can point it at any backend by implementing callbacks / `ApiKeyService`.
+APIToGo includes a UI plugin for managing API consumers and keys (create, view, update, delete). You
+can point it at any backend by implementing callbacks / `ApiKeyService`.
 
 Enable and customize from TSX when you need custom create/list logic:
 
@@ -39,13 +38,10 @@ const config = {
   apiKeys: {
     enabled: true,
     createKey: async ({ apiKey, context, auth }) => {
-      const createApiKeyRequest = new Request(
-        "https://api.example.com/v1/developer/api-key",
-        {
-          method: "POST",
-          body: JSON.stringify({ apiKey }),
-        },
-      );
+      const createApiKeyRequest = new Request("https://api.example.com/v1/developer/api-key", {
+        method: "POST",
+        body: JSON.stringify({ apiKey }),
+      });
       const signedRequest = await context.signRequest(createApiKeyRequest);
       const response = await fetch(signedRequest);
       if (!response.ok) {
@@ -66,11 +62,7 @@ enabled.
 interface ApiKeyService {
   getConsumers: (context: ApitogoContext) => Promise<ApiConsumer[]>;
   rollKey?: (consumerId: string, context: ApitogoContext) => Promise<void>;
-  deleteKey?: (
-    consumerId: string,
-    keyId: string,
-    context: ApitogoContext,
-  ) => Promise<void>;
+  deleteKey?: (consumerId: string, keyId: string, context: ApitogoContext) => Promise<void>;
   updateConsumer?: (
     consumer: { id: string; label?: string },
     context: ApitogoContext,

package/docs/mcp/go-live.md

@@ -24,8 +24,8 @@ gateway plans, and verifies the live site.
    ```
 
 3. Choose a **platform hosting** plan: **Free**, **Starter**, or **Professional**. Agents should
-   call `list_platform_plans` / explain `freeProjectsQuota` before you pick. Starter and Professional
-   use Stripe checkout (`checkoutUrl`).
+   call `list_platform_plans` / explain `freeProjectsQuota` before you pick. Starter and
+   Professional use Stripe checkout (`checkoutUrl`).
 
 ## Happy path
 
@@ -40,8 +40,8 @@ apply_product_intent({ mode: "goLive", siteDirectory, platformPlan?, ... })
 If status is `blocked`, fix the readiness checklist (missing secrets, plan, OpenAPI). Do not invent
 credentials.
 
-After success, register **`manualSteps.oidcRedirectUri`** in your IdP. When `stripeRequired` is true,
-create a Stripe webhook at `manualSteps.stripeWebhookUrl` for the listed events.
+After success, register **`manualSteps.oidcRedirectUri`** in your IdP. When `stripeRequired` is
+true, create a Stripe webhook at `manualSteps.stripeWebhookUrl` for the listed events.
 
 Do not treat warm-pool URLs as live until publish / deploy / verify succeed.
 
@@ -69,10 +69,10 @@ shape → deploy_backend → publish_dev_portal(skipBackendRedeploy: true)
 
 ## Platform plan vs API plans
 
-| Kind              | Meaning                                      | How                          |
-| ----------------- | -------------------------------------------- | ---------------------------- |
-| Platform hosting  | Free / Starter / Professional on APItoGo     | `ensure_platform_plan`       |
-| Gateway / API     | End-user SKUs and rate limits on `/pricing`  | Manifest / intent `plans`    |
+| Kind             | Meaning                                     | How                       |
+| ---------------- | ------------------------------------------- | ------------------------- |
+| Platform hosting | Free / Starter / Professional on APItoGo    | `ensure_platform_plan`    |
+| Gateway / API    | End-user SKUs and rate limits on `/pricing` | Manifest / intent `plans` |
 
 ## Publish behavior
 
@@ -85,10 +85,10 @@ shape → deploy_backend → publish_dev_portal(skipBackendRedeploy: true)
 
 ## CLI deploy vs MCP publish
 
-| Path                         | Use when                                              |
-| ---------------------------- | ----------------------------------------------------- |
-| MCP `publish_dev_portal`     | Full product go-live (plans, auth, hosting, verify)   |
-| CLI `npx apitogo deploy`      | Publish config to platform (apihub + portal)          |
+| Path                     | Use when                                            |
+| ------------------------ | --------------------------------------------------- |
+| MCP `publish_dev_portal` | Full product go-live (plans, auth, hosting, verify) |
+| CLI `npx apitogo deploy` | Publish config to platform (apihub + portal)        |
 
 See [Go live with CLI](../cli/go-live.md).
 

package/docs/mcp/overview.md

@@ -19,17 +19,17 @@ deploy, and go-live. You can use MCP tools, edit site files yourself, or mix bot
   **Professional**
 - Deploy backends and sync gateway actions after publish
 
-Prefer **`apply_product_intent`** for “create / shape / go live” prompts. See [Shape](./shape.md) and
-[Go live](./go-live.md).
+Prefer **`apply_product_intent`** for “create / shape / go live” prompts. See [Shape](./shape.md)
+and [Go live](./go-live.md).
 
 ## Prerequisites
 
 ### MCP host environment
 
-| Variable                | Required | Purpose           |
-| ----------------------- | -------- | ----------------- |
-| `APITOGO_API_KEY_ID`    | Yes      | Platform API auth |
-| `APITOGO_API_SECRET`    | Yes      | Platform API auth |
+| Variable             | Required | Purpose           |
+| -------------------- | -------- | ----------------- |
+| `APITOGO_API_KEY_ID` | Yes      | Platform API auth |
+| `APITOGO_API_SECRET` | Yes      | Platform API auth |
 
 ### Agent host
 
@@ -42,10 +42,10 @@ Prefer **`apply_product_intent`** for “create / shape / go live” prompts. Se
 
 You choose how to edit the portal:
 
-| Approach | When it helps |
-| -------- | ------------- |
-| **MCP tools** | Agent-driven changes; tools can wire navigation/config and run validation. See [Tools](./tools.md). |
-| **Edit files directly** | Full control in your editor — `apitogo.config.json`, `pages/**`, `landing/LandingPage.tsx`, etc. |
+| Approach                | When it helps                                                                                       |
+| ----------------------- | --------------------------------------------------------------------------------------------------- |
+| **MCP tools**           | Agent-driven changes; tools can wire navigation/config and run validation. See [Tools](./tools.md). |
+| **Edit files directly** | Full control in your editor — `apitogo.config.json`, `pages/**`, `landing/LandingPage.tsx`, etc.    |
 
 Useful MCP tools (optional — not required):
 

package/docs/mcp/setup.md

@@ -18,11 +18,11 @@ server is the same everywhere; only the host config file changes.
 
 Every host launches the same stdio process:
 
-| Field     | Value                                      |
-| --------- | ------------------------------------------ |
-| Command   | `npx`                                      |
-| Args      | `-y`, `@lukoweb/apitogo-mcp`               |
-| Env       | `APITOGO_API_KEY_ID`, `APITOGO_API_SECRET` |
+| Field   | Value                                      |
+| ------- | ------------------------------------------ |
+| Command | `npx`                                      |
+| Args    | `-y`, `@lukoweb/apitogo-mcp`               |
+| Env     | `APITOGO_API_KEY_ID`, `APITOGO_API_SECRET` |
 
 Optional env: `APITOGO_API_URL`, `APITOGO_DOC_TOOL_PATH` (local doc-tool for scaffold).
 
@@ -65,10 +65,10 @@ Or project-scoped under `.cursor/skills/apitogo-product`.
 
 Edit the Claude Desktop MCP config (same `mcpServers` shape as Cursor):
 
-| OS      | Path                                                                      |
-| ------- | ------------------------------------------------------------------------- |
-| macOS   | `~/Library/Application Support/Claude/claude_desktop_config.json`         |
-| Windows | `%APPDATA%\Claude\claude_desktop_config.json`                             |
+| OS      | Path                                                              |
+| ------- | ----------------------------------------------------------------- |
+| macOS   | `~/Library/Application Support/Claude/claude_desktop_config.json` |
+| Windows | `%APPDATA%\Claude\claude_desktop_config.json`                     |
 
 ```json
 {

package/docs/mcp/shape.md

@@ -53,14 +53,15 @@ Ask only for what is missing:
 2. **backend** / **openApi** — source directory and/or OpenAPI path or URL
 3. **plans** — SKUs, prices, rate limits (your choice; not invented)
 4. **auth.mode** — `native` | `oidc` | `nativeAndOidc`
-5. **gatewayPolicies.publicRoutes** — e.g. `/health` (other routes stay subscription-key protected by
-   default)
+5. **gatewayPolicies.publicRoutes** — e.g. `/health` (other routes stay subscription-key protected
+   by default)
 
 ## Customize after shape
 
 Use MCP tools (see [Tools](./tools.md)):
 
-- Pages → `add_dev_portal_page` / `update_dev_portal_page` (TSX only; `template`: docs|guide|marketing)
+- Pages → `add_dev_portal_page` / `update_dev_portal_page` (TSX only; `template`:
+  docs|guide|marketing)
 - OpenAPI → `set_dev_portal_openapi`
 - Plans / branding → `update_dev_portal_manifest`
 - Theme → `set_dev_portal_theme`