@leaflow/sdk 0.154.0 → 0.156.0

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

@@ -1,44 +0,0 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * Leaflow Canopy API
- * Canopy model inference, API keys, model catalogue, service enablement and recorded usage.
- *
- * Project inference is served on this host in each provider's own protocol:
- *
- * - OpenAI: `/v1/chat/completions`, `/v1/responses` and `/v1/embeddings`; use
- *   `https://canopy.leaflow.cloud/v1` as the OpenAI SDK base URL.
- * - Anthropic: `/v1/messages`; use `https://canopy.leaflow.cloud` as the Anthropic SDK base URL.
- * - Gemini: `/v1beta/models/{model}:generateContent` and `:streamGenerateContent`.
- *
- * Canopy does not convert between protocols. A request is accepted only for a model whose
- * `supported_endpoints` lists the endpoint it was sent to, and it is forwarded unchanged except for
- * the model name and the credentials. Reasoning settings such as `reasoning_effort` are passed
- * through as written; a model's `capabilities` lists the values its upstream accepts.
- *
- * Management operations use `/api/v1`. The management model catalogue includes pricing;
- * `/v1/models` returns the OpenAI model format with Canopy capabilities and parameter limits.
- *
- * ## Authentication
- *
- * Every request carries a scoped token; see the `bearerAuth` security scheme.
- *
- * Management and project inference accept the same verified IAM scoped token. The token is the
- * sole billing project authority; `OpenAI-Project` and historical identity headers cannot
- * override it. These endpoints do not accept a Canopy API key. The separate API-key gateway
- * accepts Canopy API keys and serves the same endpoints.
- *
- * ## Conventions
- *
- * - **The plaintext of an API key is returned once.** The `secret` appears in the response that issues it and is returned by no other endpoint. A key that has been lost has to be revoked and reissued.
- * - **Disabling and revoking are distinct.** A disabled key may be enabled again at any time, while a revocation is irreversible and is intended for a key that has been exposed. Neither removes the record, and the usage the key accrued remains readable.
- * - **A usage query must carry a time range**, spanning no more than 31 days, or 400 days for the usage timeline. `from` and `to` carry a timezone offset, which the server does not infer.
- * - **The request and response bodies do not appear in the ledger.** They are not recorded. Quote the `upstream_request_id` from the response when reporting a problem.
- * - **Usage may be estimated.** The upstream provider does not report usage on every request. Where it does not, `usage_source` is `estimated` and the figures are derived from the character classes of the payload, to within roughly fifteen per cent.
- * - **The service is enabled before use.** A project enables the model platform once, through `create-service`; the forwarding endpoints refuse its requests until the service is `active`. Requests are then billed under the service's subscription by the tokens they use, at the rates stated in each model's `pricing`.
- * OpenAPI spec version: 1.0.0
- */
-import * as zod from "zod";
-export const FeatureGrantStatus = zod
-    .enum(["scheduled", "active", "expired", "voided"])
-    .describe("Derived from the validity period. scheduled means valid_from has not yet arrived.");

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

