Metering

Understanding units vs total_aggregated_units in the current usage API response

›

How to change the calculation logic on a billable metric

›

How to bill for storage using the weighted-sum metric

›

Usage alert webhook behavior at billing period reset

›

Why adding seats charges the full new total instead of just the delta

›

Why the current usage endpoint returns outdated data after ingesting events

›

How to apply multiple charge models to the same billable metric

›

Why weighted sum metrics show 0 in the UI but track negative values internally

›

Why package pricing accumulates units across events instead of resetting per event

›

Why events ingested successfully could show zero usage

›

Per-instance billing: volume pricing with billable metric filters and group keys

›

What happens to usage events sent after the grace period ends

›

How to correct a usage event that was sent with the wrong value

›

Why a prorated graduated charge can be lower than the days active suggest

›

Why usage is missing for specific filter values when a catch-all filter is present

›

Usage still shows after deleting and recreating a billable metric

›

Idempotency keys are not supported on wallet top-up and void API calls

›

How weighted_sum bills storage, and why you must send deltas not totals

›