AI cost management and governance

Snowflake gives you a consistent way to understand, monitor, and manage AI usage alongside the rest of your platform activity. Across AI features, pricing is primarily based on consumption, including token-based usage where applicable, so teams can align spend to actual usage instead of fixed capacity. To support cost transparency, Cortex AI provides usage views that help you analyze activity over time, break down consumption, and connect usage to billing workflows already used across your organization. These views can be used for reporting, governance, showback, and internal monitoring. For detailed pricing by feature, model, and unit of consumption, refer to the consumption table, which provides the current pricing structure across Snowflake AI capabilities.

Usage views

Snowflake provides usage views to help you track AI consumption using the same core approach used across the platform. These views support analysis of usage over time and can help teams understand how AI activity maps to overall spend, whether they are monitoring adoption, reviewing trends, or supporting internal reporting. This allows finance, platform, and engineering teams to work from a common system of record when evaluating usage. Pricing details remain available in the consumption table, which outlines how individual AI features are billed. Together, usage views and pricing documentation provide a foundation for understanding and managing AI costs across your Snowflake environment.

Usage views for total cost

These views should be used when calculating AI usage and AI-related spend. Together, they provide the standard foundation for cost reporting across AI features.

NameSERVICE_TYPETime ZoneUnitsDATES
CORTEX_AGENT_USAGE_HISTORYCORTEX_AGENTSUTC Converted to local [1]Tokens, ToolsData begins 11/10/2025
CORTEX_AI_FUNCTIONS_USAGE_HISTORYAI_SERVICES

UTC

Converted to local [1]

TokensData begins 1/5/2026
CORTEX_CODE_CLI_USAGE_HISTORYCORTEX_CODE_CLIUTCTokens, ToolsData begins 2/16/2026
CORTEX_CODE_SNOWSIGHT_USAGE_HISTORYCORTEX_CODE_SNOWSIGHTUTCTokens, ToolsData begins 3/13/2026, billing begins 4/1/2026
CORTEX_ANALYST_USAGE_HISTORYAI_SERVICES

UTC

Converted to local [1]

Messages365 days of data
CORTEX_FINE_TUNING_USAGE_HISTORYAI_SERVICES

UTC

Converted to local [1]

Fine-tuning time365 days of data
CORTEX_PROVISIONED_THROUGHPUT_USAGE_HISTORYAI_SERVICESUTCPTU Hours365 days of data
CORTEX_SEARCH_DAILY_USAGE_HISTORY [3]AI_SERVICESLocalServing time, Tokens365 days of data
SNOWFLAKE_INTELLIGENCE_USAGE_HISTORYSNOWFLAKE_INTELLIGENCEUTC Converted to local [1]Tokens, ToolsData begins 11/10/2025
CORTEX_REST_API_USAGE_HISTORY [2]AI_INFERENCEUTCTokens (note: in currency)Data begins 11/1/2025

Coming Soon: Cortex AI Guardrails Account Usage View

[1] UTC Converted to local means if your account is altered to local time it will display in local time. The underlying data is still in UTC.

[2] CORTEX_REST_API_USAGE_HISTORY is billed in dollars and is not currently shown in account level DAILY_METERING_HISTORY.

[3] CORTEX_SEARCH_DAILY_USAGE_HISTORY includes embeddings which need to be excluded from combined calculations as they are also shown in CORTEX_AI_FUNCTIONS_USAGE_HISTORY.

Usage views for additional analysis

Use these views when you need more granular or feature-specific insight. They complement the primary views, but are not intended to serve as the standard source for AI cost totals.

NameService TypeTime ZoneDatesNotes
CORTEX_SEARCH_SERVING_USAGE_HISTORYAI_SERVICES

UTC

Converted to local [1]

365 days of dataThis credit total includes the embedding costs captured in CORTEX_AI_FUNCTIONS_USAGE_HISTORY.
CORTEX_SEARCH_BATCH_QUERY_USAGE_HISTORYAI_SERVICES

