@leaflow/sdk 0.121.0 → 0.123.0

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

@@ -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";
+export declare const TerminationPolicy: zod.ZodEnum<{
+    immediate: "immediate";
+    period_end: "period_end";
+}>;
+export type TerminationPolicy = zod.input<typeof TerminationPolicy>;
+export type TerminationPolicyOutput = zod.output<typeof TerminationPolicy>;

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

@@ -0,0 +1,34 @@
+/**
+ * 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 TerminationPolicy = zod
+    .enum(["immediate", "period_end"])
+    .describe("Whether a fulfilled purchase may end immediately or only after its paid term. Does not grant a refund. When absent, the terms are not configured and termination requires review.");

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

@@ -0,0 +1,38 @@
+/**
+ * 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 Tier: zod.ZodObject<{
+    up_to: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
+    unit_amount: zod.ZodString;
+    flat_amount: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type Tier = zod.input<typeof Tier>;
+export type TierOutput = zod.output<typeof Tier>;

package/dist/canopy/v1/generated/validators/tier.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";
+import { Money } from "./money.zod.js";
+export const Tier = zod.strictObject({
+    up_to: zod
+        .string()
+        .nullish()
+        .describe("The upper bound of this band. Null on the last band, which has no bound."),
+    unit_amount: Money,
+    flat_amount: Money.optional().describe("Charged once when this band is reached, in addition to the per-unit amount."),
+});

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

@@ -0,0 +1,74 @@
+/**
+ * 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 TopUp: zod.ZodObject<{
+    id: zod.ZodUUID;
+    billing_account_id: zod.ZodInt;
+    account: zod.ZodObject<{
+        id: zod.ZodInt;
+        name: zod.ZodString;
+        currency: zod.ZodString;
+    }, zod.z.core.$strict>;
+    amount: zod.ZodString;
+    currency: zod.ZodString;
+    remaining_amount: zod.ZodOptional<zod.ZodString>;
+    status: zod.ZodEnum<{
+        pending: "pending";
+        failed: "failed";
+        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>;
+    presentment_currency: zod.ZodOptional<zod.ZodString>;
+    presentment_amount: zod.ZodOptional<zod.ZodString>;
+    failure_reason: zod.ZodOptional<zod.ZodString>;
+    action: zod.ZodOptional<zod.ZodObject<{
+        type: zod.ZodEnum<{
+            redirect: "redirect";
+            qr_code: "qr_code";
+            sdk: "sdk";
+        }>;
+        provider: zod.ZodOptional<zod.ZodString>;
+        url: zod.ZodOptional<zod.ZodURL>;
+        qr_code: zod.ZodOptional<zod.ZodString>;
+        client_secret: zod.ZodOptional<zod.ZodString>;
+        public_key: zod.ZodOptional<zod.ZodString>;
+    }, zod.z.core.$strict>>;
+    created_at: zod.z.ZodISODateTime;
+    settled_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
+}, zod.z.core.$strict>;
+export type TopUp = zod.input<typeof TopUp>;
+export type TopUpOutput = zod.output<typeof TopUp>;

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

@@ -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";
+import { AccountIdentity } from "./accountIdentity.zod.js";
+import { Money } from "./money.zod.js";
+import { PaymentAction } from "./paymentAction.zod.js";
+import { PaymentCancellationReason } from "./paymentCancellationReason.zod.js";
+export const TopUp = zod
+    .strictObject({
+    id: zod.uuid(),
+    billing_account_id: zod.int(),
+    account: AccountIdentity,
+    amount: Money.describe("What is credited to the account, in the account's own currency."),
+    currency: zod.string(),
+    remaining_amount: Money.optional().describe("The part of this top-up still held in the balance. Pending refunds can temporarily\nreserve part of it; it is not a promise that the whole amount is immediately withdrawable."),
+    status: zod
+        .enum(["pending", "succeeded", "failed", "canceled"])
+        .describe("`pending` until the payment gateway reaches a result. The balance increases on `succeeded`.\n\n`failed` means the gateway declined the payment. A declined attempt ends the top-up at once\nand the payment is withdrawn at the gateway; to pay another way, create a new top-up.\n`canceled` means the attempt was withdrawn without collecting money; `cancellation_reason`\nsays why. Unknown gateway outcomes remain `pending`, and a browser redirect is not proof of\npayment.\n\n`failed` and `canceled` are final. If the gateway nevertheless collects payment for such an\nattempt, the amount is credited as a separate `succeeded` top-up."),
+    cancellation_reason: PaymentCancellationReason.optional(),
+    payment_gateway: zod.string().optional().describe("Which payment gateway collected it."),
+    method_type: zod
+        .string()
+        .optional()
+        .describe("The selected payment method, such as card, wechat_pay or alipay."),
+    presentment_currency: zod
+        .string()
+        .optional()
+        .describe("The currency the customer was actually charged in, when the checkout page collected a\nlocal one. Absent when it was the same as the account's."),
+    presentment_amount: Money.optional().describe("What was charged, in `presentment_currency`. It will not equal `amount`, and it is\nthe figure that appears on the customer's card or wallet statement."),
+    failure_reason: zod
+        .string()
+        .optional()
+        .describe("Why the gateway declined it. Present with `failed`. The value is the gateway's own code,\npassed on unchanged: the card issuer's decline code when there is one (Stripe's decline_code,\nsuch as insufficient_funds or lost_card), otherwise the gateway's error code (Stripe's code,\nsuch as card_declined, expired_card or payment_intent_authentication_failure). Clients map it\nto their own wording and treat an unknown value as a generic decline."),
+    action: PaymentAction.optional(),
+    created_at: zod.iso.datetime({ offset: true }),
+    settled_at: zod.iso
+        .datetime({ offset: true })
+        .nullish()
+        .describe("When the funds arrived. Later than `created_at` — by days for a bank transfer — so\nreconciling against a statement uses this rather than the moment it was started.\nAbsent until the payment completes."),
+})
+    .describe("A top-up attempt and its outcome. A successful top-up adds a traceable amount to the balance; it is not a credit grant and has no associated invoice.");

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

@@ -0,0 +1,45 @@
+/**
+ * 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 topUpCreatePaymentGatewayMax = 32;
+export declare const topUpCreateMethodTypeMax = 64;
+export declare const topUpCreateAmountTwoRegExp: RegExp;
+export declare const TopUpCreate: zod.ZodObject<{
+    payment_gateway: zod.ZodString;
+    method_type: zod.ZodString;
+    id: zod.ZodUUID;
+    billing_account_id: zod.ZodInt;
+    amount: zod.ZodIntersection<zod.ZodString, zod.ZodString>;
+    payment_method_id: zod.ZodOptional<zod.ZodUUID>;
+    return_url: zod.ZodOptional<zod.ZodString>;
+}, zod.z.core.$strict>;
+export type TopUpCreate = zod.input<typeof TopUpCreate>;
+export type TopUpCreateOutput = zod.output<typeof TopUpCreate>;

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

@@ -0,0 +1,57 @@
+/**
+ * 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 { Money } from "./money.zod.js";
+export const topUpCreatePaymentGatewayMax = 32;
+export const topUpCreateMethodTypeMax = 64;
+export const topUpCreateAmountTwoRegExp = new RegExp("^(?:(?:[1-9][0-9]{0,14}|0(?:[1-9][0-9]{0,13}|0(?:[1-9][0-9]{0,12}|0(?:[1-9][0-9]{0,11}|0(?:[1-9][0-9]{0,10}|0(?:[1-9][0-9]{0,9}|0(?:[1-9][0-9]{0,8}|0(?:[1-9][0-9]{0,7}|0(?:[1-9][0-9]{0,6}|0(?:[1-9][0-9]{0,5}|0(?:[1-9][0-9]{0,4}|0(?:[1-9][0-9]{0,3}|0(?:[1-9][0-9]{0,2}|0(?:[1-9][0-9]{0,1}|0[1-9]))))))))))))))([.][0-9]{1,10})?|0{1,15}[.](?:[1-9][0-9]{0,9}|0(?:[1-9][0-9]{0,8}|0(?:[1-9][0-9]{0,7}|0(?:[1-9][0-9]{0,6}|0(?:[1-9][0-9]{0,5}|0(?:[1-9][0-9]{0,4}|0(?:[1-9][0-9]{0,3}|0(?:[1-9][0-9]{0,2}|0(?:[1-9][0-9]{0,1}|0[1-9]))))))))))$");
+export const TopUpCreate = zod.strictObject({
+    payment_gateway: zod
+        .string()
+        .min(1)
+        .max(topUpCreatePaymentGatewayMax)
+        .describe("The gateway explicitly selected from the available payment options."),
+    method_type: zod
+        .string()
+        .min(1)
+        .max(topUpCreateMethodTypeMax)
+        .describe("The selected method, such as card, wechat_pay or alipay."),
+    id: zod
+        .uuid()
+        .describe("The ID of this top-up attempt. Keep it before submitting and query it after an uncertain response."),
+    billing_account_id: zod.int(),
+    amount: Money.and(zod.string().regex(topUpCreateAmountTwoRegExp)).describe("In the account's currency, and no finer than that currency's smallest unit:\ntwo decimals for most, none for the yen. A finer amount is refused here rather\nthan at the checkout page, where the customer would see the gateway's own wording\ninstead of an explanation.\n\nThere is a minimum, which differs by currency. Below it the gateway's fee\nexceeds the top-up itself, so such a payment costs more to accept than it brings.\nThe minimum in force is returned with the rejection."),
+    payment_method_id: zod
+        .uuid()
+        .optional()
+        .describe("Charge a saved method instead of opening a checkout page."),
+    return_url: zod.string().optional().describe("Where to send the customer after checkout."),
+});

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

@@ -0,0 +1,81 @@
+/**
+ * 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 TopUpList: zod.ZodObject<{
+    items: zod.ZodArray<zod.ZodObject<{
+        id: zod.ZodUUID;
+        billing_account_id: zod.ZodInt;
+        account: zod.ZodObject<{
+            id: zod.ZodInt;
+            name: zod.ZodString;
+            currency: zod.ZodString;
+        }, zod.z.core.$strict>;
+        amount: zod.ZodString;
+        currency: zod.ZodString;
+        remaining_amount: zod.ZodOptional<zod.ZodString>;
+        status: zod.ZodEnum<{
+            pending: "pending";
+            failed: "failed";
+            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>;
+        presentment_currency: zod.ZodOptional<zod.ZodString>;
+        presentment_amount: zod.ZodOptional<zod.ZodString>;
+        failure_reason: zod.ZodOptional<zod.ZodString>;
+        action: zod.ZodOptional<zod.ZodObject<{
+            type: zod.ZodEnum<{
+                redirect: "redirect";
+                qr_code: "qr_code";
+                sdk: "sdk";
+            }>;
+            provider: zod.ZodOptional<zod.ZodString>;
+            url: zod.ZodOptional<zod.ZodURL>;
+            qr_code: zod.ZodOptional<zod.ZodString>;
+            client_secret: zod.ZodOptional<zod.ZodString>;
+            public_key: zod.ZodOptional<zod.ZodString>;
+        }, zod.z.core.$strict>>;
+        created_at: zod.z.ZodISODateTime;
+        settled_at: 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 TopUpList = zod.input<typeof TopUpList>;
+export type TopUpListOutput = zod.output<typeof TopUpList>;

package/dist/canopy/v1/generated/validators/topUpList.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 { TopUp } from "./topUp.zod.js";
+export const TopUpList = zod.strictObject({
+    items: zod.array(TopUp),
+    pagination: OffsetPagination,
+});

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

@@ -0,0 +1,76 @@
+/**
+ * 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 Transaction: 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<{
+        pending: "pending";
+        failed: "failed";
+        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";
+    }>;
+    amount: zod.ZodString;
+    remaining_amount: zod.ZodString;
+    currency: zod.ZodString;
+    reason: zod.ZodOptional<zod.ZodString>;
+    created_at: zod.z.ZodISODateTime;
+}, zod.z.core.$strict>;
+export type Transaction = zod.input<typeof Transaction>;
+export type TransactionOutput = zod.output<typeof Transaction>;