> 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/consume/activate/overview.md).

# Activate a Data Product

Choose the path to consume a Data Product: BI tools, SQL clients, APIs, or AI.

Activating is the final step of the consumer journey. After you [discover](https://v2.dataos.info/consume/discover/overview.md) and [evaluate](https://v2.dataos.info/consume/evaluate/overview.md) a product, connect it to the tool or workflow that will use it. Once a product is discovered and trusted, you activate it as often as you like without re-validating.

## Open the Activate menu

The Activate menu is your single starting point for every consumption path, so you do not hunt for connection details per tool. From the product page, select **Activate** in the Quick access bar; it lists **MCP**, **BI Tools**, **APIs**, and **Database Client**. The product's **How to activate** section surfaces the same paths as cards.

## Pick a path

<table><thead><tr><th width="187.11175537109375">Path</th><th>Pick it when</th></tr></thead><tbody><tr><td><a href="https://v2.dataos.info/consume/activate/bi-tools.md">BI tools</a></td><td>Your deliverable is a report or dashboard in a business intelligence (BI) tool, built on governed semantic models without re-modeling</td></tr><tr><td><a href="https://v2.dataos.info/consume/activate/database-clients.md">Database clients</a></td><td>You would rather explore and query in a familiar desktop SQL tool</td></tr><tr><td><a href="https://v2.dataos.info/consume/activate/apis.md">APIs</a></td><td>An application, automation, or service needs governed data programmatically</td></tr><tr><td><a href="https://v2.dataos.info/consume/consume-with-ai/overview.md">Consume with AI</a></td><td>You want AI clients or agents to discover and query within governance</td></tr></tbody></table>

## When you are done

Activation is complete when the downstream tool reaches the governed product and returns the fields, metrics, or results you expect.

If you want to confirm the exact query before wiring up a tool, start with [Querying Data Products](https://v2.dataos.info/consume/activate/querying-data-products.md). To build on top of an existing product rather than rebuild it, see [Reusability](https://v2.dataos.info/consume/activate/reusability.md).


---

# 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/consume/activate/overview.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.
