Trace AI-triggered queries and jobs is now available across the Jobs API and warehouse query comments. You can now tell whether a query was triggered by AI, through which surface, and how the caller authenticated.
Previously, query metadata had no way to distinguish an AI-triggered query from a normal human-driven one, making it hard to attribute warehouse cost or audit usage by origin as AI usage grows.
We’ve added three new fields to Job info (via the Jobs API) and to the SQL comment Holistics stamps on every query it runs:
ai_triggered- whether the query was triggered by AI (true/false, or null if we can’t tell)ai_origin- which surface triggered it (ui.chat, tool.mcp, api, …)auth- how the caller authenticated (session, api_key, oauth, public)
No new integration needed - if you already parse Job ID/Source ID from query comments or the Jobs API for cost attribution, these ride along the same channels.
Learn more: Trace AI-triggered queries and jobs | Holistics Docs (4.0)