zuplo 6.70.63 → 6.70.67

package/docs/ai-gateway/fallback.mdx

@@ -0,0 +1,132 @@
+---
+title: Fallback Models
+sidebar_label: Fallbacks
+description:
+  Configure error, timeout, and quota fallback models for an AI Gateway app in
+  the Zuplo Portal so it keeps serving requests when the primary model fails or
+  goes over quota.
+---
+
+Each AI Gateway app calls a primary model: the provider, completions model, and
+optional embeddings model you select under **AI Models** on the app's
+**Settings** tab. Fallbacks let an app keep serving requests when that primary
+model fails, times out, or runs over its usage limits, instead of returning an
+error to the caller.
+
+The AI Gateway offers two independent fallback mechanisms, each triggered by a
+different condition:
+
+| Mechanism              | Triggers when…                                           | Without a fallback set…             |
+| ---------------------- | -------------------------------------------------------- | ----------------------------------- |
+| **Fallback & Timeout** | The primary returns a `4xx`/`5xx` or exceeds the timeout | The error is returned to the caller |
+| **Quota Fallback**     | One of the app's usage limits is exceeded                | The request is blocked with a `429` |
+
+Both are configured entirely in the Zuplo Portal, and either can route to _any_
+provider. The fallback doesn't have to share the primary's provider.
+
+## Error and timeout fallback
+
+The **Fallback & Timeout** section fails an app over to a second model when the
+primary model returns a `4xx` or `5xx` response, or when the request takes
+longer than the configured timeout. This protects against provider outages, rate
+limiting on the primary provider, and slow responses.
+
+### Configure an error and timeout fallback
+
+<Stepper>
+
+1. Open the [Apps](https://portal.zuplo.com/+/account/project/ai/apps) tab of
+   your AI Gateway project and select the app to edit.
+
+1. Select the **Settings** tab and find the **Fallback & Timeout** section.
+
+1. Choose a **Fallback Provider**. This can be the same provider as the primary
+   or a different one, including a [custom provider](./custom-providers.mdx).
+
+1. Select the **Fallback Completions** model. If the app uses embeddings, also
+   select a **Fallback Embeddings** model.
+
+1. Set the **Request timeout (seconds)** value to bound how long the primary
+   model call can run before the gateway fails over. The default is `60`, but
+   you can set any value that suits your app.
+
+1. Click **Save Changes**.
+
+</Stepper>
+
+<Framed>
+
+![The Fallback & Timeout section of the app Settings tab, showing the Fallback Provider, Fallback Completions, Fallback Embeddings, and Request timeout fields](./fallback-and-timeout.png)
+
+</Framed>
+
+:::note
+
+The request timeout applies _only_ when a fallback model is set. If no fallback
+is configured, the primary model call runs unbounded.
+
+:::
+
+## Quota fallback
+
+The **Quota Fallback** section routes requests to an alternate, usually cheaper,
+model when one of the app's [usage limits](./usage-limits.mdx) is exceeded,
+rather than blocking the request with a `429`. This keeps an app available after
+it crosses a budget, token, or request threshold, while shifting the overflow
+traffic to a lower-cost model.
+
+If you leave the quota fallback empty, the app blocks requests with a `429` once
+it goes over quota.
+
+### Configure a quota fallback
+
+<Stepper>
+
+1. Open the [Apps](https://portal.zuplo.com/+/account/project/ai/apps) tab and
+   select the app to edit.
+
+1. Select the **Settings** tab. Set the limits you want to enforce under **Usage
+   Limits & Thresholds**, then find the **Quota Fallback** section below them.
+
+1. Choose a **Quota Fallback Provider**, then select the **Quota Fallback
+   Completions** model. If the app uses embeddings, also select a **Quota
+   Fallback Embeddings** model.
+
+1. Click **Save Changes**.
+
+</Stepper>
+
+<Framed>
+
+![The Quota Fallback section of the app Settings tab, below Usage Limits & Thresholds, showing the Quota Fallback Provider, Quota Fallback Completions, and Quota Fallback Embeddings fields](./quota-fallback.png)
+
+</Framed>
+
+:::tip
+
+Point the quota fallback at a smaller, cheaper model so overflow traffic stays
+inexpensive while remaining available. The fallback's own usage still counts
+toward the app's limits.
+
+:::
+
+## How the two fallbacks combine
+
+The mechanisms are evaluated independently and can both be active on the same
+app:
+
+- A request that is **over quota** routes to the quota fallback model.
+- A request that is **within quota** but hits an **error or timeout** on the
+  primary routes to the error and timeout fallback model.
+
+Set whichever fallbacks match the failure modes you want to protect against.
+Neither is required.
+
+## Related resources
+
+- [Managing Apps](./managing-apps.mdx) - Create, edit, and delete AI Gateway
+  apps.
+- [Usage Limits & Thresholds](./usage-limits.mdx) - Configure the budget, token,
+  and request limits that trigger a quota fallback.
+- [Custom Providers](./custom-providers.mdx) - Add your own provider to use as a
+  primary or fallback model.

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

@@ -87,7 +87,7 @@ export ACCOUNT_NAME=my-account
 # Your bucket API URL (Found in Settings > General)
 export BUCKET_NAME=my-bucket
 # Your Zuplo API Key (Found in Settings > Zuplo API Keys)
-export ZAPI_KEY=zpka_YOUR_API_KEY
+export API_KEY=zpka_YOUR_API_KEY
 ```
 
 ### Creating a Consumer with a Key

package/docs/articles/api-key-best-practices.mdx

@@ -49,8 +49,8 @@ microseconds.
 
 Zuplo keys include a checksum signature that can be verified mathematically at
 the edge. This happens as part of the
-[validation flow](./api-key-management.mdx#how-authentication-works): the format
-and checksum are checked before any network call, rejecting invalid keys with
+[validation flow](../concepts/api-keys.md#how-validation-works): the format and
+checksum are checked before any network call, rejecting invalid keys with
 near-zero cost.
 
 ## 3. Support secret scanning and leak detection

package/docs/articles/api-key-react-component.mdx

@@ -77,7 +77,7 @@ const MyComponent = () => {
     "<ACCESS_TOKEN>"
   );
 
-  return <ApiKeyManager provider={provider} />;
+  return <ApiKeyManager provider={defaultProvider} />;
 };
 ```
 

package/docs/articles/bypass-policy-for-testing.mdx

@@ -37,7 +37,7 @@ Create the custom policy configuration in the `policies.json` file.
 
 ```json title="config/policies.json"
 {
-    "policies": [{
+  "policies": [
     {
       "name": "monetization-with-bypass-inbound",
       "policyType": "custom-code-inbound",
@@ -48,9 +48,9 @@ Create the custom policy configuration in the `policies.json` file.
           "config1": "YOUR_VALUE",
           "config2": true
         }
-      },
+      }
     }
-  }]
+  ]
 }
 ```
 

package/docs/articles/configuring-auth0-for-mcp-auth.mdx

@@ -127,7 +127,7 @@ will need to do the following:
    ```json
    {
      "name": "mcp-oauth-inbound",
-     "policyType": "oauth-inbound",
+     "policyType": "auth0-jwt-auth-inbound",
      "handler": {
        "export": "Auth0JwtInboundPolicy",
        "module": "$import(@zuplo/runtime)",

package/docs/articles/configuring-okta-for-mcp-auth.mdx

@@ -154,7 +154,7 @@ will need to do the following:
 
            "policies": {
              "inbound": [
-               "mcp-oauth-inbound"
+               "mcp-okta-oauth-inbound"
              ]
            }
          }

package/docs/articles/health-checks.mdx

@@ -63,12 +63,12 @@ ensure that it's reachable and functioning. If you have multiple backend
 services you can check each of them.
 
 ```ts title="modules/health.ts"
-import { ZuploContext, ZuploRequest, ZuploResponse } from "@zuplo/runtime";
+import { ZuploContext, ZuploRequest } from "@zuplo/runtime";
 
 export default async function handler(
   request: ZuploRequest,
   context: ZuploContext,
-): Promise<ZuploResponse> {
+): Promise<Response> {
   try {
     // Make a simple request to the backend to check its health
     const responses = await Promise.allSettled([
@@ -90,7 +90,7 @@ export default async function handler(
     ) as PromiseFulfilledResult<Response> | undefined;
     if (!backendResponse) {
       context.log.error("All backend health checks failed", { responses });
-      return new ZuploResponse("Service Unavailable", { status: 503 });
+      return new Response("Service Unavailable", { status: 503 });
     } else {
       const failedResponses = responses.filter(
         (res) => res.status === "rejected",
@@ -99,11 +99,11 @@ export default async function handler(
         statuses: failedResponses.map((res) => res.reason.status),
         statusText: failedResponses.map((res) => res.reason.statusText),
       });
-      return new ZuploResponse("Service Unavailable", { status: 503 });
+      return new Response("Service Unavailable", { status: 503 });
     }
   } catch (error) {
     context.log.error("Error during health check", { error });
-    return new ZuploResponse("Service Unavailable", { status: 503 });
+    return new Response("Service Unavailable", { status: 503 });
   }
 }
 ```

package/docs/articles/log-request-response-data.mdx

@@ -108,10 +108,10 @@ personal information. Always sanitize or redact sensitive fields before logging.
 Create an outbound policy to log response information:
 
 ```ts title="modules/log-response-headers.ts"
-import type { ZuploContext, ZuploRequest, ZuploResponse } from "@zuplo/runtime";
+import type { ZuploContext, ZuploRequest } from "@zuplo/runtime";
 
 export default async function outboundPolicy(
-  response: ZuploResponse,
+  response: Response,
   request: ZuploRequest,
   context: ZuploContext,
 ) {
@@ -136,10 +136,10 @@ Log the response body from your backend. Clone the response first to avoid
 consuming the body stream.
 
 ```ts title="modules/log-response-body.ts"
-import type { ZuploContext, ZuploRequest, ZuploResponse } from "@zuplo/runtime";
+import type { ZuploContext, ZuploRequest } from "@zuplo/runtime";
 
 export default async function outboundPolicy(
-  response: ZuploResponse,
+  response: Response,
   request: ZuploRequest,
   context: ZuploContext,
 ) {

package/docs/articles/mcp-quickstart.mdx

@@ -74,12 +74,12 @@ If you're not familiar with Zuplo, it's recommended to go through the
 
 1. Connect your MCP Client
 
-   You can use any MCP client you like. We like the OpenAPI platform's
+   You can use any MCP client you like. We like the OpenAI platform's
    playground.
 
    Go to
    [platform.openai.com/playground](https://platform.openai.com/playground)
-   (you'll need an OpenAPI account).
+   (you'll need an OpenAI account).
 
    ![Add tool](../../public/media/mcp-quickstart/openai-add-tool.png)
 
@@ -93,7 +93,7 @@ If you're not familiar with Zuplo, it's recommended to go through the
 
    ![Copy MCP Server URL](../../public/media/mcp-quickstart/copy-mcp-server-url.png)
 
-   Back to the OpenAPI playground...
+   Back to the OpenAI playground...
 
    <ModalScreenshot size="sm">
 

package/docs/articles/multiple-auth-policies.mdx

@@ -31,10 +31,10 @@ cause errors or lead to security issues.
 :::
 
 All of the Zuplo built-in authentication policies have an option called
-`allowUnauthenticatedRequests`. This option is `true` by default, meaning for an
-anonymous request, the policy will immediately return a response with a 401:
+`allowUnauthenticatedRequests`. This option is `false` by default, meaning for
+an anonymous request, the policy will immediately return a response with a 401:
 Unauthorized status. **In the case of multiple policies, this setting must be
-`false`.** This means that even if the request isn't authenticated, the policy
+`true`.** This means that even if the request isn't authenticated, the policy
 will still let the request through.
 
 :::tip

package/docs/articles/plugin-azure-event-hubs.mdx

@@ -17,7 +17,7 @@ in TypeScript and a function to extract the field data from the `Response`,
 
 The plugin is configured in the
 [Runtime Extensions](../programmable-api/runtime-extensions.mdx) file
-`zuplo.runtime.ts`: git sta
+`zuplo.runtime.ts`:
 
 ```ts title="modules/zuplo.runtime.ts"
 // The interface that describes the rows

package/docs/articles/s3-signed-url-uploads.mdx

@@ -18,8 +18,7 @@ entirely.
 
 If you require larger request sizes you can consider Zuplo's
 [Managed Dedicated](../dedicated/overview.mdx) offering which allows custom
-request size limits. Contact your Zuplo offering which allows custom request
-size limits. Contact your Zuplo representative for more information.
+request size limits. Contact your Zuplo representative for more information.
 
 :::
 
@@ -51,8 +50,8 @@ Store your AWS credentials securely in Zuplo environment variables:
 
 If you are developing locally and want code completion, etc., in your project,
 install the AWS SDK for S3 to your project. These
-dependencies](../programmable-api/node-modules.mdx) are already available in the
-Zuplo runtime.
+[dependencies](../programmable-api/node-modules.mdx) are already available in
+the Zuplo runtime.
 
 ```bash
 npm install @aws-sdk/client-s3 @aws-sdk/s3-request-presigner

package/docs/articles/use-openapi-extension-data.mdx

@@ -71,7 +71,7 @@ export default async function (request: ZuploRequest, context: ZuploContext) {
   const routeData = context.route.raw();
   const myCustomConfig = routeData["x-my-custom-config"];
 
-  // Logs "Customer config, 10"
+  // Logs "Custom config, 10"
   context.log.debug("Custom config", myCustomConfig);
 
   return "Hello";

package/docs/articles/waf-ddos-akamai.md

@@ -65,7 +65,7 @@ those requests that include the custom header and secret value.
   "name": "allow-akamai-custom-header",
   "policyType": "require-header-inbound",
   "handler": {
-    "export": "RequireHeaderInboundPolicyOptions",
+    "export": "RequireHeaderInboundPolicy",
     "module": "$import(@zuplo/runtime)",
     "options": {
       "headerName": "x-akamai-auth",

package/docs/articles/waf-ddos-aws-waf-shield.mdx

@@ -63,7 +63,7 @@ those requests that include the custom header and secret value.
   "name": "allow-cloudfront-custom-header",
   "policyType": "require-header-inbound",
   "handler": {
-    "export": "RequireHeaderInboundPolicyOptions",
+    "export": "RequireHeaderInboundPolicy",
     "module": "$import(@zuplo/runtime)",
     "options": {
       "headerName": "secure-header",

package/docs/articles/waf-ddos-fastly.mdx

@@ -136,7 +136,7 @@ export default async function (
     Math.abs(currentTimeInMilliseconds - timestampInMilliseconds) / 1000;
   const offset = options.requestOffset ?? 30;
   if (differenceInSeconds > offset) {
-    context.log.error("The request is old than 30 seconds.");
+    context.log.error(`The request is older than ${offset} seconds.`);
     return HttpProblems.unauthorized(request, context);
   }
 

package/docs/guides/geolocation-backend-routing.mdx

@@ -294,7 +294,7 @@ For Option 1 (Custom Handler):
 }
 ```
 
-For Option 2 (URL Rewrite Handler), see the configuration shown above.
+For Option 2 (URL Forward Handler), see the configuration shown above.
 
 ## Testing Your Policy
 

package/docs/guides/modify-openapi-paths.mdx

@@ -196,7 +196,7 @@ const insertSegment = process.argv[3] || "/v1";
 const inputFile = process.argv[4] || "openapi.json";
 const outputFile = process.argv[5] || "openapi-modified.json";
 
-insertPathSegment(basePrefix, insertSegment, inputFile, outputFile).catch(
+insertPathSegment(inputFile, outputFile, basePrefix, insertSegment).catch(
   console.error,
 );
 ```

package/docs/handlers/legacy-dev-portal-handler.mdx

@@ -72,7 +72,7 @@ Use the path pattern `/docs(.*)` (not `/docs/(.*)`) to match both the root path
 ### Custom Domain
 
 By default, the handler redirects to your project's default Zuplo domain (e.g.,
-`my-project-1a3ksl3.zuplo.site`). If you've set up a custom domain for your
+`my-project-1a3ksl3.zuplo.app`). If you've set up a custom domain for your
 developer portal, the handler will automatically use the custom domain instead.
 
 :::note

package/docs/handlers/redirect.mdx

@@ -39,10 +39,10 @@ following example redirects requests at the root of a domain to a docs page at
           "options": {
             "location": "/docs"
           }
+        },
+        "policies": {
+          "inbound": []
         }
-      },
-      "policies": {
-        "inbound": []
       }
     }
   }

package/docs/mcp-gateway/auth/manual-oauth-testing.mdx

@@ -220,8 +220,8 @@ REDIRECT_URI="http://localhost:8765/callback"
 
    :::warning
 
-   The authorization code is single-use and short-lived (typically 30 seconds).
-   Run the next step immediately after copying it.
+   The authorization code is single-use and short-lived (60 seconds). Run the
+   next step immediately after copying it.
 
    :::
 

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

@@ -166,7 +166,7 @@ A few notes on what's set per upstream:
           "handler": {
             "module": "$import(@zuplo/runtime/mcp-gateway)",
             "export": "McpProxyHandler",
-            "options": { "rewritePattern": "https://mcp.stripe.com/mcp" },
+            "options": { "rewritePattern": "https://mcp.stripe.com" },
           },
           "policies": {
             "inbound": ["auth0-managed-oauth", "mcp-token-exchange-stripe"],

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

@@ -219,9 +219,10 @@ The corresponding route:
 }
 ```
 
-Stripe requires the bare `mcp` scope explicitly. The default PRM URL (derived
-from the route's `rewritePattern` of `https://mcp.stripe.com/mcp`) is correct,
-so no override is needed.
+Stripe requires the bare `mcp` scope explicitly. Point the route's
+`rewritePattern` at `https://mcp.stripe.com` — Stripe serves its MCP endpoint at
+the origin root, not under `/mcp`. Stripe publishes PRM at the root well-known
+path, so the default derived PRM URL is correct and no override is needed.
 
 ### Notion (PRM override at `/mcp` path)
 

package/docs/mcp-server/prompts.mdx

@@ -277,7 +277,7 @@ Response:
 
 ### Message Organization
 
-- Use `system` messages for general behavior instructions
+- Use `assistant` messages for general behavior instructions
 - Use `assistant` messages for specific task guidance
 - Structure complex prompts as multiple focused messages
 - Keep individual messages concise and purposeful

package/docs/policies/akamai-ai-firewall/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/akamai-ai-firewall.json",
   "type": "object",
   "title": "Akamai AI Firewall",
   "isDeprecated": false,

package/docs/policies/akamai-firewall-for-ai-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/akamai-firewall-for-ai-inbound.json",
   "type": "object",
   "title": "Akamai Firewall for AI",
   "isDeprecated": false,

package/docs/policies/akamai-firewall-for-ai-outbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/akamai-firewall-for-ai-outbound.json",
   "type": "object",
   "title": "Akamai Firewall for AI",
   "isDeprecated": false,

package/docs/policies/amberflo-metering-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/amberflo-metering-inbound.json",
   "type": "object",
   "title": "Amberflo Metering / Billing",
   "isDeprecated": false,

package/docs/policies/api-key-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/api-key-inbound.json",
   "type": "object",
   "title": "API Key Authentication",
   "isDeprecated": false,

package/docs/policies/audit-log-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/audit-log-inbound.json",
   "type": "object",
   "title": "Audit Logs",
   "isDeprecated": false,

package/docs/policies/auth0-jwt-auth-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/auth0-jwt-auth-inbound.json",
   "type": "object",
   "title": "Auth0 JWT Auth",
   "isDeprecated": false,

package/docs/policies/authzen-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/authzen-inbound.json",
   "type": "object",
   "title": "AuthZEN Authorization",
   "isDeprecated": false,

package/docs/policies/axiomatics-authz-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/axiomatics-authz-inbound.json",
   "type": "object",
   "title": "Axiomatics Authorization",
   "isDeprecated": false,

package/docs/policies/basic-auth-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/basic-auth-inbound.json",
   "type": "object",
   "title": "Basic Auth",
   "isDeprecated": false,

package/docs/policies/bot-detection-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/bot-detection-inbound.json",
   "type": "object",
   "title": "Bot Detection",
   "isDeprecated": false,

package/docs/policies/brownout-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/brownout-inbound.json",
   "type": "object",
   "title": "Brown Out",
   "isDeprecated": false,

package/docs/policies/caching-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/caching-inbound.json",
   "type": "object",
   "title": "Caching",
   "isDeprecated": false,

package/docs/policies/change-method-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/change-method-inbound.json",
   "type": "object",
   "title": "Change Method",
   "isDeprecated": false,

package/docs/policies/clear-headers-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/clear-headers-inbound.json",
   "type": "object",
   "title": "Clear Request Headers",
   "isDeprecated": false,

package/docs/policies/clear-headers-outbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/clear-headers-outbound.json",
   "type": "object",
   "title": "Clear Response Headers",
   "isDeprecated": false,

package/docs/policies/clerk-jwt-auth-inbound/schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft-07/schema",
-  "$id": "http://zuplo.com/schemas/policies/auth0-jwt-auth-inbound.json",
+  "$id": "https://cdn.zuplo.com/policies/runtime/schemas/clerk-jwt-auth-inbound.json",
   "type": "object",
   "title": "Clerk JWT Auth",
   "isDeprecated": false,