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
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.
5 problems found. $1,079.63 of recorded usage will not be billed. $53.41 may be billed that your ledger does not support.
| Problem | Your customer | Money |
|---|---|---|
| Unbilled | acct_quarry | −$900.00 |
| Unmapped customer | acct_ridge | −$103.56 |
| No subscription | acct_pine | −$76.07 |
| Overbilled | acct_tallow | +$38.41 |
| Only in Stripe | (none) | +$15.00 |
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.
One config file says where your usage lives and how your customers map to Stripe. No SDK in your app, no integration to build.
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
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
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 }}
A Stripe restricted key with read access to meters, meter events, prices and subscriptions. meterproof never writes to Stripe and sends nothing to us.
Stripe processes meter events asynchronously. Usage newer than the settle window is left for the next run on both sides.
Reads your per-unit price, package rounding included, and prices every gap. Tiered prices get counts plus an optional unit price.
MIT licensed. Read every line that touches your data before you run it.
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.
meterproof check --period previous-month --settle-minutes 15The 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.
$0
$149 / month
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.
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.
/llms.txt · /openapi.json · MCP: https://meterproof.vibefrontier.com/mcpSet 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.