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

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

@@ -1,79 +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 { 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 its currency."),
-    currency: zod.string(),
-    remaining_amount: Money.optional().describe("The part of this top-up still in the balance. Pending refunds may hold part of it, so not all of it is necessarily withdrawable."),
-    status: zod
-        .enum(["pending", "succeeded", "failed", "canceled"])
-        .describe("`pending` until the payment gateway reaches a result; the balance increases on `succeeded`. `failed`: the gateway declined the payment, which is withdrawn at the gateway; create a new top-up to pay another way. `canceled`: withdrawn without collecting money, for the reason in `cancellation_reason`. Unknown gateway outcomes stay `pending`; a browser redirect is not proof of payment. `failed` and `canceled` are final; a payment the gateway collects afterwards 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 charged in when the checkout collected a local currency; absent when it is the account's."),
-    presentment_amount: Money.optional().describe("The amount charged in `presentment_currency`, as shown on the customer's statement."),
-    failure_reason: zod
-        .string()
-        .optional()
-        .describe("Why the gateway declined it; present with `failed`. The gateway's code unchanged: the issuer's decline code when there is one (Stripe decline_code, such as insufficient_funds), otherwise the gateway's error code (Stripe code, such as card_declined). 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, possibly days after `created_at`. Absent until the payment completes."),
-})
-    .describe("A top-up attempt and its outcome. A successful top-up adds to the balance; it is not a credit grant and has no invoice.");

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

@@ -1,55 +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 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

@@ -1,67 +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";
-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 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 top-up ID, chosen by the caller. Read it after an uncertain response."),
-    billing_account_id: zod.int(),
-    amount: Money.and(zod.string().regex(topUpCreateAmountTwoRegExp)).describe("In the account's currency, no finer than its smallest unit (two decimals for most currencies, none for JPY). An amount below the currency's minimum top-up is refused, and the minimum is returned with the error."),
-    payment_method_id: zod
-        .uuid()
-        .optional()
-        .describe("Charge a saved payment 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

@@ -1,91 +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 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<{
-            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>;
-        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

@@ -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 { 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

@@ -1,87 +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 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<{
-        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>;
-export type Transaction = zod.input<typeof Transaction>;
-export type TransactionOutput = zod.output<typeof Transaction>;

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

@@ -1,81 +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 { ObjectIdentity } from "./objectIdentity.zod.js";
-import { PaymentCancellationReason } from "./paymentCancellationReason.zod.js";
-import { TransactionType } from "./transactionType.zod.js";
-export const Transaction = zod
-    .strictObject({
-    invoice_id: zod.uuid().optional(),
-    transaction_id: zod.uuid().optional(),
-    credit_grant_id: zod
-        .uuid()
-        .optional()
-        .describe("The credit grant that paid, or for a refund, the credit grant restored."),
-    credit_grant: ObjectIdentity.optional(),
-    refund_id: zod.uuid().optional(),
-    refund_destination: zod
-        .enum(["balance", "credit", "gateway"])
-        .optional()
-        .describe("Present on refunds: where this part goes. `balance`: the account balance. `credit`: the credit grant that paid, keeping its original expiry. `gateway`: the payment method it was paid with."),
-    status: zod
-        .enum(["pending", "succeeded", "failed", "canceled"])
-        .optional()
-        .describe("`failed`: the operation did not succeed; for a gateway payment, the gateway declined it. `canceled`: a gateway payment was withdrawn without collecting money. Either way, the invoice it was for stays open."),
-    cancellation_reason: PaymentCancellationReason.optional(),
-    payment_gateway: zod.string().optional(),
-    method_type: zod.string().optional(),
-    failure_reason: zod
-        .string()
-        .optional()
-        .describe("Why it failed; present with `failed`. For a declined gateway payment, the gateway's code unchanged: the issuer's decline code when there is one (Stripe decline_code, such as insufficient_funds), otherwise the gateway's error code (Stripe code, such as card_declined). Treat an unknown value as a generic decline."),
-    settled_at: zod.iso.datetime({ offset: true }).optional(),
-    id: zod.uuid(),
-    billing_account_id: zod.int().optional(),
-    type: TransactionType,
-    amount: Money.describe("Signed by type: positive for `topup` and `payment`, negative for `refund`. An `adjustment` is positive when it adds to the balance and negative when it takes from it. For other types the sign does not show the effect on the balance: a payment from balance lowers it, a payment by gateway or credit does not."),
-    remaining_amount: Money.describe("How much of this transaction is still in the balance. Only top-ups, positive adjustments and gateway payments returned to the balance can be non-zero."),
-    currency: zod.string(),
-    reason: zod.string().optional(),
-    created_at: zod.iso.datetime({ offset: true }),
-})
-    .describe("A funds movement with one source. Refunds name the original transaction. Unknown gateway results stay pending.");

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

@@ -1,94 +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 TransactionList: zod.ZodObject<{
-    items: 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>>;
-    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 TransactionList = zod.input<typeof TransactionList>;
-export type TransactionListOutput = zod.output<typeof TransactionList>;