@@ -1,96 +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 Invoice: zod.ZodObject<{
-    void_requested_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    due_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    amount_refunded: zod.ZodOptional<zod.ZodString>;
-    tax_items: zod.ZodArray<zod.ZodObject<{
-        id: zod.ZodUUID;
-        invoice_id: zod.ZodUUID;
-        name: zod.ZodString;
-        percentage: zod.ZodString;
-        country: zod.ZodString;
-        state: zod.ZodOptional<zod.ZodString>;
-        taxable_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        currency: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    id: zod.ZodUUID;
-    billing_account_id: zod.ZodInt;
-    number: zod.ZodString;
-    currency: zod.ZodString;
-    status: zod.ZodEnum<{
-        void: "void";
-        open: "open";
-        draft: "draft";
-        paid: "paid";
-    }>;
-    subtotal: zod.ZodOptional<zod.ZodString>;
-    discount_amount: zod.ZodOptional<zod.ZodString>;
-    tax_amount: zod.ZodOptional<zod.ZodString>;
-    credit_applied: zod.ZodOptional<zod.ZodString>;
-    total: zod.ZodString;
-    rounding_amount: zod.ZodString;
-    amount_paid: zod.ZodOptional<zod.ZodString>;
-    pre_payment_credit_notes_amount: zod.ZodString;
-    post_payment_credit_notes_amount: zod.ZodString;
-    amount_due: zod.ZodString;
-    period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    customer_name: zod.ZodOptional<zod.ZodString>;
-    customer_email: zod.ZodOptional<zod.ZodString>;
-    customer_tax_id: zod.ZodOptional<zod.ZodString>;
-    customer_tax_exempt: zod.ZodOptional<zod.ZodEnum<{
-        none: "none";
-        reverse: "reverse";
-        exempt: "exempt";
-    }>>;
-    customer_address_line1: zod.ZodOptional<zod.ZodString>;
-    customer_address_line2: zod.ZodOptional<zod.ZodString>;
-    customer_address_city: zod.ZodOptional<zod.ZodString>;
-    customer_address_state: zod.ZodOptional<zod.ZodString>;
-    customer_address_postal_code: zod.ZodOptional<zod.ZodString>;
-    customer_address_country: zod.ZodOptional<zod.ZodString>;
-    paid_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-}, zod.z.core.$strict>;
-export type Invoice = zod.input<typeof Invoice>;
-export type InvoiceOutput = zod.output<typeof Invoice>;

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

@@ -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";
-import { InvoiceStatus } from "./invoiceStatus.zod.js";
-import { Money } from "./money.zod.js";
-import { TaxItem } from "./taxItem.zod.js";
-export const Invoice = zod.strictObject({
-    void_requested_at: zod.iso
-        .datetime({ offset: true })
-        .optional()
-        .describe("Collection has stopped; accepted return obligations are completed."),
-    due_at: zod.iso.datetime({ offset: true }).optional(),
-    amount_refunded: zod.string().optional(),
-    tax_items: zod.array(TaxItem),
-    id: zod.uuid(),
-    billing_account_id: zod.int(),
-    number: zod.string().describe("Numbered per account and per month."),
-    currency: zod.string(),
-    status: InvoiceStatus,
-    subtotal: Money.optional().describe("Sum of the line amounts before discounts. Where prices include tax, the tax contained in\neach line's discounted amount is taken out here, so that total = subtotal -\ndiscount_amount + tax_amount always holds."),
-    discount_amount: Money.optional().describe("Sum of the line discounts, taken off before tax."),
-    tax_amount: Money.optional(),
-    credit_applied: Money.optional().describe("Successful credit-grant payments, included in amount_paid; they do not reduce the receivable or tax base."),
-    total: Money.describe("Subtotal less discount plus tax. Balance and credit grants pay it plus rounding_amount; they do not reduce it."),
-    rounding_amount: Money.describe("Added to total to round the amount payable to the currency's minor unit; negative when rounded down. The rounding of a usage invoice carries over to the next invoice of the same billing period."),
-    amount_paid: Money.optional(),
-    pre_payment_credit_notes_amount: Money.describe("Issued credit notes that reduced unpaid receivables; the original invoice total is unchanged."),
-    post_payment_credit_notes_amount: Money.describe("Issued credit notes against payments already received; their refunds may not have completed."),
-    amount_due: Money.describe("What is still collectible from total plus rounding_amount after unpaid credit notes and successful payments; never below zero. Zero for a draft, whose total is the base price, and for a paid or void invoice."),
-    period_start: zod.iso.datetime({ offset: true }).nullish(),
-    period_end: zod.iso.datetime({ offset: true }).nullish().describe("Exclusive."),
-    customer_name: zod
-        .string()
-        .optional()
-        .describe("The billing details recorded when the invoice was issued."),
-    customer_email: zod.string().optional(),
-    customer_tax_id: zod.string().optional(),
-    customer_tax_exempt: zod
-        .enum(["none", "exempt", "reverse"])
-        .optional()
-        .describe("How tax applied to the customer when the invoice was issued; `reverse` means no tax was charged under the reverse-charge mechanism."),
-    customer_address_line1: zod.string().optional(),
-    customer_address_line2: zod.string().optional(),
-    customer_address_city: zod.string().optional(),
-    customer_address_state: zod.string().optional(),
-    customer_address_postal_code: zod.string().optional(),
-    customer_address_country: zod.string().optional(),
-    paid_at: zod.iso.datetime({ offset: true }).nullish(),
-});

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

@@ -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";
-export declare const InvoiceItem: zod.ZodObject<{
-    taxable: zod.ZodOptional<zod.ZodBoolean>;
-    discount_amount: zod.ZodOptional<zod.ZodString>;
-    discount_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-    coupon_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-    tax_amount: zod.ZodOptional<zod.ZodString>;
-    tax_included_amount: zod.ZodOptional<zod.ZodString>;
-    id: zod.ZodUUID;
-    project_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-    project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>, zod.ZodNull]>>;
-    resource_id: zod.ZodOptional<zod.ZodString>;
-    description: zod.ZodString;
-    unit: zod.ZodOptional<zod.ZodString>;
-    quantity: zod.ZodOptional<zod.ZodString>;
-    deducted_quantity: zod.ZodOptional<zod.ZodString>;
-    unit_amount: zod.ZodOptional<zod.ZodString>;
-    unit_quantity: zod.ZodOptional<zod.ZodString>;
-    amount: zod.ZodString;
-    rounding_amount: zod.ZodString;
-    usage_charge_count: zod.ZodInt;
-    currency: zod.ZodString;
-    period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    dimensions: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
-    prorations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-        credited_invoice_item_id: zod.ZodUUID;
-        description: zod.ZodString;
-        period_start: zod.z.ZodISODateTime;
-        period_end: zod.z.ZodISODateTime;
-        remaining_amount: zod.ZodString;
-        credited_amount: zod.ZodString;
-    }, zod.z.core.$strict>>>;
-}, zod.z.core.$strict>;
-export type InvoiceItem = zod.input<typeof InvoiceItem>;
-export type InvoiceItemOutput = zod.output<typeof InvoiceItem>;

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

