> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/organize-your-data/verified-data-models.md).

# Verified Data Models

Data models (reusable SQL definitions, formerly called data sets) can now be marked **verified** — a governance flag that tells both your team and our AI which definitions are the maintained, trusted source of truth.

### What the verified flag means

A verified data model is one that CorralData (or your data lead) maintains as the approved definition of that data — your revenue model, your appointments model, your marketing-spend rollup. Unverified models are still useful for exploration, but they're someone's working copy, not the standard.

### Why it matters for AI answers

AskCorral and the CorralData MCP server **prefer verified data models** when answering a question. If a question can be answered from a verified model, the AI grounds its answer there instead of hand-writing fresh SQL against raw tables — so two people asking the same question get the same number, computed the way your organization defined it.

When an answer is grounded this way, AskCorral surfaces the provenance — which governed metric or data model the answer was computed from — so you can trust it and reconcile it.

### What this protects against

Without the flag, an edited or experimental copy of a dataset could silently become the source for an AI answer. With it, unmaintained copies can't pollute your numbers: the verified definition wins.

{% hint style="info" %}
Want a data model verified, or a metric definition locked in as your organization's standard? Reach out to your CSM or <support@corraldata.com>.
{% 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.corraldata.com/kb/organize-your-data/verified-data-models.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.
