@leaflow/sdk 0.153.0 → 0.155.0

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

@@ -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";
-export declare const MonthlyStatement: zod.ZodObject<{
-    billing_account_id: zod.ZodInt;
-    currency: zod.ZodString;
-    period_start: zod.z.ZodISODateTime;
-    period_end: zod.z.ZodISODateTime;
-    finalized: zod.ZodBoolean;
-    finalized_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    statement_count: zod.ZodInt;
-    billed: zod.ZodObject<{
-        subtotal: zod.ZodString;
-        discount_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        total: zod.ZodString;
-    }, zod.z.core.$strict>;
-    credited_amount: zod.ZodString;
-    unbilled: zod.ZodOptional<zod.ZodObject<{
-        subtotal: zod.ZodString;
-        discount_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        total: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    credit_applied: zod.ZodString;
-    amount_paid: zod.ZodString;
-    amount_due: zod.ZodString;
-    amount_refunded: zod.ZodString;
-}, zod.z.core.$strict>;
-export type MonthlyStatement = zod.input<typeof MonthlyStatement>;
-export type MonthlyStatementOutput = zod.output<typeof MonthlyStatement>;

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

@@ -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";
-import { Money } from "./money.zod.js";
-import { StatementAmounts } from "./statementAmounts.zod.js";
-export const MonthlyStatement = zod
-    .strictObject({
-    billing_account_id: zod.int(),
-    currency: zod.string(),
-    period_start: zod.iso.datetime({ offset: true }),
-    period_end: zod.iso.datetime({ offset: true }),
-    finalized: zod
-        .boolean()
-        .describe("True after the period's final closing, which applies the month's minimum charges. Usage priced later is billed in supplement statements and added here."),
-    finalized_at: zod.iso.datetime({ offset: true }).optional(),
-    statement_count: zod.int().describe("Statements of the period, including the open one."),
-    billed: StatementAmounts,
-    credited_amount: Money,
-    unbilled: StatementAmounts.optional(),
-    credit_applied: Money,
-    amount_paid: Money,
-    amount_due: Money,
-    amount_refunded: Money,
-})
-    .describe("One billing account's usage billing for one UTC calendar month, summed over its statements. Not payable itself; each statement's invoice is collected on its own.");

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

@@ -1,76 +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 MonthlyStatementList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        billing_account_id: zod.ZodInt;
-        currency: zod.ZodString;
-        period_start: zod.z.ZodISODateTime;
-        period_end: zod.z.ZodISODateTime;
-        finalized: zod.ZodBoolean;
-        finalized_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-        statement_count: zod.ZodInt;
-        billed: zod.ZodObject<{
-            subtotal: zod.ZodString;
-            discount_amount: zod.ZodString;
-            tax_amount: zod.ZodString;
-            total: zod.ZodString;
-        }, zod.z.core.$strict>;
-        credited_amount: zod.ZodString;
-        unbilled: zod.ZodOptional<zod.ZodObject<{
-            subtotal: zod.ZodString;
-            discount_amount: zod.ZodString;
-            tax_amount: zod.ZodString;
-            total: zod.ZodString;
-        }, zod.z.core.$strict>>;
-        credit_applied: zod.ZodString;
-        amount_paid: zod.ZodString;
-        amount_due: zod.ZodString;
-        amount_refunded: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    pagination: zod.ZodObject<{
-        page: zod.ZodInt;
-        page_size: zod.ZodInt;
-        total_count: zod.ZodOptional<zod.ZodInt>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type MonthlyStatementList = zod.input<typeof MonthlyStatementList>;
-export type MonthlyStatementListOutput = zod.output<typeof MonthlyStatementList>;

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

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

@@ -1,48 +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 namedIdentityNameMax = 255;
-export declare const NamedIdentity: zod.ZodObject<{
-    id: zod.ZodUUID;
-    name: zod.ZodString;
-}, zod.z.core.$strict>;
-export type NamedIdentity = zod.input<typeof NamedIdentity>;
-export type NamedIdentityOutput = zod.output<typeof NamedIdentity>;

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

@@ -1,48 +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 namedIdentityNameMax = 255;
-export const NamedIdentity = zod
-    .strictObject({
-    id: zod.uuid(),
-    name: zod.string().max(namedIdentityNameMax),
-})
-    .describe("Which object this is, together with what a person currently calls it.\n\nThe name is for display. It is chosen by whoever owns the object, it changes, it is not unique\nbetween objects, and it may be empty when nobody has named it yet — so it must not be used to\naddress, match or deduplicate anything. Addressing is by id.\n\nThis differs from an identity carrying a lookup key: a lookup key is written once by an operator,\nis unique, and can be used to fetch the object. A name cannot.");

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

@@ -1,48 +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 ObjectIdentity: zod.ZodObject<{
-    lookup_key: zod.ZodOptional<zod.ZodString>;
-    id: zod.ZodUUID;
-    name: zod.ZodString;
-}, zod.z.core.$strict>;
-export type ObjectIdentity = zod.input<typeof ObjectIdentity>;
-export type ObjectIdentityOutput = zod.output<typeof ObjectIdentity>;

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

@@ -1,48 +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 ObjectIdentity = zod
-    .strictObject({
-    lookup_key: zod.string().optional(),
-    id: zod.uuid(),
-    name: zod.string(),
-})
-    .describe("A catalog object, inlined for display.");

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

@@ -1,181 +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 Order: zod.ZodObject<{
-    coupon_id: zod.ZodOptional<zod.ZodUUID>;
-    coupon: zod.ZodOptional<zod.ZodObject<{
-        lookup_key: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    promotion_code_id: zod.ZodOptional<zod.ZodUUID>;
-    promotion_code: zod.ZodOptional<zod.ZodString>;
-    invoice_id: zod.ZodUUID;
-    invoice: zod.ZodObject<{
-        id: zod.ZodUUID;
-        number: zod.ZodOptional<zod.ZodString>;
-        currency: zod.ZodString;
-        status: zod.ZodEnum<{
-            void: "void";
-            open: "open";
-            draft: "draft";
-            paid: "paid";
-        }>;
-        subtotal: zod.ZodString;
-        discount_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        total: zod.ZodString;
-        amount_paid: zod.ZodString;
-        pre_payment_credit_notes_amount: zod.ZodString;
-        post_payment_credit_notes_amount: zod.ZodString;
-        amount_due: zod.ZodString;
-        amount_refunded: zod.ZodString;
-        due_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    }, zod.z.core.$strict>;
-    paid_with: zod.ZodOptional<zod.ZodObject<{
-        method_type: zod.ZodString;
-        payment_gateway: zod.ZodOptional<zod.ZodString>;
-        payment_method_id: zod.ZodOptional<zod.ZodUUID>;
-        brand: zod.ZodOptional<zod.ZodString>;
-        last4: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>>;
-    account: zod.ZodOptional<zod.ZodObject<{
-        id: zod.ZodInt;
-        name: zod.ZodString;
-        currency: zod.ZodString;
-    }, zod.z.core.$strict>>;
-    change_effective_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    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]>>;
-    billing_account_id: zod.ZodOptional<zod.ZodInt>;
-    currency: zod.ZodString;
-    type: zod.ZodEnum<{
-        new: "new";
-        renew: "renew";
-        modify: "modify";
-    }>;
-    status: zod.ZodEnum<{
-        completed: "completed";
-        failed: "failed";
-        pending: "pending";
-        canceled: "canceled";
-        accepted: "accepted";
-        partially_completed: "partially_completed";
-    }>;
-    change_effective: zod.ZodOptional<zod.ZodEnum<{
-        none: "none";
-        immediate: "immediate";
-        period_end: "period_end";
-    }>>;
-    expires_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    checkout_confirmed_at: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-    created_at: zod.z.ZodISODateTime;
-    items: zod.ZodArray<zod.ZodObject<{
-        renewal_discounts_enabled: zod.ZodOptional<zod.ZodBoolean>;
-        invoice_item_ids: zod.ZodOptional<zod.ZodArray<zod.ZodUUID>>;
-        position: zod.ZodOptional<zod.ZodInt>;
-        configuration: zod.ZodOptional<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>;
-        subscription_id: zod.ZodOptional<zod.ZodUUID>;
-        interval: zod.ZodEnum<{
-            none: "none";
-            day: "day";
-            month: "month";
-            year: "year";
-        }>;
-        interval_count: zod.ZodOptional<zod.ZodInt>;
-        cancellation_policy: zod.ZodOptional<zod.ZodEnum<{
-            immediate: "immediate";
-            period_end: "period_end";
-        }>>;
-        refund_policy: zod.ZodOptional<zod.ZodEnum<{
-            none: "none";
-            prorated: "prorated";
-            short_rate: "short_rate";
-        }>>;
-        monthly_list_amount: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-        short_rate_multiplier: zod.ZodOptional<zod.ZodNullable<zod.ZodString>>;
-        short_rate_threshold_seconds: zod.ZodOptional<zod.ZodNullable<zod.ZodInt>>;
-        recurring_amount: zod.ZodOptional<zod.ZodString>;
-        setup_amount: zod.ZodOptional<zod.ZodString>;
-        type: zod.ZodEnum<{
-            one_time: "one_time";
-            recurring: "recurring";
-        }>;
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        dimensions: zod.ZodRecord<zod.ZodString, zod.ZodString>;
-        tax_amount: zod.ZodOptional<zod.ZodString>;
-        tax_included_amount: zod.ZodOptional<zod.ZodString>;
-        id: zod.ZodUUID;
-        order_id: zod.ZodOptional<zod.ZodUUID>;
-        price_id: zod.ZodUUID;
-        product_id: zod.ZodOptional<zod.ZodString>;
-        product: zod.ZodOptional<zod.ZodObject<{
-            id: zod.ZodString;
-            name: zod.ZodString;
-            description: zod.ZodOptional<zod.ZodString>;
-        }, zod.z.core.$strict>>;
-        plan_id: zod.ZodUUID;
-        plan_name: zod.ZodString;
-        quantity: zod.ZodString;
-        unit_amount: zod.ZodOptional<zod.ZodString>;
-        gross_amount: zod.ZodOptional<zod.ZodString>;
-        discount_amount: zod.ZodOptional<zod.ZodString>;
-        amount: zod.ZodOptional<zod.ZodString>;
-        currency: zod.ZodString;
-        period_start: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-        period_end: zod.ZodOptional<zod.ZodNullable<zod.z.ZodISODateTime>>;
-        status: zod.ZodEnum<{
-            completed: "completed";
-            failed: "failed";
-            pending: "pending";
-            canceled: "canceled";
-        }>;
-    }, zod.z.core.$strict>>;
-}, zod.z.core.$strict>;
-export type Order = zod.input<typeof Order>;
-export type OrderOutput = zod.output<typeof Order>;