Usage and credits
Credits and plans
How Lighthouse measures usage, and what your plan includes.
Credits measure the AI work Lighthouse does for your team. Ingestions, enhancements, and scans use credits. Browsing the dashboard and changing settings don't.
What uses credits
| Activity | Usage |
|---|---|
| Prompt enhancement | A small amount per request. |
| Pre-commit scan | Depends on the size of the change. Normal depth uses less than Max. |
| Pull request scan | Depends on the size of the pull request. Max, the default, uses more than Normal. |
| Ingestion | The most. Grows with the size of the repository. Needs at least 3,000 credits left to start. |
To use fewer credits:
- exclude files that don't matter from ingestion
- use Normal depth where speed matters more than depth
- leave draft pull requests unscanned
Your plan
Your team's plan sets its monthly credit limit. During the pilot, RewareLabs assigns plans. There's nothing to buy in the dashboard.
- Usage resets on the 1st of each month, UTC.
- Without a plan, a team can't use credits. The dashboard shows No active plan until one is assigned.
Per-key caps
An admin can give an API key its own monthly credit cap when issuing it, for example to limit a key used in CI. A key's cap can't exceed the team's limit.
Alerts
Lighthouse shows an alert when your team, or a key you own, reaches 80% and 100% of its monthly credits.
Still stuck after reading this page?