Usage metering: your customers' usage, ready to bill.
Send usage through the API and Relvo matches it to each customer's plan or contract: tokens, calls, active users or any metric you define.
Last 30 days
Usage-based billing often ends in a month-end export: someone pulls data, checks it against each customer's pricing and prepares charges by hand. With Relvo, usage arrives through the API as it happens, and variable charges are calculated automatically using the contract's rules.
From month-end exports to usage in real time. Without matching data by hand.
Before
- Usage is exported from the database at month-end.
- Someone matches usage against each customer's price in a spreadsheet.
- Nobody knows a customer's invoice amount until the period ends.
With Relvo
- Usage arrives through the API as it happens.
- Relvo matches it against each customer's pricing, without manual steps.
- See usage by customer and metric throughout the month.
How it works. From your product to payment.
- 01
Define your metrics
Tokens, calls, documents or the unit your product bills for.
- 02
Send usage
Your product sends usage to Relvo through the API.
- 03
Relvo bills it
Usage is matched to each customer's pricing and added to the invoice.
Usage you can understand and bill. By customer and metric.
Last 30 days
POST /usage
{
"customer": "nimbo-ai",
"metric": "tokens",
"quantity": 1250000
}Reliable usage, from end to end. From event to invoice line.
API, webhook, batches or bulk upload
Usage arrives in real time or in batches, as you already report it today. It can also be entered manually.
Configurable metrics
Events, transactions, GB, active seats or tokens: each unit maps to the contract's rules.
Aggregation by period
Usage adds up automatically for each cycle, whether monthly, every two weeks or a custom period.
Idempotency
Duplicate or resent events are not counted twice.
Immutable events
Events are not edited: corrections are explicit and recorded.
Traceability
Each invoice line is linked to the events that generated it.
Works with. The same engine, from end to end.
Frequently asked questions about usage metering.
How do I send usage to Relvo?
Through the API, in real time or in batches, or through a bulk upload. Your product reports each customer's usage, and Relvo aggregates it for the period.
Which metrics can I meter?
Whatever your product bills for: tokens, API calls, documents processed, active users or another unit you define.
Can I combine usage with a fixed plan?
Yes. Usage is another contract rule, so it can be combined with a fixed plan, seats or any other component.
Can I see each customer's usage during the month?
Yes, by customer and metric. Reporting also shows recurring revenue alongside usage, month by month.
Do I need to build my own usage-based billing system?
No. You send usage, and Relvo calculates, invoices and collects. Your engineering team does not have to maintain billing logic.
What happens if I send an event twice?
It is not counted twice. Relvo is idempotent: duplicate or resent events are discarded.
What happens if a customer's usage spikes?
When usage deviates unusually from previous cycles, Relvo notifies your team before invoicing.