What Generates Charges
Understand which metered activities create Revenium transactions, so you can anticipate platform charges and explain billing volume.
Revenium platform charges are based on the volume of metered transactions your application generates. This is different from AI provider spend, which is the cost you pay OpenAI, Anthropic, AWS, Google, or another provider. This page explains what creates a Revenium transaction so finance and product teams can predict billing volume and explain charges.
There are two categories of billable activity: AI completions, and metered product usage for usage-based billing & monetization.
Quick answer: A Revenium transaction is recorded each time your application sends a metered event to Revenium: an AI turn, or a subscriber's use of a metered product configured for monetization. Viewing data in the Revenium dashboard, configuring alerts, or managing subscribers does not generate transactions.
AI Completions
Each AI call routed through Revenium's metering creates one transaction. This is the primary source of Revenium billing volume for most customers.
The captured data is used for cost attribution and analytics within each transaction — showing you what your AI usage costs across providers, models, agents, and customers — but the transaction itself is the billing unit.
What counts as one completion event?
Each request-response pair with a model is one transaction (commonly referred to as a 'turn' when working with LLMs). If your application makes a single chat.completions.create call, that is one metered event. Streaming responses count as one event once the full response is received. Retries count as separate transactions if each retry reaches the model.
Metered Product Usage for Monetization
If you are using Revenium's monetization features to bill your own customers, product usage transactions are generated by your subscribers' activity against their subscriptions.
What creates a product usage transaction depends on how your product is priced:
Flat subscription
Subscription activation / renewal
Per-call / per-transaction
Each metered request by a subscriber
Transactions are only generated for active subscriptions. Subscribers who have not activated a subscription, or whose subscription has expired, do not generate product usage transactions.
What Does Not Generate a Charge
Viewing dashboards, analytics, or logs
No
Configuring alerts, budgets, or cost controls
No
Creating or managing subscribers, credentials, or products
No
AI calls blocked before reaching the model (e.g., by a Cost Control rule)
No
Revenium Tool Registry events
No
Revenium's SDK evaluating a cost control rule
No
FAQ
Last updated
Was this helpful?