@leaflow/sdk 0.0.0-dev.516.g28eeab9 → 0.0.0-dev.523.gcaeef48

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

@@ -0,0 +1,70 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+import { VideoReferenceMedia } from "./videoReferenceMedia.zod.js";
+export const videoCreateRequestReferenceMediaMax = 20;
+export const VideoCreateRequest = zod
+    .strictObject({
+    model: zod.string().min(1),
+    prompt: zod.string().optional(),
+    seconds: zod.int().min(1).optional(),
+    size: zod.string().optional(),
+    resolution: zod.string().optional(),
+    input_reference: zod
+        .string()
+        .min(1)
+        .optional()
+        .describe("Backward-compatible first-frame image URL. May be combined with a last_frame, not another first_frame."),
+    reference_media: zod
+        .array(VideoReferenceMedia)
+        .min(1)
+        .max(videoCreateRequestReferenceMediaMax)
+        .optional(),
+    audio: zod
+        .boolean()
+        .optional()
+        .describe("Whether the output has audio; separate from a reference_audio input."),
+    prompt_extend: zod.boolean().optional(),
+    watermark: zod.boolean().optional(),
+    seed: zod.int().optional(),
+    negative_prompt: zod.string().optional(),
+})
+    .describe("Provide a prompt, reference media, or both. Extra fields depend on the selected model and adapter.");

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

@@ -0,0 +1,53 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+export declare const VideoReferenceMedia: zod.ZodObject<{
+    type: zod.ZodEnum<{
+        first_frame: "first_frame";
+        last_frame: "last_frame";
+        reference_image: "reference_image";
+        reference_video: "reference_video";
+        reference_audio: "reference_audio";
+    }>;
+    url: zod.ZodString;
+}, zod.z.core.$strict>;
+export type VideoReferenceMedia = zod.input<typeof VideoReferenceMedia>;
+export type VideoReferenceMediaOutput = zod.output<typeof VideoReferenceMedia>;

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

@@ -0,0 +1,53 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+export const VideoReferenceMedia = zod
+    .strictObject({
+    type: zod.enum([
+        "first_frame",
+        "last_frame",
+        "reference_image",
+        "reference_video",
+        "reference_audio",
+    ]),
+    url: zod.string().min(1),
+})
+    .describe("A typed reference asset. Order is preserved, including order within each media type.\nWan 3.0 accepts at most one first frame, one last frame, ten reference images,\nfive reference videos and five reference audio clips. A last frame needs a first frame.\nFirst/last frames cannot be combined with reference_image, reference_video or reference_audio.\nReference images, videos and audio may be combined. Other models can accept fewer roles.\nImages accept public HTTP(S) or base64 image data URLs. Video and audio accept public\nHTTP(S) URLs only. Wan 3.0 limits reference videos and audio to 1-15 seconds each and\n15 seconds total per media type; input video plus output duration must not exceed 30 seconds.\nThe upstream validates remote asset size, format and duration. Canopy does not fetch them.");

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

