zuplo 7.6.4 → 7.6.6

package/docs/concepts/ai-gateway.mdx

@@ -21,9 +21,10 @@ Three building blocks organize an AI Gateway:
   can route to. Administrators configure providers once, including any
   [custom OpenAI-compatible providers](../ai-gateway/custom-providers.mdx), and
   consumers never see the underlying credentials.
-- **[Teams](../ai-gateway/teams.mdx)** group users and carry budget limits that
-  cascade down the hierarchy: gateway-wide limits, then team limits, then
-  per-app limits. See [Usage Limits](../ai-gateway/usage-limits.mdx).
+- **[Teams](../ai-gateway/teams.mdx)** group users and carry budget limits. Each
+  team totals usage across its sub-teams and apps. A request must remain within
+  the gateway, ancestor team, and app limits. See
+  [Usage Limits](../ai-gateway/usage-limits.mdx).
 - **[Apps](../ai-gateway/apps.mdx)** are the pieces of software that call the
   gateway — a support chatbot is one app, an internal coding agent is another.
   Each app gets its own gateway URL, its own Zuplo-managed API key, and its own
@@ -54,12 +55,12 @@ code change.
 
 ## How it fits into Zuplo
 
-An AI Gateway is a type of Zuplo project. Its routes and policy declarations
-live in a [Git repository](../ai-gateway/source-control.mdx), so gateway changes
-go through the same review workflow as the rest of your Zuplo configuration, and
-the providers, teams, and apps you configure belong to that project. The
-platform primitives — deployment model, environments, analytics — are the same
-ones described in [How Zuplo Works](./how-zuplo-works.mdx).
+An AI Gateway is a type of Zuplo project. A new project deploys without a Git
+repository; you can [connect a repository](../ai-gateway/source-control.mdx)
+later so gateway changes go through the same review workflow as the rest of your
+Zuplo configuration. The providers, teams, and apps you configure belong to that
+project. The platform primitives — deployment model, environments, analytics —
+are the same ones described in [How Zuplo Works](./how-zuplo-works.mdx).
 
 ## Next steps
 

package/docs/concepts/api-keys.md

@@ -187,7 +187,7 @@ Each project has separate buckets for production, preview, and working copy
 environments. This means API keys created in production don't work in preview,
 and vice versa.
 
-For testing, you can specify a custom bucket name on the
+For testing, you can specify a custom bucket ID on the
 [API Key Authentication](../policies/api-key-inbound.mdx) policy to share keys
 across environments. Enterprise customers can share buckets across projects or
 accounts.

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

@@ -165,14 +165,17 @@ When the firewall detects a threat, it can take one of three actions:
 
 ## Cost and Usage Controls
 
-The Zuplo AI Gateway provides hierarchical budget controls to manage AI
-spending:
-
-- **Organization limits** - Maximum daily and monthly spending across all AI
-  usage
-- **Team budgets** - Allocated budgets for departments or customer segments
-- **Application limits** - Per-application or per-use-case cost controls
-- **Rate limiting** - Request throttling to prevent abuse
+The Zuplo AI Gateway provides budget controls at every level of the hierarchy to
+manage AI spending:
+
+- **Gateway budgets** - Hourly, daily, weekly, or monthly limits across all AI
+  Gateway usage.
+- **Team budgets** - Shared or per-expression limits across a team, its
+  sub-teams, and their apps.
+- **App budgets** - Shared or per-expression limits for one app.
+- **Rate limiting** - Request throttling to prevent abuse.
+
+For more information, see [Usage Limits](../../ai-gateway/usage-limits.mdx).
 
 ## Security Model
 

package/docs/dev-portal/dev-portal-create-consumer-on-auth.mdx

@@ -56,14 +56,19 @@ secret `API_KEY` and set the value.
 
 :::info
 
