Metering & Events
Idempotent event ingestion streamed through Kafka. Retries with the same transaction ID never double-count.
A usage vendor and a Kafka topic you babysit.
Every event kept, idempotent, ready to price.
- Event
- Stream
- Idempotency
One customer. One event stream. One ledger. Pick a single layer or run the whole stack.
Each vendor in the modern AI billing stack is good at its job. The seams between them are where the margin quietly leaks — and no vendor on the bill owns the seam.
↳ the seam is the line item nobody sends
Idempotent event ingestion streamed through Kafka. Retries with the same transaction ID never double-count.
A usage vendor and a Kafka topic you babysit.
Every event kept, idempotent, ready to price.
Describe a plan in English — "$50/mo + $0.002 per GPT-4o token, 10k free" — and ship it versioned, no deploy.
Pricing changes shipped behind a quarterly release.
Plan, in plain English. Versioned. Reversible.
Nozle is the customer of record. Stripe or Razorpay moves the money — the customer, plan and invoice live in Nozle.
Stripe owns your customers, your invoices, your destiny.
Your ledger. Their rails.
nozle.can() in one call. Atomic check-and-deduct in a row-locked transaction, so two parallel calls can't double-spend a credit.
Feature flags, hand-rolled credit math, edge-case bugs.
One-call gate. Atomic deduct. No double-spend.
Track any cost — OpenAI and Anthropic usage auto-captured, everything else priced from your own rates on a Cost Sheet — joined to usage events for live per-customer gross margin. Negative-margin customers surface before the month closes.
Provider invoices reconciled to usage in spreadsheets, five days after month-end.
Costs rated as events land, joined to usage, margin live per customer.
Per-action metering with hard guardrails — cap a customer's agent spend mid-run, not at invoice time.
Agent runs that bankrupt you while finance argues over SKUs.
Caps enforced mid-run. No invoice-day surprises.
SDKs for Node, React, Python and Go, one schema, signed webhooks across every layer. OpenAPI you'd actually read.
Six SDKs, four webhook formats, zero consistency.
Four SDKs, one schema, every layer.
Start from where you are. Toggle layers on — the stack wires itself together.
Usage billing in one move — pricing edits without a deploy.
5 layers · 1 vendor · 0 reconcilesWhat changes when the billing stack becomes one platform.
Wire Nozle into your stack and see your first margin report in 60 minutes.