Observed Signal · Jul 16, 2026 · Explainer · Source: DEV Community · Impact: 3/5 · Sentiment: Positive
Agentic Semantic Layer for AI Agents
An agentic semantic layer is a metadata layer between AI agents and a data warehouse that defines governed metric definitions, enforces access control, and exposes programmatic query interfaces (e.g., MCP or REST/SDKs). Unlike legacy semantic layers built for BI dashboards, an agentic semantic layer is designed for programmatic consumers (LLMs, AI agents, SDKs) and requires machine-readable metric definitions, programmatic discovery/querying, structural multi-tenancy, pre-aggregation to handle high query volume, and schema-as-code with version control. It generates SQL from governed definitions (not from LLMs), scopes queries per-tenant via publishable keys, and returns auditable, consistent results. The article compares existing tools (Cube, dbt MetricFlow, Looker, AtScale, ThoughtSpot, Bonnard) and explains how the agentic layer fits into the modern data stack on top of ingestion, warehouses, and dbt transformations.
Defines a production-ready pattern for programmatic AI access to governed metrics, addressing consistency, authorization, auditability, and scale — relevant to data and analytics platforms that serve AI agents in B2B products.
Track Looker Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- An agentic semantic layer is a metadata layer between AI agents and a data warehouse that defines business metrics, enforces access control, and exposes governed query interfaces.
- Agents query metric definitions via standardized protocols like MCP or via REST/SDKs; they call discover/query endpoints (e.g., explore_schema, query) instead of writing raw SQL.
- The author lists five core capabilities required in production: machine-readable metric definitions, programmatic discovery/querying, structural multi-tenancy, pre-aggregation for scale, and schema-as-code with version control.
- Structural multi-tenancy is enforced per-query (publishable keys carrying a security_context) to prevent tenant data leaks; pre-aggregation is presented as a requirement at agent scale to avoid overwhelming warehouses.
- The article compares tools and vendors including Cube, dbt MetricFlow, Looker, AtScale, ThoughtSpot, and Bonnard and shows how an agentic semantic layer sits on top of ingestion and warehousing (e.g., Fivetran, Airbyte, Snowflake, BigQuery, Databricks).
Connected Companies & Entities
9 Entities mapped“Traditional semantic layers: Looker's LookML, Tableau's semantic model, Power BI's DAX measures....”
“| ThoughtSpot | Proprietary ("Spotter") | Enterprise | Proprietary | No | AI-powered BI platform |...”
“[Data Sources] → [Ingestion (Fivetran, Airbyte)] → [Warehouse (Snowflake, BigQuery)]...”
“[Data Sources] → [Ingestion (Fivetran, Airbyte)] → [Warehouse (Snowflake, BigQuery)]...”
“The semantic layer connects to your warehouse (Snowflake, BigQuery, Databricks, PostgreSQL ... ) and generates the appropriate SQL dialect....”
“The semantic layer connects to your warehouse (PostgreSQL, including Supabase, Neon, and RDS) and generates the appropriate SQL dialect....”
“The semantic layer connects to your warehouse (Snowflake, BigQuery, Databricks, PostgreSQL ... ) and generates the appropriate SQL dialect....”
“The semantic layer connects to your warehouse (PostgreSQL, including Supabase, Neon, and RDS) and generates the appropriate SQL dialect....”
“The semantic layer connects to your warehouse (Snowflake, BigQuery, Databricks, PostgreSQL (including Supabase, Neon, and RDS), Redshift, Du...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
AI Agents Need a Semantic Layer
The article argues that giving AI agents direct text-to-SQL access to data warehouses exposes a lack of shared business semantics, causing inconsistent answers, missing access controls, and no auditability. A semantic layer (an intermediary metadata/metrics layer) solves these problems by exposing governed metric definitions, enforcing row-level security and multi-tenancy, providing an API (MCP/tool APIs) rather than raw DB connections, and enabling metrics-as-code workflows (YAML + Git). The piece distinguishes 'agentic semantic layers'—designed for programmatic agent consumption—from traditional BI semantic layers, lists operational requirements (MCP support, pre-aggregation, schema-as-code, warehouse coverage), and names existing vendors/tools. It promotes discovery and query APIs and recommends versioned, governed metric definitions to ensure consistent, auditable results across dashboards, agents, and APIs.
Building AI Agents into Your Martech Framework
The article presents an "agentic stack" framework for integrating probabilistic AI agents into deterministic martech architectures. It argues that most companies enhance existing SaaS use cases with AI rather than replacing them, and that agents create a new probabilistic decisioning layer that must operate within governed systems of record (CRM, CMS, CDP, PIM, etc.). The framework defines layers from a hyperscale foundation (cloud, warehouses, LLMs) through systems of record and differentiation, up to an intent-model layer that encodes brand, compliance, and escalation rules, and agent capability and differentiation layers for third-party and custom agents. The author warns that without clear boundaries, agent sprawl increases risk and fragility, and recommends deliberately designing constraints so agents act on consistent company truth.
RAG vs Semantic Layer: Deterministic AI Governance
The article explains that Retrieval-Augmented Generation (RAG) and semantic layers solve different questions for enterprise AI and are complementary rather than competitive. RAG is optimized for retrieving unstructured document prose (e.g., contracts, policies), while semantic layers compile governed SQL over warehouse data for deterministic, auditable answers and governed permissions. The author argues that governance must include intent resolution, constrained planning, and governed execution — steps RAG alone cannot perform — and that models given compiled, governed context perform much better on enterprise data than when pointed at raw tables.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.