@leaflow/sdk 0.210.0 → 0.212.0

package/dist/assistant/v1/generated/validators/{uploadAttachmentParams.zod.js → uploadFileParams.zod.js}

@@ -20,14 +20,15 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
-export const uploadAttachmentParamsFilenameMax = 255;
-export const UploadAttachmentParams = zod.strictObject({
-    filename: zod.string().max(uploadAttachmentParamsFilenameMax).optional(),
+export const uploadFileParamsFilenameMax = 255;
+export const UploadFileParams = zod.strictObject({
+    filename: zod.string().max(uploadFileParamsFilenameMax).optional(),
 });

package/dist/assistant/v1/generated/validators/uploadListResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
@@ -36,7 +37,7 @@ export declare const UploadListResponseBody: zod.ZodObject<{
         policyId: zod.ZodString;
         expiresAt: zod.z.ZodISODateTime;
         status: zod.ZodString;
-        attachmentId: zod.ZodNullable<zod.ZodString>;
+        fileId: zod.ZodNullable<zod.ZodString>;
         parts: zod.ZodArray<zod.ZodObject<{
             number: zod.ZodInt;
             byteSize: zod.ZodInt;

package/dist/assistant/v1/generated/validators/uploadListResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/uploadPartResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/uploadPartResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/uploadResource.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
@@ -35,7 +36,7 @@ export declare const UploadResource: zod.ZodObject<{
     policyId: zod.ZodString;
     expiresAt: zod.z.ZodISODateTime;
     status: zod.ZodString;
-    attachmentId: zod.ZodNullable<zod.ZodString>;
+    fileId: zod.ZodNullable<zod.ZodString>;
     parts: zod.ZodArray<zod.ZodObject<{
         number: zod.ZodInt;
         byteSize: zod.ZodInt;

package/dist/assistant/v1/generated/validators/uploadResource.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";
@@ -36,6 +37,9 @@ export const UploadResource = zod.strictObject({
     policyId: zod.string(),
     expiresAt: zod.iso.datetime({ offset: true }),
     status: zod.string(),
-    attachmentId: zod.string().nullable(),
+    fileId: zod
+        .string()
+        .nullable()
+        .describe("The file the upload became. Null until the upload is complete."),
     parts: zod.array(UploadPartResource),
 });

package/dist/assistant/v1/generated/validators/usage.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/usage.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/verifyCodeRequestBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/verifyCodeRequestBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/webhookSecretResponseBody.zod.d.ts

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/assistant/v1/generated/validators/webhookSecretResponseBody.zod.js

@@ -20,10 +20,11 @@
  * outlines the person's messages for navigating a long conversation.
  *
  * Upload large files with /api/v1/uploads: read /api/v1/upload-configuration first, send exact-sized
- * parts, then complete the upload and send its attachment id in a message.
+ * parts, then complete the upload and send its file id in a message.
  *
- * Files uploaded that way are listed by search-attachments. Renaming or removing one does not change
- * the conversations that already use it; downloading keeps working.
+ * Files the person attached are listed by search-files. Renaming or removing one does not change
+ * the conversations that already use it; downloading keeps working. Files the assistant hands over
+ * are artifacts: they appear on the tool call that created them and are listed by list-artifacts.
  * OpenAPI spec version: 2.0.0
  */
 import * as zod from "zod";

package/dist/canopy/v1/generated/functions.d.ts

@@ -4,17 +4,26 @@
  * Leaflow Canopy API
  * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
  *
- * Project inference is served on this host in each provider's own protocol:
+ * Project inference is served on this host at each protocol's own endpoints:
  *
  * - OpenAI: `/v1/chat/completions`, `/v1/responses` and `/v1/embeddings`; use
  *   `https://canopy.leaflow.cloud/v1` as the OpenAI SDK base URL.
  * - Anthropic: `/v1/messages`; use `https://canopy.leaflow.cloud` as the Anthropic SDK base URL.
  * - Gemini: `/v1beta/models/{model}:generateContent` and `:streamGenerateContent`.
  *
- * Canopy does not convert between protocols. A request is accepted only for a model whose
- * `supported_endpoints` lists the endpoint it was sent to, and it is forwarded unchanged except for
- * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
- * through as written; a model's `capabilities` lists the values its upstream accepts.
+ * Every chat model accepts all four chat protocols: Chat Completions, Responses, Messages and Gemini
+ * generateContent. A request is forwarded unchanged, apart from the model name and the credentials, when a
+ * provider of the model speaks the protocol it was sent in; otherwise it is translated into a protocol a
+ * provider speaks, and the response is translated back. Content that cannot be translated, such as a tool
+ * that runs on another provider's servers or a reference to a file stored with another provider, is refused
+ * with 400 rather than dropped. Reasoning settings such as `reasoning_effort` are passed through as written;
+ * a model's `capabilities` lists the values it accepts.
+ *
+ * Responses is stateless: `store` must be false, and a response cannot be retrieved after it is returned.
+ * Send the output items of a response back unchanged, in their order, as input to the next request.
+ *
+ * What a model does follows from its `input_modalities`, `output_modalities` and the media blocks of its
+ * `capabilities`. Embeddings, images, audio and videos are accepted for a model whose providers serve them.
  *
  * Management operations use `/api/v1`. The management model catalogue names how each model is billed in Billing;
  * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
@@ -38,7 +47,7 @@
  * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates Billing holds for each model's `billing`.
  * OpenAPI spec version: 1.0.0
  */
-import type { APIKeyResource, APIKeyUsageListResponseBody, ChatCompletion, ChatCompletionRequest, ConflictResponse, CreateAPIKeyRequestBody, CreateServiceRequestBody, CreateServiceResponseBody, CursorPageRequestResource, EmbeddingRequest, EmbeddingResponse, Error, GetUsageSummaryParams, GetUsageTimelineParams, GetVideoContentHeaders, InferenceError, IssuedAPIKeyResource, LengthAwarePageAPIKeyResource, ListApiKeysParams, ListRequestsParams, ListUsageByApiKeyParams, ListUsageByModelParams, Model, ModelList, ModelListResponseBody, ModelResource, ModelUsageListResponseBody, NativeRequest, NativeResponse, RequestResource, ResponseCreate, ResponseDeleted, ResponseResource, ServiceResource, StreamGenerateContentParams, TotalsResource, UpdateAPIKeyRequestBody, UsageTimelineResponseBody, VideoCreateRequest, VideoTask } from "./models.js";
+import type { APIKeyResource, APIKeyUsageListResponseBody, ChatCompletion, ChatCompletionRequest, ConflictResponse, CreateAPIKeyRequestBody, CreateServiceRequestBody, CreateServiceResponseBody, CursorPageRequestResource, EmbeddingRequest, EmbeddingResponse, Error, GetUsageSummaryParams, GetUsageTimelineParams, GetVideoContentHeaders, InferenceError, IssuedAPIKeyResource, LengthAwarePageAPIKeyResource, ListApiKeysParams, ListRequestsParams, ListUsageByApiKeyParams, ListUsageByModelParams, Model, ModelList, ModelListResponseBody, ModelResource, ModelUsageListResponseBody, NativeRequest, NativeResponse, RequestResource, ResponseCreate, ResponseResource, ServiceResource, StreamGenerateContentParams, TotalsResource, UpdateAPIKeyRequestBody, UsageTimelineResponseBody, VideoCreateRequest, VideoTask } from "./models.js";
 export type HTTPStatusCode1xx = 100 | 101 | 102 | 103;
 export type HTTPStatusCode2xx = 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207;
 export type HTTPStatusCode3xx = 300 | 301 | 302 | 303 | 304 | 305 | 307 | 308;
@@ -138,50 +147,10 @@ export type createResponseResponseError = createResponseResponseDefault & {
 export type createResponseResponse = createResponseResponseSuccess | createResponseResponseError;
 export declare const getCreateResponseUrl: () => string;
 /**
- * Supports JSON, SSE and native upstream response storage. Stored continuation is restricted to the current project and original provider credential. WebSocket clients connect with GET /v1/responses and send response.create events; one response may be active on a connection at a time. The connection stays on its initial model and provider credential.
+ * Returns JSON, or Responses SSE events when `stream` is true. Accepted for every chat model, whichever protocol its providers speak. Responses are not stored, so `store` must be false; send the output items of a response back unchanged, in their order, as input to the next request. Reasoning items carry `encrypted_content`, which has to be returned as received. WebSocket clients connect with GET /v1/responses and send response.create events; one response may be active on a connection at a time, and `previous_response_id` continues a response created earlier on the same connection. The connection stays on its initial model and provider credential.
  * @summary Create a model response
  */
 export declare const createResponse: (responseCreate: ResponseCreate, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<createResponseResponse>;
-export type getResponseResponse200 = {
-    data: ResponseResource;
-    status: 200;
-};
-export type getResponseResponseDefault = {
-    data: InferenceError;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type getResponseResponseSuccess = getResponseResponse200 & {
-    headers: Headers;
-};
-export type getResponseResponseError = getResponseResponseDefault & {
-    headers: Headers;
-};
-export type getResponseResponse = getResponseResponseSuccess | getResponseResponseError;
-export declare const getGetResponseUrl: (response: string) => string;
-/**
- * @summary Get a stored response
- */
-export declare const getResponse: (response: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<getResponseResponse>;
-export type deleteResponseResponse200 = {
-    data: ResponseDeleted;
-    status: 200;
-};
-export type deleteResponseResponseDefault = {
-    data: InferenceError;
-    status: Exclude<HTTPStatusCodes, 200>;
-};
-export type deleteResponseResponseSuccess = deleteResponseResponse200 & {
-    headers: Headers;
-};
-export type deleteResponseResponseError = deleteResponseResponseDefault & {
-    headers: Headers;
-};
-export type deleteResponseResponse = deleteResponseResponseSuccess | deleteResponseResponseError;
-export declare const getDeleteResponseUrl: (response: string) => string;
-/**
- * @summary Delete a stored response
- */
-export declare const deleteResponse: (response: string, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<deleteResponseResponse>;
 export type createChatCompletionResponse200ApplicationJson = {
     data: ChatCompletion;
     status: 200;
@@ -203,7 +172,7 @@ export type createChatCompletionResponseError = createChatCompletionResponseDefa
 export type createChatCompletionResponse = createChatCompletionResponseSuccess | createChatCompletionResponseError;
 export declare const getCreateChatCompletionUrl: () => string;
 /**
- * Authenticated project inference in the OpenAI Chat Completions protocol, forwarded unchanged to an upstream that speaks it. Billing ownership comes only from the verified project token.
+ * Authenticated project inference in the OpenAI Chat Completions protocol. Accepted for every chat model, whichever protocol its providers speak. Billing ownership comes only from the verified project token.
  * @summary Create a chat completion
  */
 export declare const createChatCompletion: (chatCompletionRequest: ChatCompletionRequest, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<createChatCompletionResponse>;
@@ -249,7 +218,7 @@ export type createMessageResponseError = createMessageResponseDefault & {
 export type createMessageResponse = createMessageResponseSuccess | createMessageResponseError;
 export declare const getCreateMessageUrl: () => string;
 /**
- * Authenticated project inference in the Anthropic Messages protocol, forwarded unchanged to an upstream that speaks it. Accepts the `x-api-key` header as well as Authorization. Streams Anthropic SSE events when `stream` is true.
+ * Authenticated project inference in the Anthropic Messages protocol. Accepted for every chat model, whichever protocol its providers speak. Accepts the `x-api-key` header as well as Authorization. Streams Anthropic SSE events when `stream` is true.
  * @summary Create a message
  */
 export declare const createMessage: (nativeRequest: NativeRequest, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<createMessageResponse>;
@@ -270,7 +239,7 @@ export type generateContentResponseError = generateContentResponseDefault & {
 export type generateContentResponse = generateContentResponseSuccess | generateContentResponseError;
 export declare const getGenerateContentUrl: (model: string) => string;
 /**
- * Authenticated project inference in the Gemini protocol, forwarded unchanged to an upstream that speaks it. Accepts the `x-goog-api-key` header as well as Authorization.
+ * Authenticated project inference in the Gemini protocol. Accepted for every chat model, whichever protocol its providers speak. Accepts the `x-goog-api-key` header as well as Authorization.
  * @summary Generate content
  */
 export declare const generateContent: (model: string, nativeRequest: NativeRequest, options?: RequestInit, fetchFn?: typeof globalThis.fetch) => Promise<generateContentResponse>;

package/dist/canopy/v1/generated/functions.js

@@ -92,7 +92,7 @@ export const getCreateResponseUrl = () => {
     return `https://canopy.leaflow.cloud/v1/responses`;
 };
 /**
- * Supports JSON, SSE and native upstream response storage. Stored continuation is restricted to the current project and original provider credential. WebSocket clients connect with GET /v1/responses and send response.create events; one response may be active on a connection at a time. The connection stays on its initial model and provider credential.
+ * Returns JSON, or Responses SSE events when `stream` is true. Accepted for every chat model, whichever protocol its providers speak. Responses are not stored, so `store` must be false; send the output items of a response back unchanged, in their order, as input to the next request. Reasoning items carry `encrypted_content`, which has to be returned as received. WebSocket clients connect with GET /v1/responses and send response.create events; one response may be active on a connection at a time, and `previous_response_id` continues a response created earlier on the same connection. The connection stays on its initial model and provider credential.
  * @summary Create a model response
  */
 export const createResponse = async (responseCreate, options, fetchFn) => {
@@ -121,41 +121,11 @@ export const createResponse = async (responseCreate, options, fetchFn) => {
     const data = body;
     return { data, status: res.status, headers: res.headers };
 };
-export const getGetResponseUrl = (response) => {
-    return `https://canopy.leaflow.cloud/v1/responses/${encodeURIComponent(String(response))}`;
-};
-/**
- * @summary Get a stored response
- */
-export const getResponse = async (response, options, fetchFn) => {
-    const res = await (fetchFn ?? fetch)(getGetResponseUrl(response), {
-        ...options,
-        method: "GET",
-    });
-    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
-    const data = body ? JSON.parse(body) : {};
-    return { data, status: res.status, headers: res.headers };
-};
-export const getDeleteResponseUrl = (response) => {
-    return `https://canopy.leaflow.cloud/v1/responses/${encodeURIComponent(String(response))}`;
-};
-/**
- * @summary Delete a stored response
- */
-export const deleteResponse = async (response, options, fetchFn) => {
-    const res = await (fetchFn ?? fetch)(getDeleteResponseUrl(response), {
-        ...options,
-        method: "DELETE",
-    });
-    const body = [204, 205, 304].includes(res.status) ? null : await res.text();
-    const data = body ? JSON.parse(body) : {};
-    return { data, status: res.status, headers: res.headers };
-};
 export const getCreateChatCompletionUrl = () => {
     return `https://canopy.leaflow.cloud/v1/chat/completions`;
 };
 /**
- * Authenticated project inference in the OpenAI Chat Completions protocol, forwarded unchanged to an upstream that speaks it. Billing ownership comes only from the verified project token.
+ * Authenticated project inference in the OpenAI Chat Completions protocol. Accepted for every chat model, whichever protocol its providers speak. Billing ownership comes only from the verified project token.
  * @summary Create a chat completion
  */
 export const createChatCompletion = async (chatCompletionRequest, options, fetchFn) => {
@@ -221,7 +191,7 @@ export const getCreateMessageUrl = () => {
     return `https://canopy.leaflow.cloud/v1/messages`;
 };
 /**
- * Authenticated project inference in the Anthropic Messages protocol, forwarded unchanged to an upstream that speaks it. Accepts the `x-api-key` header as well as Authorization. Streams Anthropic SSE events when `stream` is true.
+ * Authenticated project inference in the Anthropic Messages protocol. Accepted for every chat model, whichever protocol its providers speak. Accepts the `x-api-key` header as well as Authorization. Streams Anthropic SSE events when `stream` is true.
  * @summary Create a message
  */
 export const createMessage = async (nativeRequest, options, fetchFn) => {
@@ -254,7 +224,7 @@ export const getGenerateContentUrl = (model) => {
     return `https://canopy.leaflow.cloud/v1beta/models/${encodeURIComponent(String(model))}:generateContent`;
 };
 /**
- * Authenticated project inference in the Gemini protocol, forwarded unchanged to an upstream that speaks it. Accepts the `x-goog-api-key` header as well as Authorization.
+ * Authenticated project inference in the Gemini protocol. Accepted for every chat model, whichever protocol its providers speak. Accepts the `x-goog-api-key` header as well as Authorization.
  * @summary Generate content
  */
 export const generateContent = async (model, nativeRequest, options, fetchFn) => {