Native Usage Metering
Track API consumption directly within Zuplo. Define meters that watch for event types, extract values, and aggregate usage per customer in real time.
Monetization
API Monetization
Turn your API into a revenue-generating product with native usage metering, a flexible product catalog of meters, features, and plans, and multiple pricing models.
Flexible Plan Structure
Create subscription tiers with phases, rate cards, and entitlements. Support trial periods, included usage allowances, and overage pricing in a single plan definition.
API-Managed Product Catalog
Define your entire monetization model via API. Create meters, features, and plans programmatically, then publish plans when ready for subscriptions.
Monetization
Meters, Features, and Plans
Define meters to aggregate usage data (API requests, tokens, data transfer), create metered or static features, then package them into plans with phases and rate cards. The entire product catalog is managed via API.
Learn more in the docs
Monetization
Multiple Pricing Models
Support flat-rate, per-unit, tiered, graduated, and package pricing. Configure pricing at the rate card level within each plan phase, with soft or hard limits on usage entitlements.
Learn more in the docs
Monetization
Developer Portal Integration
Customize your developer portal with custom pages and plugins to display pricing tiers, usage dashboards, and account management for your API customers.
Learn more in the docs
Frequently Asked Questions
Common questions about API Monetization.
What is the Monetization API?
The Monetization API (currently in Preview) is Zuplo's first-party metering solution. It lets you define meters, features, and plans via API, track usage natively within Zuplo, and query usage in real time for billing or quota enforcement.
How do plans and phases work?
Plans are subscription tiers (like Free, Pro, Enterprise) that contain phases. Each phase represents a time period, such as a trial or default billing period, and includes rate cards that define pricing and usage entitlements for each feature.
What are metered vs static features?
Metered features are linked to a meter and track consumption, such as API calls or token usage. Static features are boolean toggles for capabilities like access to premium endpoints or priority support.
What can I meter?
Anything you can represent as an event with a numeric value. Common examples include API request counts, LLM token consumption, and data transfer in bytes. Meters use JSONPath to extract values from event data and aggregate them per customer.
Join the Beta
Get early access to API Monetization. Sign up and we'll reach out when your access is ready.