@leaflow/sdk 0.125.1 → 0.127.0

package/dist/membership/v1/generated/schemas.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
@@ -25,7 +10,7 @@ import { MembershipCreate } from "./validators/membershipCreate.zod.js";
 import { MembershipDowngrade } from "./validators/membershipDowngrade.zod.js";
 import { MembershipUpgrade } from "./validators/membershipUpgrade.zod.js";
 /**
- * Lists the plans on sale, in ascending rank, with their prices and benefits. No authentication is required.
+ * Lists tiers on sale with prices and benefits, ordered by rank.
  * @summary List plans
  */
 export const listPlansQueryPageDefault = 1;
@@ -50,10 +35,10 @@ export const ListPlansQueryParams = zod.strictObject({
         .string()
         .regex(listPlansQueryCurrencyRegExp)
         .optional()
-        .describe("Restricts prices and currency-specific benefits to this currency. All currencies are returned while it is absent."),
+        .describe("Filters prices and currency-specific benefits. Any configured currency is allowed; omit to return all currencies."),
 });
 /**
- * Returns a plan on sale with its prices and benefits. No authentication is required.
+ * Returns a tier on sale with its prices and benefits.
  * @summary Get a plan
  */
 export const GetPlanParams = zod.strictObject({
@@ -65,10 +50,10 @@ export const GetPlanQueryParams = zod.strictObject({
         .string()
         .regex(getPlanQueryCurrencyRegExp)
         .optional()
-        .describe("Restricts prices and currency-specific benefits to this currency."),
+        .describe("Filters prices and currency-specific benefits. Any configured currency is allowed; omit to return all currencies."),
 });
 /**
- * Lists the memberships of a billing account you own, newest first, including ended ones.
+ * Lists memberships of the specified account, including ended memberships, newest first.
  * @summary List memberships
  */
 export const listMembershipsQueryPageDefault = 1;
@@ -88,13 +73,10 @@ export const ListMembershipsQueryParams = zod.strictObject({
         .max(listMembershipsQueryPageSizeMax)
         .default(listMembershipsQueryPageSizeDefault)
         .describe("Items per page. Defaults to 50; at most 200."),
-    billing_account_id: zod.int().min(1).describe("A billing account you own."),
+    billing_account_id: zod.int().min(1).describe("The account to query."),
 });
 /**
- * Places a Billing order for the plan's price on a billing account you own, and returns the pending membership with the order.
- * The membership becomes active, and its first period's benefits are issued, once Billing reports the order ready.
- *
- * Fails with 409 `MEMBERSHIP_EXISTS` when the account already has a pending or active membership, and with 422 `MEMBERSHIP_PLAN_UNAVAILABLE` when the plan is not on sale or has no price or credit in the account's currency. Billing refusals, such as `BILLING_INSUFFICIENT_FUNDS`, are returned as Billing reports them.
+ * Places a purchase order and returns the membership and invoice. Activation follows successful benefit issuance and delivery confirmation. Returns 409 MEMBERSHIP_EXISTS or 422 MEMBERSHIP_PLAN_UNAVAILABLE.
  * @summary Buy a membership
  */
 export const CreateMembershipBody = MembershipCreate;
@@ -105,7 +87,7 @@ export const GetMembershipParams = zod.strictObject({
     membershipId: zod.uuid(),
 });
 /**
- * Lists the paid periods of a membership, newest first, each with the benefits issued for it.
+ * Lists fulfilled periods and their grants, newest first.
  * @summary List membership periods
  */
 export const ListMembershipPeriodsParams = zod.strictObject({
@@ -130,9 +112,7 @@ export const ListMembershipPeriodsQueryParams = zod.strictObject({
         .describe("Items per page. Defaults to 50; at most 200."),
 });
 /**
- * Places a Billing order for the full difference between the current and the chosen plan's period prices. Once Billing reports it ready, the membership moves to the chosen plan for the rest of the period: the difference in credit is issued and the new plan's discount and allowances apply. Renewals are charged at the chosen plan's price.
- *
- * Fails with 409 `MEMBERSHIP_NOT_ACTIVE` unless the membership is active, and with 422 `MEMBERSHIP_UPGRADE_UNAVAILABLE` when the chosen plan does not rank above the current one or no upgrade is priced in the account's currency. A pending upgrade or a scheduled downgrade must finish or be canceled first (409 `MEMBERSHIP_CHANGE_PENDING`).
+ * Places an order for the full-period price difference. The upgrade takes effect after benefit issuance and delivery confirmation; renewal uses the target tier. Returns 409 MEMBERSHIP_NOT_ACTIVE or MEMBERSHIP_CHANGE_PENDING, or 422 MEMBERSHIP_UPGRADE_UNAVAILABLE.
  * @summary Upgrade a membership
  */
 export const UpgradeMembershipParams = zod.strictObject({
@@ -140,9 +120,7 @@ export const UpgradeMembershipParams = zod.strictObject({
 });
 export const UpgradeMembershipBody = MembershipUpgrade;
 /**
- * Schedules a move to a lower-ranked plan at the end of the paid period. Nothing is charged or refunded and the current period keeps its benefits. The membership's `scheduled_plan` shows the pending move.
- *
- * Fails with 409 `MEMBERSHIP_NOT_ACTIVE` unless the membership is active, 409 `MEMBERSHIP_CHANGE_PENDING` while another change is pending, and 422 `MEMBERSHIP_DOWNGRADE_INVALID` when the chosen plan does not rank below the current one or has no price in the account's currency for the membership's billing interval.
+ * Schedules a lower tier for the next period. Current benefits remain valid. Returns 409 MEMBERSHIP_NOT_ACTIVE or MEMBERSHIP_CHANGE_PENDING, or 422 MEMBERSHIP_DOWNGRADE_INVALID.
  * @summary Schedule a downgrade
  */
 export const ScheduleMembershipDowngradeParams = zod.strictObject({
@@ -150,7 +128,7 @@ export const ScheduleMembershipDowngradeParams = zod.strictObject({
 });
 export const ScheduleMembershipDowngradeBody = MembershipDowngrade;
 /**
- * Keeps the current plan at renewal. Fails with 409 `MEMBERSHIP_CHANGE_PENDING` when no downgrade is scheduled.
+ * Cancels the scheduled downgrade. Returns 409 MEMBERSHIP_CHANGE_PENDING if none is scheduled.
  * @summary Cancel a scheduled downgrade
  */
 export const CancelMembershipDowngradeParams = zod.strictObject({

package/dist/membership/v1/generated/validators/accountBalance.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/accountBalance.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/accountIdentity.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/accountIdentity.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/activeResource.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/activeResource.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/activeResourceList.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/activeResourceList.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/allowance.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/allowance.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/allowanceBenefit.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/allowanceBenefit.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
@@ -28,9 +13,9 @@ export const AllowanceBenefit = zod
     meter_id: zod.uuid(),
     meter_name: zod.string(),
     unit: zod.string(),
-    quantity: zod.string().describe("Decimal string in the meter's unit."),
+    quantity: zod.string().describe("Quantity in the meter's unit."),
     dimensions: zod
         .record(zod.string(), zod.string())
-        .describe("Exact dimension values the allowance is limited to, such as a model. Empty means every usage of the meter."),
+        .describe("Meter dimension selectors; empty means unrestricted usage."),
 })
-    .describe("Usage of a service included in each period. Usage with the listed dimension values draws from it before it is charged.");
+    .describe("Metered usage included in each period.");

package/dist/membership/v1/generated/validators/allowanceList.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/allowanceList.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/applicability.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/applicability.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/applicablePlan.zod.d.ts

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";

package/dist/membership/v1/generated/validators/applicablePlan.zod.js

@@ -2,22 +2,7 @@
  * Generated by orval 🍺
  * Do not edit manually.
  * Leaflow Membership API
- * Membership plans and the memberships held by billing accounts.
- *
- * A membership is a prepaid subscription sold through Billing. For each paid period it issues the plan's benefits to the billing account. A plan can carry several benefits across services: credit for chosen services, coupons on purchases and metered usage, and usage allowances such as model tokens, and access to features of other services. Benefits are shared by every project paid for by the account.
- *
- * ## Authentication
- *
- * Plans are public. Memberships require an access token; see the `accessTokenAuth` security scheme. Only the owner of a billing account can read or change its membership; anyone else receives 403 `MEMBERSHIP_ACCOUNT_FORBIDDEN`.
- *
- * ## Conventions
- *
- * - **One membership per billing account.** A pending or active membership must end before another is bought; change plans with upgrade and downgrade instead.
- * - **Payment goes through Billing.** Purchases and upgrades return a Billing order. With `checkout.mode` `deferred`, pay the order's invoice through Billing. Benefits are issued once Billing reports the order ready; every order has an invoice, including a zero-total one, which is paid automatically.
- * - **Cancellation and auto-renewal are managed in Billing** on the membership's `subscription_id`. A cancellation takes effect at the end of the paid period without a refund, and the period's benefits remain until then.
- * - **An upgrade takes effect immediately** for the full difference between the two plans' period prices, whatever remains of the period. The difference in credit is issued in full and the new plan's discount applies from payment. Renewals are charged at the new plan's price.
- * - **A downgrade takes effect at the end of the paid period.** The current period keeps its benefits and nothing is refunded.
- * - **Amounts are decimal strings** in the billing account's currency. There is no currency conversion: a plan without a price or credit in the account's currency cannot be bought with it.
+ * Membership tiers and account memberships. Catalog queries support any configured currency; purchases use the billing account currency.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";