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

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

@@ -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";
-export declare const ScheduledChange: zod.ZodObject<{
-    order_id: zod.ZodUUID;
-    status: zod.ZodEnum<{
-        completed: "completed";
-        failed: "failed";
-        pending: "pending";
-        canceled: "canceled";
-        accepted: "accepted";
-        partially_completed: "partially_completed";
-    }>;
-    effective_at: zod.z.ZodISODateTime;
-    plan_id: zod.ZodUUID;
-    plan_name: zod.ZodString;
-    price_id: zod.ZodUUID;
-    quantity: zod.ZodString;
-    recurring_amount: zod.ZodString;
-    currency: zod.ZodString;
-    interval: zod.ZodEnum<{
-        day: "day";
-        month: "month";
-        year: "year";
-    }>;
-    interval_count: zod.ZodInt;
-}, zod.z.core.$strict>;
-export type ScheduledChange = zod.input<typeof ScheduledChange>;
-export type ScheduledChangeOutput = zod.output<typeof ScheduledChange>;

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

@@ -1,59 +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 { OrderStatus } from "./orderStatus.zod.js";
-export const ScheduledChange = zod
-    .strictObject({
-    order_id: zod.uuid(),
-    status: OrderStatus,
-    effective_at: zod.iso
-        .datetime({ offset: true })
-        .describe("When the target terms take effect, normally the end of the current paid period."),
-    plan_id: zod.uuid(),
-    plan_name: zod.string(),
-    price_id: zod.uuid(),
-    quantity: zod.string(),
-    recurring_amount: zod.string().describe("The target licensed renewal amount before tax."),
-    currency: zod.string(),
-    interval: zod.enum(["day", "month", "year"]),
-    interval_count: zod.int().min(1),
-})
-    .describe("The next accepted period-end change of the subscription: the target terms, applied at effective_at.");

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

@@ -1,46 +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 SetProjectAssignmentRequest: zod.ZodObject<{
-    billing_account_id: zod.ZodInt;
-}, zod.z.core.$strict>;
-export type SetProjectAssignmentRequest = zod.input<typeof SetProjectAssignmentRequest>;
-export type SetProjectAssignmentRequestOutput = zod.output<typeof SetProjectAssignmentRequest>;

package/dist/canopy/v1/generated/validators/setProjectAssignmentRequest.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 SetProjectAssignmentRequest = zod.strictObject({
-    billing_account_id: zod.int(),
-});

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

