@leaflow/sdk 0.0.0-dev.377.gdbef936 → 0.0.0-dev.381.g84c72f5

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

@@ -1,64 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const Plan: zod.ZodObject<{
-    active: zod.ZodBoolean;
-    lookup_key: zod.ZodOptional<zod.ZodString>;
-    product: zod.ZodObject<{
-        id: zod.ZodString;
-        name: zod.ZodString;
-        description: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>;
-    features: zod.ZodArray<zod.ZodObject<{
-        feature: zod.ZodObject<{
-            lookup_key: zod.ZodOptional<zod.ZodString>;
-            id: zod.ZodUUID;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    id: zod.ZodUUID;
-    product_id: zod.ZodString;
-    name: zod.ZodString;
-    description: zod.ZodOptional<zod.ZodString>;
-}, zod.z.core.$strict>;
-export type Plan = zod.input<typeof Plan>;
-export type PlanOutput = zod.output<typeof Plan>;

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

@@ -1,56 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { PlanFeature } from "./planFeature.zod.js";
-import { Product } from "./product.zod.js";
-import { ProductID } from "./productID.zod.js";
-export const Plan = zod.strictObject({
-    active: zod
-        .boolean()
-        .describe("False once archived. An archived plan cannot be bought until it is active again."),
-    lookup_key: zod.string().optional(),
-    product: Product,
-    features: zod.array(PlanFeature),
-    id: zod.uuid(),
-    product_id: ProductID,
-    name: zod.string(),
-    description: zod.string().optional(),
-});

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

@@ -1,51 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const PlanFeature: zod.ZodObject<{
-    feature: zod.ZodObject<{
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>;
-    name: zod.ZodString;
-}, zod.z.core.$strict>;
-export type PlanFeature = zod.input<typeof PlanFeature>;
-export type PlanFeatureOutput = zod.output<typeof PlanFeature>;

package/dist/canopy/v1/generated/validators/planFeature.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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { ObjectIdentity } from "./objectIdentity.zod.js";
-export const PlanFeature = zod.strictObject({
-    feature: ObjectIdentity,
-    name: zod.string(),
-});

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

@@ -1,71 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const PlanList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        active: zod.ZodBoolean;
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        product: zod.ZodObject<{
-            id: zod.ZodString;
-            name: zod.ZodString;
-            description: zod.ZodOptional<zod.ZodString>;
-        }, zod.z.core.$strict>;
-        features: zod.ZodArray<zod.ZodObject<{
-            feature: zod.ZodObject<{
-                lookup_key: zod.ZodOptional<zod.ZodString>;
-                id: zod.ZodUUID;
-                name: zod.ZodString;
-            }, zod.z.core.$strict>;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>>;
-        id: zod.ZodUUID;
-        product_id: zod.ZodString;
-        name: zod.ZodString;
-        description: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>>;
-    pagination: zod.ZodObject<{
-        page: zod.ZodInt;
-        page_size: zod.ZodInt;
-        total_count: zod.ZodOptional<zod.ZodInt>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type PlanList = zod.input<typeof PlanList>;
-export type PlanListOutput = zod.output<typeof PlanList>;

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

@@ -1,47 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { OffsetPagination } from "./offsetPagination.zod.js";
-import { Plan } from "./plan.zod.js";
-export const PlanList = zod.strictObject({
-    items: zod.array(Plan),
-    pagination: OffsetPagination,
-});

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

@@ -1,119 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export declare const Price: zod.ZodObject<{
-    rate_card: zod.ZodOptional<zod.ZodObject<{
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    lookup_key: zod.ZodOptional<zod.ZodString>;
-    product: zod.ZodObject<{
-        id: zod.ZodString;
-        name: zod.ZodString;
-        description: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>;
-    plan: zod.ZodObject<{
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>;
-    meter_id: zod.ZodOptional<zod.ZodUUID>;
-    meter: zod.ZodOptional<zod.ZodObject<{
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    unit_quantity: zod.ZodString;
-    active: zod.ZodBoolean;
-    cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-        immediate: "immediate";
-        period_end: "period_end";
-    }>>;
-    refund_policy: zod.ZodOptional<zod.ZodEnum<{
-        none: "none";
-        prorated: "prorated";
-        short_rate: "short_rate";
-    }>>;
-    short_rate_multiplier: zod.ZodOptional<zod.ZodString>;
-    short_rate_threshold_seconds: zod.ZodOptional<zod.ZodInt>;
-    product_id: zod.ZodOptional<zod.ZodString>;
-    id: zod.ZodUUID;
-    plan_id: zod.ZodUUID;
-    currency: zod.ZodString;
-    type: zod.ZodEnum<{
-        one_time: "one_time";
-        recurring: "recurring";
-    }>;
-    usage_type: zod.ZodEnum<{
-        licensed: "licensed";
-        metered: "metered";
-    }>;
-    billing_scheme: zod.ZodOptional<zod.ZodEnum<{
-        per_unit: "per_unit";
-        tiered: "tiered";
-    }>>;
-    unit_amount: zod.ZodOptional<zod.ZodString>;
-    tiers_mode: zod.ZodOptional<zod.ZodEnum<{
-        none: "none";
-        graduated: "graduated";
-        volume: "volume";
-    }>>;
-    tiers: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-        up_to: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-        unit_amount: zod.ZodString;
-        flat_amount: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>>>;
-    rate_card_id: zod.ZodOptional<zod.ZodUUID>;
-    min_quantity: zod.ZodOptional<zod.ZodString>;
-    max_quantity: zod.ZodOptional<zod.ZodString>;
-    quantity_step: zod.ZodOptional<zod.ZodString>;
-    interval_count: zod.ZodOptional<zod.ZodInt>;
-    interval: zod.ZodEnum<{
-        none: "none";
-        day: "day";
-        month: "month";
-        year: "year";
-    }>;
-    setup_fee: zod.ZodOptional<zod.ZodString>;
-}, zod.z.core.$strict>;
-export type Price = zod.input<typeof Price>;
-export type PriceOutput = zod.output<typeof Price>;

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

@@ -1,111 +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 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.
- *
- * 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 stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-import { BillingScheme } from "./billingScheme.zod.js";
-import { CancellationPolicy } from "./cancellationPolicy.zod.js";
-import { Money } from "./money.zod.js";
-import { ObjectIdentity } from "./objectIdentity.zod.js";
-import { PriceType } from "./priceType.zod.js";
-import { Product } from "./product.zod.js";
-import { ProductID } from "./productID.zod.js";
-import { RefundPolicy } from "./refundPolicy.zod.js";
-import { Tier } from "./tier.zod.js";
-import { UsageType } from "./usageType.zod.js";
-export const Price = zod.strictObject({
-    rate_card: ObjectIdentity.optional(),
-    lookup_key: zod.string().optional(),
-    product: Product,
-    plan: ObjectIdentity,
-    meter_id: zod
-        .uuid()
-        .optional()
-        .describe("For a metered price with its own amounts, the meter it charges. For a licensed price, the meter its quantity is held on. Absent otherwise."),
-    meter: ObjectIdentity.optional(),
-    unit_quantity: zod.string(),
-    active: zod
-        .boolean()
-        .describe("False once archived. An archived price cannot be bought until it is active again."),
-    cancellation_policy: CancellationPolicy.optional(),
-    refund_policy: RefundPolicy.optional(),
-    short_rate_multiplier: zod
-        .string()
-        .optional()
-        .describe("Refund policy `short_rate` only, the factor applied to the value of the time used when a cancellation takes effect less than `short_rate_threshold_seconds` after the period start."),
-    short_rate_threshold_seconds: zod
-        .int()
-        .optional()
-        .describe("Refund policy `short_rate` only, how long after the period start `short_rate_multiplier` applies."),
-    product_id: ProductID.optional(),
-    id: zod.uuid(),
-    plan_id: zod.uuid(),
-    currency: zod.string(),
-    type: PriceType,
-    usage_type: UsageType,
-    billing_scheme: BillingScheme.optional().describe("Absent when the price delegates to a rate card, where the rate depends on attributes such as region or machine type."),
-    unit_amount: Money.optional().describe("Present for `per_unit`."),
-    tiers_mode: zod
-        .enum(["none", "graduated", "volume"])
-        .optional()
-        .describe("How a ladder is walked: `graduated` charges each band at its own rate, `volume` charges everything at the rate of the band the total falls in. `none` when not tiered."),
-    tiers: zod.array(Tier).optional().describe("Present for `tiered`, in ascending order."),
-    rate_card_id: zod
-        .uuid()
-        .optional()
-        .describe("Present when the price delegates to a rate card, the price list its rates are read from."),
-    min_quantity: zod
-        .string()
-        .optional()
-        .describe("The smallest quantity that can be bought. Absent means no lower bound."),
-    max_quantity: zod
-        .string()
-        .optional()
-        .describe("The largest quantity that may be bought; absent when there is no limit. A larger quantity is refused with `BILLING_PRICE_INVALID` and `field` `max_quantity`."),
-    quantity_step: zod
-        .string()
-        .optional()
-        .describe("Quantities must be a multiple of this. Absent means any quantity within the bounds."),
-    interval_count: zod
-        .int()
-        .optional()
-        .describe("For recurring licensed prices, how many interval units one period covers."),
-    interval: zod.enum(["none", "day", "month", "year"]),
-    setup_fee: Money.optional(),
-});