Snowflake Cortex: What It Is & How To Use It In 2026
Snowflake Cortex is the set of AI services built into Snowflake: SQL functions that call large language models, text-to-SQL over semantic views (Cortex Analyst), managed search over text (Cortex Search), and agents that combine them (Cortex Agents). Two apps sit on top: Snowflake CoWork, formerly Snowflake Intelligence, where business users chat with those agents, and CoCo, formerly Cortex Code, a coding agent for developers. As of November 2026, Cortex usage is billed in AI Credits at $2.00 each with global routing or $2.20 with regional routing, plus the warehouse compute that runs any SQL.
I checked each feature and price below against Snowflake's documentation in early November 2026. Snowflake renamed two of these products in June 2026, so older guides use the old names.
What Snowflake Cortex includes
Part | What it does | Where you use it |
|---|---|---|
Cortex AI Functions (launched as Cortex AISQL) | Call LLMs from SQL to classify, filter, extract, summarize, embed or generate text | SQL, Python, Snow CLI |
Cortex Analyst | Turns a plain-English question into SQL over a semantic view | REST API, or as a tool inside an agent |
Cortex Search | Managed search over text in your tables, with vector embeddings Snowflake computes | Retrieval for AI apps, or as a tool inside an agent |
Cortex Agents | Plan a multi-step answer and call Analyst, Search, code execution and custom tools | Snowsight, SQL, REST API |
Snowflake CoWork (formerly Snowflake Intelligence) | Chat app for business users over the agents you publish to it | ai.snowflake.com, mobile apps |
CoCo (formerly Cortex Code) | Coding agent that writes and explains SQL and Python (docs) | Snowsight, CLI, desktop app |
Snowflake-managed MCP server | Exposes Analyst, Search, agents, SQL and your UDFs to outside AI clients | Any MCP client |
Cortex AI Functions
SQL functions you run over rows: AI_COMPLETE for general generation, AI_CLASSIFY to sort text or images into your categories, AI_FILTER for a yes-or-no test you can put in a WHERE clause, AI_AGG to summarize a column across rows, AI_EXTRACT to pull fields from text, documents and images, plus AI_SENTIMENT, AI_EMBED and AI_PARSE_DOCUMENT (Snowflake: Cortex AI Functions). They previewed in June 2025 as AISQL and became generally available on November 4, 2025 (release note). Each function has its own privilege, so admins can allow some and not others (privileges).
Cortex Analyst and semantic views
Cortex Analyst is Snowflake's text-to-SQL service. It answers through a semantic view, a Snowflake object that names your tables, relationships, dimensions, facts and metrics in business terms, with synonyms, custom instructions and verified queries. Semantic model YAML files on a stage still work, but Snowflake recommends semantic views for new work (Snowflake: semantic view YAML). The generated SQL runs on your warehouse and is shown with the answer. Semantic views are Snowflake's own format; definitions from dbt and other tools can move into them through Open Semantic Interchange, and our semantic layer guide compares the options.
Cortex Search
Cortex Search indexes text from a query you define, together with vector embeddings it computes, and serves search over it (Snowflake: Cortex Search). Agents use it for documents, tickets and other unstructured data.
Cortex Agents
An agent plans the steps for a question and calls its tools: Cortex Analyst for tables, Cortex Search for text, Python code execution, a chart tool, and custom tools you write (Snowflake: Cortex Agents). Snowflake recommends scoping each agent narrowly before adding tools or instructions (Snowflake: build agents).
Snowflake CoWork (formerly Snowflake Intelligence)
Snowflake Intelligence became generally available on November 4, 2025 (release note) and was renamed Snowflake CoWork at Snowflake Summit in June 2026 (Snowflake CoWork). It is the ready-made chat app over your agents, and queries run with each user's own credentials, so their roles and masking policies apply (Snowflake: CoWork overview). The old name survives in SQL, in the CREATE SNOWFLAKE INTELLIGENCE privilege and the SNOWFLAKE_INTELLIGENCE_USAGE_HISTORY view.
The Snowflake-managed MCP server
Generally available since November 4, 2025, it is created with CREATE MCP SERVER and a YAML list of tools: Cortex Search, Cortex Analyst, SQL execution, an agent, or a UDF or stored procedure. Snowflake recommends exposing an agent; an Analyst tool on its own returns SQL to the client rather than running it, and it supports semantic views only (Snowflake: managed MCP server). The tools it exposes are the Cortex services priced below.
Snowflake Cortex pricing
Since April 2026, most of Snowflake's AI features bill in a separate currency, AI Credits, instead of the Platform Credits that warehouses, storage and data transfer still use (release note). An AI Credit costs the same on every edition: $2.00 with global routing, where requests may be processed in other regions, and $2.20 with regional routing, where they stay in your home region or a geography you pick. Platform Credits stay priced by edition and region. Capacity discounts don't apply to AI Credits, which get their own discounts by annual contract value (Snowflake AI pricing).
What you use | Billed in | Metered by | Plus |
|---|---|---|---|
AI Functions | AI Credits | Tokens, at a rate per million that varies by model; pages for | The warehouse running the query |
Cortex Analyst inside an agent or CoWork | AI Credits | Tokens | The warehouse running the generated SQL |
Cortex Analyst standalone API | Platform Credits (legacy) | Per 1,000 successful messages | The warehouse running the SQL |
Cortex Search | AI Credits | Serving: per GB a month of indexed data while the service runs. Embedding: per token as rows change | A warehouse for refreshes, and storage |
Cortex Agents and CoWork | AI Credits | Orchestration tokens, plus each tool called | The warehouse for SQL and custom tools |
CoCo | AI Credits | Tokens; individual CLI users can take a monthly subscription instead | Warehouse and storage at standard rates |
Sources: AI pricing, AI Functions cost, Cortex Search cost, Cortex Agents, CoCo CLI. Per-model token rates and the Analyst per-message rate sit in Snowflake's Service Consumption Table, not the docs.
Worked examples from Snowflake's docs
- Two currencies on one bill. On an Enterprise account at $3.00 per Platform Credit, 100 Platform Credits plus 100 AI Credits on global routing cost $300 plus $200, or $500 (AI pricing).
- A search index. Snowflake's example indexes 10 million rows of about 1,000 bytes with 768-dimension embeddings. At its example rate of 6.3 credits per GB a month, serving costs 256.5 credits a month, about $513 at $2.00 or $564 at $2.20, whether or not anyone searches. Embedding those rows once, at 500 tokens each and an example 0.05 credits per million tokens, costs 250 credits, about $500 (Cortex Search cost).
- Documents and audio.
AI_EXTRACTcounts each PDF, DOCX or TIFF page as 970 tokens, so a 10-page contract is 9,700 tokens before your prompt and the output. Audio bills at 50 tokens a second, 180,000 an hour (AI Functions cost).
Bills run above the raw token count for three reasons. Functions such as AI_CLASSIFY and AI_FILTER wrap your text in a prompt, and AI_CLASSIFY bills its labels again on every row. The warehouse keeps billing while a function runs; Snowflake recommends Medium or smaller, since bigger adds cost, not speed. And an agent's cost adds up across every tool it calls in one answer.
Controlling spend
Budgets for AI features have been generally available since April 2026 (release note), and Snowflake says per-user quotas are the only AI cost control with built-in enforcement (AI cost management). An agent's per-run token budget covers orchestration only, not the tokens Analyst or Search use inside the run (agent resource budgets). CORTEX_AGENT_USAGE_HISTORY splits each request into token credits and the warehouse credits its SQL used (usage view).
How to set up Cortex Analyst
- Check models in your region. If your region doesn't host them, an account admin enables cross-region inference with
CORTEX_ENABLED_CROSS_REGION(cross-region inference). Pick the narrowest setting your data residency rules allow. - Grant access. Give a role
SNOWFLAKE.CORTEX_ANALYST_USER(Analyst only) orSNOWFLAKE.CORTEX_USER(all covered AI features), plusSELECTon the tables the view uses (Cortex Analyst). - Build a semantic view. Use Semantic View Autopilot in Snowsight, which can start from a YAML, Tableau or Power BI file, or write
CREATE SEMANTIC VIEWin SQL (semantic views in SQL). Add descriptions, synonyms and verified queries for the questions people ask most. - Test it with Cortex Analyst evaluations (evaluations), and read the SQL for the questions that matter.
- Put it where people ask. Snowflake recommends calling Analyst through an agent: add the view to a Cortex Agent and publish it in CoWork, or expose it through the MCP server.
- Set a budget and quotas before opening it to everyone.
-- Only if your region lacks the models; choose the narrowest geography allowed
ALTER ACCOUNT SET CORTEX_ENABLED_CROSS_REGION = 'AWS_US';
GRANT DATABASE ROLE SNOWFLAKE.CORTEX_ANALYST_USER TO ROLE sales_analyst;
GRANT SELECT ON ALL TABLES IN SCHEMA sales.core TO ROLE sales_analyst;
Snowflake Cortex limits to plan for
- Regions and routing. Snowflake says frontier models and the full Cortex suite need cross-region inference, so requests can be processed outside your account's region, with no egress charge (cross-region inference). The 2026_06 behavior change bundle, enabled by default since September 2026, turns it on within a same-cloud geography such as
AWS_USfor eligible commercial accounts that never set the parameter; finance, healthcare, government, FedRAMP and VPS accounts are excluded (notice), so check yours. Only a global setting such asANY_REGIONgets the $2.00 AI Credit rate; a geography, or no cross-region inference at all, bills at $2.20. - Accuracy rides on the semantic view. Snowflake's accuracy figures come from its own tests (Snowflake). Basedash's BI-Bench, run on default setups, placed Cortex 10th of 11, with Basedash noting it does better on curated semantic models (Basedash), and practitioners report weaker answers when one view spans many tables (r/snowflake). Our text-to-SQL tools roundup compares the evidence across vendors.
- Snowflake data only. Data elsewhere has to be loaded first, and definitions in LookML, Power BI or dbt metrics rebuilt or converted. Agents route between semantic views, but Snowflake doesn't document joining across them in one answer.
- Governance at the edges. Inside Snowflake, roles and policies apply automatically and admins can turn AI features off (opt out). The MCP server has no dynamic client registration, External OAuth only reached general availability in July 2026, and Snowflake notes tool annotations are hints, not access control. The Slack integration for Cortex Agents was in limited-access preview at our last check (Snowflake).
Where GetDot fits alongside Snowflake Cortex
GetDot (Dot) is an AI data analyst that answers on your warehouse in Slack, Microsoft Teams, email, its web app and any MCP client, showing the SQL behind every number. On Snowflake it connects as a service user with key-pair sign-in and a read-only role you control, and tags its queries for cost tracking (Snowflake integration). Snowflake roles can sync to Dot groups, Immuta customers can run each person's queries under their own Immuta-vended role, and the Internal Marketplace can sync in so people see which data products exist (September 2026 changelog).
- Past Snowflake. 45+ data sources, joined in one answer, so a question that needs Snowflake plus Postgres or a spreadsheet doesn't wait for a pipeline.
- Your existing definitions. Dot reads dbt, LookML, Power BI semantic models, Cube and Malloy as they are; it does not read Snowflake semantic views. If you haven't picked a semantic layer, we recommend Malloy, which runs on Snowflake, and Dot's Context Agent can draft a Malloy model over your tables for you to review.
- Where people work. Native Slack and Teams apps today, scheduled PDF and PowerPoint reports, alerts that fire only past a threshold, and Root Cause Analysis for "why did this move" questions.
Where Cortex wins: it is on your Snowflake contract with no new vendor to review; data and prompts stay in Snowflake, while Dot is a separate service that syncs metadata and samples; row access policies apply with no setup; CoWork has native mobile apps; and Dot doesn't replace AI Functions in pipelines or CoCo for engineers. Our Cortex Analyst vs Dot comparison goes feature by feature.
Dot bills on credits with unlimited users, as of October 2026: Free is $0 with 300 one-time credits; Pro is $180 a month billed annually ($200 month-to-month) with 150 credits; Team is $720 a month billed annually ($800 month-to-month) with 800 credits; a chat answer costs one credit (Dot pricing). Snowflake still bills the warehouse time Dot's queries use. Dot is SOC 2 Type II and GDPR compliant, and its LLM providers run with zero data retention. Try Dot free on your Snowflake account.
FAQ
Yes. Snowflake renamed Snowflake Intelligence to Snowflake CoWork at Snowflake Summit in June 2026; it is still the chat app over Cortex Agents at ai.snowflake.com.
Cortex bills in AI Credits, $2.00 each with global routing or $2.20 with regional routing, metered mostly by tokens at model-specific rates. The standalone Cortex Analyst API bills per 1,000 messages in Platform Credits, and any SQL Cortex runs also uses warehouse compute.
Cortex Analyst turns one question into SQL over a semantic view. Cortex Agents plan multi-step answers and call Analyst, Cortex Search, code execution and custom tools; Snowflake recommends using Analyst through an agent.
It needs a semantic view or a legacy semantic model YAML file. Snowflake recommends semantic views for new work, and its managed MCP server supports only semantic views.
Yes. The Snowflake-managed MCP server, generally available since November 2025, exposes Cortex Search, Cortex Analyst, agents, SQL execution and your UDFs or stored procedures to MCP clients over OAuth.
Sven Rudolph
Sven is a co-founder of Dot. He writes about the technical side of AI analytics: MCP servers, BI integrations, and how Dot connects to the data stack.