Skip to main content
A meter defines how you price and bill usage. Each meter has:

Meter slug

Unique identifier included in forward tokens to apply specific pricing

Fee model

Fixed credits per usage unit, or a percentage of provider cost

Usage units

What you’re measuring — tokens, characters, seconds, or requests

Pricing tiers

Volume-based rate schedules that reward higher usage
Meters define pricing. Plans link to meters and provide the credit balance that usage draws from. See How Lava Monetize Works for the full picture of how meters, plans, and customers fit together.

Meter configuration

Usage units

Usage units define what metric drives pricing. Set via the field:

Fee models

The field determines how fees are calculated.
Charge a fixed number of credits per usage unit (tokens, characters, time, or requests), regardless of the provider’s dollar cost:
Example: 2 credits per 1M tokens with input+output basis
  • 500 input tokens + 200 output tokens = 700 tokens
  • Credits: 2 × 700 / 1,000,000 = 0.0014 credits

Pricing tiers

Tiers let you offer volume-based pricing. Each tier defines a usage threshold and rate. As cumulative usage increases, later tiers apply.
At least one tier is required. The first tier must start at 0, and tier starts must be in ascending order.

Example: Three-tier token pricing

For a customer that uses 5M tokens total:
  • First 1M at 5 credits/1M = 5 credits
  • Next 4M at 3 credits/1M = 12 credits
  • Total: 17 credits deducted from their balance
Tiers accumulate per customer. Each customer tracks total usage across all requests to determine the active tier.

Next steps

Checkout

Embed checkout to onboard paying customers

Gateway vs Post-Request

Choose how usage gets reported to Lava