@leaflow/sdk 0.0.0-dev.375.gbce4ffc → 0.0.0-dev.379.g796e6e7

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

@@ -1,89 +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 RateList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        meter: zod.ZodObject<{
-            lookup_key: zod.ZodOptional<zod.ZodString>;
-            id: zod.ZodUUID;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>;
-        unit: zod.ZodOptional<zod.ZodString>;
-        dimensions: zod.ZodRecord<zod.ZodString, zod.ZodString>;
-        billing_scheme: zod.ZodEnum<{
-            per_unit: "per_unit";
-            tiered: "tiered";
-        }>;
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        interval: zod.ZodEnum<{
-            none: "none";
-            day: "day";
-            month: "month";
-            year: "year";
-        }>;
-        interval_count: zod.ZodOptional<zod.ZodNullable<zod.ZodInt>>;
-        tiers_mode: zod.ZodEnum<{
-            none: "none";
-            graduated: "graduated";
-            volume: "volume";
-        }>;
-        unit_amount: zod.ZodOptional<zod.ZodString>;
-        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>>>;
-        unit_quantity: zod.ZodOptional<zod.ZodString>;
-        currency: zod.ZodString;
-        effective_from: zod.z.ZodISODateTime;
-        effective_to: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    }, 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 RateList = zod.input<typeof RateList>;
-export type RateListOutput = zod.output<typeof RateList>;

package/dist/canopy/v1/generated/validators/rateList.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 { Rate } from "./rate.zod.js";
-export const RateList = zod.strictObject({
-    items: zod.array(Rate),
-    pagination: OffsetPagination,
-});

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