@@ -0,0 +1,71 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+export declare const VideoTask: zod.ZodObject<{
+    id: zod.ZodString;
+    object: zod.ZodString;
+    status: zod.ZodEnum<{
+        completed: "completed";
+        failed: "failed";
+        in_progress: "in_progress";
+        queued: "queued";
+    }>;
+    model: zod.ZodOptional<zod.ZodString>;
+    usage: zod.ZodOptional<zod.ZodObject<{
+        seconds: zod.ZodOptional<zod.ZodNumber>;
+        resolution: zod.ZodOptional<zod.ZodString>;
+        input_seconds: zod.ZodOptional<zod.ZodNumber>;
+        output_seconds: zod.ZodOptional<zod.ZodNumber>;
+        billable_seconds: zod.ZodOptional<zod.ZodNumber>;
+    }, zod.z.core.$strict>>;
+    seconds: zod.ZodOptional<zod.ZodString>;
+    size: zod.ZodOptional<zod.ZodString>;
+    created_at: zod.ZodOptional<zod.ZodInt>;
+    completed_at: zod.ZodOptional<zod.ZodInt>;
+    expires_at: zod.ZodOptional<zod.ZodInt>;
+    progress: zod.ZodOptional<zod.ZodInt>;
+    error: zod.ZodOptional<zod.ZodObject<{
+        code: zod.ZodOptional<zod.ZodString>;
+        message: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type VideoTask = zod.input<typeof VideoTask>;
+export type VideoTaskOutput = zod.output<typeof VideoTask>;

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

@@ -0,0 +1,64 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+import { VideoUsage } from "./videoUsage.zod.js";
+export const VideoTask = zod.strictObject({
+    id: zod.string(),
+    object: zod.string(),
+    status: zod.enum(["queued", "in_progress", "completed", "failed"]),
+    model: zod.string().optional(),
+    usage: VideoUsage.optional(),
+    seconds: zod
+        .string()
+        .optional()
+        .describe("Output duration, not the duration of input references."),
+    size: zod.string().optional(),
+    created_at: zod.int().optional(),
+    completed_at: zod.int().optional(),
+    expires_at: zod.int().optional(),
+    progress: zod.int().optional(),
+    error: zod
+        .strictObject({
+        code: zod.string().optional(),
+        message: zod.string().optional(),
+    })
+        .optional(),
+});

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

@@ -0,0 +1,54 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+export declare const videoUsageSecondsMin = 0;
+export declare const videoUsageInputSecondsMin = 0;
+export declare const videoUsageOutputSecondsMin = 0;
+export declare const videoUsageBillableSecondsMin = 0;
+export declare const VideoUsage: zod.ZodObject<{
+    seconds: zod.ZodOptional<zod.ZodNumber>;
+    resolution: zod.ZodOptional<zod.ZodString>;
+    input_seconds: zod.ZodOptional<zod.ZodNumber>;
+    output_seconds: zod.ZodOptional<zod.ZodNumber>;
+    billable_seconds: zod.ZodOptional<zod.ZodNumber>;
+}, zod.z.core.$strict>;
+export type VideoUsage = zod.input<typeof VideoUsage>;
+export type VideoUsageOutput = zod.output<typeof VideoUsage>;

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

@@ -0,0 +1,62 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * 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:
+ *
+ * - 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.
+ *
+ * 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.
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * 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 serves the same endpoints.
+ *
+ * ## Conventions
+ *
+ * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
+ * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
+ * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
+ * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
+ * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
+ * - **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 * as zod from "zod";
+export const videoUsageSecondsMin = 0;
+export const videoUsageInputSecondsMin = 0;
+export const videoUsageOutputSecondsMin = 0;
+export const videoUsageBillableSecondsMin = 0;
+export const VideoUsage = zod
+    .strictObject({
+    seconds: zod
+        .number()
+        .min(videoUsageSecondsMin)
+        .optional()
+        .describe("Output duration, kept for compatibility."),
+    resolution: zod.string().optional(),
+    input_seconds: zod.number().min(videoUsageInputSecondsMin).optional(),
+    output_seconds: zod.number().min(videoUsageOutputSecondsMin).optional(),
+    billable_seconds: zod
+        .number()
+        .min(videoUsageBillableSecondsMin)
+        .optional()
+        .describe("Total measured input and output video duration, not a monetary quote."),
+})
+    .describe("Provider measurements on a task; only completed tasks are settled.");

package/dist/compute/v2/generated/models.d.ts

@@ -2146,7 +2146,7 @@ export interface CreateSecurityGroupRuleRequestBody {
     /** The last port, or the ICMP code (0–255) when the protocol is ICMP. */
     port_range_max?: number;
     /**
-     * A CIDR of the rule's IP version. Every address when omitted.
+     * An IP address or CIDR block of the rule's IP version. A single address admits only itself, and a block is recorded with its host bits cleared. Every address when omitted.
      * @maxLength 64
      */
     remote_cidr?: string;

package/dist/compute/v2/generated/validators/createSecurityGroupRuleRequestBody.zod.js

@@ -57,6 +57,6 @@ export const CreateSecurityGroupRuleRequestBody = zod.strictObject({
         .string()
         .max(createSecurityGroupRuleRequestBodyRemoteCidrMax)
         .optional()
-        .describe("A CIDR of the rule's IP version. Every address when omitted."),
+        .describe("An IP address or CIDR block of the rule's IP version. A single address admits only itself, and a block is recorded with its host bits cleared. Every address when omitted."),
     description: zod.string().max(createSecurityGroupRuleRequestBodyDescriptionMax).optional(),
 });

package/dist/proto/leaflow/fleet/virtualdesktop/datatransfer/v1/datatransfer_pb.d.ts

@@ -229,9 +229,10 @@ export type ClipboardFormatList = Message<"leaflow.fleet.virtualdesktop.datatran
      */
     items: DataTransferItem[];
     /**
-     * Files copied. The receiver fetches them as for any offer, with
-     * FileTransferRequest.clipboard set, and puts verified local copies on its
-     * clipboard; paths of the source never travel.
+     * 文件复制的首个独立文件操作。接收方按需取得正文，设置
+     * FileTransferRequest.clipboard，并仅发布本机引用，不传来源机器的路径。
+     * 该操作的完成、跳过或取消不结束复制声明；同一有效 sequence 的后续
+     * 粘贴通过 DataRequest.files 取得新的操作，不复用已结算的 transfer_id。
      *
      * @generated from field: leaflow.fleet.filetransfer.v1.FileTransferOffer file_offer = 5;
      */
@@ -982,8 +983,12 @@ export type DataRequest = Message<"leaflow.fleet.virtualdesktop.datatransfer.v1.
         case: "mimeType";
     } | {
         /**
-         * The offer of the dragged files, of a drag that announced
-         * files_available. Must be true.
+         * 必须为 true。拖放读取已声明 files_available 的来源；剪贴板读取
+         * 原 ClipboardFormatList.file_offer 对应的同一复制声明。
+         * 剪贴板每次成功读取均返回新的 transfer_id，保留原清单的 file_id、
+         * parent_id、元数据与来源文件版本，不重新扫描目录或换用当前的新复制。
+         * 读取仍检查方向权限和连接代际；复制已被替换时返回 ABORTED。
+         * 已接受的文件引用可独立完成；本次文件操作不能撤销其它读取或复制声明。
          *
          * @generated from field: bool files = 4;
          */

package/dist/routes.d.ts

@@ -1599,6 +1599,30 @@ export declare const routes: readonly [{
     readonly operationId: "get-statement-usage";
     readonly securityScheme: "AccessToken";
     readonly upstreamUrl: "https://billing.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy";
+    readonly method: "POST";
+    readonly path: "/v1/videos";
+    readonly operationId: "create-video";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy";
+    readonly method: "GET";
+    readonly path: "/v1/videos/{video}";
+    readonly operationId: "get-video";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
+}, {
+    readonly service: "canopy";
+    readonly contract: "canopy";
+    readonly method: "GET";
+    readonly path: "/v1/videos/{video}/content";
+    readonly operationId: "get-video-content";
+    readonly securityScheme: "ScopedToken";
+    readonly upstreamUrl: "https://canopy.leaflow.cloud";
 }, {
     readonly service: "canopy";
     readonly contract: "canopy";

package/dist/routes.js

@@ -1801,6 +1801,33 @@ export const routes = [
         securityScheme: "AccessToken",
         upstreamUrl: "https://billing.leaflow.cloud",
     },
+    {
+        service: "canopy",
+        contract: "canopy",
+        method: "POST",
+        path: "/v1/videos",
+        operationId: "create-video",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
+    {
+        service: "canopy",
+        contract: "canopy",
+        method: "GET",
+        path: "/v1/videos/{video}",
+        operationId: "get-video",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
+    {
+        service: "canopy",
+        contract: "canopy",
+        method: "GET",
+        path: "/v1/videos/{video}/content",
+        operationId: "get-video-content",
+        securityScheme: "ScopedToken",
+        upstreamUrl: "https://canopy.leaflow.cloud",
+    },
     {
         service: "canopy",
         contract: "canopy",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.0.0-dev.516.g28eeab9",
+  "version": "0.0.0-dev.523.gcaeef48",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {