Costs and spend caps
What Auditor costs: every model call is billed as inference to your team's Auditor key, with no seat price. Where to see what reviews, fixes and Shopify theme work cost, and how to cap it each month and on each pull request.
Costs and limits
Auditor has no seat price; the only flat fee is the optional white label add-on. Each model call is an ordinary request under the Auditor key: Directives budgets and limits apply, and every request is in Logs (key = Auditor, or session = a review's run id). The rules pass uses typesafe-ai/jev, which bills input tokens only; a small pull request usually costs a fraction of a cent. Suggested changes for rule findings, descriptions and walkthroughs are written by the description model, billed the same way. The check run shows an estimate. An automation run is billed the same way under session = its run id, with its own per-run budget and an optional monthly budget per automation under the caps below.
The Auditor page shows this month's cost for the team (the all-time total on hover; a run still settling is marked ~) and for each repository: its reviews plus, for a Shopify theme, its theme docs and theme previews, broken down on hover. Fixes and answers to replies are billed the same way. The Shopify checks and the MCP server call no model and are not billed.
Spend caps
Under Spending on the Auditor page's Reviews tab, owners and admins can cap what Auditor spends. Both caps are team settings and apply to every repository; a repository can't set its own.
- Monthly cap: the most Auditor may spend in a UTC month, across every repository, fixes, theme docs and theme previews included. It is a budget on the Auditor project, so every Auditor request is checked against it as it is admitted, and a review that reaches it stops. Once it is reached, new reviews are skipped with a neutral check run titled Monthly spend cap reached and a link to raise it; reviews start again on the 1st. Billing contacts get the team's budget alerts for it at the team's alert percentages (50, 80, 95 and 100% unless changed), and a
budget.thresholdwebhook names the Auditor project. - Per pull request: the most Auditor may spend on one pull request, across its reviews, fixes and theme preview explanations. It is checked before each review starts, so a review that starts under it runs to the end; later pushes are then skipped with a neutral Pull request spend cap reached check.
Changing the monthly cap is recorded in the audit log as a Directives change on the Auditor project. Team budgets in Directives still apply on top.
If the balance runs out or a budget or cap is used up, the review stops and the check run says why. Top up or raise the budget, then comment @auditor review.