Find the usage Stripe won't bill, before the invoice goes out.

meterproof compares your app's own usage records with what your Stripe meters recorded, customer by customer. It reports what's missing, what's counted twice and what can never reach an invoice, in dollars.

Runs on your machine or in GitHub Actions with a read-only Stripe key. Your usage data never reaches us.

meterproof check · Relay API calls Demo data

5 problems found. $1,079.63 of recorded usage will not be billed. $53.41 may be billed that your ledger does not support.

ProblemYour customerMoney
Unbilledacct_quarry−$900.00
Unmapped customeracct_ridge−$103.56
No subscriptionacct_pine−$76.07
Overbilledacct_tallow+$38.41
Only in Stripe(none)+$15.00
A fictional API company billing $0.01 per call, Nov 1–15. Full report →

Five ways metered revenue goes missing

Stripe bills what it received, not what your customers used. These are the gaps between the two, and each one shows up in the report with the customer, the days and the amount.

Unbilled
Stripe recorded less than your ledger. Events were rejected for a bad customer id or payload key, a worker stopped sending, or they arrived after the invoice finalized.In the demo: a 30-hour worker crash, 90,000 calls, $900.
Unmapped customer
Usage for a customer who never got a Stripe customer id. Nobody gets billed for it.
No subscription
Stripe has the usage, but the customer has no active subscription on the metered price, so it never reaches an invoice.
Overbilled
Stripe recorded more than your ledger, usually retries that resent events with new identifiers. Your customer pays twice and finds out first.
Only in Stripe
Stripe has usage for a customer your ledger has none for: events sent to the wrong customer, or staging traffic in the live account.

Set up in one sitting

One config file says where your usage lives and how your customers map to Stripe. No SDK in your app, no integration to build.

Install and try the demo

The demo is a fictional company with five planted mistakes. It needs no Stripe account and prints the same report your data will.

pip install git+https://github.com/vibeFrontier/meterproof
meterproof demo

Point it at your ledger

A CSV export or one read-only SQL query against Postgres or SQLite: customer, timestamp, quantity. Map your customer ids to Stripe's with a CSV, an inline map or a column you already have.

meter:
  id: mtr_61Q8...
ledger:
  postgres:
    dsn_env: DATABASE_URL
    query: >
      select account_id, occurred_at, units
      from usage_events
      where occurred_at >= %(start)s
        and occurred_at < %(end)s
customers:
  mapping_csv: customers.csv

Run it before every invoice

Locally, or daily in GitHub Actions with the report in the job summary. It exits non-zero when it finds a problem, so your usual alerts fire.

- uses: vibeFrontier/meterproof@v0
  with:
    config: meterproof.yml
  env:
    STRIPE_API_KEY: ${{ secrets.METERPROOF_STRIPE_KEY }}
    DATABASE_URL: ${{ secrets.METERPROOF_DATABASE_URL }}

Read-only, on your side

A Stripe restricted key with read access to meters, meter events, prices and subscriptions. meterproof never writes to Stripe and sends nothing to us.

No false alarms from lag

Stripe processes meter events asynchronously. Usage newer than the settle window is left for the next run on both sides.

Money, not just counts

Reads your per-unit price, package rounding included, and prices every gap. Tiered prices get counts plus an optional unit price.

Open source

MIT licensed. Read every line that touches your data before you run it.

Usage that misses the invoice is gone

Stripe drafts an invoice when a billing period ends and finalizes it about an hour later by default. Meter events that arrive after that don't count toward it, and Stripe doesn't let you correct a finalized invoice's usage.

So the check has to run while there's still time to fix what it finds: send the missing events, fix the mapping, or void the duplicates before the invoice goes out.

  1. Every dayMonth-to-date checkCatches a stopped worker or a bad deploy within a day, not at month end.
  2. Period endsStripe drafts the invoiceThe last chance to send late events for that period.
  3. + 15–30 minClosed-period checkmeterproof check --period previous-month --settle-minutes 15
  4. + ~1 hourInvoice finalizesAnything still missing is lost revenue.

Pricing

The check is free and stays free. The founding pilot is paid help from the people who build it, while you put it on your real billing.

Open-source check

$0

  • The CLI and GitHub Action, MIT licensed
  • All five problem types with money impact
  • CSV, Postgres and SQLite ledgers
  • No sign-up, no account
Read the quick start

Founding pilot

$149 / month

  • The same open-source check, plus:
  • Config review by email: send your meterproof.yml, query, mapping and workflow; we reply within one business day
  • Help reading findings: real miss or timing, and how to resend before the invoice finalizes. You choose what to share.
  • Your blocking bugs fixed first, in the open-source repo
  • Price locked while you stay subscribed. Cancel any time; first month refunded if you ask within 30 days.

Payment by Stripe Checkout. There's no hosted monitoring or alerting: the check runs in your own CI, and we never ask for your usage data or your Stripe key.

Using an AI agent? Start here

Paste this into your coding agent from your app's repository. It can read the docs, write the config and run the check; you create the Stripe key and approve any payment yourself.

Set up meterproof for this repository. Read https://meterproof.vibefrontier.com/llms.txt first.
1. Find where this app records billable usage and how it maps customers to Stripe customer ids.
2. Write meterproof.yml (the generate_config MCP tool or /api/config-template can draft it).
3. Ask me to create a Stripe restricted key with Read on Billing meters, Billing meter events, Prices and Subscriptions, and to export it as STRIPE_API_KEY. Never ask me to paste it here.
4. Run `meterproof check` and explain each problem.
5. Add the scheduled GitHub Action from the docs.
Do not change anything in Stripe.