Buy credits to continue eligible PR reviews and CLI-triggered reviews after the applicable review limit is reached.
The Usage-based add-on lets Pro, Pro+, and Enterprise organizations continue processing eligible PR reviews and CLI reviews after reaching the applicable review limit. It is the best option for teams that need uninterrupted high-volume review activity beyond their plan allowance and fair usage availability timing. Credits are consumed only when an eligible review continues over that limit. Manage credits and the add-on toggle from the Usage-based add-on tab in Subscription and Billing.
The add-on is available on the Pro plan and above and is not visible during a trial. Your organization shares one credit balance across all PR and CLI reviews.
When a review is over the applicable limit, the add-on behavior depends on whether it is enabled and whether credits are available:
Situation
Behavior
Within the applicable limit
Reviews work as normal. No credits are used.
Over limit, add-on enabled, credits available
CodeRabbit continues reviewing and charges pay-as-you-go for each eligible over-limit review. No interruption for developers.
Over limit, add-on disabled
Developers see a message that the review limit has been reached. An admin can enable the add-on to continue.
Over limit, add-on enabled, credits insufficient
Developers see a message to contact an admin to purchase more credits.
CLI-triggered reviews follow the same billing path and opt-in logic as reviews from GitHub, GitLab, and Bitbucket PR pages. Authenticated CLI and agentic API-key reviews use the assigned user’s plan allowance first. Credits are consumed only after the review reaches the applicable limit and the request is attributed to a user with an assigned seat.For Pro and Pro+ PR reviews, your plan includes a per-developer hourly allowance. Developers with typical PR review activity continue to see reviews become available normally for their plan. When one developer identity reaches the 95th percentile or higher of recent CodeRabbit PR review usage, CodeRabbit gradually spaces out additional reviews for that developer. Your plan allowance is not changed. To learn more, see our Fair Usage Limits Policy.If high volume is not intentional, tune automatic review controls before relying on credits: pause automatic incremental reviews after 1 or 2 reviewed commits, turn off automatic reviews and add a configured ready-for-review label to opt PRs in, use title exclusions for WIP or generated changes, or request reviews manually for noisy repositories. Use credits when the extra throughput is intentional and you want eligible over-limit reviews to continue without waiting for the next included review.
Admins enable and disable the add-on using the pay-as-you-go toggle in Organization Settings in the CodeRabbit dashboard. There is one toggle, one credit balance, and one billing path covering all PR and CLI reviews.
Go to Subscription and Billing in your organization settings, then open the Usage-based add-on tab.
2
Buy credits
Choose one of the available purchase options:
One-time purchase — buy a fixed credit amount as needed.
Monthly subscription — set a recurring monthly credit amount billed automatically.
Auto-refill — automatically top up your balance when it falls below a threshold. You can set a monthly cap for automated refills, with a minimum cap of $20.
Preset amounts of 20,40, 80,and100 are available, with a custom entry for larger one-time purchases.
3
Review usage and transaction history
Track total credits purchased, remaining balance, and recent usage events in
the same tab.
When auto-refill is enabled, CodeRabbit checks the configured monthly cap before each automated refill. The cap applies only to auto-refill charges in the current UTC calendar month. If the next refill would exceed the cap, CodeRabbit skips the automated refill instead of charging a smaller partial refill. Manual credit purchases are not limited by the auto-refill cap.
