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.
Credit pricing
PR review behavior
When a review is over the applicable limit, the add-on behavior depends on whether it is enabled and whether credits are available:Large pull requests
File limits per review are separate from the rolling review limits. See Plans and pricing for the included file limit for each plan. When an eligible GitHub pull request exceeds the included file limit but contains no more than 300 files, CodeRabbit skips the automatic review and can display a Review on demand using usage pricing action. Selecting the action explicitly authorizes the review to use the usage-based billing path. Generic retry and manual review commands do not authorize usage pricing for a large pull request. The review proceeds only when usage-based reviews are enabled and sufficient credits or spending capacity are available. Pull requests with more than 300 files cannot be reviewed through this action. Other Git providers show the file-limit message without the interactive usage-priced action. 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.Enable the add-on
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.Manage credits
1
Open the Usage-based add-on tab
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.
3
Review usage and transaction history
Track total credits purchased, remaining balance, and recent usage events in
the same tab.
What’s next
Plans and pricing
Compare CodeRabbit plans and understand per-developer rate limits
Billing and plans
View invoices, change your subscription plan, and adjust seat counts