> 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/operate/v1/data-consumer/modes-of-consumption.md).

# Consumption paths

A product exposes the same governed data through several paths. The right one depends on your deliverable, not the product. Setup for each path lives in [Activate](https://v2.dataos.info/consume/activate/overview) in the Consume guide; this page helps you choose.

| Path                                                                         | Pick it when                                                      |
| ---------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| [BI tools](https://v2.dataos.info/consume/activate/bi-tools)                 | Your deliverable is a report or dashboard                         |
| [Database clients](https://v2.dataos.info/consume/activate/database-clients) | You want to explore in a familiar desktop SQL client              |
| [APIs](https://v2.dataos.info/consume/activate/apis)                         | An application or automation needs governed data programmatically |
| [Consume with AI](https://v2.dataos.info/consume/consume-with-ai/overview)   | You want an AI client or agent to query within governance         |

Whichever path you use, you query the product's governed semantic layer, so the same definitions and governance apply. A number does not change because you asked for it from Power BI instead of an API.

## How to consume Data Products responsibly

* **Keep governed logic in DataOS:** if a product already exposes approved metrics, Perspectives, or semantic definitions, use them directly instead of exporting data and rebuilding the same logic in Tableau, Power BI, spreadsheets, or another downstream tool.
* **Protect your API token:** treat your [DataOS API token](https://v2.dataos.info/references/key-concepts/api-tokens) as a secret when using external tools. Do not commit it, set an appropriate expiry, and rotate it when needed.
* **Check trust before you rely on a product:** review its trust signals, such as quality, freshness, AI-readiness, lineage, and activity. See [Trust and Freshness](/operate/v1/data-consumer/trust-and-monitor.md).

## Access and trust context

What you can see through any consumption path is shaped by [governance enforced on you](/operate/v1/data-consumer/governance-enforced.md), including grants, masking, and row filters.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/operate/v1/data-consumer/modes-of-consumption.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.