@@ -1,93 +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 { InvoiceItemProration } from "./invoiceItemProration.zod.js";
-import { Money } from "./money.zod.js";
-import { NamedIdentity } from "./namedIdentity.zod.js";
-export const InvoiceItem = zod.strictObject({
-    taxable: zod.boolean().optional(),
-    discount_amount: zod.string().optional().describe("Discount applied to this line before tax."),
-    discount_id: zod.uuid().nullish().describe("The account discount applied to this line."),
-    coupon_id: zod.uuid().nullish().describe("The coupon applied to this line."),
-    tax_amount: zod
-        .string()
-        .optional()
-        .describe("Tax on the discounted line, including tax already included in the price."),
-    tax_included_amount: zod
-        .string()
-        .optional()
-        .describe("The part of tax_amount already included in amount."),
-    id: zod.uuid(),
-    project_id: zod.uuid().nullish(),
-    project: zod
-        .union([NamedIdentity, zod.null()])
-        .optional()
-        .describe("The project the charge was for and its current name. Absent when the line has no project or the project cannot be read; `project_id` still identifies it."),
-    resource_id: zod.string().optional(),
-    description: zod.string().describe("The line's wording as recorded when the invoice was issued."),
-    unit: zod.string().optional(),
-    quantity: zod.string().optional(),
-    deducted_quantity: zod
-        .string()
-        .optional()
-        .describe("The part covered by an included allowance, and therefore not charged."),
-    unit_amount: Money.optional(),
-    unit_quantity: zod
-        .string()
-        .optional()
-        .describe("The quantity `unit_amount` prices, such as 1000000 tokens or 3600 seconds: `amount` is `quantity` × `unit_amount` ÷ `unit_quantity`. Present together with `unit_amount`."),
-    amount: Money,
-    rounding_amount: Money.describe("This line's share of the invoice's rounding_amount. The line's net amount is amount - discount_amount + tax_amount - tax_included_amount + rounding_amount."),
-    usage_charge_count: zod
-        .int()
-        .describe("Usage charges billed on this line; zero for other lines."),
-    currency: zod.string(),
-    period_start: zod.iso.datetime({ offset: true }).nullish(),
-    period_end: zod.iso.datetime({ offset: true }).nullish(),
-    dimensions: zod
-        .record(zod.string(), zod.string())
-        .optional()
-        .describe("For a usage line, the values of its meter's presentation dimensions, such as the model and token kind. Empty for other lines."),
-    prorations: zod
-        .array(InvoiceItemProration)
-        .optional()
-        .describe("Present on a line that changes a subscription immediately, one entry for each paid period it\ncovers. `amount` is the sum of `remaining_amount` minus `credited_amount` over the entries."),
-});

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

