@leaflow/sdk 0.154.0 → 0.156.0

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

@@ -1,74 +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 contactNameMax = 255;
-export declare const contactLegalNameMax = 255;
-export declare const contactEmailMax = 255;
-export declare const contactTaxIdMax = 64;
-export declare const contactAddressLine1Max = 255;
-export declare const contactAddressLine2Max = 255;
-export declare const contactAddressCityMax = 128;
-export declare const contactAddressStateMax = 128;
-export declare const contactAddressPostalCodeMax = 32;
-export declare const contactAddressCountryRegExp: RegExp;
-export declare const Contact: zod.ZodObject<{
-    id: zod.ZodUUID;
-    billing_account_id: zod.ZodInt;
-    name: zod.ZodString;
-    legal_name: zod.ZodOptional<zod.ZodString>;
-    email: zod.ZodOptional<zod.ZodString>;
-    tax_id: zod.ZodOptional<zod.ZodString>;
-    address_line1: zod.ZodOptional<zod.ZodString>;
-    address_line2: zod.ZodOptional<zod.ZodString>;
-    address_city: zod.ZodOptional<zod.ZodString>;
-    address_state: zod.ZodOptional<zod.ZodString>;
-    address_postal_code: zod.ZodOptional<zod.ZodString>;
-    address_country: zod.ZodOptional<zod.ZodString>;
-    tax_exempt: zod.ZodEnum<{
-        none: "none";
-        reverse: "reverse";
-        exempt: "exempt";
-    }>;
-    active: zod.ZodBoolean;
-    created_at: zod.z.ZodISODateTime;
-}, zod.z.core.$strict>;
-export type Contact = zod.input<typeof Contact>;
-export type ContactOutput = zod.output<typeof Contact>;

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

@@ -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 const contactNameMax = 255;
-export const contactLegalNameMax = 255;
-export const contactEmailMax = 255;
-export const contactTaxIdMax = 64;
-export const contactAddressLine1Max = 255;
-export const contactAddressLine2Max = 255;
-export const contactAddressCityMax = 128;
-export const contactAddressStateMax = 128;
-export const contactAddressPostalCodeMax = 32;
-export const contactAddressCountryRegExp = new RegExp("^([A-Z]{2})?$");
-export const Contact = zod
-    .strictObject({
-    id: zod.uuid(),
-    billing_account_id: zod.int(),
-    name: zod.string().min(1).max(contactNameMax),
-    legal_name: zod.string().max(contactLegalNameMax).optional(),
-    email: zod.string().max(contactEmailMax).optional(),
-    tax_id: zod.string().max(contactTaxIdMax).optional(),
-    address_line1: zod.string().max(contactAddressLine1Max).optional(),
-    address_line2: zod.string().max(contactAddressLine2Max).optional(),
-    address_city: zod.string().max(contactAddressCityMax).optional(),
-    address_state: zod.string().max(contactAddressStateMax).optional(),
-    address_postal_code: zod.string().max(contactAddressPostalCodeMax).optional(),
-    address_country: zod.string().regex(contactAddressCountryRegExp).optional(),
-    tax_exempt: zod
-        .enum(["none", "exempt", "reverse"])
-        .describe("How tax applies to the customer, as in Stripe: `none` taxes normally, `exempt` charges no tax, `reverse` charges no tax under the reverse-charge mechanism, stated on invoices. Only operators change it."),
-    active: zod.boolean(),
-    created_at: zod.iso.datetime({ offset: true }),
-})
-    .describe("A contact of a billing account with one address. An account can hold several; a contact is not a login.");

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

@@ -1,65 +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 contactCreateNameMax = 255;
-export declare const contactCreateLegalNameMax = 255;
-export declare const contactCreateEmailMax = 255;
-export declare const contactCreateTaxIdMax = 64;
-export declare const contactCreateAddressLine1Max = 255;
-export declare const contactCreateAddressLine2Max = 255;
-export declare const contactCreateAddressCityMax = 128;
-export declare const contactCreateAddressStateMax = 128;
-export declare const contactCreateAddressPostalCodeMax = 32;
-export declare const contactCreateAddressCountryRegExp: RegExp;
-export declare const ContactCreate: zod.ZodObject<{
-    name: zod.ZodString;
-    legal_name: zod.ZodOptional<zod.ZodString>;
-    email: zod.ZodOptional<zod.ZodString>;
-    tax_id: zod.ZodOptional<zod.ZodString>;
-    address_line1: zod.ZodOptional<zod.ZodString>;
-    address_line2: zod.ZodOptional<zod.ZodString>;
-    address_city: zod.ZodOptional<zod.ZodString>;
-    address_state: zod.ZodOptional<zod.ZodString>;
-    address_postal_code: zod.ZodOptional<zod.ZodString>;
-    address_country: zod.ZodOptional<zod.ZodString>;
-}, zod.z.core.$strict>;
-export type ContactCreate = zod.input<typeof ContactCreate>;
-export type ContactCreateOutput = zod.output<typeof ContactCreate>;

