# Frequently Asked Questions ## General ### What is Agentic Data Intelligence? ADI is the control plane for AI data analytics. It sits as a thin layer between agents and your data, generating a machine-readable model of what your data means and an enforceable contract that constrains how AI agents use it. The result is consistent, trustworthy analytics above the stack you already run. ### How is ADI different from a data copilot? Copilots write SQL quickly from a natural-language question but cannot tell you whether the answer is right, and the same question can return different numbers. ADI builds an explicit model of what your data means first, then holds every query to it. Every query is checked against the contract, and within a shared contract the same question yields the same answer. Keep the copilots and agents you already use: ADI works above them, constraining how they query and holding them to what the metrics mean. ### What editions are available? Two editions, each for a different audience: - **Starter Edition** for individual developers, data engineers, and analysts adding semantic and control functionality to coding agents and IDEs - **Enterprise Edition** for teams adding a semantic and control layer to the copilots and agents they run on cloud data and analytics platforms ### What is the current product status? Starter Edition is entering Closed Beta, and Enterprise Edition is in limited Alpha. Request early access at [agentic-data.com/access](https://agentic-data.com/access). ### What data domains does ADI support? ADI is domain-agnostic. It works with financial data, operational data, marketplace data, and even blockchain data. The four-layer architecture applies the same way regardless of business domain. ### Does ADI see or store my data? No. ADI never sees your underlying data. The contract is generated from schema and context, and analysis runs in your own environment. You hold the data and the model; ADI holds the meaning and the rules. ## Starter Edition ### Which coding agents does Starter Edition support? Claude Code, Cursor, and Codex install via a dedicated plugin. OpenClaw, Manus, and any other coding agents that support either the Open Plugins Specification or the Agent Skills Specification are also supported. Any MCP-compatible client can integrate with ADI. ### Do I need to write SQL? No. You ask in business language and your agent, guided by the Skill, compiles the request into contract-governed SQL. Writing SQL by hand bypasses the contract and loses provenance. ### How does a contract get created? You author it for your own data (with your agent, using ADI's authoring spec) and validate it with `adi.validate` before use, or you start with the ready-made contract that ships with the provided synthetic dataset. ### What happens when ADI cannot answer a question? ADI refuses the request and tells you why. Refusals include a code, a plain-language reason, and recovery information such as the metrics or group-bys that are allowed. A refusal is not a dead end; it is guidance toward a valid request. ### Does a generated query carry a signature? Not in the Beta. The Beta runs at t1, which is generation-only: a generated query carries provenance (which metric, entities, joins, filters, and policies were used) but no signature. The signature (in the form `adi-sql-v1:`) and signature-gated execution, where only contract-compiled SQL runs through the verified path, are capabilities of the execution tiers (t0 and t2). ## Enterprise Edition ### How does Enterprise Edition connect to my data? Enterprise Edition runs as a native app inside your own cloud data warehouse. Snowflake and Databricks are supported now, with Google BigQuery and Amazon Redshift coming soon. Your data stays in your warehouse. ### Does ADI replace my catalogue, governance, or transformation tools? No. ADI extends your existing catalogue and governance rather than replacing them. It adds the layer of meaning and enforcement that no other tool owns, above the stack you already run. ### Can ADI's output be used in existing downstream tools? Yes. The contract's analytical model can be output to MetricFlow, so its metric definitions are usable in downstream tools, and ADI is working towards two-way Open Semantic Interchange (OSI) compatibility in a future version. ## Security and governance ### How does ADI protect personal data? Sensitive columns are classified in the contract's policy document, and requests that would expose them (for example grouping by an email address) are refused before any data is touched. Personal data does not reach the agent. Safe alternatives such as counts, cohorts, or aggregated views are offered. ### Can an agent reach data outside the contract? The contract, not the agent's prompt, decides what can be queried. When your agent asks for something outside the contract, ADI refuses it as the SQL is generated: out-of-contract requests, unsafe joins, and disallowed group-bys are all refused, and generated SQL is restricted to read operations. Enforcement at execution, where only signed SQL runs, is a capability of the execution tiers (t0 and t2). ### Is there provenance and an audit trail? Every generated query returns provenance: which metric was used, which entities and joins were involved, the group-bys and filters applied, and the policies honoured. Enterprise Edition adds full audit trails across queries and governance decisions.