
from stripemeter23
Usage-metering system for Stripe: idempotent event ingestion, late-event handling with watermarks, running counters, and delta pushes to Stripe for usage-based
StripeMeter provides a usage metering backend designed for usage-based billing with Stripe. It ingests immutable usage events with deterministic idempotency keys, materializes counters/aggregations, handles late events via watermarks, and pushes only deltas to Stripe to maintain invoice parity.
Use when implementing metered billing: tracking API calls, seats, or other usage metrics; ensuring idempotent ingestion; reconciling drift with Stripe; and testing via shadow mode before live invoicing. Ideal for teams building usage-based pricing and accurate billing pipelines.
Useful for engineering or ops agents that can provide deployment/run instructions, API request examples, and billing reconciliation guidance (e.g., Codex, CLI-capable agents, devops helpers).
StripeMeter is a Stripe-native usage metering system with idempotent event ingestion, late-event watermarks, and delta pushes to Stripe. Both scripts (preflight.sh and setup.sh) ran but failed due to missing Docker in the sandbox — expected for infrastructure-dependent tools. The SKILL.md is comprehensive with SDKs, API docs, and operational runbooks. No security concerns; placeholder Stripe keys in .env template are clearly not real credentials.
dockerdocker-composejqWell-structured skill for Stripe usage-based billing. Clean security posture — no hardcoded creds, no exfiltration, proper shell hygiene with set -euo pipefail. Scripts failed in sandbox only due to missing Docker, which is expected for an infrastructure tool. The monorepo structure with SDKs (Node.js + Python) and operational tooling (reconciliation, shadow mode, pricing simulator) shows genuine engineering depth.