zuplo 7.8.8 → 7.8.10

package/docs/ai-gateway/integrations/claude-desktop.mdx

@@ -2,156 +2,118 @@
 title: Claude Desktop
 sidebar_label: Claude Desktop
 description:
-  Point Claude Desktop at an AI Gateway app so every Chat, Cowork, and Code
-  session is authenticated, metered, and routed by the gateway.
+  Route Claude Desktop's Chat, Cowork, and Code sessions through a Zuplo AI
+  Gateway app.
 ---
 
-[Claude Desktop](https://claude.com/download) can use the Zuplo AI Gateway as
-its inference provider, so the gateway authenticates, meters, and routes every
-Chat, Cowork, and Code session started from the desktop app.
+Route [Claude Desktop](https://claude.com/download) through the Zuplo AI
+Gateway. The gateway authenticates, meters, and routes every Chat, Cowork, and
+Code session started from the app.
 
-This page covers routing Claude Desktop's model requests through the AI Gateway.
 To give Claude Desktop tools from a Zuplo MCP route instead, see
 [Connect Claude Desktop and Claude.ai](../../mcp-gateway/connect-clients/claude-desktop.mdx).
 
-## Claude Desktop Setup
+## Prerequisites
 
 <Stepper>
 
-1. Create a [new provider](../managing-providers.mdx) in the AI Gateway for
-   Anthropic
+1. Create an Anthropic [provider](../managing-providers.mdx) in the AI Gateway.
 
-2. [Set up a new team](../managing-teams.mdx)
+2. [Create a team](../managing-teams.mdx).
 
-3. Create a [new app](../managing-apps.mdx) to use with Claude Desktop and
-   assign it to the team you created
+3. [Create an app](../managing-apps.mdx) for Claude Desktop and assign it to the
+   team.
 
-4. Copy the **API URL** and **API Key** shown at the top of the app page
-
-5. Enter the API URL, API key, and model list in Claude Desktop's third-party
-   inference settings
+4. Copy the **API URL** and **API Key** from the app page.
 
 </Stepper>
 
-### Before copying: replace the provider name
-
-:::warning
-
-The examples below assume your provider is named `anthropic`. Replace that
-prefix with the name of **your** provider before copying the configuration. For
-example, a provider named `my-anthropic` routes `my-anthropic/claude-sonnet-5`,
-while a Bedrock provider named `bedrock` routes
-`bedrock/anthropic.claude-sonnet-5`. The model part must be an id that provider
-understands.
-
-:::
-
-The gateway routes every request using `providerName/model`. The provider prefix
-picks which of your providers handles the request — a gateway can contain
-several providers that serve Anthropic models.
-
-### Configure third-party inference
-
-Configure Claude Desktop's inference provider in its in-app configuration
-window, available on macOS and Windows:
+## Configure Claude Desktop
 
 <Stepper>
 
-1. From the menu bar (macOS) or the application menu (Windows), select **Help →
-   Troubleshooting → Enable Developer Mode**.
+1. Select **Help → Troubleshooting → Enable Developer Mode** from the menu bar
+   (macOS) or the application menu (Windows).
 
 2. Open **Developer → Configure Third-Party Inference**.
 
-3. In the **Connection** section, set **Inference provider** to **Gateway**.
+3. Under **Connection**, set **Inference provider** to **Gateway**.
 
-4. In the **Gateway credentials** card, set **Gateway base URL** to the app's
-   API URL, for example
+4. Under **Gateway credentials**, set **Gateway base URL** to the app's API URL,
+   for example
    `https://my-gateway-main-2e18f50.zuplo.app/config_fe0a04972d2848e0a94ae4b8bcd1497e`,
    and **Gateway API key** to the app's API key.
 
 5. Leave **Credential kind** set to **Static API key** and **Gateway auth
    scheme** set to **Bearer**.
 
-6. In the **Models** section, add the models the app may use to the **Model
-   list**. See [Add models to the Model list](#add-models-to-the-model-list).
+6. Under **Models**, add each model the app may use. See
+   [Add models](#add-models).
 
-7. Click **Apply locally**. Claude Desktop writes the configuration and
-   relaunches into it.
+7. Click **Apply locally**. Claude Desktop saves the configuration and
+   relaunches.
 
 </Stepper>
 
-:::note
+### Rules
 
-Claude Desktop appends `/v1/messages` to the base URL itself, so **Gateway base
-URL** is the app's URL _without_ the `/v1` suffix.
+- **Gateway base URL** is the app's API URL _without_ `/v1`. Claude Desktop
+  appends `/v1/messages`.
+- **Gateway auth scheme** stays **Bearer**. The gateway reads the API key from
+  the `Authorization: Bearer` header.
+- **Credential kind** stays **Static API key**. AI Gateway apps authenticate
+  with API keys, not identity-provider tokens.
 
-:::
+## Add models
 
-:::caution{title="Keep the auth scheme set to Bearer"}
+:::warning{title="Replace the provider name"}
 
-The gateway reads the API key from the `Authorization: Bearer` header, so keep
-**Gateway auth scheme** set to **Bearer**. Likewise, keep **Credential kind**
-set to **Static API key** — AI Gateway apps authenticate with their own API
-keys, not identity-provider tokens.
+The examples assume your provider is named `anthropic`. Replace that prefix with
+the name of **your** provider before entering any model. A provider named
+`my-anthropic` routes `my-anthropic/claude-sonnet-5`; a Bedrock provider named
+`bedrock` routes `bedrock/anthropic.claude-sonnet-5`. The model part must be an
+ID that provider serves. Check [your provider's page](../managing-providers.mdx)
+in the Portal.
 
 :::
 
-### Add models to the Model list
-
-The **Model list** in the **Models** section overrides the model list Claude
-Desktop discovers on its own. Click **Add** once per model the app may use, and
-fill in each entry:
+The **Model list** replaces the models Claude Desktop discovers on its own.
+Click **Add** once per model:
 
 - **Model ID** — the full `providerName/model` reference, for example
-  `anthropic/claude-sonnet-5`. A bare id such as `claude-sonnet-5` fails to
-  route through the gateway.
-- **Display name** — the name shown in the model picker, for example
-  `Claude Sonnet 5`. Leave it blank and Claude Desktop formats a name from the
-  id.
-- **Offer 1M-context variant** — leave this off unless your provider's
-  deployment accepts 1M-token context for the model.
+  `anthropic/claude-sonnet-5`. A bare ID fails with a `400`.
+- **Display name** — the name in the model picker. Leave it blank and Claude
+  Desktop formats one from the ID.
+- **Offer 1M-context variant** — off, unless your provider accepts 1M-token
+  context for the model.
 - **Tier alias** — the Claude tier (Opus, Sonnet, Haiku, or Fable) this model
-  stands in for. Setting it pins what the bare alias (for example `opus`)
-  resolves to, so tier names route to your prefixed model reference.
+  stands in for. The bare alias, for example `opus`, then resolves to it.
 
-The first entry is the default selection in the model picker. Include a
-Haiku-tier model — Claude Desktop runs background and sub-agent tasks on a
-small, fast model.
-
-The model ids in these examples reflect what was current when this page was
-written, and ids differ across providers — a Bedrock provider serves different
-ids than Anthropic directly, and availability can vary by region. Check
-[your provider's page](../managing-providers.mdx) in the portal for the models
-it currently serves, and use those ids.
+The first entry is the picker default. Include a Haiku-tier model: Claude
+Desktop runs background and sub-agent tasks on a small, fast model.
 
 The app's
 [Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy controls which models the app may use.
-
-### Verify the configuration
+policy controls which models the app can use.
 
-After Claude Desktop relaunches, send a message in a Chat conversation and start
-a Cowork session. Both requests route through the gateway and count against the
-[app](../managing-apps.mdx) in the Zuplo Portal, as do Code sessions started
-from the desktop app. Terminal Claude Code sessions outside the desktop app use
-a separate configuration — see [Claude Code](./claude-code.mdx).
+## Verify
 
-:::caution{title='HTTP 400: model must use "providerName/model"'}
+Send a message in Chat and start a Cowork session. Both appear in the app's
+usage in the Zuplo Portal, as do Code sessions started from the desktop app.
+Terminal Claude Code sessions use their own configuration. See
+[Claude Code](./claude-code.mdx).
 
-If a request fails with `The request body model must use "providerName/model"`,
-the selected model reference is missing its provider prefix. Give every entry in
-the model list a full `providerName/model` reference.
+## Troubleshooting
 
-:::
+| Error                                                        | Fix                                                                                         |
+| ------------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
+| `400` `The request body model must use "providerName/model"` | A model list entry has no provider prefix. Give every entry a full `providerName/model` ID. |
 
-### Deploy to a fleet
+## Deploy to a fleet
 
-To roll the configuration out to many devices, use the configuration window's
-**Export** menu instead of **Apply locally**. It generates a `.mobileconfig`
-profile for macOS MDM tools such as Jamf, a `.reg` policy file for Intune or
-Group Policy, and related deployment artifacts. Managed configuration takes
-precedence over local settings, so users can't point the app at a different
-endpoint. For the deployment workflow and the full configuration key reference,
-see Anthropic's
+Use the configuration window's **Export** menu instead of **Apply locally**. It
+produces a `.mobileconfig` profile for macOS MDM tools such as Jamf, a `.reg`
+policy file for Intune or Group Policy, and related artifacts. Managed
+configuration overrides local settings. See Anthropic's
 [Deploy Claude Desktop with an LLM gateway](https://claude.com/docs/third-party/claude-desktop/gateway)
 and [Deploy with MDM](https://claude.com/docs/third-party/claude-desktop/mdm).

package/docs/ai-gateway/integrations/codex.mdx

@@ -1,98 +1,104 @@
 ---
 title: Codex
 sidebar_label: Codex
-description:
-  Configure the Codex CLI to send its requests through an AI Gateway app, either
-  by rerouting the built-in OpenAI provider or by adding a Zuplo provider.
+description: Route Codex CLI requests through a Zuplo AI Gateway app.
 ---
 
-[Codex](https://developers.openai.com/codex) is a coding agent developed by
-OpenAI that you can run locally from your terminal and that can read, modify,
-and run code on your machine, in the chosen directory. It’s open-source, and
-built in Rust for speed and efficiency.
+[Codex](https://developers.openai.com/codex) is OpenAI's coding agent for the
+terminal. This guide routes its requests through the Zuplo AI Gateway.
 
 ## Prerequisites
 
-In order to use the AI Gateway with Codex you will need to complete these steps
-first:
-
 <Stepper>
 
-1. Create a [new provider](../managing-providers.mdx) in the AI Gateway for the
-   provider you want to use with Codex
+1. Create a [provider](../managing-providers.mdx) in the AI Gateway.
 
-2. [Set up a new team](../managing-teams.mdx)
+2. [Create a team](../managing-teams.mdx).
 
-3. Create a [new app](../managing-apps.mdx) to use specifically with Codex and
-   assign it to the team you created
+3. [Create an app](../managing-apps.mdx) for Codex and assign it to the team.
 
-4. Copy the **API URL** and **API Key** shown at the top of the app page
+4. Copy the **API URL** and **API Key** from the app page.
 
 </Stepper>
 
-## Configure Codex CLI
-
-There are two approaches you can take to using Codex with Zuplo's AI Gateway.
-
-1. **Route OpenAI through AI Gateway** - This would configure your OpenAI
-   provider in Codex to route requests through the AI Gateway rather than
-   directly to OpenAI
+## Configure Codex
 
-2. **Create a Zuplo specific provider** - Use Zuplo as a provider that be
-   selected in the Codex configuration and work with any OpenAI compatible
-   models
+:::warning{title="Replace the provider name"}
 
-Configuration steps for both options are below:
+The examples assume your provider is named `openai`. Replace that prefix with
+the name of **your** provider before copying anything. A provider named
+`my-openai` routes `my-openai/gpt-5`. The model part must be an ID that provider
+serves. Check [your provider's page](../managing-providers.mdx) in the Portal.
 
-### Route OpenAI through AI Gateway
+:::
 
-Open the [Codex configuration](https://developers.openai.com/codex/local-config)
-`~/.codex/config.toml` and modify the `model_providers.openai-chat-completions`
-entry so that the `base_url` points to your app's API URL with `/v1` appended,
-and set your `env_key` to the API Key of the app you created to use with Codex.
-The app page in the Zuplo Portal shows the API URL, which ends in the app's ID.
+Codex reads configuration from `~/.codex/config.toml`. Create this file (and the
+`~/.codex` directory if needed) if it does not exist. Add the following:
 
 ```toml
-[model_providers.openai-chat-completions]
-name = "OpenAI using Chat Completions"
+model_provider = "zuplo"
+model = "openai/gpt-5"
+
+[model_providers.zuplo]
+name = "Zuplo AI Gateway"
 base_url = "https://my-gateway-main-2e18f50.zuplo.app/config_fe0a04972d2848e0a94ae4b8bcd1497e/v1"
 env_key = "ZUPLO_AI_GATEWAY_API_KEY"
+wire_api = "responses"
 ```
 
-Save the file and reload Codex. Your OpenAI requests will now be routed through
-the Zuplo AI Gateway.
+- `base_url` is the app's API URL with `/v1` appended.
+- `model` is `providerName/model`.
 
-### Zuplo AI Gateway provider
+Set the API key in your environment:
 
-To add a specific provider for the AI Gateway you can add an additional entry to
-the Codex `config.toml` file.
-
-```toml
-[model_providers.zuplo]
-name = "Zuplo AI Gateway"
-base_url = "https://my-gateway-main-2e18f50.zuplo.app/config_fe0a04972d2848e0a94ae4b8bcd1497e/v1"
-env_key = "ZUPLO_AI_GATEWAY_API_KEY"
+```bash
+export ZUPLO_AI_GATEWAY_API_KEY="<your-app-api-key>"
 ```
 
-Save the file and reload Codex. Your Zuplo AI Gateway provider will now be
-available and you can switch Codex over to use it at any time by running:
+Restart Codex. All requests now go through the gateway.
+
+### Rules
+
+- `model_provider = "zuplo"` is required. Without it, Codex uses its built-in
+  `openai` provider and bypasses the gateway.
+- `wire_api` must be `responses`. Codex speaks only the Responses API; it
+  [removed](https://github.com/openai/codex/discussions/7782) support for
+  `/v1/chat/completions`, and `wire_api = "chat"` fails to load.
+- Put this configuration in the user-level file. Codex ignores `model_provider`
+  and `model_providers` in a project-level `.codex/config.toml`.
+
+## Switch models
+
+Set `model` in `config.toml`, or pass it on the command line:
 
 ```bash
-codex --config model_provider="zuplo"
+codex --config model_provider="zuplo" --model "openai/gpt-5.6-sol"
 ```
 
-### Choosing a model
+Do not use the `/model` picker. It sends model names without the provider
+prefix, and the gateway rejects them with a `400`.
+
+Codex warns that it has no metadata for a prefixed model name. Requests still
+succeed.
 
 The app's
 [Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy controls which models the app may use. Codex names the model as
-`providerName/model`, where `providerName` is the provider name configured in
-your gateway:
+policy controls which models the app can use.
+
+## Verify
 
 ```bash
-codex --config model_provider="zuplo" --model "openai/gpt-5"
+codex exec "Reply with the single word OK"
 ```
 
-A request with no model, or a model without that prefix, gets a `400`. Adding
-[Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx) with
-an allow list also supplies a default, letting requests omit the model.
+The session header shows `provider: zuplo`. The request appears in the app's
+usage in the Zuplo Portal.
+
+## Troubleshooting
+
+| Error                                                                                      | Fix                                                                 |
+| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- |
+| `400` `The request body model must use "providerName/model"`                               | Add the provider prefix to `model`. Do not use the `/model` picker. |
+| `ERROR: Missing environment variable: ZUPLO_AI_GATEWAY_API_KEY`                            | Export the variable in the shell that runs Codex.                   |
+| `401` `Authorization Failed`                                                               | The API key is wrong. Copy it from the app's **API Key** tab.       |
+| Errors mention `api.openai.com` or `not supported when using Codex with a ChatGPT account` | Codex is not using your provider. Set `model_provider = "zuplo"`.   |

package/docs/ai-gateway/vertex-ai.mdx

@@ -358,6 +358,12 @@ const response = await client.chat.completions.create({
 Streaming works the same way—set `stream: true` and read the
 `chat.completion.chunk` events.
 
+For the Vercel AI SDK, use `@ai-sdk/openai-compatible` for Gemini and Model
+Garden models and `@ai-sdk/anthropic` for Claude—see the
+[Vertex AI section](./integrations/ai-sdk.mdx#vertex-ai) of the AI SDK page. The
+`@ai-sdk/google-vertex` provider doesn't work; see
+[Troubleshooting](#troubleshooting).
+
 ### Embeddings
 
 Embeddings use the same client and the same `/v1/embeddings` endpoint as any
@@ -474,6 +480,32 @@ doesn't serve the model is the separate `400` described above.
 require the project to turn on data sharing for the `anthropic` publisher. The
 error names the `setPublisherModelConfig` setting to change.
 
+**A request fails when you use `@ai-sdk/google-vertex`.** The provider posts to
+Vertex's own publisher paths—`{model}:generateContent` for Gemini, and
+`{model}:rawPredict` on its `/anthropic` entry—which the gateway doesn't serve,
+so both return a `404`. Use `@ai-sdk/openai-compatible` for Gemini and Model
+Garden models and `@ai-sdk/anthropic` for Claude—see the
+[AI SDK Vertex section](./integrations/ai-sdk.mdx#vertex-ai). For its
+`/anthropic` (Claude) entry specifically, the
+[SDK path shim](./cookbooks/sdk-path-shim.mdx) can repoint
+`@ai-sdk/google-vertex/anthropic` onto `/v1/messages`; the Gemini entry can't be
+repointed that way.
+
+**A request fails when you use `@anthropic-ai/vertex-sdk`.** The
+`AnthropicVertex` client rewrites the request onto Vertex's
+`publishers/anthropic/models/{model}:rawPredict` path, which the gateway doesn't
+serve. Use the plain `Anthropic` client from `@anthropic-ai/sdk` with
+`authToken`—see
+[Call Claude models on the Messages API](#call-claude-models-on-the-messages-api).
+To keep using `AnthropicVertex` instead, install the
+[SDK path shim](./cookbooks/sdk-path-shim.mdx), which rewrites that publisher
+path onto `/v1/messages`.
+
+**A request fails when you use `@google/genai`.** With `vertexai: true` the
+client posts to Gemini's native `{model}:generateContent` path, and it also
+misreads a two-slash model reference as `publisher/model`. Use an OpenAI client
+on `/v1/chat/completions`—see [Call the models](#call-the-models).
+
 ## Next steps
 
 - [AI Providers](./providers.mdx)—the capability matrix across every supported

package/docs/articles/custom-domains.mdx

@@ -22,8 +22,9 @@ Zuplo supports two types of custom domains that can be configured separately:
    `cname.zuplodocs.com`. Learn more about the Developer Portal in the
    [Developer Portal documentation](/docs/dev-portal/overview).
 
-Both types of custom domains can be managed from the same Custom Domains section
-in your project settings and follow a similar configuration process.
+Manage both types of custom domains in
+[**Account Settings → Custom Domains**](https://portal.zuplo.com/+/account/settings/custom-domains).
+They follow a similar configuration process.
 
 :::note
 

package/docs/articles/source-control.mdx

@@ -65,9 +65,10 @@ If your code lives elsewhere but you want to use a specific CI/CD system:
 
 ## How Branch-Based Deployments Work
 
-Every Git branch maps to a Zuplo environment. Push to `main` and deploy to your
-main environment. Push to `feature-auth` and get a `feature-auth` environment
-automatically.
+With the GitHub integration, every Git branch maps to a Zuplo environment. Push
+to `main` and deploy to your main environment. Push to `feature-auth` and get a
+`feature-auth` environment automatically. For other providers, configure your
+CI/CD pipeline to deploy each branch.
 
 This enables powerful workflows like PR preview environments where reviewers can
 test changes against a live API before merging.

package/docs/articles/testing.mdx

@@ -140,11 +140,11 @@ and the same file supplies fixture values to `zuplo test`. See
 
 ## Test before merge
 
-Every branch pushed to your connected source control provider deploys as a
-preview environment: a full Zuplo deployment on the same edge network as
-production, at its own URL. Running your suite there is the highest-fidelity
-check available before a change merges, and it needs no shared staging
-environment.
+With the GitHub integration, pushing a feature branch automatically creates a
+preview environment at its own URL. For GitLab, Bitbucket, or Azure DevOps,
+configure a [CI/CD pipeline](./custom-ci-cd.mdx) to deploy the branch. Running
+your suite against a preview deployment lets you test changes before merging
+without a shared staging environment.
 
 - [Testing preview environments](./testing-preview-environments.mdx) — getting
   the URL into your tests, per-environment services and secrets, and what to

package/docs/articles/upstream-iam-auth.mdx

@@ -19,8 +19,8 @@ identity provider you control. For the alternatives, see
 
 ## Federated identity or stored credentials
 
-Every provider offers two paths, and the choice matters more than which cloud
-you're on.
+Zuplo offers federated identity and stored-credential policies. The available
+options depend on your cloud provider, as shown in the policy table below.
 
 **Federated identity** is the stronger option. Zuplo presents a short-lived,
 audience-bound OIDC token that proves which gateway is calling, and your cloud

package/docs/concepts/how-zuplo-works.mdx

@@ -87,7 +87,8 @@ workflow is:
 
 1. **Develop** locally or in the Zuplo Portal
 2. **Push** to your Git repository (GitHub, GitLab, Bitbucket, or Azure DevOps)
-3. **Deploy** automatically - Zuplo builds and deploys your gateway globally
+3. **Deploy** automatically with the GitHub integration, or configure a CI/CD
+   pipeline to deploy from GitLab, Bitbucket, or Azure DevOps
 
 Deployments complete in seconds. Each Git branch gets its own isolated
 environment with its own URL, making it easy to test changes before merging to

package/docs/dev-portal/migration.mdx

@@ -125,8 +125,8 @@ process, continue with the manual migration steps below.
 
    :::caution
 
-   Currently, this migration must be done locally. It cannot be done in the
-   Zuplo Portal.
+   Follow these manual migration steps locally. To migrate in the Zuplo Portal,
+   use the [built-in migration tool](#migrate-in-the-portal).
 
    :::
 

package/docs/getting-started/dev-portal/index.mdx

@@ -8,8 +8,8 @@ centered: false
 toc: false
 title: Getting Started with Developer Portal
 description:
-  Publish docs and self-serve API keys with Zudoku with Zuplo, in the Portal,
-  locally with the CLI, or with an AI agent.
+  Publish interactive API docs and let consumers manage their API keys through a
+  developer portal built in the Portal, locally, or with an AI agent.
 ---
 
 <WizardSteps build="dev-portal" />

package/docs/getting-started/gateway/add-api-key-auth/index.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Add API key authentication - Portal
@@ -166,3 +167,5 @@ Let's get started.
    [our developer portal auth docs](/docs/dev-portal/zudoku/configuration/authentication).
 
 </Stepper>
+
+<TutorialPager build="gateway" method="portal" step="add-api-key-auth" />

package/docs/getting-started/gateway/add-api-key-auth/local.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Add API key authentication - Editor
@@ -154,3 +155,5 @@ Let's get started.
    :::
 
 </Stepper>
+
+<TutorialPager build="gateway" method="local" step="add-api-key-auth" />

package/docs/getting-started/gateway/add-rate-limiting/index.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Add rate limiting - Portal
@@ -81,3 +82,5 @@ limiter.
    echo API.
 
 </Stepper>
+
+<TutorialPager build="gateway" method="portal" step="add-rate-limiting" />

package/docs/getting-started/gateway/add-rate-limiting/local.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Add rate limiting - Editor
@@ -100,3 +101,5 @@ full power of the world's best rate limiter.
    your API.
 
 </Stepper>
+
+<TutorialPager build="gateway" method="local" step="add-rate-limiting" />

package/docs/getting-started/gateway/agent.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Getting Started with API Gateway - Agent
@@ -84,7 +85,7 @@ from inside your project directory.
    2. Add the rate-limiting inbound policy (rateLimitBy: ip, 2 requests / 1 minute) to every route.
    3. Add the api-key-inbound policy to every route, ordered before rate limiting.
    4. Make rate limiting dynamic: create modules/rate-limit.ts exporting rateLimit() that returns 1000 req/min for user.data.customerType === "premium", 5 for "free", 30 otherwise, and switch the policy to rateLimitBy: "function".
-   5. Run npm run dev and verify with curl that GET /todos returns 401 without a key. I will create the free and premium keys in the Portal afterward; leave key-based tests for me.
+   5. Use the already-running dev server to verify with curl that GET /todos returns 401 without a key. I will create the free and premium keys in the Portal afterward; leave key-based tests for me.
 
    Explain each config change in one line and stop before pushing to git.
    ```

package/docs/getting-started/gateway/deploy-to-the-edge/index.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Deploy to the edge - Portal
@@ -229,3 +230,5 @@ when running commits, pulls or try to open a pull request.
 - If the GitHub repository has been renamed or moved to a different
   organization, try disconnecting and reconnecting to it. You can do this by
   going to your Zuplo project's settings > Source Control section
+
+<TutorialPager build="gateway" method="portal" step="deploy-to-the-edge" />

package/docs/getting-started/gateway/deploy-to-the-edge/local.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Deploy to the edge - Editor
@@ -132,3 +133,5 @@ Zuplo project in the Portal. The local files alone cannot receive a deployment.
    :::
 
 </Stepper>
+
+<TutorialPager build="gateway" method="local" step="deploy-to-the-edge" />

package/docs/getting-started/gateway/dynamic-rate-limiting/index.mdx

@@ -1,5 +1,6 @@
 ---
 category: API Management
+disablePager: true
 showLastModified: false
 suggestEdit: false
 title: Dynamic rate limiting - Portal
@@ -175,3 +176,5 @@ less than an hour.
   questions answered
 - Start generating revenue from your new API with our
   [Monetization tutorial](../../../articles/monetization/index.mdx)
+
+<TutorialPager build="gateway" method="portal" step="dynamic-rate-limiting" />