@@ -1,126 +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 Refund: zod.ZodObject<{
-    transaction_id: zod.ZodOptional<zod.ZodUUID>;
-    cancellation_item_id: zod.ZodOptional<zod.ZodUUID>;
-    transactions: zod.ZodArray<zod.ZodObject<{
-        invoice_id: zod.ZodOptional<zod.ZodUUID>;
-        transaction_id: zod.ZodOptional<zod.ZodUUID>;
-        credit_grant_id: zod.ZodOptional<zod.ZodUUID>;
-        credit_grant: zod.ZodOptional<zod.ZodObject<{
-            lookup_key: zod.ZodOptional<zod.ZodString>;
-            id: zod.ZodUUID;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>>;
-        refund_id: zod.ZodOptional<zod.ZodUUID>;
-        refund_destination: zod.ZodOptional<zod.ZodEnum<{
-            balance: "balance";
-            credit: "credit";
-            gateway: "gateway";
-        }>>;
-        status: zod.ZodOptional<zod.ZodEnum<{
-            failed: "failed";
-            pending: "pending";
-            canceled: "canceled";
-            succeeded: "succeeded";
-        }>>;
-        cancellation_reason: zod.ZodOptional<zod.ZodEnum<{
-            abandoned: "abandoned";
-            requested_by_customer: "requested_by_customer";
-        }>>;
-        payment_gateway: zod.ZodOptional<zod.ZodString>;
-        method_type: zod.ZodOptional<zod.ZodString>;
-        failure_reason: zod.ZodOptional<zod.ZodString>;
-        settled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-        id: zod.ZodUUID;
-        billing_account_id: zod.ZodOptional<zod.ZodInt>;
-        type: zod.ZodEnum<{
-            topup: "topup";
-            payment: "payment";
-            refund: "refund";
-            adjustment: "adjustment";
-            fee: "fee";
-        }>;
-        amount: zod.ZodString;
-        remaining_amount: zod.ZodString;
-        currency: zod.ZodString;
-        reason: zod.ZodOptional<zod.ZodString>;
-        created_at: zod.z.ZodISODateTime;
-    }, zod.z.core.$strict>>;
-    id: zod.ZodUUID;
-    billing_account_id: zod.ZodOptional<zod.ZodInt>;
-    invoice_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-    order_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-    amount: zod.ZodString;
-    balance_amount: zod.ZodString;
-    credit_amount: zod.ZodString;
-    gateway_amount: zod.ZodString;
-    settled_amount: zod.ZodOptional<zod.ZodString>;
-    currency: zod.ZodString;
-    destination: zod.ZodOptional<zod.ZodEnum<{
-        balance: "balance";
-        gateway: "gateway";
-    }>>;
-    status: zod.ZodEnum<{
-        failed: "failed";
-        pending: "pending";
-        succeeded: "succeeded";
-        processing: "processing";
-    }>;
-    settled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    reason: zod.ZodEnum<{
-        operator: "operator";
-        provisioning_failed: "provisioning_failed";
-        order_expired: "order_expired";
-        order_canceled: "order_canceled";
-        change_canceled: "change_canceled";
-        change_expired: "change_expired";
-        subscription_canceled: "subscription_canceled";
-        usage_true_up: "usage_true_up";
-        future_period_canceled: "future_period_canceled";
-        downgrade_difference: "downgrade_difference";
-        payment_not_applied: "payment_not_applied";
-    }>;
-    created_at: zod.z.ZodISODateTime;
-}, zod.z.core.$strict>;
-export type Refund = zod.input<typeof Refund>;
-export type RefundOutput = zod.output<typeof Refund>;

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

@@ -1,77 +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 { Money } from "./money.zod.js";
-import { RefundReason } from "./refundReason.zod.js";
-import { Transaction } from "./transaction.zod.js";
-export const Refund = zod.strictObject({
-    transaction_id: zod.uuid().optional(),
-    cancellation_item_id: zod.uuid().optional(),
-    transactions: zod
-        .array(Transaction)
-        .describe("The refund split by original payment source, with each result. Unknown gateway results stay pending."),
-    id: zod.uuid(),
-    billing_account_id: zod.int().optional(),
-    invoice_id: zod.uuid().nullish(),
-    order_id: zod
-        .uuid()
-        .nullish()
-        .describe("The order the refund belongs to: the order that caused it, such as a downgrade, otherwise the order of the refunded invoice. Null for refunds of top-ups and usage invoices."),
-    amount: Money.describe("The whole refund. Equals balance_amount plus credit_amount plus gateway_amount."),
-    balance_amount: Money.describe("The part returned to the account balance."),
-    credit_amount: Money.describe("The part restored to the credit grants that paid for it."),
-    gateway_amount: Money.describe("The part returned to the payment method it was paid with."),
-    settled_amount: Money.optional().describe("What has actually been returned."),
-    currency: zod.string(),
-    destination: zod
-        .enum(["balance", "gateway"])
-        .optional()
-        .describe("Use balance_amount, credit_amount and gateway_amount, which also show a refund split between destinations."),
-    status: zod
-        .enum(["pending", "processing", "succeeded", "failed"])
-        .describe("Summary of the parts in `transactions`.\n\n- `pending`: nothing has been returned yet, and at least one part is in progress.\n- `processing`: some parts have been returned, and at least one is still in progress.\n- `succeeded`: every part has been returned.\n- `failed`: no part is in progress and at least one has failed. What was returned is in\n  settled_amount.\n\nReturns to the balance and to credit grants complete shortly after the refund is made; a\nreturn to a payment method completes when the gateway confirms it."),
-    settled_at: zod.iso
-        .datetime({ offset: true })
-        .optional()
-        .describe("When the last part was returned. Present with `succeeded`."),
-    reason: RefundReason,
-    created_at: zod.iso.datetime({ offset: true }),
-});

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

@@ -1,133 +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 RefundList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        transaction_id: zod.ZodOptional<zod.ZodUUID>;
-        cancellation_item_id: zod.ZodOptional<zod.ZodUUID>;
-        transactions: zod.ZodArray<zod.ZodObject<{
-            invoice_id: zod.ZodOptional<zod.ZodUUID>;
-            transaction_id: zod.ZodOptional<zod.ZodUUID>;
-            credit_grant_id: zod.ZodOptional<zod.ZodUUID>;
-            credit_grant: zod.ZodOptional<zod.ZodObject<{
-                lookup_key: zod.ZodOptional<zod.ZodString>;
-                id: zod.ZodUUID;
-                name: zod.ZodString;
-            }, zod.z.core.$strict>>;
-            refund_id: zod.ZodOptional<zod.ZodUUID>;
-            refund_destination: zod.ZodOptional<zod.ZodEnum<{
-                balance: "balance";
-                credit: "credit";
-                gateway: "gateway";
-            }>>;
-            status: zod.ZodOptional<zod.ZodEnum<{
-                failed: "failed";
-                pending: "pending";
-                canceled: "canceled";
-                succeeded: "succeeded";
-            }>>;
-            cancellation_reason: zod.ZodOptional<zod.ZodEnum<{
-                abandoned: "abandoned";
-                requested_by_customer: "requested_by_customer";
-            }>>;
-            payment_gateway: zod.ZodOptional<zod.ZodString>;
-            method_type: zod.ZodOptional<zod.ZodString>;
-            failure_reason: zod.ZodOptional<zod.ZodString>;
-            settled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-            id: zod.ZodUUID;
-            billing_account_id: zod.ZodOptional<zod.ZodInt>;
-            type: zod.ZodEnum<{
-                topup: "topup";
-                payment: "payment";
-                refund: "refund";
-                adjustment: "adjustment";
-                fee: "fee";
-            }>;
-            amount: zod.ZodString;
-            remaining_amount: zod.ZodString;
-            currency: zod.ZodString;
-            reason: zod.ZodOptional<zod.ZodString>;
-            created_at: zod.z.ZodISODateTime;
-        }, zod.z.core.$strict>>;
-        id: zod.ZodUUID;
-        billing_account_id: zod.ZodOptional<zod.ZodInt>;
-        invoice_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-        order_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-        amount: zod.ZodString;
-        balance_amount: zod.ZodString;
-        credit_amount: zod.ZodString;
-        gateway_amount: zod.ZodString;
-        settled_amount: zod.ZodOptional<zod.ZodString>;
-        currency: zod.ZodString;
-        destination: zod.ZodOptional<zod.ZodEnum<{
-            balance: "balance";
-            gateway: "gateway";
-        }>>;
-        status: zod.ZodEnum<{
-            failed: "failed";
-            pending: "pending";
-            succeeded: "succeeded";
-            processing: "processing";
-        }>;
-        settled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-        reason: zod.ZodEnum<{
-            operator: "operator";
-            provisioning_failed: "provisioning_failed";
-            order_expired: "order_expired";
-            order_canceled: "order_canceled";
-            change_canceled: "change_canceled";
-            change_expired: "change_expired";
-            subscription_canceled: "subscription_canceled";
-            usage_true_up: "usage_true_up";
-            future_period_canceled: "future_period_canceled";
-            downgrade_difference: "downgrade_difference";
-            payment_not_applied: "payment_not_applied";
-        }>;
-        created_at: zod.z.ZodISODateTime;
-    }, 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 RefundList = zod.input<typeof RefundList>;
-export type RefundListOutput = zod.output<typeof RefundList>;

