Observed arrival · 2026-09-19
MarginCI Catches API Cost Regressions in CI
MarginCI runs the same test cases against two code revisions, measures supported paid API usage, and fails the check when cost per successful operation exceeds a configured threshold.
- For
- Teams running paid APIs in Node.js or TypeScript CI
- Worth noticing
- A sample check compares 20 successful cases and reports a 72.96% cost regression against a 20% threshold.
Field notes
MarginCI treats API spending as a regression-test output rather than a dashboard metric. The documented workflow runs baseline and candidate revisions separately, reuses the same cases, counts spending from retries and failures, and divides calculated cost by successful operations. Its example uses 20 cases and an explicit exit code, while the site cautions that configured rates and provider estimates may differ from invoice charges. The page is marked private alpha.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue