> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/interfaces/ai-activation/request-flow.md).

# Request flow

Follow how a user prompt becomes a governed Data Product MCP response.

AI activation starts in the host. The user asks a question, the model decides whether it needs external context, and the MCP client calls Data Product MCP when a Data Product tool is needed.

## Request path

1. The user asks a question in an AI host.
2. The host sends the prompt to the model with the available MCP tool descriptions.
3. The model decides whether a Data Product MCP tool is needed.
4. The host asks the MCP client to call the selected tool with structured arguments.
5. The MCP client sends the request to the Data Product MCP server.
6. Data Product MCP validates the request and calls the appropriate DataOS or Data Product APIs.
7. DataOS applies identity, tenant, policy, masking, semantic, quality, lineage, and contract checks.
8. Data Product MCP returns a structured response with data, metadata, warnings, citations, or errors.
9. The host presents the model's explanation to the user, grounded in the tool response.

## Example

A user may ask `Is orders360 fresh enough to use for today's revenue review?`

The model can call tools to:

* Inspect recent runs.
* Inspect quality status.
* Identify the owner if follow-up is needed.

The final answer is grounded in those responses. It is not a freeform guess.


---

# 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://v2.dataos.info/references/interfaces/ai-activation/request-flow.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.