package/dist/canopy/v1/generated/validators/refundList.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 { Refund } from "./refund.zod.js";
-export const RefundList = zod.strictObject({
-    items: zod.array(Refund),
-    pagination: OffsetPagination,
-});

package/dist/canopy/v1/generated/validators/refundPolicy.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 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 RefundPolicy: zod.ZodEnum<{
-    none: "none";
-    prorated: "prorated";
-    short_rate: "short_rate";
-}>;
-export type RefundPolicy = zod.input<typeof RefundPolicy>;
-export type RefundPolicyOutput = zod.output<typeof RefundPolicy>;

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

@@ -1,44 +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 RefundPolicy = zod
-    .enum(["none", "prorated", "short_rate"])
-    .describe("`none` refunds nothing.\n\n`prorated` refunds the amount paid for the current period minus the value of the time used, never below zero\nor above what remains unrefunded. Time used runs from the period start to the effective cancellation, by the\nsecond. Each whole month from the period start is valued at the order item's `monthly_list_amount`, and the\nremainder at that amount in proportion to the length of the month it falls in; without `monthly_list_amount`,\ntime used is valued at the amount paid in proportion to the length of the period. A renewal starts a new\nperiod, and an immediate change starts one at the change. Discounts and setup fees are not refunded. Refunds\nreturn to the original payment sources, with tax refunded in proportion.\n\n`short_rate` refunds as `prorated`, except that when the cancellation takes effect less than\n`short_rate_threshold_seconds` after the period start, the value of the time used is multiplied by\n`short_rate_multiplier`, up to `monthly_list_amount` for each month begun or, without `monthly_list_amount`,\nup to the amount paid.");