@@ -1,86 +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 InvoiceItemList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        taxable: zod.ZodOptional<zod.ZodBoolean>;
-        discount_amount: zod.ZodOptional<zod.ZodString>;
-        discount_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-        coupon_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-        tax_amount: zod.ZodOptional<zod.ZodString>;
-        tax_included_amount: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        project_id: zod.ZodOptional<zod.ZodNullable<zod.ZodUUID>>;
-        project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-            id: zod.ZodUUID;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>, zod.ZodNull]>>;
-        resource_id: zod.ZodOptional<zod.ZodString>;
-        description: zod.ZodString;
-        unit: zod.ZodOptional<zod.ZodString>;
-        quantity: zod.ZodOptional<zod.ZodString>;
-        deducted_quantity: zod.ZodOptional<zod.ZodString>;
-        unit_amount: zod.ZodOptional<zod.ZodString>;
-        unit_quantity: zod.ZodOptional<zod.ZodString>;
-        amount: zod.ZodString;
-        rounding_amount: zod.ZodString;
-        usage_charge_count: zod.ZodInt;
-        currency: zod.ZodString;
-        period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-        period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-        dimensions: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
-        prorations: zod.ZodOptional<zod.ZodArray<zod.ZodObject<{
-            credited_invoice_item_id: zod.ZodUUID;
-            description: zod.ZodString;
-            period_start: zod.z.ZodISODateTime;
-            period_end: zod.z.ZodISODateTime;
-            remaining_amount: zod.ZodString;
-            credited_amount: zod.ZodString;
-        }, zod.z.core.$strict>>>;
-    }, 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 InvoiceItemList = zod.input<typeof InvoiceItemList>;
-export type InvoiceItemListOutput = zod.output<typeof InvoiceItemList>;

package/dist/canopy/v1/generated/validators/invoiceItemList.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 { InvoiceItem } from "./invoiceItem.zod.js";
-import { OffsetPagination } from "./offsetPagination.zod.js";
-export const InvoiceItemList = zod.strictObject({
-    items: zod.array(InvoiceItem),
-    pagination: OffsetPagination,
-});

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

@@ -1,51 +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 InvoiceItemProration: zod.ZodObject<{
-    credited_invoice_item_id: zod.ZodUUID;
-    description: zod.ZodString;
-    period_start: zod.z.ZodISODateTime;
-    period_end: zod.z.ZodISODateTime;
-    remaining_amount: zod.ZodString;
-    credited_amount: zod.ZodString;
-}, zod.z.core.$strict>;
-export type InvoiceItemProration = zod.input<typeof InvoiceItemProration>;
-export type InvoiceItemProrationOutput = zod.output<typeof InvoiceItemProration>;