-In the code below set the variable `BUCKET_NAME` to the bucket being used by
-your Zuplo Gateway. If you don't know the name of your bucket, you can
+In the code below set the variable `API_KEY_BUCKET_ID` to the ID of the bucket
+being used by your Zuplo Gateway. Copy it from the **Bucket ID** pill on your
+project's
+[**Services → API Keys → Consumers**](https://portal.zuplo.com/+/account/project/services)
+page, or
 [list your buckets using the Developer API](https://dev.zuplo.com/docs/routes#apikeybucketsservice_list).
+For more information, see
+[Bucket identifiers](../articles/api-key-buckets.mdx#bucket-identifiers).
 
 :::
 
 Next, add the following code to your custom action. Be sure to replace the
-placeholder values with your actual account and bucket names. Click the
+placeholder values with your actual account name and bucket ID. Click the
 **Deploy** button when you are finished.
 
 ```ts
@@ -71,7 +76,7 @@ const { fetch } = require("undici");
 const { randomUUID } = require("crypto");
 
 const ZUPLO_ACCOUNT = "my-zuplo-account";
-const API_KEY_BUCKET = "my-bucket";
+const API_KEY_BUCKET_ID = "bckt_2HaK3odRyJle6NJSu8mzNKBC30BYxllxL";
 
 /**
  * Handler that will be called during the execution of a PostLogin flow.
@@ -100,7 +105,7 @@ exports.onExecutePostLogin = async (event, api) => {
   try {
     // Create the consumer
     const response = await fetch(
-      `https://dev.zuplo.com/v1/accounts/${ZUPLO_ACCOUNT}/key-buckets/${API_KEY_BUCKET}/consumers?with-api-key=true`,
+      `https://dev.zuplo.com/v1/accounts/${ZUPLO_ACCOUNT}/key-buckets/${API_KEY_BUCKET_ID}/consumers?with-api-key=true`,
       {
         method: "POST",
         body: JSON.stringify(body),

package/docs/dev-portal/zudoku/configuration/api-reference.md

@@ -276,7 +276,7 @@ Available options:
   schemes section on the info page, and the Authorize dialog in the playground). Disabled by default
   (`true`). Set to `false` to enable security scheme support
 - `disableMcpAuthInstructions`: Hide the authentication instructions on
-  [MCP server](../guides/mcp-servers.md) endpoints. The MCP card normally derives a credential
+  [MCP server](/docs/dev-portal/documenting-mcp-servers) endpoints. The MCP card normally derives a credential
   header from the operation's security scheme and shows it in every install snippet. Set to `true`
   to render the server as unauthenticated instead — no header snippets and no "replace
   `YOUR_API_KEY`" steps

package/docs/dev-portal/zudoku/configuration/llms.md

@@ -112,10 +112,6 @@ dist/
     └── ...
 ```
 
-On Vercel builds, this tree is written beneath `.vercel/output/static/` instead of `dist/`. The
-deployed public URLs remain the same. See the [Vercel deployment guide](/dev-portal/zudoku/deploy/vercel) for the
-generated routing and Markdown content-negotiation behavior.
-
 **Important:** Individual `.md` files are only kept in the final build if `publishMarkdown: true`.
 If only `llmsTxt` or `llmsTxtFull` is enabled, the `.md` files are generated temporarily during the
 build but deleted after the `llms.txt` files are created.

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

@@ -319,7 +319,7 @@ selected from the request. Each expression rule requires one or more meter rows:
 | `meter`    | `cost`, `requests`, `tokens`                         |
 | `period`   | `hourly`, `daily`, `weekly`, `monthly`               |
 | `action`   | `warn` records a warning; `block` returns HTTP `429` |
-| `value`    | A finite number greater than or equal to zero        |
+| `value`    | A finite number greater than zero                    |
 
 A rule cannot repeat the same meter, period, and action. When a meter and period
 have both actions, the `warn` value must be less than the `block` value. The

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

@@ -103,7 +103,7 @@
                         },
                         "value": {
                           "type": "number",
-                          "minimum": 0
+                          "exclusiveMinimum": 0
                         },
                         "action": {
                           "type": "string",

package/docs/policies/semantic-cache-inbound/schema.json

@@ -61,8 +61,12 @@
             },
             "cacheByPropertyPath": {
               "type": "string",
-              "description": "The path to the property in the request body (JSON) to use as cache key. For example '.userId' would read the 'userId' property from the request body. Only works with cacheBy=propertyPath.",
-              "examples": [".userId", ".data.customerId"]
+              "description": "A light path selector into the JSON request body to use as the cache key. Start with `.` for dot notation or `[` for a quoted key containing dots or slashes, for example `.userId`, `.data.customerId`, or `[\"https://example.com/cache-key\"]`. Only works with cacheBy=propertyPath.",
+              "examples": [
+                ".userId",
+                ".data.customerId",
+                "[\"https://example.com/cache-key\"]"
+              ]
             },
             "cacheByFunction": {
               "type": "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.6.4",
+  "version": "7.6.6",
   "type": "module",
   "description": "The official Zuplo CLI for local development and platform management",
   "homepage": "https://zuplo.com/docs/cli/overview",
@@ -32,9 +32,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.6.4",
-    "@zuplo/core": "7.6.4",
-    "@zuplo/runtime": "7.6.4",
-    "@zuplo/test": "7.6.4"
+    "@zuplo/cli": "7.6.6",
+    "@zuplo/core": "7.6.6",
+    "@zuplo/runtime": "7.6.6",
+    "@zuplo/test": "7.6.6"
   }
 }