FAQ
Questions we actually get.
Meter usage. Invoice in Stripe. Short answers for self-serve usage metering — the legal pages hold the contract language.
What is UsageMill?
Self-serve usage metering for Stripe. Define meters, record events, we write the invoice. One-liner: Meter usage. Invoice in Stripe.
What is an event?
One POST /api/v1/usage we persist: a meter slug, a quantity, an optional timestamp, and an idempotency key. Same tenant + key counts once. Over-cap requests return 429 — we do not silently drop usage.
Do I need a sales call?
No. Magic link, pick a plan, ship events. There is no CSM and no demo queue.
Where does money move?
In Stripe. UsageMill meters and writes invoice items or metered subscription lines. Stripe invoices and collects. We are not the merchant of record.
What are the caps?
Starter 10,000 events / 2 meters · Pro 500,000 / 20 · Scale 5,000,000 / 100. Constants in code — tune them without a quote PDF.
Is this a Metronome, Orb, or Lago replacement?
No. Those are sales-led usage platforms with commits, SQL rate cards, and true-ups. UsageMill is the self-serve cliff for indie Stripe-first products: meter usage, invoice in Stripe. If you need that catalog, buy it.
Can I use this for consumer apps?
No. B2B only — business usage events. See the Acceptable Use Policy.
How does idempotency work?
Send idempotency_key on the event (or an Idempotency-Key header). Same tenant + key returns the original event. We do not double-count.
Support?
Email, weekdays US Eastern, best effort — not a CSM. Write support@usagemill.com.
Who operates this?
Media Yard LLC, PO Box 73, Pennsauken, NJ 08110. The public domain is usagemill.com.
Still stuck? Read the docs, try plan fit, or write support@usagemill.com.