BI for Agents

The agentic analytics platform built on a semantic layer

Cube gives humans and AI agents governed, reliable access to trusted business data. People work in Analytics Chat, workbooks, dashboards, and embedded experiences; Claude, Codex, and other agents use the same business context through MCP, APIs, or CLI.

BrexWixWebflowIntuitAlconTubiDrataFreshworksand 50+
BI for Agents

One governed BI platform for people and agents

BI for agents means AI agents can use the analytics platform as first-class users — without a parallel path to raw data. Cube gives people and agents the same metrics, permissions, and analytical context across internal and embedded analytics.

  • Model the business once
    Metrics, dimensions, entities, joins, and access rules give every person and agent the same definition of the business.
  • Explore through governed workflows
    Agents discover approved concepts, query them under the asker's permissions, and iterate without re-deriving SQL from raw tables.
  • Create work people can inspect
    Answers, reports, workbooks, dashboards, and model changes retain the context and lineage people need to review the result.
Read What Is BI for Agents?
Analytics Chat

The AI analyst your whole team can talk to

  • Query in natural language
    Ask in plain English. The agent writes and runs the queries against your semantic model — no SQL required.
  • Ask follow-up questions
    Refine iteratively; context, filters, and prior queries carry forward across the thread.
  • Answers you can trust
    Charts, tables, and the reasoning behind them — every number governed and scoped to each user.
Explore Analytics Chat
Workbooks

An AI analyst inside every workbook

  • Build with the Workbook Agent
    Reports, charts, and dashboards from a request — while you keep control of every field, filter, and label.
  • Three ways to query
    Point-and-click, raw SQL, or Semantic SQL on top of governed metrics — all in one place.
  • Governed by construction
    Every chart is backed by a reusable, governed report.
See Workbooks
A Cube Workbook with a Semantic SQL query, a revenue chart, and the Workbook Agent
Dashboards

Dashboards that answer the follow-up

  • Drill deeper with the Dashboard Agent
    Break a metric down, extend the range, or explain a definition — read-only, on the same governed model.
  • Every widget you need
    Chart, KPI, filter, time-grain, text, and AI Summary widgets.
  • Scheduled and embeddable
    Scheduled refreshes, PNG and PDF snapshots, and embed-anywhere.
See Dashboards
A published Cube dashboard with filters, KPI tiles, and charts
Data Modeling

AI that builds your model — and runs on it

  • Bootstrap with the Semantic Model Agent
    Generate a model from your warehouse tables, convert existing LookML, or extend definitions in SQL-first YAML.
  • Grounded, not guessing
    Every agent reasons over governed definitions instead of raw tables — which is what makes the answers trustworthy.
  • Governed end to end
    Row-level security flows from the model to every answer, on any warehouse.
Read the modeling docs
The Cube IDE with a semantic model in YAML and the Semantic Model Agent adding a join
Integrations

Give Claude, Codex, and every agent governed business context

Connect the AI tools your team already uses through MCP, APIs, or CLI. Each agent reaches the same semantic model and production controls as every Cube surface.

  • Use the agent your team already trusts
    Claude, Codex, ChatGPT, Cursor, or one you build can work with governed business data instead of a separate copy of the logic.
  • Analytics in Slack
    Drop the Slack Agent into a thread; ask and follow up where your team already works.
  • Permissions carry through
    Can't see a metric in Cube? You won't see it in Slack either.
See all integrations

Frequently Asked Questions

BI for agents is business intelligence designed so AI agents can use the analytics platform as first-class users. Agents can discover governed business definitions, analyze data, and create analytics work through programmatic interfaces while using the same metrics, permissions, and context as people.
Yes, when the BI platform exposes governed workflows instead of only a human-oriented interface. An agent needs programmatic access through MCP, APIs, or CLI; certified metrics and relationships; inherited permissions; and a traceable result a person can review.
The agent discovers approved metrics and dimensions in the semantic layer, requests those business concepts by name, and lets the platform compile the governed warehouse query under the asker's identity and permissions. The warehouse remains the system for storage and compute.
It combines a governed semantic model with agent-native access, inherited permissions, reusable analytics artifacts, lineage, observability, and production controls. The same platform should continue to serve Analytics Chat, workbooks, dashboards, internal BI, and embedded analytics for people.

Start building with Cube

Morty Proxy This is a proxified and sanitized view of the page, visit original site.