zuplo 7.8.7 → 7.8.8

package/docs/ai-gateway/custom-policies.mdx

@@ -22,7 +22,8 @@ terms. By the end, one app on your gateway rejects a prompt containing
 ## Prerequisites
 
 - An AI Gateway project connected to a Git repository, with a provider, a team,
-  and an app—the [Getting Started](./getting-started.mdx) guide covers this
+  and an app—the [Getting Started](../getting-started/ai-gateway/portal.mdx)
+  guide covers this
 - A local clone of the gateway's repository
 
 <Stepper>

package/docs/ai-gateway/usage-limits.mdx

@@ -357,8 +357,8 @@ Each app, team, and the gateway show current usage against their limits:
 
 ## Related Resources
 
-- [Getting Started](./getting-started.mdx) - Set up your first AI Gateway
-  project with budget controls
+- [Getting Started](../getting-started/ai-gateway/portal.mdx) - Set up your
+  first AI Gateway project with budget controls
 - [Managing Teams](./managing-teams.mdx) - Configure team-level budgets
 - [Managing Apps](./managing-apps.mdx) - Configure app-level limits
 - [Fallback Models](./fallback.mdx) - Serve a cheaper model instead of blocking

package/docs/api-management/overview.md

@@ -11,8 +11,8 @@ designed for developers. It offers fast deployment, GitOps-friendly workflows,
 and unlimited environments. Whether you're an individual developer or part of an
 engineering team, Zuplo makes it easy to:
 
-- [Add authentication and access control](../articles/step-3-add-api-key-auth.mdx)
-- [Implement rate limiting](../articles/step-2-add-rate-limiting.mdx)
+- [Add authentication and access control](../getting-started/gateway/add-api-key-auth/index.mdx)
+- [Implement rate limiting](../getting-started/gateway/add-rate-limiting/index.mdx)
 - Write custom logic to run at the gateway layer
 - Build a [rich developer portal](../dev-portal/overview.mdx) with self-serve
   tools for auth and monetization

package/docs/articles/add-api-to-backstage.mdx

@@ -26,9 +26,10 @@ Add a new route with the path `/openapi`, and select the `OpenAPI Spec Handler`
 from the Request Handler selector. Save your changes and commit them to your
 production branch. If you haven't already connected your Zuplo API to a GitHub
 repository, you can follow
-[these instructions](./step-4-deploying-to-the-edge.mdx) to do so. Once your
-Zuplo API is redeployed, you should now be able to retrieve your public-ready
-OpenAPI file by hitting `https://<your-prod-zuplo-api-domain>/openapi`.
+[these instructions](../getting-started/gateway/deploy-to-the-edge/index.mdx) to
+do so. Once your Zuplo API is redeployed, you should now be able to retrieve
+your public-ready OpenAPI file by hitting
+`https://<your-prod-zuplo-api-domain>/openapi`.
 
 ![Zuplo route](../../public/media/add-api-to-backstage/image-3.png)
 

package/docs/articles/api-key-consumer-bucket-portal-ui.mdx

@@ -23,7 +23,7 @@ managers), see [Manage Keys in the Portal](./api-key-administration.mdx).
 ## Prerequisites
 
 - A Zuplo project with at least one deployed environment (see the
-  [getting started tutorial](./step-1-setup-basic-gateway.mdx))
+  [getting started tutorial](../getting-started/gateway/setup-a-basic-gateway/index.mdx))
 - The [API Key Authentication policy](../policies/api-key-inbound.mdx)
   configured on your routes
 - Permission to manage API key consumers in your project

package/docs/articles/api-key-management.mdx

@@ -11,7 +11,7 @@ your backend.
 :::tip
 
 To start using Zuplo API Keys in only a few minutes
-[see the quickstart](../articles/step-3-add-api-key-auth.mdx).
+[see the quickstart](../getting-started/gateway/add-api-key-auth/index.mdx).
 
 :::
 

package/docs/articles/migrate-from-apigee.md

@@ -401,8 +401,8 @@ between both gateways.
 
 ## Next steps
 
-- [Set up your first Zuplo gateway](./step-1-setup-basic-gateway.md)
-- [Add rate limiting](./step-2-add-rate-limiting.md)
-- [Add API key authentication](./step-3-add-api-key-auth.md)
+- [Set up your first Zuplo gateway](../getting-started/gateway/setup-a-basic-gateway/index.mdx)
+- [Add rate limiting](../getting-started/gateway/add-rate-limiting/index.mdx)
+- [Add API key authentication](../getting-started/gateway/add-api-key-auth/index.mdx)
 - [Configure your developer portal](../dev-portal/overview.mdx)
 - [Set up source control](./source-control.md)

