zuplo 7.12.6 → 7.12.7

package/docs/mcp-gateway/auth/overview.mdx

@@ -5,6 +5,9 @@ description:
   How authentication works in the Zuplo MCP Gateway — the gateway as an OAuth
   2.1 server for MCP clients, and as an OAuth client to each upstream MCP
   server.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Zuplo MCP Gateway sits in the middle of two independent OAuth relationships.

package/docs/mcp-gateway/auth/upstream-oauth.mdx

@@ -5,6 +5,9 @@ description:
   How the Zuplo MCP Gateway acts as an OAuth client to upstream MCP servers —
   the two auth modes, client registration, the consent flow users experience,
   connect-required states, and token refresh.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The gateway sits between an MCP client and the upstream MCP servers a team

package/docs/mcp-gateway/capability-filtering.mdx

@@ -6,6 +6,9 @@ description:
   templates an upstream MCP server exposes — what the
   mcp-capability-filter-inbound policy filters, how projections work, and where
   the boundary actually lives.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Model Context Protocol lets a server advertise tools, prompts, resources,

package/docs/mcp-gateway/code-config/compatibility-dates.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Compatibility dates"
 description:
   The Zuplo MCP Gateway requires compatibilityDate 2026-03-01 or later in
   zuplo.jsonc.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Zuplo MCP Gateway requires `compatibilityDate >= 2026-03-01` in

package/docs/mcp-gateway/code-config/local-development.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Local development"
 description:
   Run the MCP Gateway locally, test OAuth without an identity provider, and
   configure local callback URLs and environment variables for your MCP clients.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Use `zuplo dev` to run the MCP Gateway locally on port `9000` with hot reload.

package/docs/mcp-gateway/code-config/mcp-proxy-handler.mdx

@@ -5,6 +5,9 @@ description:
   The route handler that turns a Zuplo path into an MCP Gateway endpoint —
   forwards POST requests to an upstream MCP server, rejects GET with 405, and
   emits per-capability analytics on every call.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 `McpProxyHandler` is the route handler that backs every MCP Gateway route. It

package/docs/mcp-gateway/code-config/multi-upstream.mdx

@@ -5,6 +5,9 @@ description:
   Front many upstream MCP servers from one Zuplo project. Share a single OAuth
   policy across every route, add one token exchange policy per upstream, and let
   each user maintain independent per-upstream connections.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 A single Zuplo deployment can front any number of upstream MCP servers. One

package/docs/mcp-gateway/code-config/overview.mdx

@@ -5,6 +5,9 @@ description:
   Wire up the Zuplo MCP Gateway in routes.oas.json and policies.json — register
   the runtime plugin, configure one OAuth policy and one token-exchange policy
   per upstream, and add an MCP route.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 To turn any Zuplo project into an MCP Gateway, configure four things in source

package/docs/mcp-gateway/connect-clients/chatgpt.mdx

@@ -5,6 +5,9 @@ description:
   Connect ChatGPT to a Zuplo MCP Gateway as a custom app using Developer Mode,
   scan the gateway tools, complete the OAuth flow, and use the app in
   conversation.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 ChatGPT connects to remote MCP servers as **custom apps**. OpenAI previously

package/docs/mcp-gateway/connect-clients/claude-code.mdx

