Consumption is measured through Table Days with optional usage-based add-ons, using the Consumption Rates defined below.

Consumption Rates

Monitors

Monitors alert the user when a set of conditions (defined by a Customer or by Monte Carlo) about their data, metadata, or infrastructure are met. There are four different categories of Monitors (Table, Metric, Validation, Query Performance), and each category can contain multiple Monitor types.

Table Monitors are the only type of Monitor that consumes Table Days. Consumption Rates are as follows:

• Each asset with at least 1 Table Monitor consumes 1 Table Day per day.
• If multiple Table Monitors include the same asset, the asset still only consumes 1 Table Day per day, though fractional allocation will be used for Chargeback Reporting. In other words, you are not charged extra for overlapping Table Monitors.
• Table Monitors in a Disabled state do not consume any Table Days. Table Days will be consumed for all other Monitor statuses, and the type and frequency of the monitor's schedule does not affect its Consumption Rate.

Other categories of Monitors (Metric, Validation, Query Performance) do not consume any Table Days, but can only be enabled when the underlying table has a Table Monitor.

Agents

Troubleshooting Agent

Troubleshooting Agent automates the process of finding the root cause of a data issue, by sifting through context (changes in data, system issues, code changes, lineage, etc) and iterating through different hypotheses.

Consumption is based on the number of Alerts that Troubleshooting Agent is used on (“Investigations”). In a given month:

• The first 3 Investigations are free.
• Above that, $500 will be consumed per 20 Investigations. This is drawn directly from Committed spend or added to your monthly on-demand bill, if there is no Committed spend.
• By way of example, whether you use 5 or 20 Investigations in a given month, $500 will be consumed for that month.
• Remaining investigations do not roll over to the next month.

Metering is on the account level, not per user. Running Troubleshooting Agent multiple times on the same alert only counts as 1 Investigation. Use the Alerts Data Export to understand on which Alerts the Troubleshooting Agent has been run.

Triage Agent

Beginning September 1, 2026, usage of Triage Agent above the threshold described below will be billable. Automatic triage is free through August 31, 2026.

Triage Agent automatically scores new alerts on incident likelihood and downstream impact, prioritizing them High, Medium, or Low so your team can focus on what matters most.

Consumption is based on the number of Alerts Triaged (across automatic triage, the alerts feed, Slack, and MCP). In a given month:

• The first 20 Alerts Triaged are free.
• Above that, $1.25 will be consumed per Alert Triaged. This is drawn directly from Committed spend or added to your monthly on-demand bill, if there is no Committed spend.

Metering is on the account level, not per user or per domain. Running Triage Agent multiple times on the same alert only counts as 1 Alert Triaged.

PR Agent

PR Agent reviews the code changes in a pull request (including dbt changes) for data-reliability risk and posts its findings back on the PR, including a risk score, code-review findings with fix recommendations, generated SQL validation queries, and monitor coverage-gap suggestions.

Consumption is based on the number of pull request reviews ("Reviews"). In a given month:

• The first 3 Reviews are free.
• Above that, $200 will be consumed per 20 Reviews. This is drawn directly from Committed spend or added to your monthly on-demand bill, if there is no Committed spend.
• Remaining Reviews do not roll over to the next month.

Metering is on the account level, not per user. Re-running PR Agent on the same pull request counts as a new Review.

Agent Observability

Beginning May 1, 2026, usage of Agent Observability will billable using the Consumption Rates defined below.

Agent Observability gives you full visibility into your AI agents, from the data that powers them to the prompts they receive and the outputs they generate.

Consumption is based on the number of Agents for which Monte Carlo is observing traces, as well as the number of Agent Monitors on those Agents. Cost is per day and by Tier (Start, Scale, Enterprise, Business Critical).

By way of example:

• An account with 4 Agents and 75 Agent Monitors is a Medium
• An account with 25 Agents and 50 Agent Monitors is a Large

The count of Agents and Agent Monitors are measured once per day, and include:

• Agents for which Monte Carlo has observed traces in the past 7 days. The count of Agents is based on the number of distinct agent names. In cases where tracing is set up through instrumentation with Monte Carlo's SDK, the name is defined there. In cases where the Agent is built through an agent platform like Snowflake Intelligence, the name of the Agent is inherited from the platform.
• Agent Monitors (types are listed here) of those Agents. Any Agent Monitors with a Disabled status are not counted. The frequency of the monitor's schedule does not affect its Consumption Rate.

Performance & Cost Agent

Beginning October 1st, usage of Cost & Performance Agent moves from free preview to metered usage.

Cost & Performance Agent analyzes your warehouse for storage and compute waste — unused and stale tables, oversized or idle warehouses, and inefficient queries — and surfaces them as findings you can act on or turn into tickets.

Consumption is based on the volume of warehouse activity and storage under analysis, across two units. Each unit includes a base allowance, with usage above it charged per unit. This is drawn directly from Committed spend or added to your monthly on-demand bill, if there is no Committed spend.

Compute — the query activity analyzed.

Storage — the data under analysis.

Metering is on the account level, not per user. Findings, queries deep-dive, MCP access, chat follow-up questions, and ticket creation are included at no additional cost.. The type and frequency of the refresh scheduled-digest does not affect the Consumption Rate — consumption is based on what is under analysis, not how often it is analyzed. Warehouses can be added or removed to narrow the scope in Settings > Agentic Operations.