> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/semantic-intelligence.md).

# Semantic Intelligence

Semantic Intelligence finds every definition of a business metric across your analytics estate, groups the ones that describe the same idea into a business concept, and shows where those definitions agree and where they have started to drift or even conflict.

Most organizations do not have a maintained business glossary. The real definitions of Revenue, Customer or Headcount live inside measures and metric views, copied and adjusted by every team that needed them. Semantic Intelligence reads those metrics as they are, so there is no ontology or glossary to author before you start. It works bottom-up from what your teams already built.

#### What's inside

* [**Metric Explorer**](https://docs.datalogz.io/guides/semantic-intelligence/metric-explorer.md)**:** an estate-level view with key figures and a standardization scorecard, one row per business concept. [**Concept details**](https://docs.datalogz.io/guides/semantic-intelligence/concept-details.md)**:** every definition of one concept side by side, compared against its source definition, with a lineage view down to the reports that use it.
* [**Metrics Catalog**](https://docs.datalogz.io/guides/semantic-intelligence/metrics-catalog.md)**:** every metric that was analyzed, searchable and filterable, with its expression and the concept it belongs to.
* **Exclusions:** control which semantic models are left out of the analysis, for example test or personal copies.

{% hint style="info" %}
Semantic Intelligence is in public preview. Request your access through your Customer Success Manager.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datalogz.io/guides/semantic-intelligence.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
