zuplo 7.8.23 → 7.8.25

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

@@ -143,7 +143,7 @@ Two things they need. Send **`store: true`** on the create, since your resource
 serves them only for a response it kept. And because these requests carry no
 body, there is no `model` in them for the gateway to route on—it uses the app's
 first configured completions model instead, so the app needs a
-[Model Filtering](../policies/ai-gateway-model-filtering-v2-inbound.mdx) policy
+[Model Filtering](../policies/ai-gateway-model-filtering-inbound.mdx) policy
 whose completions allow list **starts with an OpenAI-compatible Azure
 deployment**. Without one the gateway answers `400`, asking for preselected
 routing, before reaching Azure.
@@ -556,10 +556,10 @@ Azure's Responses API model list—an embedding deployment always fails this way
 response, or listed its input items. Those requests carry no body, so there is
 no `model` for the gateway to route on and it falls back to the app's first
 configured completions model. Add a
-[Model Filtering](../policies/ai-gateway-model-filtering-v2-inbound.mdx) policy
-to the app with an **OpenAI-compatible** Azure deployment first in its
-completions allow list. A Claude deployment in that slot still fails, since
-Claude doesn't serve Responses.
+[Model Filtering](../policies/ai-gateway-model-filtering-inbound.mdx) policy to
+the app with an **OpenAI-compatible** Azure deployment first in its completions
+allow list. A Claude deployment in that slot still fails, since Claude doesn't
+serve Responses.
 
 **A model in the picker fails at request time.** The picker lists the full Azure
 catalog, but a model only works once you deploy it in your resource, and model
@@ -594,5 +594,5 @@ Pass `baseURL` set to your app's URL plus `/v1`—see
   endpoint, and understand when changes deploy.
 - [AI Gateway Apps](./apps.mdx)—create the apps that call your Azure-backed
   models.
-- [Model Filtering policy](../policies/ai-gateway-model-filtering-v2-inbound.mdx)—control
+- [Model Filtering policy](../policies/ai-gateway-model-filtering-inbound.mdx)—control
   which models each app can call.

package/docs/ai-gateway/bedrock-mantle.mdx

@@ -253,9 +253,9 @@ Two Mantle-specific notes on them:
 - The management operations carry no request body, so the gateway can't read a
   model from the request. They work on apps whose
   [policy chain](./policy-chains.mdx) includes a
