Billing & Credit Controls

Resolve AI bills for the work it does on your behalf, measured in credits. The Billing section of the Resolve app shows how many credits you have used against your contract, and lets you cap how much automated work Resolve starts. Billing has two pages:

• Usage shows credit burndown against your contract with Resolve.
• Credit controls lets you cap Resolve’s automated work.

​

Finding the Billing Page

Both pages live under Settings > Organization settings > Billing, where Usage and Credit controls appear as tabs.

​

Billable Actions

Resolve meters five types of billable actions:

• Chats — conversations with Resolve, in the app or in Slack
• Tasks — task runs, whether scheduled or started on demand
• Investigations — deep root-cause analysis that traces an issue’s causal chain
• Incidents — incidents Resolve works
• Triages — lightweight impact analysis that decides whether an alert is worth investigating further

Tasks are metered as Chats. Unless your contract lists Tasks as their own line item, task runs are grouped with Chats wherever your usage is broken down. Investigations and Triages follow the Alert Investigation Mode an alert runs under. Adaptive mode starts as a triage and meters an investigation only if it escalates.

---

​

Usage

The Usage page shows the credits you have been billed against the allowance in your contract, so you can see how much of your commitment you have consumed and how quickly you are pacing through it. Usage is broken down by billable action, so you can see which kinds of work are consuming your credits.

---

​

Credit Controls

A credit cap is a monthly ceiling on automated work. Reaching a cap pauses automated work until the month ends or you raise the cap. It never blocks manually triggered work started by a person. A cap only stops Resolve from starting new automatic work. It is not a hard spend stop: usage can pass a cap, because nothing a person starts is ever blocked. It is also not notify-only — it genuinely pauses automation. Credit caps are separate from the system rate limits described in Limits.

​

When a Cap Is Reached, What Pauses?

Automated work pauses when a cap is reached:

• Auto-investigations, including triage and adaptive mode
• Scheduled task runs
• Work triggered by external bots
• API and MCP usage from an organization-scoped token

​

What Never Pauses

People’s work keeps running, whatever your usage:

• Chats, investigations, tasks, or incidents manually started by a person
• Manual Run now on tasks
• API and MCP usage from a personal token or OAuth
• On-call paging
• Anything already running

On-call paging always continues. When a cap is reached, Resolve still pages a human and hands over the alert. It skips only the analysis it would have run first.

​

Organization and Team Caps

There are two kinds of caps, and they work independently. The organization cap is a single cap for your whole organization. When it is reached, new automatic work pauses everywhere. Team caps apply to one team at a time. Each team can use your organization’s default team cap, set its own custom amount, or have no cap at all. A team without a custom amount follows the default (if configured), and changes to the default carry over to it. Automatic work runs only while both the organization cap and the team’s cap are under their limits. Reaching one team’s cap pauses that team’s automatic work only; other teams keep running unless the organization cap is also reached.

​

The Monthly Window

A cap is a ceiling per month, and usage resets each calendar month.

​

Notifications

One notification policy covers your organization cap and every team cap. You can:

• Set warning levels — percentages of a cap — to be notified before a cap is reached
• Be notified at 100%, when a cap is reached

Notifications are delivered to a Slack channel you choose in the Notifications section of the page. Choose a channel to start receiving them.