package/docs/articles/migrate-from-aws-api-gateway.md

@@ -241,8 +241,8 @@ secrets to secure the connection between Zuplo and your AWS backends.
 
 ## Next steps
 
-- [Set up your first Zuplo gateway](./step-1-setup-basic-gateway.md)
-- [Add rate limiting](./step-2-add-rate-limiting.md)
-- [Add API key authentication](./step-3-add-api-key-auth.md)
+- [Set up your first Zuplo gateway](../getting-started/gateway/setup-a-basic-gateway/index.mdx)
+- [Add rate limiting](../getting-started/gateway/add-rate-limiting/index.mdx)
+- [Add API key authentication](../getting-started/gateway/add-api-key-auth/index.mdx)
 - [Configure your developer portal](../dev-portal/overview.mdx)
 - [Set up source control](./source-control.md)

package/docs/articles/migrate-from-azure-apim.md

@@ -285,8 +285,8 @@ connection between Zuplo and your Azure backends.
 
 ## Next steps
 
-- [Set up your first Zuplo gateway](./step-1-setup-basic-gateway.md)
-- [Add rate limiting](./step-2-add-rate-limiting.md)
-- [Add API key authentication](./step-3-add-api-key-auth.md)
+- [Set up your first Zuplo gateway](../getting-started/gateway/setup-a-basic-gateway/index.mdx)
+- [Add rate limiting](../getting-started/gateway/add-rate-limiting/index.mdx)
+- [Add API key authentication](../getting-started/gateway/add-api-key-auth/index.mdx)
 - [Configure your developer portal](../dev-portal/overview.mdx)
 - [Set up source control](./source-control.md)

package/docs/articles/migrate-from-kong.md

@@ -293,8 +293,8 @@ configuration-as-code. Zuplo takes this further with native GitOps:
 
 ## Next steps
 
-- [Set up your first Zuplo gateway](./step-1-setup-basic-gateway.md)
-- [Add rate limiting](./step-2-add-rate-limiting.md)
-- [Add API key authentication](./step-3-add-api-key-auth.md)
+- [Set up your first Zuplo gateway](../getting-started/gateway/setup-a-basic-gateway/index.mdx)
+- [Add rate limiting](../getting-started/gateway/add-rate-limiting/index.mdx)
+- [Add API key authentication](../getting-started/gateway/add-api-key-auth/index.mdx)
 - [Configure your developer portal](../dev-portal/overview.mdx)
 - [Set up source control](./source-control.md)

package/docs/articles/source-control-setup-github.mdx

@@ -11,8 +11,8 @@ configuration required.
 
 This guide assumes you have a Zuplo project created. If you don't have one yet,
 follow the steps in
-[Step 1 - Setup a Basic Gateway](./step-1-setup-basic-gateway.mdx) to create a
-new Zuplo project.
+[Step 1 - Setup a Basic Gateway](../getting-started/gateway/setup-a-basic-gateway/index.mdx)
+to create a new Zuplo project.
 
 <Stepper>
 

package/docs/cli/create-zuplo-api.mdx

