Sample report: Relay API calls
The real output of meterproof demo: a fictional API company billing $0.01 per call, with five planted mistakes and one batch of usage Stripe hasn't finished processing. Your own run prints the same report.
5 problems found. $1,079.63 of recorded usage will not be billed. $53.41 may be billed that your ledger does not support.
Problems
Days that differ
cus_demo_quarry (acct_quarry): unbilled
cus_demo_tallow (acct_tallow): overbilled
cus_demo_orphan: only in stripe
What each problem means
- Unbilled: Stripe recorded less usage than your ledger. The missing usage will not be on the invoice. Usual causes: events rejected by Stripe (bad customer id, payload key, or timestamp), a worker that stopped sending, or events sent after the invoice finalized.
- Unmapped customer: Your ledger has usage for a customer with no Stripe customer id in the mapping, so nobody is billed for it. Add the customer to the mapping, or check why it never got a Stripe customer.
- No subscription: The Stripe customer has usage but no active subscription on the metered price, so the usage never reaches an invoice.
- Overbilled: Stripe recorded more usage than your ledger. The customer will be charged too much. Usual cause: retries that sent the same event twice with different identifiers.
- Only in Stripe: Stripe recorded usage for a customer your ledger has none for in this window. Check for events sent to the wrong customer or test traffic in the live account.
Notes
- 42 ledger row(s) after 2026-11-15 09:00 UTC were left for the next run (settle window 60 min).
meterproof 0.1.0, run 2026-11-15 10:30 UTC, 11 Stripe read requests. Read-only: nothing was changed in Stripe. Help reading this report: https://meterproof.vibefrontier.com/docs/#problems-it-finds