@@ -5,6 +5,9 @@ description:
   Connect Claude Code's CLI to a Zuplo MCP Gateway using `claude mcp add`,
   authenticate over OAuth, and manage the connection from the `/mcp` slash
   command.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 [Claude Code](https://code.claude.com/) is Anthropic's command-line coding

package/docs/mcp-gateway/connect-clients/claude-desktop.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Claude Desktop"
 description:
   Connect Claude Desktop or Claude.ai to a Zuplo MCP Gateway as a custom remote
   connector, complete the OAuth flow, and start using your tools.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Claude Desktop and Claude.ai connect to remote MCP servers through **Custom

package/docs/mcp-gateway/connect-clients/cursor.mdx

@@ -5,6 +5,9 @@ description:
   Connect Cursor to a Zuplo MCP Gateway using a one-click deeplink or by editing
   `mcp.json` directly, complete the OAuth flow, and use gateway tools in Cursor
   Composer.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 [Cursor](https://cursor.com/) is an AI-first code editor. It speaks the MCP

package/docs/mcp-gateway/connect-clients/other-clients.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Other clients"
 description:
   Add a Zuplo MCP Gateway to Windsurf, Goose, Gemini CLI, GitHub Copilot CLI,
   Postman, MCPJam, Continue, LibreChat, and JetBrains AI Assistant.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Zuplo MCP Gateway works with any MCP client that speaks the Streamable HTTP

package/docs/mcp-gateway/connect-clients/overview.mdx

@@ -5,6 +5,9 @@ description:
   Learn how MCP clients connect to a Zuplo MCP Gateway, where to find the
   connection URL, what the OAuth flow looks like on first use, and which clients
   support which spec features.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Zuplo MCP Gateway exposes each MCP route at a stable HTTPS URL that any

package/docs/mcp-gateway/connect-clients/vs-code.mdx

@@ -5,6 +5,9 @@ description:
   Connect VS Code with GitHub Copilot to a Zuplo MCP Gateway through
   `.vscode/mcp.json`, the `code --add-mcp` CLI, or the Extensions view, and use
   gateway tools in Copilot Chat's Agent mode.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 VS Code with GitHub Copilot connects to remote MCP servers and exposes their

package/docs/mcp-gateway/cross-app-access/overview.mdx

@@ -6,6 +6,9 @@ description: |
   (ID-JAG) are, the problem they solve for AI agents and MCP, and how the Zuplo
   MCP Gateway performs the token exchange so your MCP servers and clients don't
   have to.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Cross App Access (XAA) lets one application reach another application's API on a

package/docs/mcp-gateway/cross-app-access/policy-reference.mdx

@@ -5,6 +5,9 @@ description: |
   Every configuration option for Cross App Access (XAA) on the Zuplo MCP Gateway
   — the id-jag mode on the token-exchange policy, where the gateway acts as the
   XAA requesting app.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Cross App Access is configured on the

package/docs/mcp-gateway/cross-app-access/quickstart.mdx

@@ -6,6 +6,9 @@ description: |
   Zuplo Portal — no repository to clone. The gateway fronts Okta's hosted
   xaa.dev Todo0 server and performs the Cross App Access (XAA) token exchange on
   every request.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 This quickstart builds a working Cross App Access (XAA) gateway entirely in the

package/docs/mcp-gateway/how-it-works.mdx

@@ -4,6 +4,9 @@ sidebar_label: "How it works"
 description:
   Architecture overview — request lifecycle, the two OAuth surfaces, the
   Streamable HTTP transport, and the configuration model.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP Gateway is a set of policies and a route handler that run inside any

package/docs/mcp-gateway/how-to/connect-upstream-api-key.mdx

@@ -5,6 +5,9 @@ description:
   Front an MCP server that authenticates with a static API key over a Bearer
   token. Configure a custom upstream in the wizard, strip the inbound auth
   token, and inject the upstream key with the Add or Set Request Headers policy.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Not every upstream MCP server uses OAuth. Many authenticate with a static API

package/docs/mcp-gateway/how-to/connect-upstream-oauth.mdx

@@ -5,6 +5,9 @@ description:
   Attach the mcp-token-exchange-inbound policy to an MCP route so the Zuplo MCP
   Gateway authenticates each user against an OAuth-protected upstream MCP
   server.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 When an upstream MCP server requires OAuth — either per user or as a shared

package/docs/mcp-gateway/how-to/curate-tools-local.mdx

@@ -5,6 +5,9 @@ description:
   Restrict and re-project the tools, prompts, resources, and resource templates
   a Zuplo MCP Gateway route exposes from its upstream MCP server by configuring
   the mcp-capability-filter-inbound policy in code.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 <CurateToolsPicker

package/docs/mcp-gateway/how-to/curate-tools.mdx

@@ -5,6 +5,9 @@ description:
   Restrict which tools, prompts, and resources a Zuplo MCP Gateway Virtual
   Server exposes from its upstream MCP server, using the Curate option in the
   Portal wizard.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 <CurateToolsPicker

package/docs/mcp-gateway/observability/analytics.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Analytics"
 description:
   What events the Zuplo MCP Gateway emits, the dimensions you'll filter by, and
   the kinds of operational questions the analytics dashboard answers.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Every authenticated MCP request the Zuplo MCP Gateway handles produces a set of

package/docs/mcp-gateway/observability/logging.mdx

@@ -5,6 +5,9 @@ description:
   How the Zuplo MCP Gateway logs — structured event-keyed entries with
   auto-attached route and subject fields, what the gateway intentionally
   excludes, and how the logs cross-reference analytics events.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Zuplo MCP Gateway emits structured logs alongside its analytics events. Each

package/docs/mcp-gateway/overview.mdx

@@ -5,6 +5,9 @@ description:
   Overview of the Zuplo MCP Gateway — a single OAuth-protected MCP endpoint that
   fronts multiple upstream MCP servers with curated tools and per-call
   analytics.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The Zuplo MCP Gateway fronts one or more remote

package/docs/mcp-gateway/policies/overview.mdx

@@ -2,6 +2,9 @@
 title: MCP Gateway policies overview
 sidebar_label: Overview
 description: Every policy available to an MCP Gateway and what each one does.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 import policies from "../../../policies.ui.json";

package/docs/mcp-gateway/reference.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Reference"
 description:
   URL catalog, OAuth scopes, default TTLs, required headers, and configuration
   constants for the Zuplo MCP Gateway.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 This page is the lookup table for facts about the gateway — every URL it

package/docs/mcp-gateway/server-registry.mdx

@@ -5,6 +5,9 @@ description:
   The read-only MCP Server Registry API (v0.1) the gateway serves by default —
   advertises every MCP route so clients and subregistries can discover them
   without authentication.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP Gateway serves a read-only

package/docs/mcp-gateway/test-clients.mdx

@@ -5,6 +5,9 @@ description:
   Use the MCP Inspector and MCPJam Inspector to manually exercise your Zuplo MCP
   Gateway routes — walk the OAuth flow, list tools, call them, and inspect every
   JSON-RPC message.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 A regular MCP client like Claude Desktop or Cursor is great for using a gateway,

package/docs/mcp-gateway/troubleshooting.mdx

@@ -4,6 +4,9 @@ sidebar_label: "Troubleshooting"
 description:
   Symptoms, likely causes, and fixes for the issues most commonly hit when
   setting up or running the Zuplo MCP Gateway.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 This page covers the issues people hit most often with the MCP Gateway,

package/docs/mcp-server/configuration-migration-guide.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server Configuration Migration Guide
 sidebar_label: Configuration Migration Guide
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 This guide explains how to migrate from the deprecated MCP server configuration

package/docs/mcp-server/custom-tools.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server Custom Tools
 sidebar_label: Custom Tools
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP Server Handler supports custom tools that allow you to create

package/docs/mcp-server/graphql.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server GraphQL Endpoints
 sidebar_label: GraphQL
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP Server Handler supports GraphQL endpoints through the `x-zuplo-route`

package/docs/mcp-server/openai-apps-sdk.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server With OpenAI Apps SDK
 sidebar_label: OpenAI Apps SDK
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The [OpenAI Apps SDK](https://developers.openai.com/apps-sdk) is an integration

package/docs/mcp-server/overview.mdx

@@ -4,6 +4,9 @@ sidebar_label: Overview
 description:
   Expose OpenAPI operations to AI clients as MCP tools, prompts, and resources
   with Zuplo's MCP Server handler.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 <span id="whats-mcp" />

package/docs/mcp-server/prompts.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server Prompts
 sidebar_label: Prompts
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP (Model Context Protocol) Server handler supports prompts in addition to

package/docs/mcp-server/resources.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server Resources
 sidebar_label: Resources
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP (Model Context Protocol) Server handler supports resources in addition

package/docs/mcp-server/testing.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server Testing
 sidebar_label: Testing
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 ## Using MCP Inspector

package/docs/mcp-server/tools.mdx

@@ -1,6 +1,9 @@
 ---
 title: MCP Server Tools
 sidebar_label: Tools
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The MCP (Model Context Protocol) Server handler supports tools, enabling you to

package/docs/mcp-server/troubleshooting.mdx

@@ -6,6 +6,9 @@ description:
   that returns 200 while the client errors, and invalid-argument rejections —
   using debug logging, the structured-content configuration, and the tool's
   advertised input schema.
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 When an AI client calls a tool exposed by the

package/docs/policies/_index.md

@@ -8,7 +8,7 @@
 | ai-gateway-configuration-executor-inbound | AI Gateway Configuration Executor | Loads the app configuration for the request (when auth or the configuration loader has not already), runs the inbound policy chain from that configuration, and enforces limits inherited from parent teams or the gateway root.  Place this policy on AI Gateway routes after optional authentication and optional `ai-gateway-configuration-loader-inbound`. When either of those already populated the app-configuration channel, this policy reuses it. Otherwise it loads the configuration with the route's `app_id` path parameter. Applications select from policies pre-declared by the gateway. Applications without a `inboundPolicyChain`, or with an empty chain, run no application-selected policies. Entry options replace the declaration's options as a complete object; omit them to inherit the declaration, including environment-backed credentials. Each occurrence receives a private deep copy of its entry options, so a policy mutating its options cannot corrupt the cached app configuration. | ai-gateway |
 | ai-gateway-configuration-loader-inbound | AI Gateway Configuration Loader | Loads the AI Gateway app configuration for the request into the request-scoped channel and does nothing else.  Place this policy on AI Gateway routes before `ai-gateway-configuration-executor-inbound` when you want configuration loading separated from chain execution. When `ai-gateway-auth-inbound` already populated the channel, this policy reuses it. Otherwise it loads the configuration with the route's `app_id` path parameter.  If this policy is omitted, the configuration executor still loads configuration itself before running the application chain. | ai-gateway |
 | ai-gateway-fallback-model-inbound | AI Gateway Fallback Model | Adds failure and quota fallbacks to an existing AI Gateway model selection.  Place this policy after AI Gateway Model Filtering. It never creates a model selection, so a misplaced policy cannot bypass filtering. | ai-gateway |
-| ai-gateway-metering-inbound | AI Gateway Metering | Meters AI Gateway usage for the application.  The authentication policy must run before this policy so the app configuration id is available for meter storage and analytics. Budgets are declared with `budgetRules` and enforced by the configuration executor. | ai-gateway |
+| ai-gateway-metering-inbound | AI Gateway Metering | Meters AI Gateway usage for the application.  The policy seeds the request's baseline increments for analytics and claims metering for the request so a repeated chain entry cannot count it twice. Usage is recorded in request analytics. Budgets are declared with `budgetRules` and enforced by the configuration executor through Gateway Service.  The authentication policy must run before this policy so the app configuration is available. | ai-gateway |
 | ai-gateway-model-filtering-inbound | AI Gateway Model Filtering | Matches AI Gateway requests against curated allow lists or open block lists, then stores the winning model reference for the route handler. | ai-gateway |
 | ai-gateway-model-override-inbound | AI Gateway Model Override | Forces one model for every request, or supplies a default model when a request omits one, then stores that selection for the AI Gateway handler.  An earlier policy's model selection is never overwritten, so a custom routing policy placed before this one stays authoritative. | ai-gateway |
 | ai-gateway-semantic-cache-inbound | AI Gateway Semantic Cache | AI Gateway Semantic Cache policy. This inbound policy looks up the semantic cache on entry and, on a miss, registers a response-sending hook to write the upstream response back into the cache.  Caching parameters (semanticTolerance, expirationSecondsTtl, namespace, recentMessageCount) come from the policy options, and presence in the route's chain is what enables it. An id from the authenticated app configuration always provides the cache namespace so application-supplied options cannot cross tenant partitions. The cache key covers the system prompt plus the last `recentMessageCount` messages (default 1) — applied when storing and when matching — so multi-turn conversations can hit entries cached from earlier, shorter ones.  Cache outcomes are reported on the response via the RFC 9211 `Cache-Status` header under the cache name `zp-aigw-sem-cache` (hit: `zp-aigw-sem-cache; hit; detail="similarity=0.93"`; miss: `zp-aigw-sem-cache; fwd=miss; stored`). Responses also include the `x-ai-gateway-cache: HIT\|MISS` and `x-ai-gateway-cache-similarity` headers. | ai-gateway |

package/docs/policies/ai-gateway-metering-inbound/doc.md

@@ -14,8 +14,7 @@ fallback model or returns `429 Too Many Requests`. Cached responses are also
 subject to budgets: a blocked cache hit returns `429 Too Many Requests` without
 using a fallback model.
 
-Place Metering after Model Filtering. Place it before Semantic Cache so cache
-hits count toward request limits.
+Place Metering after Model Filtering and before Semantic Cache.
 
 ## Example
 
@@ -23,7 +22,6 @@ hits count toward request limits.
 {
   "name": "ai-gateway-metering-inbound",
   "options": {
-    "throwOnFailure": false,
     "budgetRules": [
       {
         "budgetBy": "app",
@@ -241,7 +239,8 @@ Budget changes can take time to take effect. Usage is recorded asynchronously,
 so concurrent requests can exceed a budget before further requests are blocked.
 
 If a budget check is unavailable, requests can proceed unless a budget has
-already been determined to block them. The `throwOnFailure` option controls
-whether this policy fails the request when recording usage fails; it does not
-change how application, team, or gateway `budgetRules` handle unavailable
-checks.
+already been determined to block them.
+
+The `throwOnFailure` option is deprecated and has no effect. This policy no
+longer calls the metering service, so it has no failure to throw on. Usage is
+recorded in analytics, and budgets are checked by the gateway.

package/docs/policies/ai-gateway-metering-inbound/intro.md

@@ -9,6 +9,5 @@ expression its own budget, such as one budget per user with
 `request.headers.get("x-user-id")`.
 
 Place it after Model Filtering and before policies such as Semantic Cache that
-may answer without calling a provider. Metering fails open by default when
-recording usage fails; set `throwOnFailure` to `true` to fail the request
-instead.
+may answer without calling a provider. Budget checks fail open when the budget
+service is unavailable.

package/docs/policies/ai-gateway-metering-inbound/schema.json

@@ -12,7 +12,7 @@
   "requiresAI": true,
   "policyType": "ai-gateway-metering",
   "products": ["ai-gateway"],
-  "description": "Meters AI Gateway usage for the application.\n\nThe authentication policy must run before this policy so the app configuration id is available for meter storage and analytics. Budgets are declared with `budgetRules` and enforced by the configuration executor.",
+  "description": "Meters AI Gateway usage for the application.\n\nThe policy seeds the request's baseline increments for analytics and claims metering for the request so a repeated chain entry cannot count it twice. Usage is recorded in request analytics. Budgets are declared with `budgetRules` and enforced by the configuration executor through Gateway Service.\n\nThe authentication policy must run before this policy so the app configuration is available.",
   "deprecatedMessage": "",
   "required": ["handler"],
   "properties": {
@@ -55,15 +55,17 @@
                     }
                   ]
                 }
-              ],
-              "throwOnFailure": false
+              ]
             }
           ],
           "properties": {
             "throwOnFailure": {
               "type": "boolean",
               "default": false,
-              "description": "Fail the request instead of logging the error when recording usage with the metering service fails."
+              "deprecated": true,
+              "doNotSuggest": true,
+              "x-advanced": true,
+              "description": "Deprecated and has no effect. This policy no longer calls the metering service, so there is no failure to throw on."
             },
             "budgetRules": {
               "type": "array",
@@ -372,8 +374,7 @@
                   }
                 ]
               }
