@leaflow/sdk 0.140.0 → 0.142.0

package/dist/canopy/v1/generated/validators/modelPricing.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/modelPricing.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/modelResource.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
  *
@@ -49,15 +51,55 @@ export declare const ModelResource: zod.ZodObject<{
             unit_quantity: zod.ZodNullable<zod.ZodString>;
         }, zod.z.core.$strict>>;
     }, zod.z.core.$strict>, zod.ZodNull]>;
-    reasoning_tiers: zod.ZodArray<zod.ZodString>;
     status: zod.ZodEnum<{
         available: "available";
         draining: "draining";
         retired: "retired";
     }>;
-    supports_reasoning: zod.ZodBoolean;
-    supports_tools: zod.ZodBoolean;
-    supports_vision: zod.ZodBoolean;
+    developer: zod.ZodString;
+    description: zod.ZodString;
+    input_modalities: zod.ZodNullable<zod.ZodArray<zod.ZodEnum<{
+        file: "file";
+        text: "text";
+        image: "image";
+        audio: "audio";
+        video: "video";
+        embedding: "embedding";
+    }>>>;
+    output_modalities: zod.ZodNullable<zod.ZodArray<zod.ZodEnum<{
+        file: "file";
+        text: "text";
+        image: "image";
+        audio: "audio";
+        video: "video";
+        embedding: "embedding";
+    }>>>;
+    capabilities: zod.ZodRecord<zod.ZodString, zod.ZodObject<{
+        function_calling: zod.ZodNullable<zod.ZodBoolean>;
+        structured_output: zod.ZodNullable<zod.ZodBoolean>;
+        reasoning: zod.ZodUnion<readonly [zod.ZodObject<{
+            supported: zod.ZodBoolean;
+            effort_levels: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+            default_effort: zod.ZodNullable<zod.ZodString>;
+            modes: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+            budget_tokens: zod.ZodNullable<zod.ZodObject<{
+                min: zod.ZodInt;
+                max: zod.ZodInt;
+            }, zod.z.core.$strict>>;
+            summary: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
+        }, zod.z.core.$strict>, zod.ZodNull]>;
+    }, zod.z.core.$strict>>;
+    supported_endpoints: zod.ZodArray<zod.ZodEnum<{
+        "/v1/chat/completions": "/v1/chat/completions";
+        "/v1/responses": "/v1/responses";
+        "/v1/embeddings": "/v1/embeddings";
+        "/v1/images/generations": "/v1/images/generations";
+        "/v1/images/edits": "/v1/images/edits";
+        "/v1/audio/transcriptions": "/v1/audio/transcriptions";
+        "/v1/audio/translations": "/v1/audio/translations";
+        "/v1/audio/speech": "/v1/audio/speech";
+        "/v1/realtime": "/v1/realtime";
+    }>>;
 }, zod.z.core.$strict>;
 export type ModelResource = zod.input<typeof ModelResource>;
 export type ModelResourceOutput = zod.output<typeof ModelResource>;

package/dist/canopy/v1/generated/validators/modelResource.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
  *
@@ -29,6 +31,9 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
+import { Modality } from "./modality.zod.js";
+import { ModelCapabilities } from "./modelCapabilities.zod.js";
+import { ModelEndpoint } from "./modelEndpoint.zod.js";
 import { ModelPricing } from "./modelPricing.zod.js";
 export const ModelResource = zod.strictObject({
     context_length: zod
@@ -43,11 +48,21 @@ export const ModelResource = zod.strictObject({
     pricing: zod
         .union([ModelPricing, zod.null()])
         .describe("What requests to this model cost. Null when the project has no billing account."),
-    reasoning_tiers: zod
-        .array(zod.string())
-        .describe("The values accepted for `reasoning_effort`. Empty means it is not supported"),
     status: zod.enum(["available", "draining", "retired"]),
-    supports_reasoning: zod.boolean(),
-    supports_tools: zod.boolean(),
-    supports_vision: zod.boolean(),
+    developer: zod
+        .string()
+        .describe("The model developer; not the upstream provider or model family."),
+    description: zod.string(),
+    input_modalities: zod
+        .array(Modality)
+        .nullable()
+        .describe("Accepted input modalities. Null means unknown."),
+    output_modalities: zod
+        .array(Modality)
+        .nullable()
+        .describe("Produced output modalities. Image input does not imply image generation."),
+    capabilities: ModelCapabilities,
+    supported_endpoints: zod
+        .array(ModelEndpoint)
+        .describe("Explicitly supported API endpoints. Requests to any other endpoint are rejected before upstream admission."),
 });

package/dist/canopy/v1/generated/validators/modelUsageListResponseBody.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/modelUsageListResponseBody.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/modelUsageResource.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/modelUsageResource.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/money.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/money.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/monthlyStatement.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/monthlyStatement.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/monthlyStatementList.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/monthlyStatementList.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/namedIdentity.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
  *