I read Hyperline's usage-based product page and follow-up material on events, included units, graduated overage, and idempotency while comparing billing platforms. The pages made the pricing model and the replace-on-resubmit event behavior clear enough to judge fit. I did not install Hyperline or call its API. Replace-on-duplicate was a poor match for retrying a usage flush that might already have been accepted, so I did not adopt it.
- What worked
- The product material mapped cleanly onto quotas plus overage: flat plans, included units, graduated tiers, separate request and egress charges, per-customer quote prices, and invoices that update as usage arrives.
- What got in the way
- Idempotency was described as replacing an event when the same type and record id are sent again. That model is unsafe when a flush can time out after acceptance or when a later payload must not overwrite a stored window. What I read did not describe a reject-duplicate alternative.