stripemeter

Reconcile Stripe usage billing drift by deduplicating events and aligning counters.

25|6|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/geminimir/meterguard --skill stripemeter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripemeter
Source: https://github.com/geminimir/meterguard/tree/main
Command: npx skills add https://github.com/geminimir/meterguard --skill stripemeter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams prevent billing drift in Stripe usage-based pricing by keeping local usage counts, replayed events, and invoiced totals aligned before invoices close.

Core Features & Use Cases

  • Idempotent ingestion: Deduplicates retries so repeated usage events are counted once.
  • Late-event handling: Uses watermarks and replay logic to safely incorporate out-of-order or backfilled events.
  • Pre-invoice reconciliation: Compares local counters with Stripe usage totals, then pushes only the delta to restore parity.
  • Operational visibility: Surfaces health checks, metrics, alerts, and runbooks for production operations.
  • Use case: A SaaS team tracking API calls can ingest events, replay a late batch, and verify that Stripe will bill the same total the dashboard shows.

Quick Start

Clone the repository, copy the example environment file, start the local services, and run the app so you can ingest usage and verify parity against Stripe.

Frequently Asked Questions about stripemeter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reconcile Stripe usage billing drift before invoices close?

Stripe usage billing drift is reconciled by deduplicating events, handling late arrivals, and aligning local counters with Stripe totals. The system compares local counters with Stripe usage totals, then pushes only the delta to restore parity before invoicing.

What is the best way to handle late events and backfills in Stripe metering?

Late events and backfills in Stripe metering are handled using watermark-aware aggregation and replay logic. This safely incorporates out-of-order events into local counters without duplicating previously processed usage data.

How do I prevent duplicate Stripe usage records from API retries?

Duplicate Stripe usage records from API retries are prevented through idempotent ingestion. By assigning idempotency keys to events, repeated usage events are deduplicated so they are only counted once.

Can I run pre-invoice parity checks for SaaS API call metering?

Pre-invoice parity checks for SaaS API call metering are fully supported. The system verifies that local usage counters match Stripe usage totals, ensuring the dashboard and the final Stripe invoice bill the exact same amount.

How do I set up local services to verify Stripe usage parity?

To verify Stripe usage parity, clone the repository, copy the example environment file, and start the local services. Running the app allows you to ingest usage events and verify parity against Stripe totals.

What should I do if my Stripe usage totals do not match my local counters?

If Stripe usage totals do not match local counters, run a reconciliation report to identify the discrepancy. The system calculates the exact delta and pushes that difference to Stripe to restore billing parity.