package/dist/canopy/v1/generated/validators/contactCreate.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";
-export const contactCreateNameMax = 255;
-export const contactCreateLegalNameMax = 255;
-export const contactCreateEmailMax = 255;
-export const contactCreateTaxIdMax = 64;
-export const contactCreateAddressLine1Max = 255;
-export const contactCreateAddressLine2Max = 255;
-export const contactCreateAddressCityMax = 128;
-export const contactCreateAddressStateMax = 128;
-export const contactCreateAddressPostalCodeMax = 32;
-export const contactCreateAddressCountryRegExp = new RegExp("^([A-Z]{2})?$");
-export const ContactCreate = zod.strictObject({
-    name: zod.string().min(1).max(contactCreateNameMax),
-    legal_name: zod.string().max(contactCreateLegalNameMax).optional(),
-    email: zod.string().max(contactCreateEmailMax).optional(),
-    tax_id: zod.string().max(contactCreateTaxIdMax).optional(),
-    address_line1: zod.string().max(contactCreateAddressLine1Max).optional(),
-    address_line2: zod.string().max(contactCreateAddressLine2Max).optional(),
-    address_city: zod.string().max(contactCreateAddressCityMax).optional(),
-    address_state: zod.string().max(contactCreateAddressStateMax).optional(),
-    address_postal_code: zod.string().max(contactCreateAddressPostalCodeMax).optional(),
-    address_country: zod.string().regex(contactCreateAddressCountryRegExp).optional(),
-});

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

@@ -1,71 +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 ContactList: zod.ZodObject<{
-    items: zod.ZodArray<zod.ZodObject<{
-        id: zod.ZodUUID;
-        billing_account_id: zod.ZodInt;
-        name: zod.ZodString;
-        legal_name: zod.ZodOptional<zod.ZodString>;
-        email: zod.ZodOptional<zod.ZodString>;
-        tax_id: zod.ZodOptional<zod.ZodString>;
-        address_line1: zod.ZodOptional<zod.ZodString>;
-        address_line2: zod.ZodOptional<zod.ZodString>;
-        address_city: zod.ZodOptional<zod.ZodString>;
-        address_state: zod.ZodOptional<zod.ZodString>;
-        address_postal_code: zod.ZodOptional<zod.ZodString>;
-        address_country: zod.ZodOptional<zod.ZodString>;
-        tax_exempt: zod.ZodEnum<{
-            none: "none";
-            reverse: "reverse";
-            exempt: "exempt";
-        }>;
-        active: zod.ZodBoolean;
-        created_at: zod.z.ZodISODateTime;
-    }, zod.z.core.$strict>>;
-    pagination: zod.ZodObject<{
-        page: zod.ZodInt;
-        page_size: zod.ZodInt;
-        total_count: zod.ZodOptional<zod.ZodInt>;
-    }, zod.z.core.$strict>;
-}, zod.z.core.$strict>;
-export type ContactList = zod.input<typeof ContactList>;
-export type ContactListOutput = zod.output<typeof ContactList>;

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

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

@@ -1,66 +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 contactUpdateNameMax = 255;
-export declare const contactUpdateLegalNameMax = 255;
-export declare const contactUpdateEmailMax = 255;
-export declare const contactUpdateTaxIdMax = 64;
-export declare const contactUpdateAddressLine1Max = 255;
-export declare const contactUpdateAddressLine2Max = 255;
-export declare const contactUpdateAddressCityMax = 128;
-export declare const contactUpdateAddressStateMax = 128;
-export declare const contactUpdateAddressPostalCodeMax = 32;
-export declare const contactUpdateAddressCountryRegExp: RegExp;
-export declare const ContactUpdate: zod.ZodObject<{
-    name: zod.ZodOptional<zod.ZodString>;
-    legal_name: zod.ZodOptional<zod.ZodString>;
-    email: zod.ZodOptional<zod.ZodString>;
-    tax_id: zod.ZodOptional<zod.ZodString>;
-    address_line1: zod.ZodOptional<zod.ZodString>;
-    address_line2: zod.ZodOptional<zod.ZodString>;
-    address_city: zod.ZodOptional<zod.ZodString>;
-    address_state: zod.ZodOptional<zod.ZodString>;
-    address_postal_code: zod.ZodOptional<zod.ZodString>;
-    address_country: zod.ZodOptional<zod.ZodString>;
-    active: zod.ZodOptional<zod.ZodBoolean>;
-}, zod.z.core.$strict>;
-export type ContactUpdate = zod.input<typeof ContactUpdate>;
-export type ContactUpdateOutput = zod.output<typeof ContactUpdate>;

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

@@ -1,64 +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 contactUpdateNameMax = 255;
-export const contactUpdateLegalNameMax = 255;
-export const contactUpdateEmailMax = 255;
-export const contactUpdateTaxIdMax = 64;
-export const contactUpdateAddressLine1Max = 255;
-export const contactUpdateAddressLine2Max = 255;
-export const contactUpdateAddressCityMax = 128;
-export const contactUpdateAddressStateMax = 128;
-export const contactUpdateAddressPostalCodeMax = 32;
-export const contactUpdateAddressCountryRegExp = new RegExp("^([A-Z]{2})?$");
-export const ContactUpdate = zod.strictObject({
-    name: zod.string().min(1).max(contactUpdateNameMax).optional(),
-    legal_name: zod.string().max(contactUpdateLegalNameMax).optional(),
-    email: zod.string().max(contactUpdateEmailMax).optional(),
-    tax_id: zod.string().max(contactUpdateTaxIdMax).optional(),
-    address_line1: zod.string().max(contactUpdateAddressLine1Max).optional(),
-    address_line2: zod.string().max(contactUpdateAddressLine2Max).optional(),
-    address_city: zod.string().max(contactUpdateAddressCityMax).optional(),
-    address_state: zod.string().max(contactUpdateAddressStateMax).optional(),
-    address_postal_code: zod.string().max(contactUpdateAddressPostalCodeMax).optional(),
-    address_country: zod.string().regex(contactUpdateAddressCountryRegExp).optional(),
-    active: zod.boolean().optional(),
-});