-            ],
-            "throwOnFailure": false
+            ]
           }
         }
       ]

package/docs/programmable-api/background-dispatcher.mdx

@@ -1,6 +1,9 @@
 ---
 title: BackgroundDispatcher
 sidebar_label: BackgroundDispatcher
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The BackgroundDispatcher class batches outbound transmissions for efficient

package/docs/programmable-api/background-loader.mdx

@@ -1,6 +1,9 @@
 ---
 title: BackgroundLoader
 sidebar_label: BackgroundLoader
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The BackgroundLoader class provides asynchronous loading of configuration data

package/docs/programmable-api/cache.mdx

@@ -2,6 +2,9 @@
 title: Cache
 sidebar_label: Cache
 draft: false
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 The [Cache API](https://developer.mozilla.org/en-US/docs/Web/API/Cache) provides

package/docs/programmable-api/compatibility-dates.mdx

@@ -1,5 +1,8 @@
 ---
 title: Compatibility Dates
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Zuplo is constantly shipping updates to the underlying runtime of projects.

package/docs/programmable-api/console-logging.mdx

@@ -1,6 +1,9 @@
 ---
 title: Console Logging
 sidebar_label: Console Logging
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 Zuplo supports standard JavaScript console logging methods as a convenience for

package/docs/programmable-api/context-data.mdx

@@ -1,6 +1,9 @@
 ---
 title: ContextData - Sharing Request Data
 sidebar_label: ContextData
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 It's often useful to store data throughout the life of a single request. This

package/docs/programmable-api/custom-cors-policy.mdx

@@ -1,6 +1,9 @@
 ---
 title: CORS Policy Configuration
 sidebar_label: CORS Policy Configuration
+applies_to:
+  product: gateway
+  hosting: all
 ---
 
 For a complete guide on configuring CORS including built-in policies, wildcard

package/docs/programmable-api/environment.mdx

@@ -1,6 +1,16 @@
 ---
 title: Gateway Environment Variables
 sidebar_label: Environment Variables
+applies_to:
+  product: gateway
+  hosting: all
+  differs:
+    managed-dedicated: >-
+      `ZUPLO_ENVIRONMENT_TYPE` values depend on the hosting environment, so
+      check for the values your deployment reports instead of assuming `edge`.
+    self-hosted: >-
+      `ZUPLO_ENVIRONMENT_TYPE` values depend on the hosting environment, so
+      check for the values your deployment reports instead of assuming `edge`.
 ---
 
 Your API gateway can read every environment variable set for its environment,