@leaflow/sdk 0.139.0 → 0.141.0

package/dist/canopy/v1/generated/schemas.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
  *
@@ -29,6 +31,38 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
+/**
+ * Authenticated project inference. Billing ownership comes only from the verified project token; no Canopy API key or project header is required.
+ * @summary Create a chat completion
+ */
+export declare const CreateChatCompletionBody: zod.ZodObject<{
+    model: zod.ZodString;
+    messages: zod.ZodArray<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
+    stream: zod.ZodOptional<zod.ZodBoolean>;
+    max_tokens: zod.ZodOptional<zod.ZodInt>;
+    max_completion_tokens: zod.ZodOptional<zod.ZodInt>;
+    reasoning_effort: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+/**
+ * Authenticated project inference. Billing ownership comes only from the verified project token; no Canopy API key or project header is required.
+ * @summary Create embeddings
+ */
+export declare const CreateEmbeddingsBody: zod.ZodObject<{
+    model: zod.ZodString;
+    input: zod.ZodUnion<readonly [zod.ZodString, zod.ZodArray<zod.ZodUnknown>]>;
+    encoding_format: zod.ZodOptional<zod.ZodEnum<{
+        base64: "base64";
+        float: "float";
+    }>>;
+    dimensions: zod.ZodOptional<zod.ZodInt>;
+    user: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+/**
+ * @summary Get a callable model with capabilities and parameter limits
+ */
+export declare const GetInferenceModelParams: zod.ZodObject<{
+    model: zod.ZodString;
+}, zod.z.core.$strict>;
 /**
  * @summary List API keys
  */

package/dist/canopy/v1/generated/schemas.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,9 +31,27 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
+import { ChatCompletionRequest } from "./validators/chatCompletionRequest.zod.js";
 import { CreateAPIKeyRequestBody } from "./validators/createAPIKeyRequestBody.zod.js";
 import { CreateServiceRequestBody } from "./validators/createServiceRequestBody.zod.js";
+import { EmbeddingRequest } from "./validators/embeddingRequest.zod.js";
 import { UpdateAPIKeyRequestBody } from "./validators/updateAPIKeyRequestBody.zod.js";
+/**
+ * Authenticated project inference. Billing ownership comes only from the verified project token; no Canopy API key or project header is required.
+ * @summary Create a chat completion
+ */
+export const CreateChatCompletionBody = ChatCompletionRequest;
+/**
+ * Authenticated project inference. Billing ownership comes only from the verified project token; no Canopy API key or project header is required.
+ * @summary Create embeddings
+ */
+export const CreateEmbeddingsBody = EmbeddingRequest;
+/**
+ * @summary Get a callable model with capabilities and parameter limits
+ */
+export const GetInferenceModelParams = zod.strictObject({
+    model: zod.string(),
+});
 /**
  * @summary List API keys
  */

package/dist/canopy/v1/generated/validators/aPIKeyResource.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/aPIKeyResource.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/aPIKeyUsageListResponseBody.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/aPIKeyUsageListResponseBody.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/aPIKeyUsageResource.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/aPIKeyUsageResource.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/accountBalance.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/accountBalance.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/accountIdentity.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/accountIdentity.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/activeResource.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/activeResource.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/activeResourceList.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/activeResourceList.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
  *