> 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/discover/search-the-hub.md).

# Search the Hub

The Hub is where you find Data Products, [perspectives](/consume/v1/discover/search-the-hub/perspectives.md), and metrics by name, topic, tag, or intent. Reach for it when you already know part of what you need: a product name, a domain, a keyword.

{% hint style="success" %}
Confirm the right tenant is selected and products are available. If not, start with [Before you begin](/consume/v1/get-started/before-you-begin.md).
{% endhint %}

## Open the Hub

From the DataOS home page, select **Products**. The Hub lists every product in the selected tenant as a card in a grid.

![](/files/2H5RVGzrdZixIpWj7Kq9)

## Read a card before you open it

Each card carries enough signal to decide whether a product is worth opening, without leaving the list:

* The product icon and name, to recognize it at a glance.
* A short description, to judge whether it covers your use case.
* A **Quality** indicator that warns you when the product has open quality issues.
* A **Last run** indicator that warns you when the most recent run failed, so you can avoid stale or broken outputs.

Not every indicator appears on every card. A card with none is a quick signal that quality is clean and the last run succeeded. Hover a card to reveal the info (**i**) icon and preview details before opening the product.

## Narrow the list

* **Switch views.** Use the toggle at the top right to move between grid (visual browsing) and list (names and glossary terms as rows). List view is faster for scanning a large set.
* **My Data Products.** Select this next to **All** to cut the list to products you own or are a member of.
* **Filter.** Click the filter icon to narrow by domain, type, quality, last-run status, tags, and members, combining several at once. See [Filters](/consume/v1/discover/search-the-hub/filters.md).
* **Search by keyword.** Type in the search field to match by name, description, tags, or topic. The Hub narrows as you type and shows a result count.

## Switch the search scope

Sometimes the fastest answer is not a whole product but a reusable query or a single measure. Open the scope selector next to the search field and choose **Data Products**, **Perspectives**, or **Metrics**:

* **Perspectives:** a saved, governed query built on a product's semantic layer. Reuse one instead of building a query yourself. See [Perspectives](/consume/v1/discover/search-the-hub/perspectives.md).
* **Metrics:** a ready-made business measure. Pick one up without writing a query. See [Metrics](/consume/v1/discover/search-the-hub/metrics.md).

## Open a product

When a product looks promising, select its card or row to open the product page. Continue to [Evaluate](/consume/v1/evaluate/overview.md), where the overview, [assets](/consume/v1/evaluate/assets.md), [trust and freshness](/consume/v1/evaluate/trust-and-freshness.md), and [activity](/consume/v1/evaluate/track-activity.md) help you decide whether it is trustworthy and fit for use.


---

# 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/discover/search-the-hub.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.