Skip to main content
Gruv.ai logo
Usage Metering

Show how usage becomes a charge

Connect the calls you count to the allowance and rate in the plan. Give billing a clear calculation to review before an invoice is issued.

Discuss usage billingFollow the count

SUB-521 · Usage preview

Open cycle · No invoice issued

Accepted API calls
1,250
Included in the plan
− 1,000
Billable calls
250

250 × USD 0.02 = USD 5

USD 100 base + USD 5 usage

USD 105

Preview total before tax

Start with the calls that count

The preview uses 1,250 accepted API calls. Each call contributes one unit; the plan includes the first 1,000 and charges USD 0.02 for each extra call.

This September period includes events from 1 September at 00:00 UTC up to, but excluding, 1 October at 00:00 UTC. The event’s occurrence time places it in the period.

How do repeated submissions affect the count?

Send the same idempotency key when retrying an event for the same workspace and meter. Gruv returns the original event for that key. A new key identifies a separate submission; reusing an old key does not correct its recorded quantity.

A few submissions from SUB-521

  1. call-184

    First submission

    1 call accepted

  2. call-184

    Retry with the same key

    Original event returned

  3. call-185

    Next call, new key

    1 call accepted

These three submissions contribute two calls to the period’s accepted usage.

Handle late usage before the next decision

An event can arrive after the usage total was prepared. Check its occurrence time and acceptance window, then check whether an invoice has been issued.

Open cycle · No invoice

Review the preview

The USD 105 preview reflects the accepted quantity used for that calculation. An authorized recompute can include newly accepted, in-period usage while the cycle remains open and uninvoiced.

Check the refreshed quantity and charge before issuing an invoice. The base price stays separate from the usage calculation.

Invoice already issued

Review the difference

The existing invoice stays unchanged. This recompute path is closed once the cycle has an invoice.

Give billing the late-event details and the original invoice so the team can decide the correction needed. A new usage event does not revise an issued invoice.

Does a late event refresh the total by itself?

A saved cycle summary keeps the quantity from its last calculation. Newly accepted events need an explicit recompute for an open, uninvoiced cycle. Configure the event-age window and agree who reviews late usage during setup.

The worked preview has one base subscription and no coupon, add-ons, setup fees or tax. It shows the current accepted usage, not a forecast of the final bill.

More in Subscriptions

Explore more in Subscriptions

Recurring billing

Connect the billing period, invoice and collection result.

Subscription pricing

Define the base price and billing interval behind the subscription.

Subscription Lifecycle

Review trial, pause and cancellation decisions alongside billing.

Frequently Asked Questions

What happens below the included allowance?+
Billable usage is zero when the accepted quantity is at or below the included units. The subscription base price still applies.
What quantity should our product send?+
Send nonnegative whole-number units for the meter, with the subscription, occurrence time and a stable idempotency key. Define the unit clearly, such as one API call, before connecting your event source.
Can usage charges sit alongside a base subscription?+
Yes. The invoice calculation combines the base line with rated usage lines. In this preview, USD 100 base plus USD 5 usage gives USD 105 before tax.

Make usage billing clear

Bring the event you want to count, the included allowance and the price per unit. We’ll work through the calculation and how your team handles late usage.

Discuss usage billing