> 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/v1/get-started/before-you-begin.md).

# Before you begin

Three things must be in place before you consume a Data Product.

<table><thead><tr><th width="223.751220703125">Prerequisite</th><th>Why it matters</th></tr></thead><tbody><tr><td>Tenant access</td><td>Determines which products appear in the Hub and which semantic models, outputs, and APIs you can query. Without access to the right domain, the product cannot be found or reached.</td></tr><tr><td>A deployed Data Product</td><td>Provides the governed inputs, models, metrics, quality checks, and endpoints you interact with. If nothing relevant is deployed, there is nothing to discover or consume.</td></tr><tr><td>A DataOS API token</td><td>Authenticates external tools: Power BI, Tableau, MySQL clients, Data APIs, and AI clients such as Cursor or Claude. Generate it before connecting any tool.</td></tr></tbody></table>

## Get tenant access

Request tenant access from your DataOS Operator or Tenant Admin. Include the business or technical goal, the tenant name if you know it, and the products or domain you need. If you do not know the tenant, the Operator can identify it from the domain or products you describe. Once granted, the tenant is accessible to consume Data Products. You must have a [data consumer role](https://v2.dataos.info/operate/data-product-consumer) to be able to consume a Data Product.

## Confirm a Data Product is deployed

Check the [Hub](/consume/v1/discover/search-the-hub.md) for the product you need. If it does not appear, ask the team that owns it, typically a Data Developer, to build and deploy it before you continue.

## Get a DataOS API token

Generate and copy the token before connecting any external tool.

1. Open **Home** in DataOS. From the profile menu in the top-right corner, select **API Tokens**.
2. Select **+ New**, give the token a name you will recognize later, and set an expiry (in hours or as a date) so it does not outlive its purpose. Select **Save**.
3. Copy the token value as soon as it appears. It is shown only once.
4. Store it securely. The API Tokens page lists the token with its name, creation date, and expiry, so you can track and revoke it later.

How you use the token depends on the path: MySQL clients use it as the **password**; BI tools and AI clients use it as a **bearer token** or API-token field. See [API tokens](https://v2.dataos.info/references/key-concepts/api-tokens) in References for more on how tokens work.

With access and a token in place, go to [Discover](/consume/v1/discover/overview.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 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/consume/v1/get-started/before-you-begin.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.