@leaflow/sdk 0.0.0-dev.377.gdbef936 → 0.0.0-dev.379.g796e6e7

package/dist/canopy/v1/generated/validators/cancellationPolicy.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 CancellationPolicy = zod
-    .enum(["immediate", "period_end"])
-    .describe("Whether a cancellation of a delivered purchase may take effect immediately or only at the end of its paid term; refunds follow the refund policy. When absent, no cancellation terms were agreed.");

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

@@ -1,84 +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 CancellationRefundPreview: zod.ZodObject<{
-    mode: zod.ZodEnum<{
-        immediate: "immediate";
-        period_end: "period_end";
-    }>;
-    scheduled_at: zod.ZodOptional<zod.z.ZodISODateTime>;
-    proration_date: zod.ZodOptional<zod.z.ZodISODateTime>;
-    currency: zod.ZodString;
-    unused_amount: zod.ZodString;
-    short_rate_surcharge_amount: zod.ZodString;
-    refundable_amount: zod.ZodString;
-    refund_amount: zod.ZodString;
-    credit_amount: zod.ZodString;
-    tax_amount: zod.ZodString;
-    forfeited_amount: zod.ZodString;
-    items: zod.ZodArray<zod.ZodObject<{
-        subscription_id: zod.ZodUUID;
-        plan_id: zod.ZodUUID;
-        plan_name: zod.ZodString;
-        project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-            id: zod.ZodUUID;
-            name: zod.ZodString;
-        }, zod.z.core.$strict>, zod.ZodNull]>>;
-        type: zod.ZodEnum<{
-            one_time: "one_time";
-            recurring: "recurring";
-        }>;
-        usage_type: zod.ZodEnum<{
-            licensed: "licensed";
-            metered: "metered";
-        }>;
-        auto_renew: zod.ZodBoolean;
-        unused_amount: zod.ZodString;
-        short_rate_surcharge_amount: zod.ZodString;
-        refundable_amount: zod.ZodString;
-        refund_amount: zod.ZodString;
-        credit_amount: zod.ZodString;
-        tax_amount: zod.ZodString;
-        forfeited_amount: zod.ZodString;
-    }, zod.z.core.$strict>>;
-}, zod.z.core.$strict>;
-export type CancellationRefundPreview = zod.input<typeof CancellationRefundPreview>;
-export type CancellationRefundPreviewOutput = zod.output<typeof CancellationRefundPreview>;

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

@@ -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";
-import { CancellationPolicy } from "./cancellationPolicy.zod.js";
-import { CancellationRefundPreviewItem } from "./cancellationRefundPreviewItem.zod.js";
-import { Money } from "./money.zod.js";
-export const CancellationRefundPreview = zod
-    .strictObject({
-    mode: CancellationPolicy,
-    scheduled_at: zod.iso
-        .datetime({ offset: true })
-        .optional()
-        .describe("For `period_end`, when release begins, the end of the paid terms."),
-    proration_date: zod.iso
-        .datetime({ offset: true })
-        .optional()
-        .describe("For `immediate`, the second the refund is computed as of. Give it when creating the cancellation."),
-    currency: zod.string(),
-    unused_amount: Money,
-    short_rate_surcharge_amount: Money,
-    refundable_amount: Money,
-    refund_amount: Money,
-    credit_amount: Money,
-    tax_amount: Money,
-    forfeited_amount: Money,
-    items: zod.array(CancellationRefundPreviewItem),
-})
-    .describe("What the cancellation would return, per subscription and in total, as of now. Give `proration_date` and\n`refundable_amount` when creating the cancellation.\n\n- `unused_amount`: before tax, the amount paid for the current periods in proportion to the time remaining.\n- `short_rate_surcharge_amount`: before tax, the part of `forfeited_amount` due to the short rate of the\n  refund policy.\n- `refundable_amount`: what is returned the way it was paid, tax included; `refund_amount` plus\n  `credit_amount`.\n- `refund_amount`: the part returned to the balance or the payment method.\n- `credit_amount`: the part restored to the credit grants that paid.\n- `tax_amount`: the tax included in `refundable_amount`.\n- `forfeited_amount`: before tax, the part of `unused_amount` the refund terms do not return.\n\nMetered and one-time subscriptions show zero; their usage until release is charged as usual.");

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

@@ -1,68 +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 CancellationRefundPreviewItem: zod.ZodObject<{
-    subscription_id: zod.ZodUUID;
-    plan_id: zod.ZodUUID;
-    plan_name: zod.ZodString;
-    project: zod.ZodOptional<zod.ZodUnion<readonly [zod.ZodObject<{
-        id: zod.ZodUUID;
-        name: zod.ZodString;
-    }, zod.z.core.$strict>, zod.ZodNull]>>;
-    type: zod.ZodEnum<{
-        one_time: "one_time";
-        recurring: "recurring";
-    }>;
-    usage_type: zod.ZodEnum<{
-        licensed: "licensed";
-        metered: "metered";
-    }>;
-    auto_renew: zod.ZodBoolean;
-    unused_amount: zod.ZodString;
-    short_rate_surcharge_amount: zod.ZodString;
-    refundable_amount: zod.ZodString;
-    refund_amount: zod.ZodString;
-    credit_amount: zod.ZodString;
-    tax_amount: zod.ZodString;
-    forfeited_amount: zod.ZodString;
-}, zod.z.core.$strict>;
-export type CancellationRefundPreviewItem = zod.input<typeof CancellationRefundPreviewItem>;
-export type CancellationRefundPreviewItemOutput = zod.output<typeof CancellationRefundPreviewItem>;

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

@@ -1,68 +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 { NamedIdentity } from "./namedIdentity.zod.js";
-import { PriceType } from "./priceType.zod.js";
-import { UsageType } from "./usageType.zod.js";
-export const CancellationRefundPreviewItem = zod
-    .strictObject({
-    subscription_id: zod.uuid(),
-    plan_id: zod.uuid(),
-    plan_name: zod.string(),
-    project: zod
-        .union([NamedIdentity, zod.null()])
-        .optional()
-        .describe("The project and its current name. Absent for an account-level purchase or when the project cannot be read."),
-    type: PriceType,
-    usage_type: UsageType,
-    auto_renew: zod
-        .boolean()
-        .describe("Whether automatic renewal is on now. Creating the cancellation turns it off; withdrawing it turns it back on for a metered subscription but not for a licensed one."),
-    unused_amount: Money,
-    short_rate_surcharge_amount: Money,
-    refundable_amount: Money,
-    refund_amount: Money,
-    credit_amount: Money,
-    tax_amount: Money,
-    forfeited_amount: Money,
-})
-    .describe("One subscription of the quoted cancellation.");

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(),
-});