Your account
Your key stays in this browser tab and is only sent to the Usage Lab API.
Events this month (): of
Meters:
| Meter | Aggregation | Month-to-date total | Customers |
|---|
Not on Pro or Ultra yet? See plans.
Send each customer's monthly usage straight to your own Stripe Billing Meters, retry-safe. Included in Pro and Ultra. See plans · How it works
Pushes run every 15 minutes once enabled. Your key is encrypted at rest and never shown again. Docs
1. Connect a Stripe restricted key
In Stripe: Developers → API keys → Create restricted key. Permissions: Billing Meters: Read and Meter Events: Write. Nothing else.
2. Map meters (Usage Lab meter → Stripe meter event name)
→
| Usage Lab meter | Stripe event name |
|---|
3. Map customers (your subscription id → Stripe cus_…)
→
| Subscription | Stripe customer |
|---|
4. Push
| Meter | Subscription | Month | Delta | Status |
|---|
Recent pushes
| Time | Meter | Subscription | Month | Delta | Status |
|---|
Cancels any active subscription, then permanently deletes your account, API keys, meters, usage events and rollups. This cannot be undone.
- Playground: validate a usage event in your browser
- Usage event validator: check event JSON and idempotency keys
- Drop-in LLM metering helper + margin calculator
- Usage-based pricing calculator (LLM tokens or events)
- Live end-to-end demo
- API docs
- Quickstart: meter an AI app
- Code examples
- Metering usage for Stripe usage-based billing
- Deduping usage events with idempotency keys
- Backfilling late usage events: replays, late windows and adjustments
- Usage Lab vs UsageBox: an honest comparison
- Metronome and Orb alternatives for small SaaS teams
- How to meter LLM token usage per customer for billing
- Stripe Billing Meters vs a usage ledger: when you need both