Read-only · your data never leaves Stripe's read APIs

Connect Stripe, get your real number.

Paste a restricted, read-only Stripe key. We validate it, store it encrypted, and run a read-only scan — we can't move money or message your customers.

  1. Stripe Dashboard → Developers → API keys → Create restricted key
  2. Set every permission to Read (or None). Name it “MeterGuard”.
  3. Copy the rk_… key and paste it below.

Read-only, by design — five things that make this safe

  1. §1
    Restricted key, all scopes set to Read or None — Stripe enforces this, not us.
  2. §2
    We only call GET endpoints (/v1/billing/meters, /v1/invoices, /v1/subscriptions, /v1/prices) — never POST, never PATCH.
  3. §3
    Your key is encrypted at rest with AES-256-GCM using an env-isolated 32-byte key; never logged in plaintext.
  4. §4
    Revoke any time in your Stripe dashboard — kills our access instantly, no email to us needed.
  5. §5
    We look back 12 months by default — enough to surface compounded drift without dragging on early-stage accounts.

What we will not do

We will not write to your Stripe. We will not email or charge your customers. We will not move money. We're a smoke detector, not a plumber.

Typical scan: 30–90 seconds. We page through 12 months of meters, invoices, and subscriptions, then re-rate every line. If the scan finds $0, you've confirmed your billing is tight — the scan costs nothing either way.

By scanning you agree to the Terms and Privacy policy. Your report link arrives on screen — nothing is emailed to anyone else.

We only ever call Stripe's read endpoints. The key is encrypted at rest and can be revoked anytime from your Stripe dashboard.

Not ready to paste a key? See the exact report you'd get → or run the no-connection estimate →