@openmeter/sdk 1.0.0-beta-0f4e99f7857e → 1.0.0-beta-1659b7d437ee

package/dist/src/zod/index.d.ts

@@ -1,9 +1,9 @@
 /**
- * Generated by orval v8.7.0 🍺
+ * Generated by orval v8.15.0 🍺
  * Do not edit manually.
  * OpenMeter Cloud API
  * OpenMeter is a cloud native usage metering service.
-The OpenMeter API allows you to ingest events, query meter usage, and manage resources.
+ * The OpenMeter API allows you to ingest events, query meter usage, and manage resources.
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from 'zod';
@@ -548,8 +548,8 @@ export declare const GetAddonQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Soft delete add-on by id.
-
-Once a add-on is deleted it cannot be undeleted.
+ *
+ * Once a add-on is deleted it cannot be undeleted.
  * @summary Delete add-on
  */
 export declare const deleteAddonPathAddonIdRegExp: RegExp;
@@ -698,8 +698,8 @@ export declare const UninstallAppParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Update the Stripe API key.
-
-⚠️ __Deprecated__: Use [`PUT /api/v1/apps/{id}`](#tag/apps/put/api/v1/apps/{id}) instead.
+ *
+ * ⚠️ __Deprecated__: Use [`PUT /api/v1/apps/{id}`](#tag/apps/put/api/v1/apps/{id}) instead.
  * @deprecated
  * @summary Update Stripe API key
  */
@@ -729,12 +729,12 @@ export declare const AppStripeWebhookBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List customer overrides using the specified filters.
-
-The response will include the customer override values and the merged billing profile values.
-
-If the includeAllCustomers is set to true, the list contains all customers. This mode is
-useful for getting the current effective billing workflow settings for all users regardless
-if they have customer orverrides or not.
+ *
+ * The response will include the customer override values and the merged billing profile values.
+ *
+ * If the includeAllCustomers is set to true, the list contains all customers. This mode is
+ * useful for getting the current effective billing workflow settings for all users regardless
+ * if they have customer orverrides or not.
  * @summary List customer overrides
  */
 export declare const listBillingProfileCustomerOverridesQueryBillingProfileItemRegExp: RegExp;
@@ -772,10 +772,10 @@ export declare const ListBillingProfileCustomerOverridesQueryParams: zod.ZodObje
 }, zod.z.core.$strip>;
 /**
  * The customer override can be used to pin a given customer to a billing profile
-different from the default one.
-
-This can be used to test the effect of different billing profiles before making them
-the default ones or have different workflow settings for example for enterprise customers.
+ * different from the default one.
+ *
+ * This can be used to test the effect of different billing profiles before making them
+ * the default ones or have different workflow settings for example for enterprise customers.
  * @summary Create a new or update a customer override
  */
 export declare const upsertBillingProfileCustomerOverridePathCustomerIdRegExp: RegExp;
@@ -788,11 +788,11 @@ export declare const UpsertBillingProfileCustomerOverrideBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get a customer override by customer id.
-
-The response will include the customer override values and the merged billing profile values.
-
-If the customer override is not found, the default billing profile's values are returned. This behavior
-allows for getting a merged profile regardless of the customer override existence.
+ *
+ * The response will include the customer override values and the merged billing profile values.
+ *
+ * If the customer override is not found, the default billing profile's values are returned. This behavior
+ * allows for getting a merged profile regardless of the customer override existence.
  * @summary Get a customer override
  */
 export declare const getBillingProfileCustomerOverridePathCustomerIdRegExp: RegExp;
@@ -807,9 +807,9 @@ export declare const GetBillingProfileCustomerOverrideQueryParams: zod.ZodObject
 }, zod.z.core.$strip>;
 /**
  * Delete a customer override by customer id.
-
-This will remove the customer override and the customer will be subject to the default
-billing profile's settings again.
+ *
+ * This will remove the customer override and the customer will be subject to the default
+ * billing profile's settings again.
  * @summary Delete a customer override
  */
 export declare const deleteBillingProfileCustomerOverridePathCustomerIdRegExp: RegExp;
@@ -818,13 +818,13 @@ export declare const DeleteBillingProfileCustomerOverrideParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Create a new pending line item (charge).
-
-This call is used to create a new pending line item for the customer if required a new
-gathering invoice will be created.
-
-A new invoice will be created if:
-- there is no invoice in gathering state
-- the currency of the line item doesn't match the currency of any invoices in gathering state
+ *
+ * This call is used to create a new pending line item for the customer if required a new
+ * gathering invoice will be created.
+ *
+ * A new invoice will be created if:
+ * - there is no invoice in gathering state
+ * - the currency of the line item doesn't match the currency of any invoices in gathering state
  * @summary Create pending line items
  */
 export declare const createPendingInvoiceLinePathCustomerIdRegExp: RegExp;
@@ -1052,10 +1052,10 @@ export declare const CreatePendingInvoiceLineBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Simulate an invoice for a customer.
-
-This call will simulate an invoice for a customer based on the pending line items.
-
-The call will return the total amount of the invoice and the line items that will be included in the invoice.
+ *
+ * This call will simulate an invoice for a customer based on the pending line items.
+ *
+ * The call will return the total amount of the invoice and the line items that will be included in the invoice.
  * @summary Simulate an invoice for a customer
  */
 export declare const simulateInvoicePathCustomerIdRegExp: RegExp;
@@ -1291,11 +1291,11 @@ export declare const SimulateInvoiceBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List invoices based on the specified filters.
-
-The expand option can be used to include additional information (besides the invoice header and totals)
-in the response. For example by adding the expand=lines option the invoice lines will be included in the response.
-
-Gathering invoices will always show the current usage calculated on the fly.
+ *
+ * The expand option can be used to include additional information (besides the invoice header and totals)
+ * in the response. For example by adding the expand=lines option the invoice lines will be included in the response.
+ *
+ * Gathering invoices will always show the current usage calculated on the fly.
  * @summary List invoices
  */
 export declare const listInvoicesQueryCustomersItemRegExp: RegExp;