-  [Model Filtering](../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-  policy with an allow list (the gateway routes them with the first listed
-  model); without one they fail with a `400` error.
+  [Model Filtering](../policies/ai-gateway-model-filtering-inbound.mdx) policy
+  with an allow list (the gateway routes them with the first listed model);
+  without one they fail with a `400` error.
 - Whether `DELETE` succeeds is a permission of your Bedrock API key (the
   `bedrock-mantle:DeleteInference` action in AWS IAM—see
   [AWS's Bedrock Mantle documentation](https://docs.aws.amazon.com/bedrock/latest/userguide/bedrock-mantle.html)).
@@ -343,5 +343,5 @@ Use another provider for embeddings.
   region, and understand when changes deploy.
 - [AI Gateway Apps](./apps.mdx)—create the apps that call your Mantle-backed
   models.
-- [Model Filtering policy](../policies/ai-gateway-model-filtering-v2-inbound.mdx)—control
+- [Model Filtering policy](../policies/ai-gateway-model-filtering-inbound.mdx)—control
   which models each app can call.

package/docs/ai-gateway/bedrock-runtime.mdx

@@ -254,14 +254,14 @@ gateway parses, so a policy that reads the body applies its `onUnknownShape`
 setting instead. Each policy's default follows from its job: a guardrail fails
 closed, while an observer or an optimization fails open.
 
-| Policy                                                                                                                        | On Bedrock Runtime routes                                                                                                                              |
-| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [Authentication](../policies/ai-gateway-auth-v2-inbound.mdx)                                                                  | Works. Reads the app key from `Authorization: Bearer`                                                                                                  |
-| [Model Filtering](../policies/ai-gateway-model-filtering-v2-inbound.mdx)                                                      | Works. Refuses a model outside the allow list before any AWS call                                                                                      |
-| [Metering and budgets](../policies/ai-gateway-metering-v2-inbound.mdx)                                                        | Works. Meters tokens and cost on all four operations, streamed or not                                                                                  |
-| [DLP](../policies/ai-gateway-dlp-inbound.mdx) and content guardrails                                                          | **Blocks by default.** The gateway can't read these bodies, so the policy denies the request. Set `onUnknownShape` to `skip` to forward it uninspected |
-| [Galileo](../policies/galileo-tracing-v2-inbound.mdx) and [Comet Opik](../policies/comet-opik-tracing-v2-inbound.mdx) tracing | **Skipped by default.** The request goes through untraced. Set `onUnknownShape` to `deny` to make a trace a hard requirement                           |
-| Semantic Cache                                                                                                                | Skipped                                                                                                                                                |
+| Policy                                                                                                                                  | On Bedrock Runtime routes                                                                                                                              |
+| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [Authentication](../policies/ai-gateway-auth-inbound.mdx)                                                                               | Works. Reads the app key from `Authorization: Bearer`                                                                                                  |
+| [Model Filtering](../policies/ai-gateway-model-filtering-inbound.mdx)                                                                   | Works. Refuses a model outside the allow list before any AWS call                                                                                      |
+| [Metering and budgets](../policies/ai-gateway-metering-inbound.mdx)                                                                     | Works. Meters tokens and cost on all four operations, streamed or not                                                                                  |
+| [DLP](../policies/ai-gateway-dlp-inbound.mdx) and content guardrails                                                                    | **Blocks by default.** The gateway can't read these bodies, so the policy denies the request. Set `onUnknownShape` to `skip` to forward it uninspected |
+| [Galileo](../policies/ai-gateway-galileo-tracing-inbound.mdx) and [Comet Opik](../policies/ai-gateway-opik-tracing-inbound.mdx) tracing | **Skipped by default.** The request goes through untraced. Set `onUnknownShape` to `deny` to make a trace a hard requirement                           |
+| Semantic Cache                                                                                                                          | Skipped                                                                                                                                                |
 
 The table lists every policy the gateway supports on these routes. It audits the
 chain and refuses any other policy, such as a custom policy, Smart Router, or
@@ -325,5 +325,5 @@ native paths.
 - [Managing Providers](./managing-providers.mdx)—edit models, keys, and the
   region, and understand when changes deploy.
 - [AI Gateway Apps](./apps.mdx)—create the apps that call your models.
-- [Model Filtering policy](../policies/ai-gateway-model-filtering-v2-inbound.mdx)—control
+- [Model Filtering policy](../policies/ai-gateway-model-filtering-inbound.mdx)—control
   which models each app can call.

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

@@ -45,8 +45,8 @@ Models are referenced as `providerName/model`, where `providerName` is the
 provider name configured in your gateway. By default an app can reach any model
 offered by the providers configured for the Zuplo project. To limit it to a
 curated set, add the
-[Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy to the app—it applies separate rules to completions (`generateText`,
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+to the app—it applies separate rules to completions (`generateText`,
 `streamText`) and embeddings (`embed`), and rejects a capability it doesn't
 configure.
 

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

@@ -59,7 +59,7 @@ project. Add the block for your approach, then restart Claude Code.
   [`modelOverrides`](https://code.claude.com/docs/en/model-config#override-model-ids-per-version)
   maps exact IDs; the `/model` picker can select either.
 - The app's
-  [Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
+  [Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx)
   policy controls which models the app can use.
 
 ## Use a provider key
@@ -133,8 +133,8 @@ In the **JSON** editor:
 
 - The provider still needs an API key to save. Passthrough requests never use
   it. Apps without passthrough and every
-  [Fallback Model](../../policies/ai-gateway-fallback-model-v2-inbound.mdx)
-  target do. If nothing uses it, a placeholder value works.
+  [Fallback Model](../../policies/ai-gateway-fallback-model-inbound.mdx) target
+  do. If nothing uses it, a placeholder value works.
 - The Portal playground sends the app key as `Authorization: Bearer`, so it
   can't call a passthrough app. Test from Claude Code.
 - Do not set `ANTHROPIC_AUTH_TOKEN` or `ANTHROPIC_API_KEY`, in the settings file

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

@@ -93,8 +93,8 @@ 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 can use.
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+controls which models the app can use.
 
 ## Verify
 

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

@@ -108,8 +108,8 @@ On the team's [policy template](../policy-templates.mdx), or on the app's
 `401 Invalid Authorization Scheme`.
 
 The provider still needs an API key saved. Passthrough requests never use it;
-[Fallback Model](../../policies/ai-gateway-fallback-model-v2-inbound.mdx)
-targets do. A placeholder value works if nothing else uses it.
+[Fallback Model](../../policies/ai-gateway-fallback-model-inbound.mdx) targets
+do. A placeholder value works if nothing else uses it.
 
 ### Rules
 
@@ -138,8 +138,8 @@ 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 can use.
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+controls which models the app can use.
 
 ## Verify
 

package/docs/ai-gateway/integrations/github-copilot.mdx

@@ -132,8 +132,8 @@ Three lines carry the integration:
   key, use **Chat: Manage Language Models**.
 - **`requestHeaders`** sends the key as `Authorization: Bearer <key>`, the
   header the gateway's
-  [Authentication policy](../../policies/ai-gateway-auth-v2-inbound.mdx) reads.
-  VS Code's default header depends on the API type, so set it on every model.
+  [Authentication policy](../../policies/ai-gateway-auth-inbound.mdx) reads. VS
+  Code's default header depends on the API type, so set it on every model.
 - **`apiType`** and the `url` path select the API the model speaks: `responses`
   for OpenAI's reasoning models such as GPT-5.x, `messages` for Claude through
   the gateway's native Messages passthrough, and `chat-completions` with a
@@ -146,8 +146,8 @@ Save the file and pick a model from the chat model picker.
 
 Chat and agent requests, on both surfaces. Copilot's inline code completions
 stay on GitHub's infrastructure. The app's
-[Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy decides which models Copilot may use.
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+decides which models Copilot may use.
 
 ## Troubleshooting
 

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

@@ -66,9 +66,9 @@ configuration approaches depending on which version you choose.
 :::note
 
 The app's
-[Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy controls which models the app may use, so the model you enter here must
-be one that policy allows.
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+controls which models the app may use, so the model you enter here must be one
+that policy allows.
 
 :::
 

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

@@ -77,6 +77,6 @@ Always name the model as `providerName/model`, where `providerName` is the
 provider name configured in your gateway. The gateway needs the prefix to know
 which provider to route to, and a request with no model, or a model without that
 prefix, gets a `400`. Adding the
-[Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy restricts an app to certain models, and an allow list also supplies a
-default so requests may omit the model.
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+restricts an app to certain models, and an allow list also supplies a default so
+requests may omit the model.

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

@@ -45,9 +45,9 @@ Always name the model as `providerName/model`, where `providerName` is the
 provider name configured in your gateway. The gateway needs the prefix to know
 which provider to route to, and a request with no model, or a model without that
 prefix, gets a `400`. Adding the
-[Model Filtering](../../policies/ai-gateway-model-filtering-v2-inbound.mdx)
-policy restricts an app to certain models, and an allow list also supplies a
-default so requests may omit the model.
+[Model Filtering](../../policies/ai-gateway-model-filtering-inbound.mdx) policy
+restricts an app to certain models, and an allow list also supplies a default so
+requests may omit the model.
 
 ```typescript
 import OpenAI from "openai";

package/docs/ai-gateway/universal-api.mdx

@@ -55,9 +55,9 @@ console.log(response.choices[0].message.content);
 :::tip
 
 If the app's
-[Model Filtering](../policies/ai-gateway-model-filtering-v2-inbound.mdx) policy
-has an allow list, a request that omits `model` uses the first model in the
-list—so clients that can't set a model still work.
+[Model Filtering](../policies/ai-gateway-model-filtering-inbound.mdx) policy has
+an allow list, a request that omits `model` uses the first model in the list—so
+clients that can't set a model still work.
 
 :::
 

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

@@ -185,7 +185,7 @@ it during that period still counts. Expressions are also case-sensitive:
 
 To configure budgets in JSON, use the `budgetRules` option in **Budgets and
 Costs**. For the available options, see the
-[Budgets and Costs policy reference](../policies/ai-gateway-metering-v2-inbound.mdx).
+[Budgets and Costs policy reference](../policies/ai-gateway-metering-inbound.mdx).
 
 This rule set budgets each user, each organization, and the app as a whole:
 

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

@@ -516,5 +516,5 @@ on `/v1/chat/completions`—see [Call the models](#call-the-models).
   location, and the project, and understand when changes deploy.
 - [AI Gateway Apps](./apps.mdx)—create the apps that call your Vertex-backed
   models.
-- [Model Filtering policy](../policies/ai-gateway-model-filtering-v2-inbound.mdx)—control
+- [Model Filtering policy](../policies/ai-gateway-model-filtering-inbound.mdx)—control
   which models each app can call.

package/docs/dedicated/akamai/ai-powered-applications.mdx

@@ -146,7 +146,7 @@ For more information, see the
 
 ## AI Firewall Protection
 
-The [Akamai AI Firewall](../../policies/akamai-ai-firewall-v2-inbound.mdx)
+The [Akamai AI Firewall](../../policies/ai-gateway-akamai-firewall-inbound.mdx)
 provides enterprise-grade security for AI interactions:
 
 - **Prompt injection defense** - Detects and blocks attempts to manipulate the
@@ -220,7 +220,7 @@ Deployment options include:
   Akamai Connected Cloud
 - [MCP Server Handler](../../handlers/mcp-server.mdx) - Technical documentation
   for MCP server configuration
-- [Akamai AI Firewall](../../policies/akamai-ai-firewall-v2-inbound.mdx) - AI
-  security policy configuration
+- [Akamai AI Firewall](../../policies/ai-gateway-akamai-firewall-inbound.mdx) -
+  AI security policy configuration
 - [Zuplo AI Gateway](../../ai-gateway/overview.mdx) - Overview of AI Gateway
   capabilities

package/docs/policies/_index.md

@@ -4,14 +4,15 @@
 | --- | --- | --- | --- |
 | set-query-params-inbound | Add or Set Query Parameters | Adds or sets query parameters on the incoming request. | api-gateway |
 | set-headers-inbound | Add or Set Request Headers | Adds or sets headers on the incoming request. | api-gateway |
-| ai-gateway-auth-v2-inbound | AI Gateway Authentication | Authenticates requests to an AI Gateway endpoint with application API keys.  Add this policy to an application's `inboundPolicyChain` to require a key for that app only, or place it on the route before the configuration executor to require a key for every application on the route. The policies that follow can read the authenticated application from `request.user` (`sub` is the application name, `data` its metadata), and the application's AI Gateway configuration takes effect for the request. Use `authHeader` and `authScheme` when clients send their app key somewhere other than the default `Authorization: Bearer` header. Enable `credentialPassthrough`, with the application key in a separate header, to forward the caller's `Authorization` header to the primary provider as its credential.  When the matched route captures an `app_id` path parameter (platform catch-all `/:app_id/(.*)`), this policy also requires the stored configuration ID to match the URL (adding `config_` for `/a`). It returns 403 on mismatch.  On a User App route (`/u/{app_id}`), only a personal API key issued for that User App authenticates. `request.user.sub` is then the key owner's user ID. An application API key on a User App route, or a personal API key on any other route, returns 403. Validation results are cached for `cacheTtlSeconds`, so a revoked key stops working within that window. | ai-gateway |
-| ai-gateway-configuration-executor-v2-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-v2-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-v2-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-v2-inbound` when you want configuration loading separated from chain execution. When `ai-gateway-auth-v2-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-v2-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-v2-inbound | AI Gateway Metering | Meters AI Gateway usage and enforces limits configured by the application.  The authentication policy must run before this policy so the app configuration id is available for meter storage and analytics. | ai-gateway |
-| ai-gateway-model-filtering-v2-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-semantic-cache-v2-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 |
-| akamai-ai-firewall-v2-inbound | Akamai AI Firewall | Akamai AI Firewall Inbound Policy | ai-gateway |
+| ai-gateway-auth-inbound | AI Gateway Authentication | Authenticates requests to an AI Gateway endpoint with application API keys.  Add this policy to an application's `inboundPolicyChain` to require a key for that app only, or place it on the route before the configuration executor to require a key for every application on the route. The policies that follow can read the authenticated application from `request.user` (`sub` is the application name, `data` its metadata), and the application's AI Gateway configuration takes effect for the request. Use `authHeader` and `authScheme` when clients send their app key somewhere other than the default `Authorization: Bearer` header. Enable `credentialPassthrough`, with the application key in a separate header, to forward the caller's `Authorization` header to the primary provider as its credential.  When the matched route captures an `app_id` path parameter (platform catch-all `/:app_id/(.*)`), this policy also requires the stored configuration ID to match the URL (adding `config_` for `/a`). It returns 403 on mismatch.  On a User App route (`/u/{app_id}`), only a personal API key issued for that User App authenticates. `request.user.sub` is then the key owner's user ID. An application API key on a User App route, or a personal API key on any other route, returns 403. Validation results are cached for `cacheTtlSeconds`, so a revoked key stops working within that window. | ai-gateway |
+| 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-v2-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-v2-inbound` when you want configuration loading separated from chain execution. When `ai-gateway-auth-v2-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 and enforces limits configured by the application.  The authentication policy must run before this policy so the app configuration id is available for meter storage and analytics. | 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 |
+| ai-gateway-akamai-firewall-inbound | Akamai AI Firewall | Akamai AI Firewall Inbound Policy | ai-gateway |
 | akamai-firewall-for-ai-outbound | Akamai Firewall for AI | Inspects each upstream response with Akamai's Firewall for AI detect API and replaces the response with a `403 Forbidden` if Akamai returns a `deny` rule. Useful behind AI-powered APIs to filter unsafe completions, sensitive data exposure, and toxic content before they reach the client.  The body, headers, URL, and query string sent to Akamai are configurable; by default only the response body is captured. Bodies are read from a clone so the client still receives the original. | api-gateway |
 | akamai-firewall-for-ai-inbound | Akamai Firewall for AI | Inspects each incoming request with Akamai's Firewall for AI detect API and blocks the request if Akamai returns a `deny` rule. Useful in front of AI-powered APIs to filter prompt injection, jailbreaks, and other unsafe inputs before they reach the model.  The body, headers, URL, and query string sent to Akamai are configurable; by default only the request body is captured. Bodies are read from a clone so the upstream handler still sees the original. | api-gateway |
 | amberflo-metering-inbound | Amberflo Metering / Billing | Amberflo is a usage metering and billing service. This policy allows you to send metering calls for each API to their meter ingest endpoint. | api-gateway |
@@ -30,7 +31,7 @@
 | clear-headers-inbound | Clear Request Headers | Removes all headers from the incoming request except for those in the exclude list. | api-gateway |
 | clear-headers-outbound | Clear Response Headers | Removes all headers from the response except for those in the exclude list. | api-gateway |
 | clerk-jwt-auth-inbound | Clerk JWT Auth | Authenticate users using Clerk issued JWT tokens. | api-gateway |
-| comet-opik-tracing-v2-inbound | Comet Opik Tracing | Comet Opik Tracing Inbound Policy | ai-gateway |
+| ai-gateway-opik-tracing-inbound | Comet Opik Tracing | Comet Opik Tracing Inbound Policy | ai-gateway |
 | complex-rate-limit-inbound | Complex Rate Limiting | The Complex Rate Limiting policy is an advanced rate limiting policy that let's you set rate limits based on custom counters (not just requests) | api-gateway |
 | composite-inbound | Composite Inbound (Group Policies) | Creates a composite, or group policy - composed of other inbound policies. For reuse across routes. | api-gateway |
 | composite-outbound | Composite Outbound (Group Policies) | Creates a composite, or group policy - composed of other outbound policies. For reuse across routes. | api-gateway |
@@ -43,7 +44,7 @@
 | ai-gateway-internal-only-inbound | Ensure Gateway Internal Invocation Only | Accepts only requests that this gateway made itself with `context.invokeRoute`, and rejects every request that arrived over the network with `403 Forbidden`.  Use it in place of AI Gateway Authentication on an application that is only ever called by other routes and policies on the same gateway, such as the classifier application behind the Smart Router or Prompt Injection Protection policies. Those calls never leave the gateway, so an API key on them protects nothing. This policy asserts the one thing that matters: the request originated inside the deployment.  The check reads `context.parentContext`, which the runtime sets only on the child context that `context.invokeRoute` creates. A client cannot supply it through a header, the URL, or the body. The policy has no options, makes no network calls, reads no body, and leaves `request.user` unset. | ai-gateway |
 | firebase-jwt-inbound | Firebase JWT Auth | Authenticate users using Firebase issued JWT tokens. | api-gateway |
 | formdata-to-json-inbound | Form Data to JSON | Converts form data in the incoming request to JSON. | api-gateway |
-| galileo-tracing-v2-inbound | Galileo Tracing | Galileo Tracing Inbound Policy | ai-gateway |
+| ai-gateway-galileo-tracing-inbound | Galileo Tracing | Galileo Tracing Inbound Policy | ai-gateway |
 | geo-filter-inbound | Geo-location filtering | Block requests based on geo-location parameters: country, region code, and ASN | api-gateway |
 | graphql-analytics-outbound | GraphQL Analytics | Reports GraphQL errors returned in response bodies to Zuplo's GraphQL analytics. GraphQL servers following the standard Apollo / graphql-yoga pattern return `200 OK` with an `errors[]` array in the body when an operation fails, which HTTP-level analytics alone report as a success — add this policy to a GraphQL route and failed operations show up as failures on the GraphQL dashboard, classified by error type.  Each error in `errors[]` is classified from its `extensions.code` following the Apollo Server conventions (`GRAPHQL_PARSE_FAILED` → `syntax`, `GRAPHQL_VALIDATION_FAILED` → `validation`, `UNAUTHENTICATED` / `FORBIDDEN` → `auth`, timeout codes → `timeout`); custom codes can be mapped with `errorCodeClassification`, and anything unrecognized falls back to `defaultErrorClass` (`resolver`). Optionally set `logErrors` to also write a structured warning per errored response. The policy reads up to `maxScanBytes` of the body (128 KiB by default, 5 MiB maximum), scanning it for the `errors` token; a response larger than that is treated as error-free. When the token is found and the body fits, it is parsed and its errors reported.  The response always passes through unchanged — the body is read from a clone, and any internal failure is swallowed so reporting can never break the request. The route must be marked `x-graphql: true` in `routes.oas.json` (which enables GraphQL analytics for the route); without the marker the policy logs a warning and does nothing. | api-gateway |
 | graphql-cache-inbound | GraphQL Cache | Caches GraphQL query responses at the edge so identical queries are served without a round-trip to the origin.  Unlike CDN caching that keys on the raw request body, this policy parses the GraphQL document and normalizes it before hashing: insignificant whitespace, field formatting, and fragment layout are collapsed, and variable object keys are sorted. Two requests that are semantically identical therefore share a cache entry even when their bodies differ byte-for-byte. There is no query size or nesting-depth limit.  Only `query` operations are cached. Mutations, subscriptions, malformed documents, and non-JSON bodies are forwarded to the origin untouched. Cache hits and misses are reported on the `x-cache` response header, with a short key fingerprint on `x-cache-key`.  To avoid serving one user's data to another, requests carrying an `authorization` or `cookie` header are not cached by default. Use `cacheKeyHeaders` to opt into caching them: each listed header's value is included in the cache key, so distinct credentials get distinct cache entries. | api-gateway |

package/docs/policies/{akamai-ai-firewall-v2-inbound → ai-gateway-akamai-firewall-inbound}/doc.md

@@ -18,9 +18,9 @@ by default, include it in the team's policy template.
 ```json
 {
   "name": "akamai-ai-firewall-v2-inbound",
-  "policyType": "akamai-ai-firewall-v2",
+  "policyType": "ai-gateway-akamai-firewall",
   "handler": {
-    "export": "AkamaiAIFirewallV2InboundPolicy",
+    "export": "AIGatewayAkamaiFirewallInboundPolicy",
     "module": "$import(@zuplo/runtime)",
     "options": {
       "configurationId": "your-configuration-id",

package/docs/policies/{akamai-ai-firewall-v2-inbound → ai-gateway-akamai-firewall-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/akamai-ai-firewall-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-akamai-firewall-inbound.json",
   "type": "object",
   "title": "Akamai AI Firewall",
   "isDeprecated": false,
@@ -10,7 +10,7 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "akamai-ai-firewall-v2",
+  "policyType": "ai-gateway-akamai-firewall",
   "products": ["ai-gateway"],
   "description": "Akamai AI Firewall Inbound Policy",
   "deprecatedMessage": "",
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AkamaiAIFirewallV2InboundPolicy",
+          "const": "AIGatewayAkamaiFirewallInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "akamai-ai-firewall-v2",
-          "title": "AkamaiAIFirewallPolicyOptions",
+          "title": "AIGatewayAkamaiFirewallInboundPolicyOptions",
           "type": "object",
           "description": "The options for the Akamai AI Firewall policy.",
           "examples": [
@@ -123,7 +122,7 @@
       },
       "examples": [
         {
-          "export": "AkamaiAIFirewallV2InboundPolicy",
+          "export": "AIGatewayAkamaiFirewallInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "configurationId": "$env(AKAMAI_AI_FIREWALL_CONFIGURATION_ID)",

package/docs/policies/{ai-gateway-auth-v2-inbound → ai-gateway-auth-inbound}/doc.md

@@ -25,9 +25,9 @@ Declare the policy in `config/policies.json`:
   "policies": [
     {
       "name": "ai-gateway-auth-v2-inbound",
-      "policyType": "ai-gateway-auth-v2",
+      "policyType": "ai-gateway-auth",
       "handler": {
-        "export": "AIGatewayAuthV2InboundPolicy",
+        "export": "AIGatewayAuthInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -128,9 +128,9 @@ empty string when the header contains only the key:
 ```json
 {
   "name": "ai-gateway-auth-v2-inbound",
-  "policyType": "ai-gateway-auth-v2",
+  "policyType": "ai-gateway-auth",
   "handler": {
-    "export": "AIGatewayAuthV2InboundPolicy",
+    "export": "AIGatewayAuthInboundPolicy",
     "module": "$import(@zuplo/runtime)",
     "options": {
       "authHeader": "x-api-key",

package/docs/policies/{ai-gateway-auth-v2-inbound → ai-gateway-auth-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-auth-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-auth-inbound.json",
   "type": "object",
   "title": "AI Gateway Authentication",
   "isDeprecated": false,
@@ -10,7 +10,7 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "ai-gateway-auth-v2",
+  "policyType": "ai-gateway-auth",
   "products": ["ai-gateway"],
   "description": "Authenticates requests to an AI Gateway endpoint with application API keys.\n\nAdd this policy to an application's `inboundPolicyChain` to require a key for that app only, or place it on the route before the configuration executor to require a key for every application on the route. The policies that follow can read the authenticated application from `request.user` (`sub` is the application name, `data` its metadata), and the application's AI Gateway configuration takes effect for the request. Use `authHeader` and `authScheme` when clients send their app key somewhere other than the default `Authorization: Bearer` header. Enable `credentialPassthrough`, with the application key in a separate header, to forward the caller's `Authorization` header to the primary provider as its credential.\n\nWhen the matched route captures an `app_id` path parameter (platform catch-all `/:app_id/(.*)`), this policy also requires the stored configuration ID to match the URL (adding `config_` for `/a`). It returns 403 on mismatch.\n\nOn a User App route (`/u/{app_id}`), only a personal API key issued for that User App authenticates. `request.user.sub` is then the key owner's user ID. An application API key on a User App route, or a personal API key on any other route, returns 403. Validation results are cached for `cacheTtlSeconds`, so a revoked key stops working within that window.",
   "deprecatedMessage": "",
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AIGatewayAuthV2InboundPolicy",
+          "const": "AIGatewayAuthInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-auth-v2",
-          "title": "AIGatewayAuthV2InboundPolicyOptions",
+          "title": "AIGatewayAuthInboundPolicyOptions",
           "type": "object",
           "description": "The options for this policy.",
           "additionalProperties": false,
@@ -86,7 +85,7 @@
       },
       "examples": [
         {
-          "export": "AIGatewayAuthV2InboundPolicy",
+          "export": "AIGatewayAuthInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "cacheTtlSeconds": 10,

package/docs/policies/{ai-gateway-configuration-executor-v2-inbound → ai-gateway-configuration-executor-inbound}/doc.md

@@ -75,9 +75,9 @@ chooses the policies it needs in its `inboundPolicyChain`:
   "policies": [
     {
       "name": "ai-gateway-auth-v2-inbound",
-      "policyType": "ai-gateway-auth-v2",
+      "policyType": "ai-gateway-auth",
       "handler": {
-        "export": "AIGatewayAuthV2InboundPolicy",
+        "export": "AIGatewayAuthInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -86,9 +86,9 @@ chooses the policies it needs in its `inboundPolicyChain`:
     },
     {
       "name": "ai-gateway-configuration-loader-v2-inbound",
-      "policyType": "ai-gateway-configuration-loader-v2",
+      "policyType": "ai-gateway-configuration-loader",
       "handler": {
-        "export": "AIGatewayConfigurationLoaderV2InboundPolicy",
+        "export": "AIGatewayConfigurationLoaderInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -97,9 +97,9 @@ chooses the policies it needs in its `inboundPolicyChain`:
     },
     {
       "name": "ai-gateway-configuration-executor-v2-inbound",
-      "policyType": "ai-gateway-configuration-executor-v2",
+      "policyType": "ai-gateway-configuration-executor",
       "handler": {
-        "export": "AIGatewayConfigurationExecutorV2InboundPolicy",
+        "export": "AIGatewayConfigurationExecutorInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "cacheTtlSeconds": 60
@@ -108,18 +108,18 @@ chooses the policies it needs in its `inboundPolicyChain`:
     },
     {
       "name": "ai-gateway-metering-v2-inbound",
-      "policyType": "ai-gateway-metering-v2",
+      "policyType": "ai-gateway-metering",
       "handler": {
-        "export": "AIGatewayMeteringV2InboundPolicy",
+        "export": "AIGatewayMeteringInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {}
       }
     },
     {
       "name": "ai-gateway-model-filtering-v2-inbound",
-      "policyType": "ai-gateway-model-filtering-v2",
+      "policyType": "ai-gateway-model-filtering",
       "handler": {
-        "export": "AIGatewayModelFilteringV2InboundPolicy",
+        "export": "AIGatewayModelFilteringInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "models": {
@@ -132,9 +132,9 @@ chooses the policies it needs in its `inboundPolicyChain`:
     },
     {
       "name": "ai-gateway-fallback-model-v2-inbound",
-      "policyType": "ai-gateway-fallback-model-v2",
+      "policyType": "ai-gateway-fallback-model",
       "handler": {
-        "export": "AIGatewayFallbackModelV2InboundPolicy",
+        "export": "AIGatewayFallbackModelInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "models": {
@@ -148,9 +148,9 @@ chooses the policies it needs in its `inboundPolicyChain`:
     },
     {
       "name": "ai-gateway-semantic-cache-v2-inbound",
-      "policyType": "ai-gateway-semantic-cache-v2",
+      "policyType": "ai-gateway-semantic-cache",
       "handler": {
-        "export": "AIGatewaySemanticCacheV2InboundPolicy",
+        "export": "AIGatewaySemanticCacheInboundPolicy",
         "module": "$import(@zuplo/runtime)",
         "options": {
           "semanticTolerance": 0.4,
@@ -366,8 +366,8 @@ distinct value gets its own budget.
 
 The expression grammar, the selectable properties, what a value must be, and
 what happens when an expression does not resolve are documented once, on the
-[AI Gateway Metering](/docs/policies/ai-gateway-metering-v2-inbound) policy
-page. The same grammar applies here.
+[AI Gateway Metering](/docs/policies/ai-gateway-metering-inbound) policy page.
+The same grammar applies here.
 
 Two things are specific to application configuration. A policy that sets a value
 an expression reads must run before Semantic Cache, which can answer without

package/docs/policies/{ai-gateway-configuration-executor-v2-inbound → ai-gateway-configuration-executor-inbound}/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-configuration-executor-v2-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/ai-gateway-configuration-executor-inbound.json",
   "type": "object",
   "title": "AI Gateway Configuration Executor",
   "isDeprecated": false,
@@ -10,7 +10,7 @@
   "isBeta": false,
   "isHidden": false,
   "requiresAI": true,
-  "policyType": "ai-gateway-configuration-executor-v2",
+  "policyType": "ai-gateway-configuration-executor",
   "products": ["ai-gateway"],
   "description": "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.\n\nPlace this policy on AI Gateway routes after optional authentication and optional `ai-gateway-configuration-loader-v2-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.",
   "deprecatedMessage": "",
@@ -22,7 +22,7 @@
       "required": ["export", "module", "options"],
       "properties": {
         "export": {
-          "const": "AIGatewayConfigurationExecutorV2InboundPolicy",
+          "const": "AIGatewayConfigurationExecutorInboundPolicy",
           "description": "The name of the exported type"
         },
         "module": {
@@ -30,8 +30,7 @@
           "description": "The module containing the policy"
         },
         "options": {
-          "x-zuplo-policy-type": "ai-gateway-configuration-executor-v2",
-          "title": "AIGatewayConfigurationExecutorV2InboundPolicyOptions",
+          "title": "AIGatewayConfigurationExecutorInboundPolicyOptions",
           "type": "object",
           "description": "Options for loading each application's AI Gateway configuration and running its inbound policy chain.",
           "additionalProperties": false,
@@ -48,7 +47,7 @@
       },
       "examples": [
         {
-          "export": "AIGatewayConfigurationExecutorV2InboundPolicy",
+          "export": "AIGatewayConfigurationExecutorInboundPolicy",
           "module": "$import(@zuplo/runtime)",
           "options": {
             "cacheTtlSeconds": 10