@leaflow/sdk 0.125.1 → 0.126.0

package/dist/membership/v1/generated/validators/listMembershipsParams.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/listPlansParams.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/listPlansParams.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/membership.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/membership.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";
@@ -29,7 +14,7 @@ export const Membership = zod.strictObject({
     plan: PlanSummary,
     status: zod
         .enum(["pending", "active", "ended"])
-        .describe("pending until Billing reports the first order ready; active while paid; ended afterwards."),
+        .describe("Pending until delivery is confirmed; active afterwards; ended when terminated."),
     ended_reason: zod
         .union([
         zod.literal("canceled"),
@@ -39,17 +24,15 @@ export const Membership = zod.strictObject({
         zod.literal(null),
     ])
         .nullable()
-        .describe("canceled: the subscription was canceled and the paid period ended.\nreclaimed: Billing reclaimed the subscription after non-payment.\nrevoked: an operator ended the membership.\nabandoned: the first order was canceled or expired before payment."),
+        .describe("Cancellation, reclamation, operator revocation, or an unfulfilled first order."),
     subscription_id: zod
         .uuid()
         .nullable()
-        .describe("The Billing subscription. Cancel it or change auto-renewal in Billing. Null until Billing reports the first order ready."),
+        .describe("Billing subscription ID; null until activation."),
     current_period: zod
         .union([Period, zod.null()])
-        .describe("The period in effect now. Null when the membership is pending or ended."),
-    scheduled_plan: zod
-        .union([PlanSummary, zod.null()])
-        .describe("The plan a scheduled downgrade moves to at the end of the paid period."),
+        .describe("Current fulfilled period; null while pending or ended."),
+    scheduled_plan: zod.union([PlanSummary, zod.null()]).describe("The scheduled downgrade target."),
     created_at: zod.iso.datetime({ offset: true }),
     ended_at: zod.iso.datetime({ offset: true }).nullable(),
 });

package/dist/membership/v1/generated/validators/membershipCreate.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/membershipCreate.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";
@@ -27,6 +12,6 @@ export const MembershipCreate = zod.strictObject({
     plan_id: zod.uuid(),
     price_id: zod
         .uuid()
-        .describe("One of the plan's prices in the account's currency. It sets the billing interval."),
+        .describe("A tier price matching the account currency and chosen billing interval."),
     checkout: CheckoutOptions.optional(),
 });

package/dist/membership/v1/generated/validators/membershipDowngrade.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/membershipDowngrade.zod.js

@@ -2,27 +2,12 @@
  * 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";
 export const MembershipDowngrade = zod.strictObject({
     plan_id: zod
         .uuid()
-        .describe("A plan ranked below the current one, priced for the membership's billing interval in the account's currency."),
+        .describe("A lower-ranked tier supporting the account currency and billing interval."),
 });

package/dist/membership/v1/generated/validators/membershipList.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/membershipList.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/membershipPurchase.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/membershipPurchase.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,4 +13,4 @@ export const MembershipPurchase = zod
     membership: Membership,
     order: PlacedOrder,
 })
-    .describe("The membership and the Billing order placed for it.");
+    .describe("The membership and its Billing purchase order.");

package/dist/membership/v1/generated/validators/membershipUpgrade.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/membershipUpgrade.zod.js

@@ -2,27 +2,12 @@
  * 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";
 import { CheckoutOptions } from "./checkoutOptions.zod.js";
 export const MembershipUpgrade = zod.strictObject({
-    plan_id: zod.uuid().describe("A plan ranked above the current one."),
+    plan_id: zod.uuid().describe("A higher-ranked target tier."),
     checkout: CheckoutOptions.optional(),
 });

package/dist/membership/v1/generated/validators/money.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/money.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/namedIdentity.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/namedIdentity.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/objectIdentity.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/objectIdentity.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";