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.

MeterRelay API calls (mtr_demo_relay_api_calls), aggregated by sum
Window2026-11-01 00:00 to 2026-11-15 09:00 UTC
Timingusage newer than 60 min is left for the next run; edges allow 5 min of timestamp drift
Customers checked9 (4 match, 5 with problems)
Ledger rows10,139
PricingStripe price price_demo_relay_per_call (USD)

Problems

ProblemStripe customerYour customerYour ledgerStripeDifferenceMoney
Unbilledcus_demo_quarryacct_quarry848,659758,659-90,000-$900.00
Unmapped customer(none)acct_ridge10,3560-10,356-$103.56
No subscriptioncus_demo_pineacct_pine7,6077,6070-$76.07
Overbilledcus_demo_tallowacct_tallow455,767459,608+3,841+$38.41
Only in Stripecus_demo_orphan(none)01,500+1,500+$15.00

Days that differ

cus_demo_quarry (acct_quarry): unbilled

Day (UTC)Your ledgerStripeDifference
2026-11-0858,82452,824-6,000
2026-11-0972,0000-72,000
2026-11-1059,30847,308-12,000

cus_demo_tallow (acct_tallow): overbilled

Day (UTC)Your ledgerStripeDifference
2026-11-1232,21736,058+3,841

cus_demo_orphan: only in stripe

Day (UTC)Your ledgerStripeDifference
2026-11-0601,500+1,500

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