UTC

Converted to local [1]

Data begins on 3/26/2026This credit total includes the embedding costs captured in CORTEX_AI_FUNCTIONS_USAGE_HISTORY.
CORTEX_AISQL_USAGE_HISTORYAI_SERVICESData starts on 11/21/2025

Slated for deprecation on 1/15/2027

This view includes totals of all functions except AI_EXTRACT.

CORTEX_DOCUMENT_PROCESSING_USAGE_HISTORYAI_SERVICES365 days of data

Slated for deprecation on

This view includes document processing now captured in CORTEX_AI_FUNCTIONS_USAGE_HISTORY.

CORTEX_FUNCTIONS_QUERY_USAGE_HISTORYAI_SERVICESData ends on 11/21/2025

Slated for deprecation on 11/22/2026

Please use CORTEX_AI_FUNCTIONS_USAGE_HISTORY.

CORTEX_FUNCTIONS_USAGE_HISTORYAI_SERVICESData ends on 11/21/2025

Slated for deprecation on 11/22/2026

Please use CORTEX_AI_FUNCTIONS_USAGE_HISTORY.

Total Cost of Operations

Tokens, Messages, and others are not the only ways in which you are billed for Cortex AI, you also are billed for the query, warehouse time, and any other associated Snowflake charges. Through query_id, warehouse_id, user_id you should be able to calculate your total cost of operation. For more details please see the associated usage view or contact support.

Budget features

Snowflake budgets help organizations monitor credit usage and respond when spending approaches or exceeds configured thresholds. These features can support internal planning, alerting, and broader governance processes for AI usage as part of an overall cost management strategy. A budget defines a monthly spending limit for an account or for a custom group of Snowflake objects. Budgets can send notifications when spend is projected to exceed the configured limit, and Snowflake also supports custom actions for budgets based on either projected or actual consumption. This allows teams to pair spend monitoring with operational responses, using the same core budgeting model across Snowflake cost management workflows.

Resource budgets for AI features

Resource budgets let administrators define a monthly credit limit for a tagged Cortex Agent object and evaluate spend against that budget on a periodic basis. Because they use Snowflake’s tag-based cost attribution model, they fit into broader governance and budget management patterns already used across the platform. Snowflake also announced resource budgets for Snowflake Intelligence on the same date, extending this model across additional AI experiences.

Shared resource budgets for AI Features

A shared resource budget lets you track and control credit consumption for AI features – such as AI Functions, Cortex Agents, Cortex Code, and Snowflake Intelligence – broken down by the team or cost center consuming them. Instead of budgeting a resource that belongs to a single owner or with a single budget, this budget tracks AI features that are used by specific users. Those users are identified with tags, so you can group them into logical units like a cost center or team. For example, if both an engineering team and a finance team call the same AI function, you can set up separate budgets that each track only the credits consumed by their respective tagged users, even though both teams are using the same underlying AI feature.

Budget capability by feature

FeatureBudget capabilities
Cortex AgentsResource budgets, shared resource budgets
Cortex AI FunctionsShared resource budgets
Cortex Code CLI (Consumption)Shared resource budgets, credit usage limits
Cortex Code in SnowsightShared resource budgets, credit usage limits
Snowflake IntelligenceResource budgets, shared resource budgets
*Cortex Search**Planned resource budgets for the coming year*

Not supported nor planned: Cortex Analyst, Cortex Fine-tuning.

Budget timing, enforcement, and automated actions

For Resource Budgets and Shared Resource Budgets you can attach stored procedures that are executed when spending reaches specific thresholds, which are expressed as a percentage of the spending limit and apply to the monthly budget period. Budget evaluation and enforcement are calculated periodically rather than instantaneously. After a budget threshold is exceeded, actions can take up to eight hours to take effect under normal operation, or up to two hours when using the latency-optimized option. Budgets are useful for ongoing spend management and policy enforcement, while still being part of a broader cost governance strategy that may also include usage monitoring and internal operational review.