Module
Count what counts — and bill it.
Record usage per customer as amount + reason via the credits API. Florentin settles it against balance and billing and serves the breakdown via /usage/summary.
The problem
You don't want to build this yourself.
Usage-based billing means: reliably record every call per customer and settle it against credits and billing. Florentin does this server-side via the credits API — with request_id to avoid double-counting.
- Capture events losslessly and idempotently
- Aggregate per customer, product and period
- Hand metrics cleanly to billing and credits
Features
What Metering does
✓
Per unitamount + reason per usage.
✓
Freely labelledreason names the unit.
✓
Read-outGET /usage/summary per customer.
✓
Real timeBalance drops instantly.
✓
Billing hookSettled against credits & plan.
✓
Webhookusage.metrics_updated.
How it works
In three steps
Define usage
Decide amount + reason per unit.
Record
POST /credits/consume per usage.
Reconcile
Florentin draws down balance and reports it.
In detail
Specifications
Verbuchungamount + reason (free)
Granularitätper customer (+ team)
Latenzreal time
Dedupevia request_id
Anbindungcredits & billing
POST /api/v1/credits/consume # Verbrauch verbuchen (Provider-Token)
{
"customer_id": "7b9c3e2a-1f4d-4a8b-9c2e-0d1f2a3b4c5d",
"amount": 1,
"reason": "api_call",
"request_id": "req_3kf9"
}
← 200 { "consumed": true, "amount": 1, "reason": "api_call" }FAQ
Frequently asked
What about duplicate records?
request_id prevents double-counting — you never count twice.
How do I see usage?
GET /usage/summary returns the breakdown per customer.
Build your product. We'll handle the rest.
All integrated — auth, billing, credits, portal, access. Stripe fully included.
Start free →