@leaflow/sdk 0.0.0-dev.377.gdbef936 → 0.0.0-dev.379.g796e6e7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.0.0-dev.377.gdbef936",
+  "version": "0.0.0-dev.379.g796e6e7",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {

package/dist/billing/v1/generated/validators/orderRefundQuoteInput.zod.js

@@ -1,20 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Financial operations require an account access token and billing-account authorization. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-export const orderRefundQuoteInputOrderItemIdsMax = 100;
-export const OrderRefundQuoteInput = zod
-    .strictObject({
-    order_id: zod.uuid(),
-    order_item_ids: zod
-        .array(zod.uuid())
-        .min(1)
-        .max(orderRefundQuoteInputOrderItemIdsMax)
-        .optional()
-        .describe("Estimate only these items. Omit to estimate the whole order. Every item must belong to the order."),
-})
-    .describe("An estimate of the refundable value of an order or selected items; nothing is canceled or refunded.");

package/dist/billing/v1/generated/validators/quoteCancellation.zod.js

@@ -1,20 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Billing API
- * Products, prices, orders, subscriptions and account billing. Financial operations require an account access token and billing-account authorization. Public catalogue operations declare no security requirement.
- * OpenAPI spec version: v1
- */
-import * as zod from "zod";
-import { CancellationPolicy } from "./cancellationPolicy.zod.js";
-export const quoteCancellationSubscriptionIdsMax = 50;
-export const QuoteCancellation = zod
-    .strictObject({
-    subscription_ids: zod
-        .array(zod.uuid())
-        .min(1)
-        .max(quoteCancellationSubscriptionIdsMax)
-        .describe("The subscriptions to end together, all of one service, including every subscription released with a resource."),
-    mode: CancellationPolicy,
-})
-    .describe("A cancellation to quote: what ending these subscriptions together would return, for one mode; quote `immediate` and `period_end` separately to compare. Refused with 409 `BILLING_SUBSCRIPTION_OPERATION_PENDING` when a subscription is already being canceled (`meta.cancellation_id`), is being reclaimed (`meta.reason` `reclaim_requested`) or has a paid change waiting to switch (`meta.order_id`).");

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

@@ -1,168 +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 AccountBalance: zod.ZodObject<{
-    available_credit: zod.ZodString;
-    estimated_credit_applied: zod.ZodString;
-    unbilled_amount: zod.ZodString;
-    billing_account_id: zod.ZodInt;
-    currency: zod.ZodString;
-    balance: zod.ZodString;
-    credits: zod.ZodString;
-    restricted_credits: zod.ZodString;
-    credit_groups: zod.ZodArray<zod.ZodObject<{
-        applies_to: zod.ZodObject<{
-            products: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-                id: zod.ZodString;
-                name: zod.ZodString;
-                description: zod.ZodOptional<zod.ZodString>;
-            }, zod.z.core.$strict>>>;
-            plans: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-                id: zod.ZodUUID;
-                name: zod.ZodString;
-                active: zod.ZodBoolean;
-            }, zod.z.core.$strict>>>;
-            prices: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-                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>;
-                billing_scheme: zod.ZodOptional<zod.ZodEnum<{
-                    per_unit: "per_unit";
-                    tiered: "tiered";
-                }>>;
-                unit_quantity: zod.ZodString;
-                id: zod.ZodUUID;
-                currency: zod.ZodString;
-                type: zod.ZodEnum<{
-                    one_time: "one_time";
-                    recurring: "recurring";
-                }>;
-                usage_type: zod.ZodEnum<{
-                    licensed: "licensed";
-                    metered: "metered";
-                }>;
-                interval: zod.ZodEnum<{
-                    none: "none";
-                    day: "day";
-                    month: "month";
-                    year: "year";
-                }>;
-                interval_count: zod.ZodOptional<zod.ZodInt>;
-                unit_amount: zod.ZodOptional<zod.ZodString>;
-                active: zod.ZodBoolean;
-            }, zod.z.core.$strict>>>;
-            price_types: zod.ZodOptional<zod.ZodArray<zod.ZodEnum<{
-                one_time: "one_time";
-                recurring: "recurring";
-            }>>>;
-            usage_types: zod.ZodOptional<zod.ZodArray<zod.ZodEnum<{
-                licensed: "licensed";
-                metered: "metered";
-            }>>>;
-            operations: zod.ZodOptional<zod.ZodArray<zod.ZodEnum<{
-                new: "new";
-                renew: "renew";
-                modify: "modify";
-            }>>>;
-            min_term_months: zod.ZodOptional<zod.ZodInt>;
-            max_term_months: zod.ZodOptional<zod.ZodInt>;
-            excluded_products: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-                id: zod.ZodString;
-                name: zod.ZodString;
-                description: zod.ZodOptional<zod.ZodString>;
-            }, zod.z.core.$strict>>>;
-            excluded_plans: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-                id: zod.ZodUUID;
-                name: zod.ZodString;
-                active: zod.ZodBoolean;
-            }, zod.z.core.$strict>>>;
-            excluded_prices: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-                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>;
-                billing_scheme: zod.ZodOptional<zod.ZodEnum<{
-                    per_unit: "per_unit";
-                    tiered: "tiered";
-                }>>;
-                unit_quantity: zod.ZodString;
-                id: zod.ZodUUID;
-                currency: zod.ZodString;
-                type: zod.ZodEnum<{
-                    one_time: "one_time";
-                    recurring: "recurring";
-                }>;
-                usage_type: zod.ZodEnum<{
-                    licensed: "licensed";
-                    metered: "metered";
-                }>;
-                interval: zod.ZodEnum<{
-                    none: "none";
-                    day: "day";
-                    month: "month";
-                    year: "year";
-                }>;
-                interval_count: zod.ZodOptional<zod.ZodInt>;
-                unit_amount: zod.ZodOptional<zod.ZodString>;
-                active: zod.ZodBoolean;
-            }, zod.z.core.$strict>>>;
-        }, zod.z.core.$strict>;
-        first_purchase_only: zod.ZodOptional<zod.ZodBoolean>;
-        amount: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    due: zod.ZodString;
-    pending_returns_amount: zod.ZodString;
-}, zod.z.core.$strict>;
-export type AccountBalance = zod.input<typeof AccountBalance>;
-export type AccountBalanceOutput = zod.output<typeof AccountBalance>;

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