@@ -1,63 +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 SpendRow: zod.ZodObject<{
-    product: zod.ZodOptional<zod.ZodObject<{
-        id: zod.ZodString;
-        name: zod.ZodString;
-        description: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>>;
-    plan_id: zod.ZodOptional<zod.ZodUUID>;
-    plan_name: zod.ZodOptional<zod.ZodString>;
-    resource_id: zod.ZodOptional<zod.ZodString>;
-    meter: zod.ZodOptional<zod.ZodObject<{
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    unit: zod.ZodOptional<zod.ZodString>;
-    quantity: zod.ZodOptional<zod.ZodString>;
-    dimensions: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
-    amount: zod.ZodString;
-    currency: zod.ZodString;
-}, zod.z.core.$strict>;
-export type SpendRow = zod.input<typeof SpendRow>;
-export type SpendRowOutput = zod.output<typeof SpendRow>;

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

@@ -1,62 +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 { Product } from "./product.zod.js";
-export const SpendRow = zod.strictObject({
-    product: Product.optional(),
-    plan_id: zod.uuid().optional(),
-    plan_name: zod.string().optional(),
-    resource_id: zod.string().optional().describe("Present only when grouped by resource."),
-    meter: ObjectIdentity.optional().describe("Present only when grouped by meter."),
-    unit: zod.string().optional().describe("Present only when grouped by meter."),
-    quantity: zod
-        .string()
-        .optional()
-        .describe("Net usage quantity, present only when grouped by meter."),
-    dimensions: zod
-        .record(zod.string(), zod.string())
-        .optional()
-        .describe("The values of the meter's presentation dimensions, present only when grouped by meter."),
-    amount: Money,
-    currency: zod.string(),
-});

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

@@ -1,72 +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 SpendRowList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        product: zod.ZodOptional<zod.ZodObject<{
-            id: zod.ZodString;
-            name: zod.ZodString;
-            description: zod.ZodOptional<zod.ZodString>;
-        }, zod.z.core.$strict>>;
-        plan_id: zod.ZodOptional<zod.ZodUUID>;
-        plan_name: zod.ZodOptional<zod.ZodString>;
-        resource_id: zod.ZodOptional<zod.ZodString>;
-        meter: zod.ZodOptional<zod.ZodObject<{
-            lookup_key: zod.ZodOptional<zod.ZodString>;
-            id: zod.ZodUUID;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>>;
-        unit: zod.ZodOptional<zod.ZodString>;
-        quantity: zod.ZodOptional<zod.ZodString>;
-        dimensions: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodString>>;
-        amount: zod.ZodString;
-        currency: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    total: zod.ZodString;
-    currency: zod.ZodString;
-    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 SpendRowList = zod.input<typeof SpendRowList>;
-export type SpendRowListOutput = zod.output<typeof SpendRowList>;

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

@@ -1,50 +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 { OffsetPagination } from "./offsetPagination.zod.js";
-import { SpendRow } from "./spendRow.zod.js";
-export const SpendRowList = zod.strictObject({
-    items: zod.array(SpendRow),
-    total: Money.describe("The total over all matching groups, not only the page returned."),
-    currency: zod.string(),
-    pagination: OffsetPagination,
-});

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

@@ -1,72 +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 Statement: zod.ZodObject<{
-    id: zod.ZodUUID;
-    billing_account_id: zod.ZodInt;
-    currency: zod.ZodString;
-    period_start: zod.z.ZodISODateTime;
-    period_end: zod.z.ZodISODateTime;
-    sequence: zod.ZodInt;
-    status: zod.ZodEnum<{
-        open: "open";
-        closed: "closed";
-    }>;
-    type: zod.ZodEnum<{
-        interim: "interim";
-        final: "final";
-        supplement: "supplement";
-    }>;
-    estimated: zod.ZodBoolean;
-    amounts: zod.ZodObject<{
-        subtotal: zod.ZodString;
-        discount_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        total: zod.ZodString;
-    }, zod.z.core.$strict>;
-    closed_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    invoice_id: zod.ZodOptional<zod.ZodUUID>;
-    created_at: zod.z.ZodISODateTime;
-    calculated_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    credited_amount: zod.ZodString;
-}, zod.z.core.$strict>;
-export type Statement = zod.input<typeof Statement>;
-export type StatementOutput = zod.output<typeof Statement>;

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

@@ -1,69 +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 { StatementAmounts } from "./statementAmounts.zod.js";
-import { StatementStatus } from "./statementStatus.zod.js";
-import { StatementType } from "./statementType.zod.js";
-export const Statement = zod
-    .strictObject({
-    id: zod.uuid(),
-    billing_account_id: zod.int(),
-    currency: zod.string(),
-    period_start: zod.iso.datetime({ offset: true }),
-    period_end: zod.iso.datetime({ offset: true }),
-    sequence: zod.int().describe("Increases with each closing of the period."),
-    status: StatementStatus,
-    type: StatementType,
-    estimated: zod
-        .boolean()
-        .describe("True while the statement is open. The estimate prices the period's usage so far at tier prices and adds tax for the current invoice contact. Minimum charges are added at the period's final closing, and a tier reduction larger than this statement's charges is credited to the period's earlier invoices at closing."),
-    amounts: StatementAmounts,
-    closed_at: zod.iso.datetime({ offset: true }).optional(),
-    invoice_id: zod
-        .uuid()
-        .optional()
-        .describe("The invoice issued at this closing, when it produced one."),
-    created_at: zod.iso.datetime({ offset: true }),
-    calculated_at: zod.iso.datetime({ offset: true }).optional(),
-    credited_amount: Money,
-})
-    .describe("An account's consumption for one billing period up to one closing. Usage is invoiced after every settlement run, about hourly: each closing issues an invoice for the usage priced since the previous one and collects it from credits and balance, and later usage goes into the next statement of the same period. A closed statement does not change. The period's consumption is the sum of its statements.");