orb-billing 4.48.0 → 4.50.0

package/resources/subscriptions.d.ts

@@ -17,7 +17,7 @@ export declare class Subscriptions extends APIResource {
      *
      * The default configuration for subscriptions in Orb is **In-advance billing** and
      * **Beginning of month alignment** (see
-     * [Subscription](../guides/concepts#subscription) for more details).
+     * [Subscription](/core-concepts##subscription) for more details).
      *
      * In order to change the alignment behavior, Orb also supports billing
      * subscriptions on the day of the month they are created. If
@@ -42,9 +42,10 @@ export declare class Subscriptions extends APIResource {
      * subscription being created. This is useful when a customer has prices that
      * differ from the default prices for a specific plan.
      *
-     * :::info This feature is only available for accounts that have migrated to
-     * Subscription Overrides Version 2. You can find your Subscription Overrides
-     * Version at the bottom of your [Plans page](https://app.withorb.com/plans) :::
+     * <Note>
+     * This feature is only available for accounts that have migrated to Subscription Overrides Version 2. You can find your
+     * Subscription Overrides Version at the bottom of your [Plans page](https://app.withorb.com/plans)
+     * </Note>
      *
      * ### Adding Prices
      *
@@ -52,17 +53,17 @@ export declare class Subscriptions extends APIResource {
      * the list must specify an existing add-on price with a `price_id` or
      * `external_price_id` field, or create a new add-on price by including an object
      * with the key `price`, identical to what would be used in the request body for
-     * the [create price endpoint](../reference/create-price). See the
-     * [Price resource](../reference/price) for the specification of different price
-     * model configurations possible in this object.
+     * the [create price endpoint](/api-reference/price/create-price). See the
+     * [Price resource](/product-catalog/price-configuration) for the specification of
+     * different price model configurations possible in this object.
      *
      * If the plan has phases, each object in the list must include a number with
      * `plan_phase_order` key to indicate which phase the price should be added to.
      *
      * An object in the list can specify an optional `start_date` and optional
      * `end_date`. This is equivalent to creating a price interval with the
-     * [add/edit price intervals endpoint](../reference/add-edit-price-intervals). If
-     * unspecified, the start or end date of the phase or subscription will be used.
+     * [add/edit price intervals endpoint](/api-reference/price-interval/add-or-edit-price-intervals).
+     * If unspecified, the start or end date of the phase or subscription will be used.
      *
      * An object in the list can specify an optional `minimum_amount`,
      * `maximum_amount`, or `discounts`. This will create adjustments which apply only
@@ -87,14 +88,15 @@ export declare class Subscriptions extends APIResource {
      * either referencing an existing add-on price with a `price_id` or
      * `external_price_id` field, or by creating a new add-on price by including an
      * object with the key `price`, identical to what would be used in the request body
-     * for the [create price endpoint](../reference/create-price). See the
-     * [Price resource](../reference/price) for the specification of different price
-     * model configurations possible in this object.
+     * for the [create price endpoint](/api-reference/price/create-price). See the
+     * [Price resource](/product-catalog/price-configuration) for the specification of
+     * different price model configurations possible in this object.
      *
      * For fixed fees, an object in the list can supply a `fixed_price_quantity`
      * instead of a `price`, `price_id`, or `external_price_id` field. This will update
      * only the quantity for the price, similar to the
-     * [Update price quantity](../reference/update-fixed-fee-quantity) endpoint.
+     * [Update price quantity](/api-reference/subscription/update-price-quantity)
+     * endpoint.
      *
      * The replacement price will have the same phase, if applicable, and the same
      * start and end dates as the price it replaces.
@@ -113,7 +115,7 @@ export declare class Subscriptions extends APIResource {
      * To add adjustments, provide a list of objects with the key `add_adjustments`. An
      * object in the list must include an object with the key `adjustment`, identical
      * to the adjustment object in the
-     * [add/edit price intervals endpoint](../reference/add-edit-price-intervals).
+     * [add/edit price intervals endpoint](/api-reference/price-interval/add-or-edit-price-intervals).
      *
      * If the plan has phases, each object in the list must include a number with
      * `plan_phase_order` key to indicate which phase the adjustment should be added
@@ -136,17 +138,17 @@ export declare class Subscriptions extends APIResource {
      * replace with the `replaces_adjustment_id` key, and it must specify an adjustment
      * to replace it with by including an object with the key `adjustment`, identical
      * to the adjustment object in the
-     * [add/edit price intervals endpoint](../reference/add-edit-price-intervals).
+     * [add/edit price intervals endpoint](/api-reference/price-interval/add-or-edit-price-intervals).
      *
      * The replacement adjustment will have the same phase, if applicable, and the same
      * start and end dates as the adjustment it replaces.
      *
      * ## Price overrides (DEPRECATED)
      *
-     * :::info Price overrides are being phased out in favor adding/removing/replacing
-     * prices. (See
-     * [Customize your customer's subscriptions](../reference/create-subscription#customize-your-customers-subscriptions))
-     * :::
+     * <Note>
+     * Price overrides are being phased out in favor adding/removing/replacing prices. (See
+     * [Customize your customer's subscriptions](/api-reference/subscription/create-subscription))
+     * </Note>
      *
      * Price overrides are used to update some or all prices in a plan for the specific
      * subscription being created. This is useful when a new customer has negotiated a
@@ -155,9 +157,9 @@ export declare class Subscriptions extends APIResource {
      * To override prices, provide a list of objects with the key `price_overrides`.
      * The price object in the list of overrides is expected to contain the existing
      * price id, the `model_type` and configuration. (See the
-     * [Price resource](../reference/price) for the specification of different price
-     * model configurations.) The numerical values can be updated, but the billable
-     * metric, cadence, type, and name of a price can not be overridden.
+     * [Price resource](/product-catalog/price-configuration) for the specification of
+     * different price model configurations.) The numerical values can be updated, but
+     * the billable metric, cadence, type, and name of a price can not be overridden.
      *
      * ### Maximums and Minimums
      *
@@ -271,9 +273,9 @@ export declare class Subscriptions extends APIResource {
     update(subscriptionId: string, body: SubscriptionUpdateParams, options?: Core.RequestOptions): Core.APIPromise<Subscription>;
     /**
      * This endpoint returns a list of all subscriptions for an account as a
-     * [paginated](../reference/pagination) list, ordered starting from the most
+     * [paginated](/api-reference/pagination) list, ordered starting from the most
      * recently created subscription. For a full discussion of the subscription
-     * resource, see [Subscription](../guides/concepts#subscription).
+     * resource, see [Subscription](/core-concepts##subscription).
      *
      * Subscriptions can be filtered for a specific customer by using either the
      * customer_id or external_customer_id query parameters. To filter subscriptions
@@ -343,11 +345,11 @@ export declare class Subscriptions extends APIResource {
      * current period. If the cancellation is before the most recently issued invoice,
      * Orb will void the intervening invoice and generate a new one based on the new
      * dates for the subscription. See the section on
-     * [cancellation behaviors](../guides/product-catalog/creating-subscriptions.md#cancellation-behaviors).
+     * [cancellation behaviors](/product-catalog/creating-subscriptions#cancellation-behaviors).
      */
     cancel(subscriptionId: string, body: SubscriptionCancelParams, options?: Core.RequestOptions): Core.APIPromise<SubscriptionCancelResponse>;
     /**
-     * This endpoint is used to fetch a [Subscription](../guides/concepts#subscription)
+     * This endpoint is used to fetch a [Subscription](/core-concepts##subscription)
      * given an identifier.
      */
     fetch(subscriptionId: string, options?: Core.RequestOptions): Core.APIPromise<Subscription>;
@@ -366,7 +368,7 @@ export declare class Subscriptions extends APIResource {
     fetchCosts(subscriptionId: string, query?: SubscriptionFetchCostsParams, options?: Core.RequestOptions): Core.APIPromise<SubscriptionFetchCostsResponse>;
     fetchCosts(subscriptionId: string, options?: Core.RequestOptions): Core.APIPromise<SubscriptionFetchCostsResponse>;
     /**
-     * This endpoint returns a [paginated](../reference/pagination) list of all plans
+     * This endpoint returns a [paginated](/api-reference/pagination) list of all plans
      * associated with a subscription along with their start and end dates. This list
      * contains the subscription's initial plan along with past and future plan
      * changes.
@@ -573,9 +575,9 @@ export declare class Subscriptions extends APIResource {
     fetchUsage(subscriptionId: string, options?: Core.RequestOptions): Core.APIPromise<SubscriptionUsage>;
     /**
      * This endpoint is used to add and edit subscription
-     * [price intervals](../reference/price-interval). By making modifications to a
-     * subscription’s price intervals, you can
-     * [flexibly and atomically control the billing behavior of a subscription](../guides/product-catalog/modifying-subscriptions).
+     * [price intervals](/api-reference/price-interval/add-or-edit-price-intervals). By
+     * making modifications to a subscription’s price intervals, you can
+     * [flexibly and atomically control the billing behavior of a subscription](/product-catalog/modifying-subscriptions).
      *
      * ## Adding price intervals
      *
@@ -691,9 +693,10 @@ export declare class Subscriptions extends APIResource {
      * subscription when you schedule the plan change. This is useful when a customer
      * has prices that differ from the default prices for a specific plan.
      *
-     * :::info This feature is only available for accounts that have migrated to
-     * Subscription Overrides Version 2. You can find your Subscription Overrides
-     * Version at the bottom of your [Plans page](https://app.withorb.com/plans) :::
+     * <Note>
+     * This feature is only available for accounts that have migrated to Subscription Overrides Version 2. You can find your
+     * Subscription Overrides Version at the bottom of your [Plans page](https://app.withorb.com/plans)
+     * </Note>
      *
      * ### Adding Prices
      *
@@ -701,17 +704,17 @@ export declare class Subscriptions extends APIResource {
      * the list must specify an existing add-on price with a `price_id` or
      * `external_price_id` field, or create a new add-on price by including an object
      * with the key `price`, identical to what would be used in the request body for
-     * the [create price endpoint](../reference/create-price). See the
-     * [Price resource](../reference/price) for the specification of different price
-     * model configurations possible in this object.
+     * the [create price endpoint](/api-reference/price/create-price). See the
+     * [Price resource](/product-catalog/price-configuration) for the specification of
+     * different price model configurations possible in this object.
      *
      * If the plan has phases, each object in the list must include a number with
      * `plan_phase_order` key to indicate which phase the price should be added to.
      *
      * An object in the list can specify an optional `start_date` and optional
      * `end_date`. This is equivalent to creating a price interval with the
-     * [add/edit price intervals endpoint](../reference/add-edit-price-intervals). If
-     * unspecified, the start or end date of the phase or subscription will be used.
+     * [add/edit price intervals endpoint](/api-reference/price-interval/add-or-edit-price-intervals).
+     * If unspecified, the start or end date of the phase or subscription will be used.
      *
      * An object in the list can specify an optional `minimum_amount`,
      * `maximum_amount`, or `discounts`. This will create adjustments which apply only
@@ -736,14 +739,15 @@ export declare class Subscriptions extends APIResource {
      * either referencing an existing add-on price with a `price_id` or
      * `external_price_id` field, or by creating a new add-on price by including an
      * object with the key `price`, identical to what would be used in the request body
-     * for the [create price endpoint](../reference/create-price). See the
-     * [Price resource](../reference/price) for the specification of different price
-     * model configurations possible in this object.
+     * for the [create price endpoint](/api-reference/price/create-price). See the
+     * [Price resource](/product-catalog/price-configuration) for the specification of
+     * different price model configurations possible in this object.
      *
      * For fixed fees, an object in the list can supply a `fixed_price_quantity`
      * instead of a `price`, `price_id`, or `external_price_id` field. This will update
      * only the quantity for the price, similar to the
-     * [Update price quantity](../reference/update-fixed-fee-quantity) endpoint.
+     * [Update price quantity](/api-reference/subscription/update-price-quantity)
+     * endpoint.
      *
      * The replacement price will have the same phase, if applicable, and the same
      * start and end dates as the price it replaces.
@@ -762,7 +766,7 @@ export declare class Subscriptions extends APIResource {
      * To add adjustments, provide a list of objects with the key `add_adjustments`. An
      * object in the list must include an object with the key `adjustment`, identical
      * to the adjustment object in the
-     * [add/edit price intervals endpoint](../reference/add-edit-price-intervals).
+     * [add/edit price intervals endpoint](/api-reference/price-interval/add-or-edit-price-intervals).
      *
      * If the plan has phases, each object in the list must include a number with
      * `plan_phase_order` key to indicate which phase the adjustment should be added
@@ -785,17 +789,17 @@ export declare class Subscriptions extends APIResource {
      * replace with the `replaces_adjustment_id` key, and it must specify an adjustment
      * to replace it with by including an object with the key `adjustment`, identical
      * to the adjustment object in the
-     * [add/edit price intervals endpoint](../reference/add-edit-price-intervals).
+     * [add/edit price intervals endpoint](/api-reference/price-interval/add-or-edit-price-intervals).
      *
      * The replacement adjustment will have the same phase, if applicable, and the same
      * start and end dates as the adjustment it replaces.
      *
      * ## Price overrides (DEPRECATED)
      *
-     * :::info Price overrides are being phased out in favor adding/removing/replacing
-     * prices. (See
-     * [Customize your customer's subscriptions](../reference/schedule-plan-change#customize-your-customers-subscriptions))
-     * :::
+     * <Note>
+     * Price overrides are being phased out in favor adding/removing/replacing prices. (See
+     * [Customize your customer's subscriptions](/api-reference/subscription/schedule-plan-change))
+     * </Note>
      *
      * Price overrides are used to update some or all prices in a plan for the specific
      * subscription being created. This is useful when a new customer has negotiated a
@@ -804,9 +808,9 @@ export declare class Subscriptions extends APIResource {
      * To override prices, provide a list of objects with the key `price_overrides`.
      * The price object in the list of overrides is expected to contain the existing
      * price id, the `model_type` and configuration. (See the
-     * [Price resource](../reference/price) for the specification of different price
-     * model configurations.) The numerical values can be updated, but the billable
-     * metric, cadence, type, and name of a price can not be overridden.
+     * [Price resource](/product-catalog/price-configuration) for the specification of
+     * different price model configurations.) The numerical values can be updated, but
+     * the billable metric, cadence, type, and name of a price can not be overridden.
      *
      * ### Maximums, and minimums
      *
@@ -826,7 +830,7 @@ export declare class Subscriptions extends APIResource {
      * By default, Orb calculates the prorated difference in any fixed fees when making
      * a plan change, adjusting the customer balance as needed. For details on this
      * behavior, see
-     * [Modifying subscriptions](../guides/product-catalog/modifying-subscriptions.md#prorations-for-in-advance-fees).
+     * [Modifying subscriptions](/product-catalog/modifying-subscriptions#prorations-for-in-advance-fees).
      */
     schedulePlanChange(subscriptionId: string, body: SubscriptionSchedulePlanChangeParams, options?: Core.RequestOptions): Core.APIPromise<SubscriptionSchedulePlanChangeResponse>;
     /**
@@ -900,8 +904,8 @@ export declare class SubscriptionsPage extends Page<Subscription> {
 export declare class SubscriptionFetchScheduleResponsesPage extends Page<SubscriptionFetchScheduleResponse> {
 }
 /**
- * A [subscription](../guides/core-concepts.mdx#subscription) represents the
- * purchase of a plan by a customer.
+ * A [subscription](/core-concepts#subscription) represents the purchase of a plan
+ * by a customer.
  *
  * By default, subscriptions begin on the day that they're created and renew
  * automatically for each billing cycle at the cadence that's configured in the
@@ -966,7 +970,7 @@ export interface Subscription {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -975,9 +979,8 @@ export interface Subscription {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -1018,9 +1021,9 @@ export interface Subscription {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -1374,229 +1377,8 @@ export declare namespace Subscription {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -1722,7 +1504,7 @@ export interface SubscriptionCreateResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -1731,9 +1513,8 @@ export interface SubscriptionCreateResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -1774,9 +1555,9 @@ export interface SubscriptionCreateResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -2130,229 +1911,8 @@ export declare namespace SubscriptionCreateResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -2423,7 +1983,7 @@ export interface SubscriptionCancelResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -2432,9 +1992,8 @@ export interface SubscriptionCancelResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -2475,9 +2034,9 @@ export interface SubscriptionCancelResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -2831,229 +2390,8 @@ export declare namespace SubscriptionCancelResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -3106,229 +2444,8 @@ export declare namespace SubscriptionFetchCostsResponse {
              * is serialized differently in a given Price object. The model_type field
              * determines the key for the configuration object that is present.
              *
-             * ## Unit pricing
-             *
-             * With unit pricing, each unit costs a fixed amount.
-             *
-             * ```json
-             * {
-             *     ...
-             *     "model_type": "unit",
-             *     "unit_config": {
-             *         "unit_amount": "0.50"
-             *     }
-             *     ...
-             * }
-             * ```
-             *
-             * ## Tiered pricing
-             *
-             * In tiered pricing, the cost of a given unit depends on the tier range that it
-             * falls into, where each tier range is defined by an upper and lower bound. For
-             * example, the first ten units may cost $0.50 each and all units thereafter may
-             * cost $0.10 each.
-             *
-             * ```json
-             * {
-             *     ...
-             *     "model_type": "tiered",
-             *     "tiered_config": {
-             *         "tiers": [
-             *             {
-             *                 "first_unit": 1,
-             *                 "last_unit": 10,
-             *                 "unit_amount": "0.50"
-             *             },
-             *             {
-             *                 "first_unit": 11,
-             *                 "last_unit": null,
-             *                 "unit_amount": "0.10"
-             *             }
-             *         ]
-             *     }
-             *     ...
-             * ```
-             *
-             * ## Bulk pricing
-             *
-             * Bulk pricing applies when the number of units determine the cost of all units.
-             * For example, if you've bought less than 10 units, they may each be $0.50 for a
-             * total of $5.00. Once you've bought more than 10 units, all units may now be
-             * priced at $0.40 (i.e. 101 units total would be $40.40).
-             *
-             * ```json
-             * {
-             *     ...
-             *     "model_type": "bulk",
-             *     "bulk_config": {
-             *         "tiers": [
-             *             {
-             *                 "maximum_units": 10,
-             *                 "unit_amount": "0.50"
-             *             },
-             *             {
-             *                 "maximum_units": 1000,
-             *                 "unit_amount": "0.40"
-             *             }
-             *         ]
-             *     }
-             *     ...
-             * }
-             * ```
-             *
-             * ## Package pricing
-             *
-             * Package pricing defines the size or granularity of a unit for billing purposes.
-             * For example, if the package size is set to 5, then 4 units will be billed as 5
-             * and 6 units will be billed at 10.
-             *
-             * ```json
-             * {
-             *     ...
-             *     "model_type": "package",
-             *     "package_config": {
-             *         "package_amount": "0.80",
-             *         "package_size": 10
-             *     }
-             *     ...
-             * }
-             * ```
-             *
-             * ## BPS pricing
-             *
-             * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-             * percent (the number of basis points to charge), as well as a cap per event to
-             * assess. For example, this would allow you to assess a fee of 0.25% on every
-             * payment you process, with a maximum charge of $25 per payment.
-             *
-             * ```json
-             * {
-             *     ...
-             *     "model_type": "bps",
-             *     "bps_config": {
-             *        "bps": 125,
-             *        "per_unit_maximum": "11.00"
-             *     }
-             *     ...
-             *  }
-             * ```
-             *
-             * ## Bulk BPS pricing
-             *
-             * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-             * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-             * a given event depends on the tier range that the billing period falls into. Each
-             * tier range is defined by an upper bound. For example, after $1.5M of payment
-             * volume is reached, each individual payment may have a lower cap or a smaller
-             * take-rate.
-             *
-             * ```json
-             *     ...
-             *     "model_type": "bulk_bps",
-             *     "bulk_bps_config": {
-             *         "tiers": [
-             *            {
-             *                 "maximum_amount": "1000000.00",
-             *                 "bps": 125,
-             *                 "per_unit_maximum": "19.00"
-             *            },
-             *           {
-             *                 "maximum_amount": null,
-             *                 "bps": 115,
-             *                 "per_unit_maximum": "4.00"
-             *             }
-             *         ]
-             *     }
-             *     ...
-             * }
-             * ```
-             *
-             * ## Tiered BPS pricing
-             *
-             * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-             * event's applicable parameter is a function of its marginal addition to the
-             * period total. Similar to tiered pricing, the BPS parameters of a given event
-             * depends on the tier range that it falls into, where each tier range is defined
-             * by an upper and lower bound. For example, the first few payments may have a 0.8
-             * BPS take-rate and all payments after a specific volume may incur a take-rate of
-             * 0.5 BPS each.
-             *
-             * ```json
-             *     ...
-             *     "model_type": "tiered_bps",
-             *     "tiered_bps_config": {
-             *         "tiers": [
-             *            {
-             *                 "minimum_amount": "0",
-             *                 "maximum_amount": "1000000.00",
-             *                 "bps": 125,
-             *                 "per_unit_maximum": "19.00"
-             *            },
-             *           {
-             *                 "minimum_amount": "1000000.00",
-             *                 "maximum_amount": null,
-             *                 "bps": 115,
-             *                 "per_unit_maximum": "4.00"
-             *             }
-             *         ]
-             *     }
-             *     ...
-             * }
-             * ```
-             *
-             * ## Matrix pricing
-             *
-             * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-             * `dimensions` defines the two event property values evaluated in this pricing
-             * model. In a one-dimensional matrix, the second value is `null`. Every
-             * configuration has a list of `matrix_values` which give the unit prices for
-             * specified property values. In a one-dimensional matrix, the matrix values will
-             * have `dimension_values` where the second value of the pair is null. If an event
-             * does not match any of the dimension values in the matrix, it will resort to the
-             * `default_unit_amount`.
-             *
-             * ```json
-             * {
-             *     "model_type": "matrix"
-             *     "matrix_config": {
-             *         "default_unit_amount": "3.00",
-             *         "dimensions": [
-             *             "cluster_name",
-             *             "region"
-             *         ],
-             *         "matrix_values": [
-             *             {
-             *                 "dimension_values": [
-             *                     "alpha",
-             *                     "west"
-             *                 ],
-             *                 "unit_amount": "2.00"
-             *             },
-             *             ...
-             *         ]
-             *     }
-             * }
-             * ```
-             *
-             * ## Fixed fees
-             *
-             * Fixed fees are prices that are applied independent of usage quantities, and
-             * follow unit pricing. They also have an additional parameter
-             * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-             * the quantity of units applied.
-             *
-             * ```json
-             * {
-             *     ...
-             *     "id": "price_id",
-             *     "model_type": "unit",
-             *     "unit_config": {
-             *        "unit_amount": "2.00"
-             *     },
-             *     "fixed_price_quantity": 3.0
-             *     ...
-             * }
-             * ```
+             * For more on the types of prices, see
+             * [the core concepts documentation](/core-concepts#plan-and-price)
              */
             price: PricesAPI.Price;
             /**
@@ -3410,7 +2527,7 @@ export interface SubscriptionPriceIntervalsResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -3419,9 +2536,8 @@ export interface SubscriptionPriceIntervalsResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -3462,9 +2578,9 @@ export interface SubscriptionPriceIntervalsResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -3818,229 +2934,8 @@ export declare namespace SubscriptionPriceIntervalsResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -4111,7 +3006,7 @@ export interface SubscriptionSchedulePlanChangeResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -4120,9 +3015,8 @@ export interface SubscriptionSchedulePlanChangeResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -4163,9 +3057,9 @@ export interface SubscriptionSchedulePlanChangeResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -4519,229 +3413,8 @@ export declare namespace SubscriptionSchedulePlanChangeResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -4812,7 +3485,7 @@ export interface SubscriptionTriggerPhaseResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -4821,9 +3494,8 @@ export interface SubscriptionTriggerPhaseResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -4864,9 +3536,9 @@ export interface SubscriptionTriggerPhaseResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -5220,229 +3892,8 @@ export declare namespace SubscriptionTriggerPhaseResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -5513,7 +3964,7 @@ export interface SubscriptionUnscheduleCancellationResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -5522,9 +3973,8 @@ export interface SubscriptionUnscheduleCancellationResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -5565,9 +4015,9 @@ export interface SubscriptionUnscheduleCancellationResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -5921,229 +4371,8 @@ export declare namespace SubscriptionUnscheduleCancellationResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -6214,7 +4443,7 @@ export interface SubscriptionUnscheduleFixedFeeQuantityUpdatesResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -6223,9 +4452,8 @@ export interface SubscriptionUnscheduleFixedFeeQuantityUpdatesResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -6266,9 +4494,9 @@ export interface SubscriptionUnscheduleFixedFeeQuantityUpdatesResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -6622,229 +4850,8 @@ export declare namespace SubscriptionUnscheduleFixedFeeQuantityUpdatesResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -6915,7 +4922,7 @@ export interface SubscriptionUnschedulePendingPlanChangesResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -6924,9 +4931,8 @@ export interface SubscriptionUnschedulePendingPlanChangesResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -6967,9 +4973,9 @@ export interface SubscriptionUnschedulePendingPlanChangesResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -7323,229 +5329,8 @@ export declare namespace SubscriptionUnschedulePendingPlanChangesResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -7616,7 +5401,7 @@ export interface SubscriptionUpdateFixedFeeQuantityResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -7625,9 +5410,8 @@ export interface SubscriptionUpdateFixedFeeQuantityResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -7668,9 +5452,9 @@ export interface SubscriptionUpdateFixedFeeQuantityResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -8024,229 +5808,8 @@ export declare namespace SubscriptionUpdateFixedFeeQuantityResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -8317,7 +5880,7 @@ export interface SubscriptionUpdateTrialResponse {
      * it's often desirable to have these match existing identifiers in your system. To
      * avoid having to denormalize Orb ID information, you can pass in an
      * `external_customer_id` with your own identifier. See
-     * [Customer ID Aliases](../guides/events-and-metrics/customer-aliases) for further
+     * [Customer ID Aliases](/events-and-metrics/customer-aliases) for further
      * information about how these aliases work in Orb.
      *
      * In addition to having an identifier in your system, a customer may exist in a
@@ -8326,9 +5889,8 @@ export interface SubscriptionUpdateTrialResponse {
      *
      * A customer also has a timezone (from the standard
      * [IANA timezone database](https://www.iana.org/time-zones)), which defaults to
-     * your account's timezone. See
-     * [Timezone localization](../guides/product-catalog/timezones.md) for information
-     * on what this timezone parameter influences within Orb.
+     * your account's timezone. See [Timezone localization](/essentials/timezones) for
+     * information on what this timezone parameter influences within Orb.
      */
     customer: CustomersAPI.Customer;
     /**
@@ -8369,9 +5931,9 @@ export interface SubscriptionUpdateTrialResponse {
      */
     net_terms: number;
     /**
-     * The [Plan](../guides/core-concepts.mdx#plan-and-price) resource represents a
-     * plan that can be subscribed to by a customer. Plans define the billing behavior
-     * of the subscription. You can see more about how to configure prices in the
+     * The [Plan](/core-concepts#plan-and-price) resource represents a plan that can be
+     * subscribed to by a customer. Plans define the billing behavior of the
+     * subscription. You can see more about how to configure prices in the
      * [Price resource](/reference/price).
      */
     plan: PlansAPI.Plan;
@@ -8725,229 +6287,8 @@ export declare namespace SubscriptionUpdateTrialResponse {
          * is serialized differently in a given Price object. The model_type field
          * determines the key for the configuration object that is present.
          *
-         * ## Unit pricing
-         *
-         * With unit pricing, each unit costs a fixed amount.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *         "unit_amount": "0.50"
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered pricing
-         *
-         * In tiered pricing, the cost of a given unit depends on the tier range that it
-         * falls into, where each tier range is defined by an upper and lower bound. For
-         * example, the first ten units may cost $0.50 each and all units thereafter may
-         * cost $0.10 each.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "tiered",
-         *     "tiered_config": {
-         *         "tiers": [
-         *             {
-         *                 "first_unit": 1,
-         *                 "last_unit": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "first_unit": 11,
-         *                 "last_unit": null,
-         *                 "unit_amount": "0.10"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * ```
-         *
-         * ## Bulk pricing
-         *
-         * Bulk pricing applies when the number of units determine the cost of all units.
-         * For example, if you've bought less than 10 units, they may each be $0.50 for a
-         * total of $5.00. Once you've bought more than 10 units, all units may now be
-         * priced at $0.40 (i.e. 101 units total would be $40.40).
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bulk",
-         *     "bulk_config": {
-         *         "tiers": [
-         *             {
-         *                 "maximum_units": 10,
-         *                 "unit_amount": "0.50"
-         *             },
-         *             {
-         *                 "maximum_units": 1000,
-         *                 "unit_amount": "0.40"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Package pricing
-         *
-         * Package pricing defines the size or granularity of a unit for billing purposes.
-         * For example, if the package size is set to 5, then 4 units will be billed as 5
-         * and 6 units will be billed at 10.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "package",
-         *     "package_config": {
-         *         "package_amount": "0.80",
-         *         "package_size": 10
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## BPS pricing
-         *
-         * BPS pricing specifies a per-event (e.g. per-payment) rate in one hundredth of a
-         * percent (the number of basis points to charge), as well as a cap per event to
-         * assess. For example, this would allow you to assess a fee of 0.25% on every
-         * payment you process, with a maximum charge of $25 per payment.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "model_type": "bps",
-         *     "bps_config": {
-         *        "bps": 125,
-         *        "per_unit_maximum": "11.00"
-         *     }
-         *     ...
-         *  }
-         * ```
-         *
-         * ## Bulk BPS pricing
-         *
-         * Bulk BPS pricing specifies BPS parameters in a tiered manner, dependent on the
-         * total quantity across all events. Similar to bulk pricing, the BPS parameters of
-         * a given event depends on the tier range that the billing period falls into. Each
-         * tier range is defined by an upper bound. For example, after $1.5M of payment
-         * volume is reached, each individual payment may have a lower cap or a smaller
-         * take-rate.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "bulk_bps",
-         *     "bulk_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Tiered BPS pricing
-         *
-         * Tiered BPS pricing specifies BPS parameters in a graduated manner, where an
-         * event's applicable parameter is a function of its marginal addition to the
-         * period total. Similar to tiered pricing, the BPS parameters of a given event
-         * depends on the tier range that it falls into, where each tier range is defined
-         * by an upper and lower bound. For example, the first few payments may have a 0.8
-         * BPS take-rate and all payments after a specific volume may incur a take-rate of
-         * 0.5 BPS each.
-         *
-         * ```json
-         *     ...
-         *     "model_type": "tiered_bps",
-         *     "tiered_bps_config": {
-         *         "tiers": [
-         *            {
-         *                 "minimum_amount": "0",
-         *                 "maximum_amount": "1000000.00",
-         *                 "bps": 125,
-         *                 "per_unit_maximum": "19.00"
-         *            },
-         *           {
-         *                 "minimum_amount": "1000000.00",
-         *                 "maximum_amount": null,
-         *                 "bps": 115,
-         *                 "per_unit_maximum": "4.00"
-         *             }
-         *         ]
-         *     }
-         *     ...
-         * }
-         * ```
-         *
-         * ## Matrix pricing
-         *
-         * Matrix pricing defines a set of unit prices in a one or two-dimensional matrix.
-         * `dimensions` defines the two event property values evaluated in this pricing
-         * model. In a one-dimensional matrix, the second value is `null`. Every
-         * configuration has a list of `matrix_values` which give the unit prices for
-         * specified property values. In a one-dimensional matrix, the matrix values will
-         * have `dimension_values` where the second value of the pair is null. If an event
-         * does not match any of the dimension values in the matrix, it will resort to the
-         * `default_unit_amount`.
-         *
-         * ```json
-         * {
-         *     "model_type": "matrix"
-         *     "matrix_config": {
-         *         "default_unit_amount": "3.00",
-         *         "dimensions": [
-         *             "cluster_name",
-         *             "region"
-         *         ],
-         *         "matrix_values": [
-         *             {
-         *                 "dimension_values": [
-         *                     "alpha",
-         *                     "west"
-         *                 ],
-         *                 "unit_amount": "2.00"
-         *             },
-         *             ...
-         *         ]
-         *     }
-         * }
-         * ```
-         *
-         * ## Fixed fees
-         *
-         * Fixed fees are prices that are applied independent of usage quantities, and
-         * follow unit pricing. They also have an additional parameter
-         * `fixed_price_quantity`. If the Price represents a fixed cost, this represents
-         * the quantity of units applied.
-         *
-         * ```json
-         * {
-         *     ...
-         *     "id": "price_id",
-         *     "model_type": "unit",
-         *     "unit_config": {
-         *        "unit_amount": "2.00"
-         *     },
-         *     "fixed_price_quantity": 3.0
-         *     ...
-         * }
-         * ```
+         * For more on the types of prices, see
+         * [the core concepts documentation](/core-concepts#plan-and-price)
          */
         price: PricesAPI.Price;
         /**
@@ -9017,8 +6358,8 @@ export interface SubscriptionCreateParams {
     /**
      * An additional filter to apply to usage queries. This filter must be expressed as
      * a boolean
-     * [computed property](../guides/extensibility/advanced-metrics#computed-properties).
-     * If null, usage queries will not include any additional filter.
+     * [computed property](/extensibility/advanced-metrics#computed-properties). If
+     * null, usage queries will not include any additional filter.
      */
     filter?: string | null;
     /**
@@ -16095,8 +13436,7 @@ export interface SubscriptionSchedulePlanChangeParams {
     billing_cycle_anchor_configuration?: SubscriptionSchedulePlanChangeParams.BillingCycleAnchorConfiguration | null;
     /**
      * The date that the plan change should take effect. This parameter can only be
-     * passed if the `change_option` is `requested_date`. If a date with no time is
-     * passed, the plan change will happen at midnight in the customer's timezone.
+     * passed if the `change_option` is `requested_date`.
      */
     change_date?: string | null;
     /**
@@ -16119,8 +13459,8 @@ export interface SubscriptionSchedulePlanChangeParams {
     /**
      * An additional filter to apply to usage queries. This filter must be expressed as
      * a boolean
-     * [computed property](../guides/extensibility/advanced-metrics#computed-properties).
-     * If null, usage queries will not include any additional filter.
+     * [computed property](/extensibility/advanced-metrics#computed-properties). If
+     * null, usage queries will not include any additional filter.
      */
     filter?: string | null;
     /**