Skip to main content

Buyer guide

Greptile Review Tiers & Spend Plan: Credits, Tier Rules, and Recharge

Where Base, Plus, Apex, and Auto apply, which events should start a review, and the recharge setting that keeps prepaid credits predictable.

Reading time
2 min read
Sources
11 cited
In this piece
Greptile+40 Positive

Base, Plus, and Apex reviews use 1, 3, and 10 credits, and Pro credits cost US$1 each from one prepaid organization pool. Default Greptile to Auto, keep Apex for production-bound and large pull requests, limit which events start a review, and decide on automatic recharge before coding agents multiply review volume.

When you need this

  • Coding agents open many small or stacked pull requests, and every push can start a review.
  • A handful of prolific authors account for most of your reviews.
  • Finance wants a predictable monthly figure for AI code review.

Evaluation criteria

  1. Default tier

    Which tier runs when nobody asks for one?

    Look forUse Auto as Greptile recommends. Most pull requests receive Base, with Plus or Apex for changes that need closer review. Greptile bills the tier that ran. Plus and Apex appear beside the confidence score.

  2. Tier rules

    Which pull requests earn Apex?

    Look forSet Apex rules for your production target branch and changes above 30 files, as Greptile recommends. Rules also match labels such as security or file paths. The highest tier applies when a pull request touches directories with different tiers.

  3. Review triggers

    How many reviews does one pull request use?

    Look forGreptile bills completed reviews. Configure autoReview to choose which opening, push, or rebase events trigger them. Set it to open to avoid credit charges on fix pushes. Anyone can still request review with @greptileai. One public maintainer disabled update reviews after exhausting the monthly quota.

  4. Per-author math

    Who drives credit spend?

    Look forEvery author draws on the same organization pool, and Settings, Usage shows credits used by each developer. One builder reported 571 agent pull requests in one month and estimated a monthly bill above US$500 under per-review pricing.

  5. Caps and recharge

    What stops a runaway month?

    Look forThe prepaid balance. When credits run out, new reviews pause until you add more. Automatic recharge buys credits whenever the balance runs low, so turn it on only with a monthly budget agreed.

Questions to ask vendors

  1. Based on last month's pull requests, how many credits would Auto have spent?
  2. Do annual or multi-year contracts lower the per-credit price?
  3. Do Plus and Apex find enough more on our repositories to justify 3 and 10 credits?
  4. Can automatic recharge be capped at a monthly amount?
  5. Do repositories in the open source program draw on our paid credits?

Red flags

  • Reviews on every push for agent-authored pull requests, with automatic recharge on.
  • Apex set as the organization default.
  • Bots and service accounts counted as active developers.
  • Credits bought with no one reading Settings, Usage per developer.

Products in this piece

Sources

Official documentation
7
Public source
4
  1. Greptile docs: Review tiersOfficial documentationgreptile.com
  2. Greptile docs: BillingOfficial documentationgreptile.com
  3. Greptile pricingOfficial documentationgreptile.com
  4. Greptile docs: Controlling nitpickinessOfficial documentationgreptile.com
  5. Greptile docs: Greptile CLIOfficial documentationgreptile.com
  6. Greptile docs: ChangelogOfficial documentationgreptile.com
  7. Greptile open source programOfficial documentationgreptile.com
  8. X: Matt Galligan on per-review pricing at 571 pull requests in 30 days (Mar 6, 2026)Public sourcex.com
  9. X: Kristoffer Remback on overage notices and spending limits (Apr 14, 2026)Public sourcex.com
  10. GitHub: Viktor Farcic plans a Qodo and Greptile head-to-head (Sep 23, 2026)Public sourcegithub.com
  11. GitHub: tradecraft replaces Greptile with its own reviewer (Sep 24, 2026)Public sourcegithub.com

Keep reading

  1. Buyer guideGreptile Review Playbook: Comments Your Engineers Act OnPer-directory strictness and comment types, training Greptile with reactions and replies, handing fixes to your coding agent, and a human approval before merge.
  2. Buyer guideGreptile Team Rollout Checklist: What a Pilot Has to ProveA five-step pilot for teams deciding whether Greptile Pro's prepaid review credits, US$1 each with no seat fees, are worth it after the 14-day trial, with the billing settings that prevent surprise charges.
  3. Buyer guideGreptile Data & Deployment Checklist: Storage, Training, and Self-HostingWhat Greptile Cloud stores and what it can train on, the settings to change before connecting repositories, SSO and directory sync, and when to self-host.
Read the research