@@ -1,60 +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 { CreditGroup } from "./creditGroup.zod.js";
-import { Money } from "./money.zod.js";
-export const AccountBalance = zod
-    .strictObject({
-    available_credit: Money.describe("Balance minus pending balance returns and the part of unbilled_amount and due that estimated_credit_applied does not cover. Negative only when the balance and applicable credit fall short of what the account owes."),
-    estimated_credit_applied: Money.describe("Credit expected to pay unbilled_amount and due, matching each charge to the grants whose scope, validity and conditions it meets, in the order credit is applied at payment. Nothing is deducted until an invoice is paid, so credits still includes this amount."),
-    unbilled_amount: Money.describe("Current estimate of priced usage that has not been invoiced. Final pricing and tax are fixed at issuance."),
-    billing_account_id: zod.int(),
-    currency: zod.string(),
-    balance: Money.describe("Topped-up funds in the account's currency, excluding credits. May be negative after a payment dispute. Amounts owed are reported in due; this is not a withdrawable amount."),
-    credits: Money.describe("Remaining credit, including restricted grants; not withdrawable and not part of balance. credit_groups shows currently valid credit by permitted use; positive credits do not mean due is zero."),
-    restricted_credits: Money.describe("Currently valid credit restricted to certain products, operations or conditions; part of credits, not of balance."),
-    credit_groups: zod
-        .array(CreditGroup)
-        .describe("Currently valid unspent credit grouped by permitted use. Each group covers only the charges its restrictions and validity allow, and the groups may differ from the recorded credits total."),
-    due: Money.describe("Amount still payable on issued invoices. The invoice of an order not yet accepted is excluded, here and from available_credit. Usage not yet invoiced is reported separately."),
-    pending_returns_amount: Money,
-})
-    .describe("Balance, credits and unpaid charges, each reported separately.");

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

@@ -1,52 +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 AccountDeletionObjection: zod.ZodEnum<{
-    ARREARS: "ARREARS";
-    PROJECTS_ASSIGNED: "PROJECTS_ASSIGNED";
-    ACTIVE_SUBSCRIPTION: "ACTIVE_SUBSCRIPTION";
-    OPEN_ORDER: "OPEN_ORDER";
-    UNPAID_INVOICE: "UNPAID_INVOICE";
-    UNBILLED_USAGE: "UNBILLED_USAGE";
-    PENDING_TRANSACTION: "PENDING_TRANSACTION";
-}>;
-export type AccountDeletionObjection = zod.input<typeof AccountDeletionObjection>;
-export type AccountDeletionObjectionOutput = zod.output<typeof AccountDeletionObjection>;

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

@@ -1,52 +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 const AccountDeletionObjection = zod
-    .enum([
-    "ARREARS",
-    "PROJECTS_ASSIGNED",
-    "ACTIVE_SUBSCRIPTION",
-    "OPEN_ORDER",
-    "UNPAID_INVOICE",
-    "UNBILLED_USAGE",
-    "PENDING_TRANSACTION",
-])
-    .describe("`ARREARS`: the balance is negative. `PROJECTS_ASSIGNED`: the account still pays for a project, yours or anyone\nelse's. `ACTIVE_SUBSCRIPTION`: a subscription it bought has not ended. `OPEN_ORDER`: an order is not finished.\n`UNPAID_INVOICE`: an issued invoice is not settled. `UNBILLED_USAGE`: usage has not been invoiced yet; it is\ninvoiced in the next billing run. `PENDING_TRANSACTION`: a top-up, refund or withdrawal is still pending.");

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