@@ -42,7 +42,7 @@ npx create-zuplo-api@latest
   (`claude`, `copilot`, `cursor`, `windsurf`, `codex`), or `none` to skip agent
   setup. See [Configuring AI coding agents](#configuring-ai-coding-agents)
 - `--template <template-name>` - A built-in template to bootstrap the API with
-  (`default`, `default-empty`, or `ai-gateway-v2`). Can't be combined with
+  (`default`, `default-empty`, or `ai-gateway`). Can't be combined with
   `--example` or `--empty`. See [Choosing a template](#choosing-a-template)
 - `-e, --example <example-name|github-url>` - An example to bootstrap the API
   with. You can use an example name from the official Zuplo repository or a
@@ -88,18 +88,18 @@ flag you get the `default` template.
 | --------------- | --------------------------------------------------------------------------------------------- |
 | `default`       | Sample `/todos` routes, a `hello-world` module, a dev portal in `docs/`, and VS Code settings |
 | `default-empty` | The same project with no routes defined and no VS Code settings                               |
-| `ai-gateway-v2` | An [AI Gateway](../ai-gateway/overview.mdx) project, without a dev portal                     |
+| `ai-gateway`    | An [AI Gateway](../ai-gateway/overview.mdx) project, without a dev portal                     |
 
 `--empty` is shorthand for `--template default-empty`.
 
-The `ai-gateway-v2` template scaffolds `config/ai.oas.json`, which routes
+The `ai-gateway` template scaffolds `config/ai.oas.json`, which routes
 `/:app_id/v1/*` to the AI Gateway handler, and `config/policies.json`, which
 declares the policies an application's policy chain can select. It ships no
 `docs/` directory, so the CLI skips the
 [dev portal](../dev-portal/overview.mdx) workspace:
 
 ```bash
-npx create-zuplo-api@latest my-gateway --template ai-gateway-v2
+npx create-zuplo-api@latest my-gateway --template ai-gateway
 ```
 
 `--template` names a built-in template, which is why it can't be combined with

package/docs/cli/openapi-merge.mdx

@@ -125,7 +125,7 @@ To rename the destination file, use the `--destination` option.
 ```bash
 zuplo openapi merge \
   --source https://example.com/path/to/openapi.json \
-  --destination new-name
+  --destination ./config/new-name.oas.json
 ```
 
 </CliCommand>

package/docs/cli/openapi-merge.partial.mdx

@@ -25,5 +25,5 @@ To rename the destination file, use the `--destination` option.
 ```bash
 zuplo openapi merge \
   --source https://example.com/path/to/openapi.json \
-  --destination new-name
+  --destination ./config/new-name.oas.json
 ```

package/docs/concepts/ai-gateway.mdx

@@ -64,7 +64,7 @@ are the same ones described in [How Zuplo Works](./how-zuplo-works.mdx).
 
 ## Next steps
 
-- [Get started with the AI Gateway](../ai-gateway/getting-started.mdx)
+- [Get started with the AI Gateway](../getting-started/ai-gateway/portal.mdx)
 - [Browse the SDK integrations](../ai-gateway/integrations/openai.mdx) for
   OpenAI, the Vercel AI SDK, LangChain, Claude Code, Codex, and Goose
 - Explore the [AI Gateway policies](../ai-gateway/policies/overview.mdx)

package/docs/concepts/mcp.mdx

@@ -55,9 +55,9 @@ apply to any other route.
 
 ## Next steps
 
-- [MCP Gateway quickstart](../mcp-gateway/quickstart.mdx) — expose an upstream
-  MCP server and connect Claude Desktop
-- [MCP quickstart for the MCP Server handler](../articles/mcp-quickstart.mdx) —
-  turn an API into MCP tools
+- [MCP Gateway quickstart](../getting-started/mcp-gateway/portal.mdx) — expose
+  an upstream MCP server and connect Claude Desktop
+- [MCP quickstart for the MCP Server handler](../getting-started/mcp-server/portal.mdx)
+  — turn an API into MCP tools
 - [Connect MCP clients](../mcp-gateway/connect-clients/overview.mdx) — Claude,
   ChatGPT, Cursor, VS Code, and others

package/docs/dedicated/architecture.mdx

@@ -19,7 +19,7 @@ A managed dedicated instance of Zuplo consists of the following components:
   authorization, rate limiting, and other features.
 - **Gateway Services**: Zuplo, being a highly distributed gateway, uses services
   to facilitate features such as
-  [Rate Limiting](../articles/step-2-add-rate-limiting.mdx) and
+  [Rate Limiting](../getting-started/gateway/add-rate-limiting/index.mdx) and
   [API Key Authentication](../articles/api-key-management.mdx).
 - **Control Plane**: The Control Plane manages the configuration of the Zuplo
   Gateway. It deploys new configurations, manages the lifecycle of the Zuplo

package/docs/errors/not-found.mdx

@@ -40,4 +40,4 @@ response when no route matches. See
 ## Related resources
 
 - [Routes Designer](../articles/local-development-routes-designer.mdx)
-- [Deploying to the Edge](../articles/step-4-deploying-to-the-edge.mdx)
+- [Deploying to the Edge](../getting-started/gateway/deploy-to-the-edge/index.mdx)

package/docs/getting-started/ai-gateway/portal.mdx

@@ -0,0 +1,181 @@
+---
+category: AI Gateway
+showLastModified: false
+suggestEdit: false
+sidebar_label: Portal
+title: Getting Started with AI Gateway - Portal
+description:
+  Create an AI Gateway in the Portal, try the free demo model, and send an
+  authenticated chat request with cURL or the OpenAI SDK.
+---
+
+<WizardSteps build="ai-gateway" method="portal" />
+
+Create an AI Gateway, send a chat request through it, and connect an OpenAI SDK
+client. This tutorial uses the free Zuplo Demo provider, so you don't need a
+provider API key.
+
+## Prerequisites
+
+- A [Zuplo account](https://portal.zuplo.com).
+- A terminal with cURL to test the gateway from outside the Portal.
+
+## Create and test your AI Gateway
+
+<Stepper>
+
+1. **Create an AI Gateway project**
+
+   Open [**Projects**](https://portal.zuplo.com/+/account/projects), click **New
+   Project**, and select **AI Gateway**. Name the project `my-ai-gateway` and
+   click **Create Project**.
+
+   <ModalScreenshot>
+
+   ![New project dialog with AI Gateway selected](/media/ai-gateway-getting-started/create-project.png)
+
+   </ModalScreenshot>
+
+   When setup finishes, the project opens with **Create your first app**. The
+   gateway is already deployed.
+
+2. **Check the demo provider**
+
+   Open
+   [**Settings → AI Providers**](https://portal.zuplo.com/+/account/project/ai/settings/data-models).
+   The new project includes **Zuplo Demo**, which provides test models without a
+   provider API key. This tutorial uses `zuplodemo/pirate`.
+
+   <ModalScreenshot>
+
+   ![AI provider settings with the Zuplo Demo provider](/media/ai-gateway-getting-started/providers.png)
+
+   </ModalScreenshot>
+
+   The part before `/` names the provider; the part after `/` names the model.
+   Later, use **Add Provider** to configure your own provider and its models.
+   See [AI Providers](../../ai-gateway/providers.mdx).
+
+3. **Create an app**
+
+   Open [**Apps**](https://portal.zuplo.com/+/account/project/ai/apps) and click
+   **Create App**. Enter `Tutorial app` as the **App name**. Keep the
+   **Default** pool selected and click **Create app**.
+
+   <ModalScreenshot>
+
+   ![New app dialog with an app name and the Default pool](/media/ai-gateway-getting-started/create-app.png)
+
+   </ModalScreenshot>
+
+   An app represents the software that calls your gateway. Each app has its own
+   URL and API key. The first app also creates the Default pool, which groups
+   apps and supplies shared policy settings.
+
+4. **Review authentication**
+
+   Open the app's **Policies** tab. The new app inherits **API Key
+   Authentication** from its pool. Keep this policy in place: requests must send
+   the app's key in the `Authorization` header.
+
+   <ModalScreenshot>
+
+   ![App policy chain with inherited API Key Authentication](/media/ai-gateway-getting-started/policies.png)
+
+   </ModalScreenshot>
+
+   You can add policies for model filtering, budgets, and other controls here.
+   For this first request, keep the default chain. See
+   [Policy Chains](../../ai-gateway/policy-chains.mdx).
+
+5. **Send a request in the Playground**
+
+   Click **Playground** in the app header. Select `zuplodemo/pirate`, enter
+   `Say hello`, and send the message. A pirate-themed reply confirms that the
+   app can reach the provider through the gateway.
+
+   <ModalScreenshot>
+
+   ![AI Playground showing a successful response from the pirate demo model](/media/ai-gateway-getting-started/playground.png)
+
+   </ModalScreenshot>
+
+6. **Call the gateway from a terminal**
+
+   In the **Playground**, click **Copy cURL**. Paste the copied command into
+   your terminal and run it. The command includes the selected model, your
+   conversation, and the app's API key. The response streams into the terminal
+   as it arrives.
+
+   Treat the copied command as a credential because it contains your API key.
+
+</Stepper>
+
+## Connect the OpenAI SDK
+
+Copy **API URL** from the app header and the app's key from its **API Key** tab.
+The URL includes the app ID after the hostname. Copy the complete URL without
+adding `/v1` yet.
+
+<ModalScreenshot>
+
+![App API Key tab with the key concealed](/media/ai-gateway-getting-started/api-key.png)
+
+</ModalScreenshot>
+
+Set these values in your terminal, replacing the placeholders:
+
+```bash
+export ZUPLO_APP_URL="https://YOUR_GATEWAY.zuplo.app/YOUR_APP_ID"
+export ZUPLO_APP_API_KEY="YOUR_APP_API_KEY"
+```
+
+With Node.js 24 or later installed, create a directory for the sample and
+install the SDK in the same terminal:
+
+```bash
+mkdir ai-gateway-client
+cd ai-gateway-client
+npm init -y
+npm install openai
+```
+
+Save this as `sample.mjs` and run `node sample.mjs` from the terminal where you
+set the environment variables:
+
+```javascript title="sample.mjs"
+import OpenAI from "openai";
+
+const client = new OpenAI({
+  baseURL: `${process.env.ZUPLO_APP_URL}/v1`,
+  apiKey: process.env.ZUPLO_APP_API_KEY,
+});
+
+const result = await client.chat.completions.create({
+  model: "zuplodemo/pirate",
+  messages: [{ role: "user", content: "Say hello" }],
+});
+
+console.log(result.choices[0].message.content);
+```
+
+The OpenAI SDK uses the app URL with `/v1` appended. It sends the app key to
+Zuplo; provider credentials stay in the gateway. See the
+[OpenAI SDK integration](../../ai-gateway/integrations/openai.mdx) for more
+examples.
+
+## Troubleshooting
+
+| Result                         | What to check                                                                                             |
+| ------------------------------ | --------------------------------------------------------------------------------------------------------- |
+| `401 Unauthorized`             | Use the app's API key, not a provider key. Include the `Bearer` prefix.                                   |
+| `404`                          | Copy the complete app URL, including its app ID, then append `/v1/chat/completions`.                      |
+| Model not found or not allowed | Use `zuplodemo/pirate` and confirm Zuplo Demo is enabled. If you added Model Filtering, allow this model. |
+
+## Next steps
+
+- [Add providers](../../ai-gateway/providers.mdx) to connect your own models.
+- [Configure policy chains](../../ai-gateway/policy-chains.mdx) to restrict
+  models or add budgets and guardrails.
+- [Connect source control](../../ai-gateway/source-control.mdx) to deploy code
+  changes from Git.

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

@@ -0,0 +1,148 @@
+---
+category: Developer Portal
+showLastModified: false
+suggestEdit: false
+sidebar_label: Agent
+title: Getting Started with Developer Portal - Agent
+description:
+  Build a developer portal with a coding agent, review its API key
+  configuration, and verify a signed-in request from the API playground.
+---
+
+<WizardSteps build="dev-portal" method="agent" />
+
+<MethodTabs build="dev-portal" method="agent" />
+
+Have a coding agent build a developer portal with an introduction, interactive
+API reference, and API key management. You'll assign a test key and verify the
+portal yourself.
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org/en/download) 24 or later and Git.
+- A [Zuplo account](https://portal.zuplo.com).
+- An installed coding agent and an email address for the portal sign-in test.
+
+## Build your developer portal with an agent
+
+<Stepper>
+
+1. **Create the project**
+
+   Run:
+
+   ```bash
+   npx create-zuplo-api@latest my-api-project
+   cd my-api-project
+   ```
+
+   When prompted, choose **Yes** to create a matching Portal project, complete
+   sign-in, and select your Zuplo account. Select the coding agent you use when
+   asked. The CLI creates and links the hosted project. See
+   [`create-zuplo-api`](../../cli/create-zuplo-api.mdx).
+
+   :::tip{title="Zuplo skills"}
+
+   The scaffold installs Zuplo skills in this project for Codex and Cursor and
+   configures the Claude Code plugin. If setup fails, follow
+   [Agent Skills](../../build-with-ai.mdx#agent-skills) from this directory
+   before starting your agent.
+
+   :::
+
+2. **Ask the agent to build the portal**
+
+   Open your agent in the project directory and give it this prompt:
+
+   ```text
+   Read the project instructions and bundled Zuplo docs. Customize the default
+   developer portal for a Todo API. Keep the generated project structure.
+
+   In docs/zudoku.config.tsx, set site.title and metadata.title to
+   "Todo Developer Portal" and metadata.description to
+   "Explore the Todo API and manage your API keys." Keep the API reference
+   sourced from ../config/routes.oas.json at /api. Keep demo authentication
+   and apiKeys.enabled for this tutorial.
+
+   Replace docs/pages/introduction.mdx with a short introduction telling users
+   to sign in, find their assigned key under their profile's API Keys menu,
+   and try Get all todos in API Reference. Keep it in navigation. Explain
+   that an administrator assigns a consumer to the user's key manager email;
+   do not implement automatic provisioning.
+
+   In config/policies.json add api-key-auth, policyType api-key-inbound,
+   using ApiKeyInboundPolicy from $import(@zuplo/runtime) with
+   allowUnauthenticatedRequests false. Put it first in the inbound chain for
+   GET /todos in config/routes.oas.json. Preserve the existing URL forward
+   handler. Set this route's corsPolicy to anything-goes for the browser demo.
+   Update info.description so it says GET /todos requires a bearer API key.
+   Do not claim the other sample routes are protected.
+
+   Ensure .env and .env.zuplo are ignored and do not read or print credentials.
+   Run npm run dev. Report the gateway and Docs Server URLs. Verify GET /todos
+   without a key returns 401. Do not deploy; show me the diff and explain how
+   to finish the signed-in browser test with a Dev consumer.
+   ```
+
+3. **Review and open the result**
+
+   Review `git diff`. Confirm the reference still points to
+   `../config/routes.oas.json`, API keys remain enabled, and authentication is
+   attached to `GET /todos`.
+
+   With `npm run dev` running, open the **Docs Server** URL printed in the
+   terminal, normally `http://localhost:9200`. Open `/introduction` to check
+   your new page, then open **API Reference** to check the Todo API.
+
+4. **Assign a test key**
+
+   In the Zuplo Portal, open your project and go to
+   [**Services → API Keys → Consumers**](https://portal.zuplo.com/+/account/project/services).
+   Select **Dev** and click **Create Consumer**. Enter `tutorial-consumer` for
+   **Subject**, your email under **Key managers**, and `{}` for **Metadata**.
+   Click **Save consumer**.
+
+   <ModalScreenshot>
+
+   ![Create a consumer and assign a key manager email](/media/api-key-consumer-bucket-portal-ui/create-consumer-modal.png)
+
+   </ModalScreenshot>
+
+5. **Verify the signed-in experience**
+
+   Sign in to the local developer portal with the key manager email. Open **API
+   Keys** from your profile menu and confirm the key appears. Then open **API
+   Reference → Get all todos**, click **Test**, expand **Authentication**,
+   select `tutorial-consumer`, and click **Send**. Expect `200 OK` and todos in
+   the response.
+
+   Test without credentials in a terminal:
+
+   ```bash
+   curl -i http://localhost:9000/todos
+   ```
+
+   Expect `401 Unauthorized`. If browser requests fail while cURL succeeds,
+   check the route's [CORS configuration](../../articles/cors.mdx). If the key
+   is missing, check the consumer's email and Dev bucket.
+
+6. **Publish after review**
+
+   Follow [Deploy to the edge](../gateway/deploy-to-the-edge/local.mdx), then
+   open **Deployment URLs → Dev Portal** in the Zuplo Portal. Create a consumer
+   in the **Prod** bucket to test the deployed portal.
+
+   Replace the demo authentication with your own
+   [identity provider](../../dev-portal/zudoku/configuration/authentication.md)
+   and restrict CORS to your portal's origin before inviting users.
+
+</Stepper>
+
+## Next steps
+
+- [Editor tutorial](./local.mdx) for the exact policy configuration and manual
+  walkthrough.
+- [Create consumers on login](../../dev-portal/dev-portal-create-consumer-on-auth.mdx)
+  to automate key assignment with your own identity provider.
+- [Customize navigation](../../dev-portal/zudoku/configuration/navigation.mdx)
+  and add pages for your API's users.

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

@@ -0,0 +1,26 @@
+---
+category: Developer Portal
+fullWidth: true
+disablePager: true
+showLastModified: false
+suggestEdit: false
+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.
+---
+
+<WizardSteps build="dev-portal" />
+
+A developer portal gives your API's users a place to read documentation, sign
+in, and test requests. This tutorial creates a portal with Zudoku, Zuplo's
+open-source documentation framework, using a sample Todo API.
+
+Choose a workflow to publish the reference docs and connect API key management.
+You assign a key to a consumer (the person or application calling your API),
+then sign in to test it. You need an email address you can access for the
+sign-in step.
+
+<MethodPicker build="dev-portal" />