@leaflow/sdk 0.211.0 → 0.212.0

package/dist/routes.d.ts

@@ -1695,22 +1695,6 @@ export declare const routes: readonly [{
     readonly operationId: "create-response";
     readonly securityScheme: "ScopedToken";
     readonly upstreamUrl: "https://canopy.leaflow.cloud";
-}, {
-    readonly service: "canopy";
-    readonly contract: "canopy";
-    readonly method: "GET";
-    readonly path: "/v1/responses/{response}";
-    readonly operationId: "get-response";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://canopy.leaflow.cloud";
-}, {
-    readonly service: "canopy";
-    readonly contract: "canopy";
-    readonly method: "DELETE";
-    readonly path: "/v1/responses/{response}";
-    readonly operationId: "delete-response";
-    readonly securityScheme: "ScopedToken";
-    readonly upstreamUrl: "https://canopy.leaflow.cloud";
 }, {
     readonly service: "canopy";
     readonly contract: "canopy";

package/dist/routes.js

@@ -1909,24 +1909,6 @@ export const routes = [
         securityScheme: "ScopedToken",
         upstreamUrl: "https://canopy.leaflow.cloud",
     },
-    {
-        service: "canopy",
-        contract: "canopy",
-        method: "GET",
-        path: "/v1/responses/{response}",
-        operationId: "get-response",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://canopy.leaflow.cloud",
-    },
-    {
-        service: "canopy",
-        contract: "canopy",
-        method: "DELETE",
-        path: "/v1/responses/{response}",
-        operationId: "delete-response",
-        securityScheme: "ScopedToken",
-        upstreamUrl: "https://canopy.leaflow.cloud",
-    },
     {
         service: "canopy",
         contract: "canopy",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.211.0",
+  "version": "0.212.0",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {

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

@@ -1,100 +0,0 @@
-/**
- * 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 EndpointCapabilities: zod.ZodObject<{
-    function_calling: zod.ZodNullable<zod.ZodBoolean>;
-    structured_output: zod.ZodNullable<zod.ZodBoolean>;
-    reasoning: zod.ZodUnion<readonly [zod.ZodObject<{
-        supported: zod.ZodBoolean;
-        effort_levels: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        default_effort: zod.ZodNullable<zod.ZodString>;
-        modes: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        budget_tokens: zod.ZodNullable<zod.ZodObject<{
-            min: zod.ZodInt;
-            max: zod.ZodInt;
-        }, zod.z.core.$strict>>;
-        summary: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-    }, zod.z.core.$strict>, zod.ZodNull]>;
-    image: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-        sizes: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        qualities: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        response_formats: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        max_n: zod.ZodNullable<zod.ZodInt>;
-        supports_stream: zod.ZodNullable<zod.ZodBoolean>;
-    }, zod.z.core.$strict>, zod.ZodNull]>>;
-    audio: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-        voices: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        formats: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        response_formats: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        max_input_bytes: zod.ZodNullable<zod.ZodInt>;
-        supports_stream: zod.ZodNullable<zod.ZodBoolean>;
-    }, zod.z.core.$strict>, zod.ZodNull]>>;
-    video: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-        duration_range: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-            min: zod.ZodInt;
-            max: zod.ZodInt;
-            step: zod.ZodInt;
-        }, zod.z.core.$strict>, zod.ZodNull]>>;
-        seconds: zod.ZodNullable<zod.ZodArray<zod.ZodInt>>;
-        sizes: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        resolutions: zod.ZodNullable<zod.ZodArray<zod.ZodString>>;
-        supports_input_reference: zod.ZodNullable<zod.ZodBoolean>;
-        supports_remix: zod.ZodNullable<zod.ZodBoolean>;
-        supports_characters: zod.ZodNullable<zod.ZodBoolean>;
-    }, zod.z.core.$strict>, zod.ZodNull]>>;
-    parameters: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<zod.ZodObject<{
-        name: zod.ZodString;
-        description: zod.ZodString;
-        type: zod.ZodEnum<{
-            string: "string";
-            number: "number";
-            boolean: "boolean";
-            object: "object";
-            array: "array";
-            integer: "integer";
-        }>;
-        required: zod.ZodBoolean;
-        default: zod.ZodOptional<zod.ZodUnknown>;
-        values: zod.ZodOptional<zod.ZodNullable<zod.ZodArray<zod.ZodString>>>;
-    }, zod.z.core.$strict>>>>;
-}, zod.z.core.$strict>;
-export type EndpointCapabilities = zod.input<typeof EndpointCapabilities>;
-export type EndpointCapabilitiesOutput = zod.output<typeof EndpointCapabilities>;

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

@@ -1,67 +0,0 @@
-/**
- * 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 { AudioCapabilities } from "./audioCapabilities.zod.js";
-import { ImageCapabilities } from "./imageCapabilities.zod.js";
-import { ModelParameter } from "./modelParameter.zod.js";
-import { ReasoningCapabilities } from "./reasoningCapabilities.zod.js";
-import { VideoCapabilities } from "./videoCapabilities.zod.js";
-export const EndpointCapabilities = zod.strictObject({
-    function_calling: zod.boolean().nullable(),
-    structured_output: zod.boolean().nullable(),
-    reasoning: zod.union([ReasoningCapabilities, zod.null()]),
-    image: zod
-        .union([ImageCapabilities, zod.null()])
-        .optional()
-        .describe("Present on image generation and edit endpoints. Null or absent elsewhere."),
-    audio: zod
-        .union([AudioCapabilities, zod.null()])
-        .optional()
-        .describe("Present on speech and transcription endpoints. Null or absent elsewhere."),
-    video: zod
-        .union([VideoCapabilities, zod.null()])
-        .optional()
-        .describe("Present on the videos endpoint. Null or absent elsewhere."),
-    parameters: zod
-        .array(ModelParameter)
-        .nullish()
-        .describe("Non-standard request fields this endpoint accepts, sent at the top level of the request body. Null or absent means none are declared."),
-});

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

@@ -1,69 +0,0 @@
-/**
- * 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 ModelEndpoint: zod.ZodEnum<{
-    "/v1/chat/completions": "/v1/chat/completions";
-    "/v1/responses": "/v1/responses";
-    "/v1/embeddings": "/v1/embeddings";
-    "/v1/messages": "/v1/messages";
-    "/v1beta/models/{model}:generateContent": "/v1beta/models/{model}:generateContent";
-    "/v1/images/generations": "/v1/images/generations";
-    "/v1/images/edits": "/v1/images/edits";
-    "/v1/audio/transcriptions": "/v1/audio/transcriptions";
-    "/v1/audio/translations": "/v1/audio/translations";
-    "/v1/audio/speech": "/v1/audio/speech";
-    "/v1/realtime": "/v1/realtime";
-    "/v1/completions": "/v1/completions";
-    "/v1/rerank": "/v1/rerank";
-    "/v1/moderations": "/v1/moderations";
-    "/v1/images/variations": "/v1/images/variations";
-    "/v1/files": "/v1/files";
-    "/v1/uploads": "/v1/uploads";
-    "/v1/batches": "/v1/batches";
-    "/v1/fine_tuning/jobs": "/v1/fine_tuning/jobs";
-    "/v1/assistants": "/v1/assistants";
-    "/v1/threads": "/v1/threads";
-    "/v1/vector_stores": "/v1/vector_stores";
-    "/v1/containers": "/v1/containers";
-    "/v1/videos": "/v1/videos";
-}>;
-export type ModelEndpoint = zod.input<typeof ModelEndpoint>;
-export type ModelEndpointOutput = zod.output<typeof ModelEndpoint>;

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

@@ -1,67 +0,0 @@
-/**
- * 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 ModelEndpoint = zod.enum([
-    "/v1/chat/completions",
-    "/v1/responses",
-    "/v1/embeddings",
-    "/v1/messages",
-    "/v1beta/models/{model}:generateContent",
-    "/v1/images/generations",
-    "/v1/images/edits",
-    "/v1/audio/transcriptions",
-    "/v1/audio/translations",
-    "/v1/audio/speech",
-    "/v1/realtime",
-    "/v1/completions",
-    "/v1/rerank",
-    "/v1/moderations",
-    "/v1/images/variations",
-    "/v1/files",
-    "/v1/uploads",
-    "/v1/batches",
-    "/v1/fine_tuning/jobs",
-    "/v1/assistants",
-    "/v1/threads",
-    "/v1/vector_stores",
-    "/v1/containers",
-    "/v1/videos",
-]);

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

@@ -1,48 +0,0 @@
-/**
- * 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 ResponseDeleted: zod.ZodObject<{
-    id: zod.ZodString;
-    object: zod.ZodString;
-    deleted: zod.ZodBoolean;
-}, zod.z.core.$strict>;
-export type ResponseDeleted = zod.input<typeof ResponseDeleted>;
-export type ResponseDeletedOutput = zod.output<typeof ResponseDeleted>;

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

@@ -1,46 +0,0 @@
-/**
- * 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 ResponseDeleted = zod.strictObject({
-    id: zod.string(),
-    object: zod.string(),
-    deleted: zod.boolean(),
-});