@@ -1,78 +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 AccountDeletionReadiness: zod.ZodObject<{
-    accounts: zod.ZodArray<zod.ZodObject<{
-        account: zod.ZodObject<{
-            invoice_contact_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-            id: zod.ZodInt;
-            name: zod.ZodOptional<zod.ZodString>;
-            currency: zod.ZodString;
-            status: zod.ZodEnum<{
-                active: "active";
-                suspended: "suspended";
-                closed: "closed";
-            }>;
-            suspended_by: zod.ZodEnum<{
-                none: "none";
-                operator: "operator";
-                owner: "owner";
-            }>;
-            grace_amount: zod.ZodOptional<zod.ZodString>;
-            grace_period_seconds: zod.ZodOptional<zod.ZodInt>;
-            closed_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-            created_at: zod.z.ZodISODateTime;
-        }, zod.z.core.$strict>;
-        balance: zod.ZodString;
-        credits: zod.ZodString;
-        objections: zod.ZodArray<zod.ZodEnum<{
-            ARREARS: "ARREARS";
-            PROJECTS_ASSIGNED: "PROJECTS_ASSIGNED";
-            ACTIVE_SUBSCRIPTION: "ACTIVE_SUBSCRIPTION";
-            OPEN_ORDER: "OPEN_ORDER";
-            UNPAID_INVOICE: "UNPAID_INVOICE";
-            UNBILLED_USAGE: "UNBILLED_USAGE";
-            PENDING_TRANSACTION: "PENDING_TRANSACTION";
-        }>>;
-    }, zod.z.core.$strict>>;
-}, zod.z.core.$strict>;
-export type AccountDeletionReadiness = zod.input<typeof AccountDeletionReadiness>;
-export type AccountDeletionReadinessOutput = zod.output<typeof AccountDeletionReadiness>;

package/dist/canopy/v1/generated/validators/accountDeletionReadiness.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 { AccountDeletionReadinessItem } from "./accountDeletionReadinessItem.zod.js";
-export const AccountDeletionReadiness = zod.strictObject({
-    accounts: zod
-        .array(AccountDeletionReadinessItem)
-        .describe("Every billing account you own that is not closed; empty when you own none."),
-});

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

@@ -1,76 +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 AccountDeletionReadinessItem: zod.ZodObject<{
-    account: zod.ZodObject<{
-        invoice_contact_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-        id: zod.ZodInt;
-        name: zod.ZodOptional<zod.ZodString>;
-        currency: zod.ZodString;
-        status: zod.ZodEnum<{
-            active: "active";
-            suspended: "suspended";
-            closed: "closed";
-        }>;
-        suspended_by: zod.ZodEnum<{
-            none: "none";
-            operator: "operator";
-            owner: "owner";
-        }>;
-        grace_amount: zod.ZodOptional<zod.ZodString>;
-        grace_period_seconds: zod.ZodOptional<zod.ZodInt>;
-        closed_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-        created_at: zod.z.ZodISODateTime;
-    }, zod.z.core.$strict>;
-    balance: zod.ZodString;
-    credits: zod.ZodString;
-    objections: zod.ZodArray<zod.ZodEnum<{
-        ARREARS: "ARREARS";
-        PROJECTS_ASSIGNED: "PROJECTS_ASSIGNED";
-        ACTIVE_SUBSCRIPTION: "ACTIVE_SUBSCRIPTION";
-        OPEN_ORDER: "OPEN_ORDER";
-        UNPAID_INVOICE: "UNPAID_INVOICE";
-        UNBILLED_USAGE: "UNBILLED_USAGE";
-        PENDING_TRANSACTION: "PENDING_TRANSACTION";
-    }>>;
-}, zod.z.core.$strict>;
-export type AccountDeletionReadinessItem = zod.input<typeof AccountDeletionReadinessItem>;
-export type AccountDeletionReadinessItemOutput = zod.output<typeof AccountDeletionReadinessItem>;

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

@@ -1,52 +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 { AccountDeletionObjection } from "./accountDeletionObjection.zod.js";
-import { BillingAccount } from "./billingAccount.zod.js";
-import { Money } from "./money.zod.js";
-export const AccountDeletionReadinessItem = zod.strictObject({
-    account: BillingAccount,
-    balance: Money.describe("Topped-up funds, in the account's currency, forfeited when it closes. Negative means arrears."),
-    credits: Money.describe("Remaining credit, in the account's currency, forfeited when it closes."),
-    objections: zod
-        .array(AccountDeletionObjection)
-        .describe("What stops this account from closing; empty when it can close."),
-});