@@ -1346,14 +1346,14 @@ export declare const ListInvoicesQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Create a new invoice from the pending line items.
-
-This should be only called if for some reason we need to invoice a customer outside of the normal billing cycle.
-
-When creating an invoice, the pending line items will be marked as invoiced and the invoice will be created with the total amount of the pending items.
-
-New pending line items will be created for the period between now() and the next billing cycle's begining date for any metered item.
-
-The call can return multiple invoices if the pending line items are in different currencies.
+ *
+ * This should be only called if for some reason we need to invoice a customer outside of the normal billing cycle.
+ *
+ * When creating an invoice, the pending line items will be marked as invoiced and the invoice will be created with the total amount of the pending items.
+ *
+ * New pending line items will be created for the period between now() and the next billing cycle's begining date for any metered item.
+ *
+ * The call can return multiple invoices if the pending line items are in different currencies.
  * @summary Invoice a customer based on the pending line items
  */
 export declare const invoicePendingLinesActionBodyFiltersOneLineIdsItemRegExp: RegExp;
@@ -1368,8 +1368,8 @@ export declare const InvoicePendingLinesActionBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get an invoice by ID.
-
-Gathering invoices will always show the current usage calculated on the fly.
+ *
+ * Gathering invoices will always show the current usage calculated on the fly.
  * @summary Get an invoice
  */
 export declare const getInvoicePathInvoiceIdRegExp: RegExp;
@@ -1387,10 +1387,10 @@ export declare const GetInvoiceQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Delete an invoice
-
-Only invoices that are in the draft (or earlier) status can be deleted.
-
-Invoices that are post finalization can only be voided.
+ *
+ * Only invoices that are in the draft (or earlier) status can be deleted.
+ *
+ * Invoices that are post finalization can only be voided.
  * @summary Delete an invoice
  */
 export declare const deleteInvoicePathInvoiceIdRegExp: RegExp;
@@ -1399,8 +1399,8 @@ export declare const DeleteInvoiceParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Update an invoice
-
-Only invoices in draft or earlier status can be updated.
+ *
+ * Only invoices in draft or earlier status can be updated.
  * @summary Update an invoice
  */
 export declare const updateInvoicePathInvoiceIdRegExp: RegExp;
@@ -1707,10 +1707,10 @@ export declare const UpdateInvoiceBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Advance the invoice's state to the next status.
-
-The call doesn't "approve the invoice", it only advances the invoice to the next status if the transition would be automatic.
-
-The action can be called when the invoice's statusDetails' actions field contain the "advance" action.
+ *
+ * The call doesn't "approve the invoice", it only advances the invoice to the next status if the transition would be automatic.
+ *
+ * The action can be called when the invoice's statusDetails' actions field contain the "advance" action.
  * @summary Advance the invoice's state to the next status
  */
 export declare const advanceInvoiceActionPathInvoiceIdRegExp: RegExp;
@@ -1719,12 +1719,12 @@ export declare const AdvanceInvoiceActionParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Approve an invoice and start executing the payment workflow.
-
-This call instantly sends the invoice to the customer using the configured billing profile app.
-
-This call is valid in two invoice statuses:
-- `draft`: the invoice will be sent to the customer, the invluce state becomes issued
-- `manual_approval_needed`: the invoice will be sent to the customer, the invoice state becomes issued
+ *
+ * This call instantly sends the invoice to the customer using the configured billing profile app.
+ *
+ * This call is valid in two invoice statuses:
+ * - `draft`: the invoice will be sent to the customer, the invluce state becomes issued
+ * - `manual_approval_needed`: the invoice will be sent to the customer, the invoice state becomes issued
  * @summary Send the invoice to the customer
  */
 export declare const approveInvoiceActionPathInvoiceIdRegExp: RegExp;
@@ -1733,8 +1733,8 @@ export declare const ApproveInvoiceActionParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Retry advancing the invoice after a failed attempt.
-
-The action can be called when the invoice's statusDetails' actions field contain the "retry" action.
+ *
+ * The action can be called when the invoice's statusDetails' actions field contain the "retry" action.
  * @summary Retry advancing the invoice after a failed attempt.
  */
 export declare const retryInvoiceActionPathInvoiceIdRegExp: RegExp;
@@ -1743,11 +1743,11 @@ export declare const RetryInvoiceActionParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Snapshot quantities for usage based line items.
-
-This call will snapshot the quantities for all usage based line items in the invoice.
-
-This call is only valid in `draft.waiting_for_collection` status, where the collection period
-can be skipped using this action.
+ *
+ * This call will snapshot the quantities for all usage based line items in the invoice.
+ *
+ * This call is only valid in `draft.waiting_for_collection` status, where the collection period
+ * can be skipped using this action.
  * @summary Snapshot quantities for usage based line items
  */
 export declare const snapshotQuantitiesInvoiceActionPathInvoiceIdRegExp: RegExp;
@@ -1756,8 +1756,8 @@ export declare const SnapshotQuantitiesInvoiceActionParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Recalculate an invoice's tax amounts (using the app set in the customer's billing profile)
-
-Note: charges might apply, depending on the tax provider.
+ *
+ * Note: charges might apply, depending on the tax provider.
  * @summary Recalculate an invoice's tax amounts
  */
 export declare const recalculateInvoiceTaxActionPathInvoiceIdRegExp: RegExp;
