Valistry

Snowflake Cortex

Cortex AI Functions run from SQL, per day. Credits and tokens, by function and model. Also pages read and the number of queries. Never your tables, a prompt or a reply. Cortex Agents, Analyst and REST API use are not read yet.

Access

Kind
A read-only key you paste
What to give
Account, token and a warehouse
Why that one
A programmatic access token for a user who can read the account usage views, and a warehouse to run one query on. Valistry runs that query and nothing else.

What it attributes on its own

From the source
day; Cortex function; model where one was named; queries; tokens in and out, or pages; what Snowflake billed in credits, at your price per credit
Needs a rule or a trace
who ran the query — the view carries a user id, which is not read in this version; team, workflow and agent unless a rule maps the function; outcome

Connecting it

  1. Create Valistry's user and token. In Snowsight: Projects → Workspaces → SQL file. Run all of it. Paste the token. Open ↗
  2. Find your price per credit. On your Snowflake contract or last invoice, in US dollars.

Snowflake's own usage is on the bill in credits; where a Cortex model is also reached through a gateway you connect, connect only one of the two for that traffic.

Settings worth turning on in Snowsight

  1. Tag objects by team. Tags let a budget follow one team's AI spend.
  2. Create a budget. Snowflake emails you when spend will pass the limit.
  3. Set per-user AI quotas. A quota stops one user's AI use at a credit limit.
  4. Allow only chosen models. The model allowlist keeps calls to models you approve.

Questions about Snowflake Cortex

What access does Valistry need?Its own user, with a read-only usage role, a token and a small warehouse.
Why do you ask our price per credit?Your contract sets it. Valistry never guesses a price.
Does it read our tables?No. It reads one Cortex usage view, which holds no prompts.