@leaflow/sdk 0.139.0 → 0.141.0

package/dist/canopy/v1/generated/validators/objectIdentity.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/offsetPagination.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/offsetPagination.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/order.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *
@@ -104,6 +106,7 @@ export declare const Order: zod.ZodObject<{
     checkout_confirmed_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
     created_at: zod.z.ZodISODateTime;
     items: zod.ZodArray<zod.ZodObject<{
+        renewal_discounts_enabled: zod.ZodOptional<zod.ZodBoolean>;
         invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
         position: zod.ZodOptional<zod.ZodInt>;
         configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;

package/dist/canopy/v1/generated/validators/order.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderCancel.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderCancel.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderItem.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *
@@ -31,6 +33,7 @@
 import * as zod from "zod";
 export declare const orderItemPositionMin = 0;
 export declare const OrderItem: zod.ZodObject<{
+    renewal_discounts_enabled: zod.ZodOptional<zod.ZodBoolean>;
     invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
     position: zod.ZodOptional<zod.ZodInt>;
     configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;

package/dist/canopy/v1/generated/validators/orderItem.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *
@@ -38,6 +40,10 @@ import { TerminationPolicy } from "./terminationPolicy.zod.js";
 export const orderItemPositionMin = 0;
 export const OrderItem = zod
     .strictObject({
+    renewal_discounts_enabled: zod
+        .boolean()
+        .optional()
+        .describe("Whether new account discounts may apply to future renewals. A fixed operator renewal agreement disables automatic discounts; catalog repricing or a newly selected purchase agreement enables them."),
     invoice_item_ids: zod
         .array(zod.uuid())
         .optional()

package/dist/canopy/v1/generated/validators/orderItemList.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *
@@ -31,6 +33,7 @@
 import * as zod from "zod";
 export declare const OrderItemList: zod.ZodObject<{
     items: zod.ZodArray<zod.ZodObject<{
+        renewal_discounts_enabled: zod.ZodOptional<zod.ZodBoolean>;
         invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
         position: zod.ZodOptional<zod.ZodInt>;
         configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;

package/dist/canopy/v1/generated/validators/orderItemList.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderItemStatus.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderItemStatus.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderList.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *
@@ -105,6 +107,7 @@ export declare const OrderList: zod.ZodObject<{
         checkout_confirmed_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
         created_at: zod.z.ZodISODateTime;
         items: zod.ZodArray<zod.ZodObject<{
+            renewal_discounts_enabled: zod.ZodOptional<zod.ZodBoolean>;
             invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
             position: zod.ZodOptional<zod.ZodInt>;
             configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;

package/dist/canopy/v1/generated/validators/orderList.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderRefundQuote.zod.d.ts

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *

package/dist/canopy/v1/generated/validators/orderRefundQuote.zod.js

@@ -2,21 +2,23 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Canopy API
- * Management of API keys, together with the models available and the usage recorded against them.
+ * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ * OpenAI-compatible project inference is served on this host at `/v1/chat/completions`,
+ * `/v1/embeddings`, `/v1/models` and `/v1/models/{model}`. Use `https://canopy.leaflow.cloud/v1`
+ * as the OpenAI SDK base URL. Chat completions support `stream=true` SSE.
  *
- * ```
- * POST /v1/chat/completions                    OpenAI
- * POST /v1/messages                            Anthropic
- * POST /v1beta/models/{model}:generateContent  Gemini
- * ```
+ * Management operations use `/api/v1`. The management model catalogue includes pricing;
+ * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
  *
  * ## Authentication
  *
  * Every request carries a scoped token; see the `bearerAuth` security scheme.
  *
- * These management endpoints do not accept a Canopy API key. On this userapi host, the OpenAI-compatible `/v1/chat/completions`, `/v1/embeddings`, `/v1/models` and `/v1/models/{model}` endpoints accept the same project token; see the project inference contract. The separate API-key gateway continues to accept Canopy API keys.
+ * Management and project inference accept the same verified IAM scoped token. The token is the
+ * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
+ * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
+ * accepts Canopy API keys and supports OpenAI, Anthropic and Gemini request formats.
  *
  * ## Conventions
  *