@@ -1766,10 +1766,10 @@ export declare const RecalculateInvoiceTaxActionParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Void an invoice
-
-Only invoices that have been alread issued can be voided.
-
-Voiding an invoice will mark it as voided, the user can specify how to handle the voided line items.
+ *
+ * Only invoices that have been alread issued can be voided.
+ *
+ * Voiding an invoice will mark it as voided, the user can specify how to handle the voided line items.
  * @summary Void an invoice
  */
 export declare const voidInvoiceActionPathInvoiceIdRegExp: RegExp;
@@ -1811,10 +1811,10 @@ export declare const VoidInvoiceActionBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List all billing profiles matching the specified filters.
-
-The expand option can be used to include additional information (besides the billing profile)
-in the response. For example by adding the expand=apps option the apps used by the billing profile
-will be included in the response.
+ *
+ * The expand option can be used to include additional information (besides the billing profile)
+ * in the response. For example by adding the expand=apps option the apps used by the billing profile
+ * will be included in the response.
  * @summary List billing profiles
  */
 export declare const listBillingProfilesQueryIncludeArchivedDefault = false;
@@ -1842,9 +1842,9 @@ export declare const ListBillingProfilesQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Create a new billing profile
-
-Billing profiles are representations of a customer's billing information. Customer overrides
-can be applied to a billing profile to customize the billing behavior for a specific customer.
+ *
+ * Billing profiles are representations of a customer's billing information. Customer overrides
+ * can be applied to a billing profile to customize the billing behavior for a specific customer.
  * @summary Create a new billing profile
  */
 export declare const createBillingProfileBodyNameMax = 256;
@@ -1954,11 +1954,11 @@ export declare const CreateBillingProfileBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Delete a billing profile by id.
-
-Only such billing profiles can be deleted that are:
-- not the default one
-- not pinned to any customer using customer overrides
-- only have finalized invoices
+ *
+ * Only such billing profiles can be deleted that are:
+ * - not the default one
+ * - not pinned to any customer using customer overrides
+ * - only have finalized invoices
  * @summary Delete a billing profile
  */
 export declare const deleteBillingProfilePathIdRegExp: RegExp;
@@ -1967,10 +1967,10 @@ export declare const DeleteBillingProfileParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get a billing profile by id.
-
-The expand option can be used to include additional information (besides the billing profile)
-in the response. For example by adding the expand=apps option the apps used by the billing profile
-will be included in the response.
+ *
+ * The expand option can be used to include additional information (besides the billing profile)
+ * in the response. For example by adding the expand=apps option the apps used by the billing profile
+ * will be included in the response.
  * @summary Get a billing profile
  */
 export declare const getBillingProfilePathIdRegExp: RegExp;
@@ -1984,9 +1984,9 @@ export declare const GetBillingProfileQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Update a billing profile by id.
-
-The apps field cannot be updated directly, if an app change is desired a new
-profile should be created.
+ *
+ * The apps field cannot be updated directly, if an app change is desired a new
+ * profile should be created.
  * @summary Update a billing profile
  */
 export declare const updateBillingProfilePathIdRegExp: RegExp;
@@ -2507,7 +2507,7 @@ export declare const GetCustomerEntitlementValueQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get stripe app data for a customer.
-Only returns data if the customer billing profile is linked to a stripe app.
+ * Only returns data if the customer billing profile is linked to a stripe app.
  * @summary Get customer stripe app data
  */
 export declare const getCustomerStripeAppDataPathCustomerIdOrKeyOneRegExp: RegExp;
@@ -2517,7 +2517,7 @@ export declare const GetCustomerStripeAppDataParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Upsert stripe app data for a customer.
-Only updates data if the customer billing profile is linked to a stripe app.
+ * Only updates data if the customer billing profile is linked to a stripe app.
  * @summary Upsert customer stripe app data
  */
 export declare const upsertCustomerStripeAppDataPathCustomerIdOrKeyOneRegExp: RegExp;
@@ -2531,10 +2531,10 @@ export declare const UpsertCustomerStripeAppDataBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Create Stripe customer portal session.
-Only returns URL if the customer billing profile is linked to a stripe app and customer.
-
-Useful to redirect the customer to the Stripe customer portal to manage their payment methods,
-change their billing address and access their invoice history.
+ * Only returns URL if the customer billing profile is linked to a stripe app and customer.
+ *
+ * Useful to redirect the customer to the Stripe customer portal to manage their payment methods,
+ * change their billing address and access their invoice history.
  * @summary Create Stripe customer portal session
  */
 export declare const createCustomerStripePortalSessionPathCustomerIdOrKeyOneRegExp: RegExp;
