Review usage and limits
Understand how reviews use your plan allowance and where to check your remaining balance.
How review deductions work
A review run can use more than one unit of your monthly allowance. GitHub pull request reviews, VS Code reviews, and MCP review_code reviews use the total number of added and deleted lines in the submitted changes.
| Lines added and deleted | Allowance units used |
|---|---|
| Up to 100 | 1 |
| 101–500 | 2 |
| 501–2,000 | 3 |
| More than 2,000 | 5 |
For example, a review with 200 added lines and 50 deleted lines uses 2 units. A 50-line review uses 1 unit even if no issues are found. The number of findings does not determine review usage.
Other actions
Checking your balance with MCP check_credits does not use your allowance. MCP ask_codepeel and the extension's code questions use 1 unit per request. A suggested fix and a complete review are different actions; do not assume that every MCP tool has the same cost.
Personal and team allowances
Personal Free includes 30 units per month and Personal Pro includes 500. Personal Max has no monthly allowance cap; review rate limits still apply.
Team Pro has a shared allowance of 500 units per purchased seat, with a 500-unit monthly limit per member. Team Max has a shared allowance of 5,000 units per purchased seat, with a 5,000-unit monthly limit per member. A member needs room in both their individual limit and the team's remaining balance.
Personal and team balances are separate. For repository reviews, CodePeel uses the repository's eligible team plan first. When no repository team applies, CodePeel selects an eligible plan from your personal and team coverage. Joining multiple teams does not combine their balances into one pool.
When allowance runs out
A review needs enough remaining allowance for its size. If the available balance is too low, the review is blocked. Check your balance and reset date in Billing before trying again, or review the available upgrade options.
Hourly review limits are separate from monthly usage. Reaching an hourly limit can temporarily stop reviews even when monthly allowance remains. Follow the retry guidance shown with the review.
Failed reviews
An IDE or MCP review that fails after its allowance has been deducted can still count toward usage. Do not assume a failed request is free. If a review failed and your balance looks incorrect, contact support with the repository, approximate time, and error message. Never include an API token.
Check your usage
Open Billing to inspect your plan, usage, and reset information. You can also ask your MCP assistant to call check_credits.
For subscription payments and cancellation, see Billing and plans. For collaboration, see Teams.