@leaflow/sdk 0.129.1 → 0.130.0

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

@@ -0,0 +1,40 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 withdrawalAllocationAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalAllocationFeeAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalAllocationRefundAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const WithdrawalAllocation = zod.strictObject({
+    source_transaction_id: zod.uuid(),
+    amount: zod.string().regex(withdrawalAllocationAmountRegExp),
+    fee_amount: zod.string().regex(withdrawalAllocationFeeAmountRegExp),
+    refund_amount: zod.string().regex(withdrawalAllocationRefundAmountRegExp),
+});

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

@@ -0,0 +1,48 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 withdrawalCreateAmountRegExp: RegExp;
+export declare const withdrawalCreateExpectedRefundAmountRegExp: RegExp;
+export declare const withdrawalCreateExpectedItemsMax = 200;
+export declare const WithdrawalCreate: zod.ZodObject<{
+    id: zod.ZodUUID;
+    billing_account_id: zod.ZodInt;
+    amount: zod.ZodString;
+    expected_refund_amount: zod.ZodString;
+    expected_items: zod.ZodArray<zod.ZodObject<{
+        source_transaction_id: zod.ZodUUID;
+        amount: zod.ZodString;
+        fee_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type WithdrawalCreate = zod.input<typeof WithdrawalCreate>;
+export type WithdrawalCreateOutput = zod.output<typeof WithdrawalCreate>;

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

@@ -0,0 +1,42 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 { WithdrawalAllocation } from "./withdrawalAllocation.zod.js";
+export const withdrawalCreateAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalCreateExpectedRefundAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalCreateExpectedItemsMax = 200;
+export const WithdrawalCreate = zod.strictObject({
+    id: zod.uuid(),
+    billing_account_id: zod.int(),
+    amount: zod.string().regex(withdrawalCreateAmountRegExp),
+    expected_refund_amount: zod.string().regex(withdrawalCreateExpectedRefundAmountRegExp),
+    expected_items: zod.array(WithdrawalAllocation).min(1).max(withdrawalCreateExpectedItemsMax),
+});

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

@@ -0,0 +1,69 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 withdrawalItemAmountRegExp: RegExp;
+export declare const withdrawalItemFeeAmountRegExp: RegExp;
+export declare const withdrawalItemRefundAmountRegExp: RegExp;
+export declare const withdrawalItemCurrencyMin = 3;
+export declare const withdrawalItemCurrencyMax = 3;
+export declare const WithdrawalItem: zod.ZodObject<{
+    source_transaction_id: zod.ZodUUID;
+    amount: zod.ZodString;
+    fee_amount: zod.ZodString;
+    refund_amount: zod.ZodString;
+    id: zod.ZodUUID;
+    withdrawal_id: zod.ZodUUID;
+    billing_account_id: zod.ZodInt;
+    currency: zod.ZodString;
+    refund_id: zod.ZodUUID;
+    fee_transaction_id: zod.ZodOptional<zod.ZodUUID>;
+    status: zod.ZodEnum<{
+        pending: "pending";
+        failed: "failed";
+        succeeded: "succeeded";
+        reversed: "reversed";
+    }>;
+    completed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+    payment_gateway: zod.ZodString;
+    method_type: zod.ZodString;
+    source: zod.ZodObject<{
+        amount: zod.ZodString;
+        currency: zod.ZodString;
+        received_at: zod.z.ZodISODateTime;
+        payment_gateway: zod.ZodString;
+        method_type: zod.ZodString;
+        card_brand: zod.ZodOptional<zod.ZodString>;
+        card_last4: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>;
+    failure_code: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type WithdrawalItem = zod.input<typeof WithdrawalItem>;
+export type WithdrawalItemOutput = zod.output<typeof WithdrawalItem>;

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

@@ -0,0 +1,60 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 { WithdrawalSource } from "./withdrawalSource.zod.js";
+export const withdrawalItemAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalItemFeeAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalItemRefundAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalItemCurrencyMin = 3;
+export const withdrawalItemCurrencyMax = 3;
+export const WithdrawalItem = zod
+    .strictObject({
+    source_transaction_id: zod.uuid(),
+    amount: zod.string().regex(withdrawalItemAmountRegExp),
+    fee_amount: zod.string().regex(withdrawalItemFeeAmountRegExp),
+    refund_amount: zod.string().regex(withdrawalItemRefundAmountRegExp),
+    id: zod.uuid(),
+    withdrawal_id: zod.uuid(),
+    billing_account_id: zod.int(),
+    currency: zod.string().min(withdrawalItemCurrencyMin).max(withdrawalItemCurrencyMax),
+    refund_id: zod.uuid(),
+    fee_transaction_id: zod.uuid().optional(),
+    status: zod.enum(["pending", "succeeded", "failed", "reversed"]),
+    completed_at: zod.iso.datetime({ offset: true }).optional(),
+    payment_gateway: zod.string(),
+    method_type: zod.string(),
+    source: WithdrawalSource,
+    failure_code: zod
+        .string()
+        .optional()
+        .describe("The original gateway failure code when a refund failed, or refund_reversed when a completed refund was reversed. Absent while pending or successful."),
+})
+    .describe("The fixed principal deduction, withdrawal fee and exact refund obligation for one original top-up. Each item has its own refund; payment_gateway and method_type identify the original route.");

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

@@ -0,0 +1,71 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 WithdrawalItemList: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        source_transaction_id: zod.ZodUUID;
+        amount: zod.ZodString;
+        fee_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        id: zod.ZodUUID;
+        withdrawal_id: zod.ZodUUID;
+        billing_account_id: zod.ZodInt;
+        currency: zod.ZodString;
+        refund_id: zod.ZodUUID;
+        fee_transaction_id: zod.ZodOptional<zod.ZodUUID>;
+        status: zod.ZodEnum<{
+            pending: "pending";
+            failed: "failed";
+            succeeded: "succeeded";
+            reversed: "reversed";
+        }>;
+        completed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        payment_gateway: zod.ZodString;
+        method_type: zod.ZodString;
+        source: zod.ZodObject<{
+            amount: zod.ZodString;
+            currency: zod.ZodString;
+            received_at: zod.z.ZodISODateTime;
+            payment_gateway: zod.ZodString;
+            method_type: zod.ZodString;
+            card_brand: zod.ZodOptional<zod.ZodString>;
+            card_last4: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>;
+        failure_code: 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 WithdrawalItemList = zod.input<typeof WithdrawalItemList>;
+export type WithdrawalItemListOutput = zod.output<typeof WithdrawalItemList>;

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

@@ -0,0 +1,37 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 { WithdrawalItem } from "./withdrawalItem.zod.js";
+export const WithdrawalItemList = zod.strictObject({
+    items: zod.array(WithdrawalItem),
+    pagination: OffsetPagination,
+});

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

@@ -0,0 +1,62 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 WithdrawalList: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        id: zod.ZodUUID;
+        billing_account_id: zod.ZodInt;
+        currency: zod.ZodString;
+        amount: zod.ZodString;
+        fee_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        deducted_amount: zod.ZodString;
+        settled_amount: zod.ZodString;
+        charged_fee_amount: zod.ZodString;
+        status: zod.ZodEnum<{
+            pending: "pending";
+            failed: "failed";
+            succeeded: "succeeded";
+            processing: "processing";
+            partially_completed: "partially_completed";
+            reversed: "reversed";
+        }>;
+        created_at: zod.z.ZodISODateTime;
+        completed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
+        created_by: 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 WithdrawalList = zod.input<typeof WithdrawalList>;
+export type WithdrawalListOutput = zod.output<typeof WithdrawalList>;

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

@@ -0,0 +1,37 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 { Withdrawal } from "./withdrawal.zod.js";
+export const WithdrawalList = zod.strictObject({
+    items: zod.array(Withdrawal),
+    pagination: OffsetPagination,
+});

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

@@ -0,0 +1,63 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 withdrawalPreviewCurrencyMin = 3;
+export declare const withdrawalPreviewCurrencyMax = 3;
+export declare const withdrawalPreviewAvailableAmountRegExp: RegExp;
+export declare const withdrawalPreviewAmountRegExp: RegExp;
+export declare const withdrawalPreviewFeeAmountRegExp: RegExp;
+export declare const withdrawalPreviewRefundAmountRegExp: RegExp;
+export declare const withdrawalPreviewItemsMax = 200;
+export declare const WithdrawalPreview: zod.ZodObject<{
+    billing_account_id: zod.ZodInt;
+    currency: zod.ZodString;
+    available_amount: zod.ZodString;
+    amount: zod.ZodString;
+    fee_amount: zod.ZodString;
+    refund_amount: zod.ZodString;
+    items: zod.ZodArray<zod.ZodObject<{
+        source_transaction_id: zod.ZodUUID;
+        amount: zod.ZodString;
+        fee_amount: zod.ZodString;
+        refund_amount: zod.ZodString;
+        source: zod.ZodObject<{
+            amount: zod.ZodString;
+            currency: zod.ZodString;
+            received_at: zod.z.ZodISODateTime;
+            payment_gateway: zod.ZodString;
+            method_type: zod.ZodString;
+            card_brand: zod.ZodOptional<zod.ZodString>;
+            card_last4: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>;
+    }, zod.z.core.$strict>>;
+}, zod.z.core.$strict>;
+export type WithdrawalPreview = zod.input<typeof WithdrawalPreview>;
+export type WithdrawalPreviewOutput = zod.output<typeof WithdrawalPreview>;

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

@@ -0,0 +1,48 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 { WithdrawalPreviewItem } from "./withdrawalPreviewItem.zod.js";
+export const withdrawalPreviewCurrencyMin = 3;
+export const withdrawalPreviewCurrencyMax = 3;
+export const withdrawalPreviewAvailableAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalPreviewAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalPreviewFeeAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalPreviewRefundAmountRegExp = new RegExp("^[0-9]{1,15}([.][0-9]{1,10})?$");
+export const withdrawalPreviewItemsMax = 200;
+export const WithdrawalPreview = zod.strictObject({
+    billing_account_id: zod.int(),
+    currency: zod.string().min(withdrawalPreviewCurrencyMin).max(withdrawalPreviewCurrencyMax),
+    available_amount: zod.string().regex(withdrawalPreviewAvailableAmountRegExp),
+    amount: zod.string().regex(withdrawalPreviewAmountRegExp),
+    fee_amount: zod.string().regex(withdrawalPreviewFeeAmountRegExp),
+    refund_amount: zod.string().regex(withdrawalPreviewRefundAmountRegExp),
+    items: zod.array(WithdrawalPreviewItem).max(withdrawalPreviewItemsMax),
+});

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

@@ -0,0 +1,51 @@
+/**
+ * Generated by orval 🍺
+ * Do not edit manually.
+ * Leaflow Canopy API
+ * Management of API keys, together with the models available and the usage recorded against them.
+ *
+ * **These endpoints do not perform inference.** Requests are issued to the forwarding address, which accepts the OpenAI, Anthropic and Gemini request formats:
+ *
+ * ```
+ * POST /v1/chat/completions                    OpenAI
+ * POST /v1/messages                            Anthropic
+ * POST /v1beta/models/{model}:generateContent  Gemini
+ * ```
+ *
+ * ## Authentication
+ *
+ * Every request carries a scoped token; see the `bearerAuth` security scheme.
+ *
+ * These endpoints do not accept an API key, and the forwarding endpoints do not accept a scoped token.
+ *
+ * ## 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. `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 withdrawalPreviewItemAmountRegExp: RegExp;
+export declare const withdrawalPreviewItemFeeAmountRegExp: RegExp;
+export declare const withdrawalPreviewItemRefundAmountRegExp: RegExp;
+export declare const WithdrawalPreviewItem: zod.ZodObject<{
+    source_transaction_id: zod.ZodUUID;
+    amount: zod.ZodString;
+    fee_amount: zod.ZodString;
+    refund_amount: zod.ZodString;
+    source: zod.ZodObject<{
+        amount: zod.ZodString;
+        currency: zod.ZodString;
+        received_at: zod.z.ZodISODateTime;
+        payment_gateway: zod.ZodString;
+        method_type: zod.ZodString;
+        card_brand: zod.ZodOptional<zod.ZodString>;
+        card_last4: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>;
+}, zod.z.core.$strict>;
+export type WithdrawalPreviewItem = zod.input<typeof WithdrawalPreviewItem>;
+export type WithdrawalPreviewItemOutput = zod.output<typeof WithdrawalPreviewItem>;