MergeCost

MergeCost documentation

MergeCost comments the estimated monthly AWS and LLM cost of each pull request, with the exact line that causes it and a suggested fix. It measures what your code does in your own CI, using the tests you already have.

How it fits into your workflow

  1. You install the MergeCost GitHub App on a repository and merge the setup pull request it opens.
  2. On every pull request, a GitHub Actions job runs your tests on the base and head commits and records, per endpoint, database queries, LLM tokens, outbound API calls, log volume and response size.
  3. MergeCost prices the difference with your traffic and current AWS/LLM prices and posts one comment on the PR, updated on every push.

Where to start

Requirement: MergeCost prices the endpoints your tests call. Your repository needs API tests (for example Django's test client, FastAPI's TestClient, Flask's test_client() or supertest).