@@ -2580,10 +2580,10 @@ export declare const ListCustomerSubscriptionsQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List all entitlements for all the subjects and features. This endpoint is intended for administrative purposes only.
-To fetch the entitlements of a specific subject please use the /api/v1/subjects/{subjectKeyOrID}/entitlements endpoint.
-If page is provided that takes precedence and the paginated response is returned.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/entitlements`](#tag/entitlements/get/api/v2/entitlements) instead.
+ * To fetch the entitlements of a specific subject please use the /api/v1/subjects/{subjectKeyOrID}/entitlements endpoint.
+ * If page is provided that takes precedence and the paginated response is returned.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/entitlements`](#tag/entitlements/get/api/v2/entitlements) instead.
  * @deprecated
  * @summary List all entitlements
  */
@@ -2620,8 +2620,8 @@ export declare const ListEntitlementsQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get entitlement by ID.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/entitlements/{entitlementId}`](#tag/entitlements/get/api/v2/entitlements/{entitlementId}) instead.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/entitlements/{entitlementId}`](#tag/entitlements/get/api/v2/entitlements/{entitlementId}) instead.
  * @deprecated
  * @summary Get entitlement by ID
  */
@@ -2631,8 +2631,8 @@ export declare const GetEntitlementByIdParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List ingested events within a time range.
-
-If the from query param is not provided it defaults to last 72 hours.
+ *
+ * If the from query param is not provided it defaults to last 72 hours.
  * @summary List ingested events
  */
 export declare const listEventsQueryClientIdMax = 36;
@@ -2654,9 +2654,8 @@ export declare const ListEventsQueryParams: zod.ZodObject<{
  * Ingests an event or batch of events following the CloudEvents specification.
  * @summary Ingest events
  */
-export declare const ingestEventsBodyOneSpecversionDefault = "1.0";
-export declare const ingestEventsBodyTwoItemSpecversionDefault = "1.0";
-export declare const IngestEventsBody: zod.ZodUnion<readonly [zod.ZodObject<{
+export declare const ingestEventsBodySpecversionDefault = "1.0";
+export declare const IngestEventsBody: zod.ZodObject<{
     data: zod.ZodOptional<zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>>;
     datacontenttype: zod.ZodOptional<zod.ZodNullable<zod.ZodEnum<{
         "application/json": "application/json";
@@ -2668,19 +2667,7 @@ export declare const IngestEventsBody: zod.ZodUnion<readonly [zod.ZodObject<{
     subject: zod.z.ZodCoercedString<unknown>;
     time: zod.ZodOptional<zod.ZodNullable<zod.z.ZodCoercedDate<unknown>>>;
     type: zod.z.ZodCoercedString<unknown>;
-}, zod.z.core.$strip>, zod.ZodArray<zod.ZodObject<{
-    data: zod.ZodOptional<zod.ZodNullable<zod.ZodRecord<zod.ZodString, zod.ZodUnknown>>>;
-    datacontenttype: zod.ZodOptional<zod.ZodNullable<zod.ZodEnum<{
-        "application/json": "application/json";
-    }>>>;
-    dataschema: zod.ZodOptional<zod.ZodNullable<zod.ZodURL>>;
-    id: zod.z.ZodCoercedString<unknown>;
-    source: zod.z.ZodCoercedString<unknown>;
-    specversion: zod.ZodDefault<zod.z.ZodCoercedString<unknown>>;
-    subject: zod.z.ZodCoercedString<unknown>;
-    time: zod.ZodOptional<zod.ZodNullable<zod.z.ZodCoercedDate<unknown>>>;
-    type: zod.z.ZodCoercedString<unknown>;
-}, zod.z.core.$strip>>]>;
+}, zod.z.core.$strip>;
 /**
  * List features.
  * @summary List features
@@ -2715,8 +2702,8 @@ export declare const ListFeaturesQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Features are either metered or static. A feature is metered if meterSlug is provided at creation.
-For metered features you can pass additional filters that will be applied when calculating feature usage, based on the meter's groupBy fields.
-Meters with SUM, COUNT, UNIQUE_COUNT and LATEST aggregations are supported for features.
+ * For metered features you can pass additional filters that will be applied when calculating feature usage, based on the meter's groupBy fields.
+ * Meters with SUM, COUNT, UNIQUE_COUNT and LATEST aggregations are supported for features.
  * @summary Create feature
  */
 export declare const createFeatureBodyKeyMax = 64;
@@ -2784,9 +2771,9 @@ export declare const GetFeatureParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Archive a feature by ID.
-
-Once a feature is archived it cannot be unarchived. If a feature is archived, new entitlements cannot be created for it, but archiving the feature does not affect existing entitlements.
-This means, if you want to create a new feature with the same key, and then create entitlements for it, the previous entitlements have to be deleted first on a per subject basis.
+ *
+ * Once a feature is archived it cannot be unarchived. If a feature is archived, new entitlements cannot be created for it, but archiving the feature does not affect existing entitlements.
+ * This means, if you want to create a new feature with the same key, and then create entitlements for it, the previous entitlements have to be deleted first on a per subject basis.
  * @summary Delete feature
  */
 export declare const DeleteFeatureParams: zod.ZodObject<{
@@ -2794,10 +2781,10 @@ export declare const DeleteFeatureParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List all grants for all the subjects and entitlements. This endpoint is intended for administrative purposes only.
-To fetch the grants of a specific entitlement please use the /api/v1/subjects/{subjectKeyOrID}/entitlements/{entitlementOrFeatureID}/grants endpoint.
-If page is provided that takes precedence and the paginated response is returned.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/grants`](#tag/entitlements/get/api/v2/grants) instead.
+ * To fetch the grants of a specific entitlement please use the /api/v1/subjects/{subjectKeyOrID}/entitlements/{entitlementOrFeatureID}/grants endpoint.
+ * If page is provided that takes precedence and the paginated response is returned.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/grants`](#tag/entitlements/get/api/v2/grants) instead.
  * @deprecated
  * @summary List grants
  */
@@ -2830,7 +2817,7 @@ export declare const ListGrantsQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Voiding a grant means it is no longer valid, it doesn't take part in further balance calculations. Voiding a grant does not retroactively take effect, meaning any usage that has already been attributed to the grant will remain, but future usage cannot be burnt down from the grant.
-For example, if you have a single grant for your metered entitlement with an initial amount of 100, and so far 60 usage has been metered, the grant (and the entitlement itself) would have a balance of 40. If you then void that grant, balance becomes 0, but the 60 previous usage will not be affected.
+ * For example, if you have a single grant for your metered entitlement with an initial amount of 100, and so far 60 usage has been metered, the grant (and the entitlement itself) would have a balance of 40. If you then void that grant, balance becomes 0, but the 60 previous usage will not be affected.
  * @summary Void grant
  */
 export declare const VoidGrantParams: zod.ZodObject<{
@@ -2903,7 +2890,7 @@ export declare const MarketplaceAppAPIKeyInstallBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Install an app via OAuth.
-Returns a URL to start the OAuth 2.0 flow.
+ * Returns a URL to start the OAuth 2.0 flow.
  * @summary Get OAuth2 install URL
  */
 export declare const MarketplaceOAuth2InstallGetURLParams: zod.ZodObject<{
@@ -2915,7 +2902,7 @@ export declare const MarketplaceOAuth2InstallGetURLParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Authorize OAuth2 code.
-Verifies the OAuth code and exchanges it for a token and refresh token
+ * Verifies the OAuth code and exchanges it for a token and refresh token
  * @summary Install app via OAuth2
  */
 export declare const MarketplaceOAuth2InstallAuthorizeParams: zod.ZodObject<{
@@ -3203,8 +3190,8 @@ export declare const GetNotificationChannelParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Soft delete notification channel by id.
-
-Once a notification channel is deleted it cannot be undeleted.
+ *
+ * Once a notification channel is deleted it cannot be undeleted.
  * @summary Delete a notification channel
  */
 export declare const deleteNotificationChannelPathChannelIdRegExp: RegExp;
@@ -3433,8 +3420,8 @@ export declare const GetNotificationRuleParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Soft delete notification rule by id.
-
-Once a notification rule is deleted it cannot be undeleted.
+ *
+ * Once a notification rule is deleted it cannot be undeleted.
  * @summary Delete a notification rule
  */
 export declare const deleteNotificationRulePathRuleIdRegExp: RegExp;
@@ -3765,7 +3752,7 @@ export declare const CreatePlanBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Create a new draft version from plan.
-It returns error if there is already a plan in draft or planId does not reference the latest published version.
+ * It returns error if there is already a plan in draft or planId does not reference the latest published version.
  * @deprecated
  * @summary New draft plan
  */
@@ -4058,8 +4045,8 @@ export declare const GetPlanQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Soft delete plan by plan.id.
-
-Once a plan is deleted it cannot be undeleted.
+ *
+ * Once a plan is deleted it cannot be undeleted.
  * @summary Delete plan
  */
 export declare const deletePlanPathPlanIdRegExp: RegExp;
@@ -4146,8 +4133,8 @@ export declare const GetPlanAddonParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Delete add-on assignment for plan.
-
-Once a plan is deleted it cannot be undeleted.
+ *
+ * Once a plan is deleted it cannot be undeleted.
  * @summary Delete add-on assignment for plan
  */
 export declare const deletePlanAddonPathPlanIdRegExp: RegExp;
@@ -4352,11 +4339,11 @@ export declare const CreateStripeCheckoutSessionBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Upserts a subject. Creates or updates subject.
-
-If the subject doesn't exist, it will be created.
-If the subject exists, it will be partially updated with the provided fields.
-
-⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
+ *
+ * If the subject doesn't exist, it will be created.
+ * If the subject exists, it will be partially updated with the provided fields.
+ *
+ * ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
  * @deprecated
  * @summary Upsert subject
  */
@@ -4378,8 +4365,8 @@ export declare const UpsertSubjectBody: zod.ZodArray<zod.ZodObject<{
 }, zod.z.core.$strip>>;
 /**
  * Get subject by ID or key.
-
-⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
+ *
+ * ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
  * @deprecated
  * @summary Get subject
  */
@@ -4388,8 +4375,8 @@ export declare const GetSubjectParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Delete subject by ID or key.
-
-⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
+ *
+ * ⚠️ __Deprecated__: Subjects as managable entities are being depracated, use customers with subject key usage attribution instead.
  * @deprecated
  * @summary Delete subject
  */
@@ -4398,16 +4385,16 @@ export declare const DeleteSubjectParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * OpenMeter has three types of entitlements: metered, boolean, and static. The type property determines the type of entitlement. The underlying feature has to be compatible with the entitlement type specified in the request (e.g., a metered entitlement needs a feature associated with a meter).
-
-- Boolean entitlements define static feature access, e.g. "Can use SSO authentication".
-- Static entitlements let you pass along a configuration while granting access, e.g. "Using this feature with X Y settings" (passed in the config).
-- Metered entitlements have many use cases, from setting up usage-based access to implementing complex credit systems.  Example: The customer can use 10000 AI tokens during the usage period of the entitlement.
-
-A given subject can only have one active (non-deleted) entitlement per featureKey. If you try to create a new entitlement for a featureKey that already has an active entitlement, the request will fail with a 409 error.
-
-Once an entitlement is created you cannot modify it, only delete it.
-
-⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements) instead.
+ *
+ * - Boolean entitlements define static feature access, e.g. "Can use SSO authentication".
+ * - Static entitlements let you pass along a configuration while granting access, e.g. "Using this feature with X Y settings" (passed in the config).
+ * - Metered entitlements have many use cases, from setting up usage-based access to implementing complex credit systems.  Example: The customer can use 10000 AI tokens during the usage period of the entitlement.
+ *
+ * A given subject can only have one active (non-deleted) entitlement per featureKey. If you try to create a new entitlement for a featureKey that already has an active entitlement, the request will fail with a 409 error.
+ *
+ * Once an entitlement is created you cannot modify it, only delete it.
+ *
+ * ⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements) instead.
  * @deprecated
  * @summary Create a subject entitlement
  */
@@ -4493,8 +4480,8 @@ export declare const CreateEntitlementBody: zod.ZodUnion<readonly [zod.ZodObject
 }, zod.z.core.$strip>]>;
 /**
  * List all entitlements for a subject. For checking entitlement access, use the /value endpoint instead.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements) instead.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements) instead.
  * @deprecated
  * @summary List subject entitlements
  */
@@ -4507,8 +4494,8 @@ export declare const ListSubjectEntitlementsQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List all grants issued for an entitlement. The entitlement can be defined either by its id or featureKey.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
  * @deprecated
  * @summary List subject entitlement grants
  */
@@ -4528,18 +4515,18 @@ export declare const ListEntitlementGrantsQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Grants define a behavior of granting usage for a metered entitlement. They can have complicated recurrence and rollover rules, thanks to which you can define a wide range of access patterns with a single grant, in most cases you don't have to periodically create new grants. You can only issue grants for active metered entitlements.
-
-A grant defines a given amount of usage that can be consumed for the entitlement. The grant is in effect between its effective date and its expiration date. Specifying both is mandatory for new grants.
-
-Grants have a priority setting that determines their order of use. Lower numbers have higher priority, with 0 being the highest priority.
-
-Grants can have a recurrence setting intended to automate the manual reissuing of grants. For example, a daily recurrence is equal to reissuing that same grant every day (ignoring rollover settings).
-
-Rollover settings define what happens to the remaining balance of a grant at a reset. Balance_After_Reset = MIN(MaxRolloverAmount, MAX(Balance_Before_Reset, MinRolloverAmount))
-
-Grants cannot be changed once created, only deleted. This is to ensure that balance is deterministic regardless of when it is queried.
-
-⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
+ *
+ * A grant defines a given amount of usage that can be consumed for the entitlement. The grant is in effect between its effective date and its expiration date. Specifying both is mandatory for new grants.
+ *
+ * Grants have a priority setting that determines their order of use. Lower numbers have higher priority, with 0 being the highest priority.
+ *
+ * Grants can have a recurrence setting intended to automate the manual reissuing of grants. For example, a daily recurrence is equal to reissuing that same grant every day (ignoring rollover settings).
+ *
+ * Rollover settings define what happens to the remaining balance of a grant at a reset. Balance_After_Reset = MIN(MaxRolloverAmount, MAX(Balance_Before_Reset, MinRolloverAmount))
+ *
+ * Grants cannot be changed once created, only deleted. This is to ensure that balance is deterministic regardless of when it is queried.
+ *
+ * ⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants) instead.
  * @deprecated
  * @summary Create subject entitlement grant
  */
@@ -4582,10 +4569,10 @@ export declare const CreateGrantBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Overriding an entitlement creates a new entitlement from the provided inputs and soft deletes the previous entitlement for the provided subject-feature pair. If the previous entitlement is already deleted or otherwise doesnt exist, the override will fail.
-
-This endpoint is useful for upgrades, downgrades, or other changes to entitlements that require a new entitlement to be created with zero downtime.
-
-⚠️ __Deprecated__: Use [`PUT /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override`](#tag/entitlements/put/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override) instead.
+ *
+ * This endpoint is useful for upgrades, downgrades, or other changes to entitlements that require a new entitlement to be created with zero downtime.
+ *
+ * ⚠️ __Deprecated__: Use [`PUT /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override`](#tag/entitlements/put/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/override) instead.
  * @deprecated
  * @summary Override subject entitlement
  */
@@ -4672,10 +4659,10 @@ export declare const OverrideEntitlementBody: zod.ZodUnion<readonly [zod.ZodObje
 }, zod.z.core.$strip>]>;
 /**
  * This endpoint should be used for access checks and enforcement. All entitlement types share the hasAccess property in their value response, but multiple other properties are returned based on the entitlement type.
-
-For convenience reasons, /value works with both entitlementId and featureKey.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value) instead.
+ *
+ * For convenience reasons, /value works with both entitlementId and featureKey.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/value) instead.
  * @deprecated
  * @summary Get subject entitlement value
  */
@@ -4688,8 +4675,8 @@ export declare const GetEntitlementValueQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get entitlement by id. For checking entitlement access, use the /value endpoint instead.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
  * @deprecated
  * @summary Get subject entitlement
  */
@@ -4699,9 +4686,9 @@ export declare const GetEntitlementParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Deleting an entitlement revokes access to the associated feature. As a single subject can only have one entitlement per featureKey, when "migrating" features you have to delete the old entitlements as well.
-As access and status checks can be historical queries, deleting an entitlement populates the deletedAt timestamp. When queried for a time before that, the entitlement is still considered active, you cannot have retroactive changes to access, which is important for, among other things, auditing.
-
-⚠️ __Deprecated__: Use [`DELETE /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/delete/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
+ * As access and status checks can be historical queries, deleting an entitlement populates the deletedAt timestamp. When queried for a time before that, the entitlement is still considered active, you cannot have retroactive changes to access, which is important for, among other things, auditing.
+ *
+ * ⚠️ __Deprecated__: Use [`DELETE /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}`](#tag/entitlements/delete/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}) instead.
  * @deprecated
  * @summary Delete subject entitlement
  */
@@ -4711,12 +4698,12 @@ export declare const DeleteEntitlementParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Returns historical balance and usage data for the entitlement. The queried history can span accross multiple reset events.
-
-BurndownHistory returns a continous history of segments, where the segments are seperated by events that changed either the grant burndown priority or the usage period.
-
-WindowedHistory returns windowed usage data for the period enriched with balance information and the list of grants that were being burnt down in that window.
-
-⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history) instead.
+ *
+ * BurndownHistory returns a continous history of segments, where the segments are seperated by events that changed either the grant burndown priority or the usage period.
+ *
+ * WindowedHistory returns windowed usage data for the period enriched with balance information and the list of grants that were being burnt down in that window.
+ *
+ * ⚠️ __Deprecated__: Use [`GET /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history`](#tag/entitlements/get/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/history) instead.
  * @deprecated
  * @summary Get subject entitlement history
  */
@@ -4738,10 +4725,10 @@ export declare const GetEntitlementHistoryQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Reset marks the start of a new usage period for the entitlement and initiates grant rollover. At the start of a period usage is zerod out and grants are rolled over based on their rollover settings. It would typically be synced with the subjects billing period to enforce usage based on their subscription.
-
-Usage is automatically reset for metered entitlements based on their usage period, but this endpoint allows to manually reset it at any time. When doing so the period anchor of the entitlement can be changed if needed.
-
-⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset) instead.
+ *
+ * Usage is automatically reset for metered entitlements based on their usage period, but this endpoint allows to manually reset it at any time. When doing so the period anchor of the entitlement can be changed if needed.
+ *
+ * ⚠️ __Deprecated__: Use [`POST /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset`](#tag/entitlements/post/api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/reset) instead.
  * @deprecated
  * @summary Reset subject entitlement
  */
@@ -5075,7 +5062,7 @@ export declare const GetSubscriptionQueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Batch processing commands for manipulating running subscriptions.
-The key format is `/phases/{phaseKey}` or `/phases/{phaseKey}/items/{itemKey}`.
+ * The key format is `/phases/{phaseKey}` or `/phases/{phaseKey}/items/{itemKey}`.
  * @summary Edit subscription
  */
 export declare const editSubscriptionPathSubscriptionIdRegExp: RegExp;
@@ -5440,7 +5427,7 @@ export declare const UpdateSubscriptionAddonBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Cancels the subscription.
-Will result in a scheduling conflict if there are other subscriptions scheduled to start after the cancellation time.
+ * Will result in a scheduling conflict if there are other subscriptions scheduled to start after the cancellation time.
  * @summary Cancel subscription
  */
 export declare const cancelSubscriptionPathSubscriptionIdRegExp: RegExp;
@@ -5455,7 +5442,7 @@ export declare const CancelSubscriptionBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Closes a running subscription and starts a new one according to the specification.
-Can be used for upgrades, downgrades, and plan changes.
+ * Can be used for upgrades, downgrades, and plan changes.
  * @summary Change subscription
  */
 export declare const changeSubscriptionPathSubscriptionIdRegExp: RegExp;
@@ -5760,8 +5747,8 @@ export declare const ChangeSubscriptionBody: zod.ZodUnion<readonly [zod.ZodObjec
 }, zod.z.core.$strip>]>;
 /**
  * Migrates the subscripiton to the provided version of the current plan.
-If possible, the migration will be done immediately.
-If not, the migration will be scheduled to the end of the current billing period.
+ * If possible, the migration will be done immediately.
+ * If not, the migration will be scheduled to the end of the current billing period.
  * @summary Migrate subscription
  */
 export declare const migrateSubscriptionPathSubscriptionIdRegExp: RegExp;
@@ -5780,7 +5767,7 @@ export declare const MigrateSubscriptionBody: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Restores a canceled subscription.
-Any subscription scheduled to start later will be deleted and this subscription will be continued indefinitely.
+ * Any subscription scheduled to start later will be deleted and this subscription will be continued indefinitely.
  * @deprecated
  * @summary Restore subscription
  */
@@ -5798,14 +5785,14 @@ export declare const UnscheduleCancelationParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * OpenMeter has three types of entitlements: metered, boolean, and static. The type property determines the type of entitlement. The underlying feature has to be compatible with the entitlement type specified in the request (e.g., a metered entitlement needs a feature associated with a meter).
-
-- Boolean entitlements define static feature access, e.g. "Can use SSO authentication".
-- Static entitlements let you pass along a configuration while granting access, e.g. "Using this feature with X Y settings" (passed in the config).
-- Metered entitlements have many use cases, from setting up usage-based access to implementing complex credit systems.  Example: The customer can use 10000 AI tokens during the usage period of the entitlement.
-
-A given customer can only have one active (non-deleted) entitlement per featureKey. If you try to create a new entitlement for a featureKey that already has an active entitlement, the request will fail with a 409 error.
-
-Once an entitlement is created you cannot modify it, only delete it.
+ *
+ * - Boolean entitlements define static feature access, e.g. "Can use SSO authentication".
+ * - Static entitlements let you pass along a configuration while granting access, e.g. "Using this feature with X Y settings" (passed in the config).
+ * - Metered entitlements have many use cases, from setting up usage-based access to implementing complex credit systems.  Example: The customer can use 10000 AI tokens during the usage period of the entitlement.
+ *
+ * A given customer can only have one active (non-deleted) entitlement per featureKey. If you try to create a new entitlement for a featureKey that already has an active entitlement, the request will fail with a 409 error.
+ *
+ * Once an entitlement is created you cannot modify it, only delete it.
  * @summary Create a customer entitlement
  */
 export declare const createCustomerEntitlementV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -5957,7 +5944,7 @@ export declare const ListCustomerEntitlementsV2QueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Get entitlement by feature key. For checking entitlement access, use the /value endpoint instead.
-If featureKey is used, the entitlement is resolved for the current timestamp.
+ * If featureKey is used, the entitlement is resolved for the current timestamp.
  * @summary Get customer entitlement
  */
 export declare const getCustomerEntitlementV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -5970,7 +5957,7 @@ export declare const GetCustomerEntitlementV2Params: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Deleting an entitlement revokes access to the associated feature. As a single customer can only have one entitlement per featureKey, when "migrating" features you have to delete the old entitlements as well.
-As access and status checks can be historical queries, deleting an entitlement populates the deletedAt timestamp. When queried for a time before that, the entitlement is still considered active, you cannot have retroactive changes to access, which is important for, among other things, auditing.
+ * As access and status checks can be historical queries, deleting an entitlement populates the deletedAt timestamp. When queried for a time before that, the entitlement is still considered active, you cannot have retroactive changes to access, which is important for, among other things, auditing.
  * @summary Delete customer entitlement
  */
 export declare const deleteCustomerEntitlementV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -6020,16 +6007,16 @@ export declare const ListCustomerEntitlementGrantsV2QueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Grants define a behavior of granting usage for a metered entitlement. They can have complicated recurrence and rollover rules, thanks to which you can define a wide range of access patterns with a single grant, in most cases you don't have to periodically create new grants. You can only issue grants for active metered entitlements.
-
-A grant defines a given amount of usage that can be consumed for the entitlement. The grant is in effect between its effective date and its expiration date. Specifying both is mandatory for new grants.
-
-Grants have a priority setting that determines their order of use. Lower numbers have higher priority, with 0 being the highest priority.
-
-Grants can have a recurrence setting intended to automate the manual reissuing of grants. For example, a daily recurrence is equal to reissuing that same grant every day (ignoring rollover settings).
-
-Rollover settings define what happens to the remaining balance of a grant at a reset. Balance_After_Reset = MIN(MaxRolloverAmount, MAX(Balance_Before_Reset, MinRolloverAmount))
-
-Grants cannot be changed once created, only deleted. This is to ensure that balance is deterministic regardless of when it is queried.
+ *
+ * A grant defines a given amount of usage that can be consumed for the entitlement. The grant is in effect between its effective date and its expiration date. Specifying both is mandatory for new grants.
+ *
+ * Grants have a priority setting that determines their order of use. Lower numbers have higher priority, with 0 being the highest priority.
+ *
+ * Grants can have a recurrence setting intended to automate the manual reissuing of grants. For example, a daily recurrence is equal to reissuing that same grant every day (ignoring rollover settings).
+ *
+ * Rollover settings define what happens to the remaining balance of a grant at a reset. Balance_After_Reset = MIN(MaxRolloverAmount, MAX(Balance_Before_Reset, MinRolloverAmount))
+ *
+ * Grants cannot be changed once created, only deleted. This is to ensure that balance is deterministic regardless of when it is queried.
  * @summary Create customer entitlement grant
  */
 export declare const createCustomerEntitlementGrantV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -6075,10 +6062,10 @@ export declare const CreateCustomerEntitlementGrantV2Body: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Returns historical balance and usage data for the entitlement. The queried history can span accross multiple reset events.
-
-BurndownHistory returns a continous history of segments, where the segments are seperated by events that changed either the grant burndown priority or the usage period.
-
-WindowedHistory returns windowed usage data for the period enriched with balance information and the list of grants that were being burnt down in that window.
+ *
+ * BurndownHistory returns a continous history of segments, where the segments are seperated by events that changed either the grant burndown priority or the usage period.
+ *
+ * WindowedHistory returns windowed usage data for the period enriched with balance information and the list of grants that were being burnt down in that window.
  * @summary Get customer entitlement history
  */
 export declare const getCustomerEntitlementHistoryV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -6103,8 +6090,8 @@ export declare const GetCustomerEntitlementHistoryV2QueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * Overriding an entitlement creates a new entitlement from the provided inputs and soft deletes the previous entitlement for the provided customer-feature pair. If the previous entitlement is already deleted or otherwise doesnt exist, the override will fail.
-
-This endpoint is useful for upgrades, downgrades, or other changes to entitlements that require a new entitlement to be created with zero downtime.
+ *
+ * This endpoint is useful for upgrades, downgrades, or other changes to entitlements that require a new entitlement to be created with zero downtime.
  * @summary Override customer entitlement
  */
 export declare const overrideCustomerEntitlementV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -6232,8 +6219,8 @@ export declare const OverrideCustomerEntitlementV2Body: zod.ZodUnion<readonly [z
 }, zod.z.core.$strip>]>;
 /**
  * Reset marks the start of a new usage period for the entitlement and initiates grant rollover. At the start of a period usage is zerod out and grants are rolled over based on their rollover settings. It would typically be synced with the customers billing period to enforce usage based on their subscription.
-
-Usage is automatically reset for metered entitlements based on their usage period, but this endpoint allows to manually reset it at any time. When doing so the period anchor of the entitlement can be changed if needed.
+ *
+ * Usage is automatically reset for metered entitlements based on their usage period, but this endpoint allows to manually reset it at any time. When doing so the period anchor of the entitlement can be changed if needed.
  * @summary Reset customer entitlement
  */
 export declare const resetCustomerEntitlementUsageV2PathCustomerIdOrKeyOneRegExp: RegExp;
@@ -6266,7 +6253,7 @@ export declare const GetCustomerEntitlementValueV2QueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List all entitlements for all the customers and features. This endpoint is intended for administrative purposes only.
-To fetch the entitlements of a specific subject please use the /api/v2/customers/{customerIdOrKey}/entitlements endpoint.
+ * To fetch the entitlements of a specific subject please use the /api/v2/customers/{customerIdOrKey}/entitlements endpoint.
  * @summary List all entitlements
  */
 export declare const listEntitlementsV2QueryExcludeInactiveDefault = false;
@@ -6323,8 +6310,8 @@ export declare const ListEventsV2QueryParams: zod.ZodObject<{
 }, zod.z.core.$strip>;
 /**
  * List all grants for all the customers and entitlements. This endpoint is intended for administrative purposes only.
-To fetch the grants of a specific entitlement please use the /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants endpoint.
-If page is provided that takes precedence and the paginated response is returned.
+ * To fetch the grants of a specific entitlement please use the /api/v2/customers/{customerIdOrKey}/entitlements/{entitlementIdOrFeatureKey}/grants endpoint.
+ * If page is provided that takes precedence and the paginated response is returned.
  * @summary List grants
  */
 export declare const listGrantsV2QueryCustomerItemOneRegExp: RegExp;