BETA FEATUREPackages are currently in beta and only accessible through the API. Contact your Metronome representative for access.
Prerequisites
Before creating a package, you must have:- Your usage events connected to Metronome
- A billable metric
- A product
- A rate card
Creating a Package
Create packages using the /packages/create endpoint. Package creation is nearly identical to contract creation, with the following exceptions:- Packages are customer agnostic. Do not pass a
customer_idor a customer billing configuration when creating a package - Packages are time-relative. Set
starting_at_offsetanddurationfor relative length instead ofstarting_atandending_beforedates. - Packages support aliases [coming soon]. Similar to rate card aliases, packages support aliases that aid in programmatically managing new package rollouts.
- a $10 recurring sign-up credit applied to input and output tokens for the first 3 months
- a $10 monthly subscription fee
- Standard input and output token rates
INFOUse
starting_at_offset on package terms to define starting_at
relative to contract start date and duration to define ending_before relative
to the starting_at_offset. For terms with point-in-time dates without a
duration, use date_offsetProvision customers with a package
Provision a customer using the /contracts/create endpoint. To provision a customer with the example Starter Plan package, execute the following API call:STANDARD PACKAGES ONLYProvision a customer with a package using
package_id only. Passing in any additional terms to the createContract call
will return a 400 error when used in conjunction with packages.PACKAGES CANNOT BE EDITEDCreate a new package and provision a customer
with the new package or edit the underlying contract using editContract.
What should I expect to see in future releases?
Future releases will enable:- UI improvements, including the ability to create and view packages directly in the Metronome app.
- Cohort management in the UI and API: Easily pull a list of customers and contracts associated with a given package to make changes and understand spend across cohorts.
- Package transitions in the UI and API: Add an alias to a package with an attached schedule to facilitate the introduction of new pricing plans. Use an alias in your customer provisioning workflows so that new customers are automatically provisioned to the package that the alias points to, without needing to update code.
- Improved package creation in the UI and API: Add overrides with absolute dates to model certain discounted periods (e.g., all customers have 20% during the month of January, regardless of sign-up date). Set custom fields on package terms to connect downstream systems or enable more granular tagging of terms.