# Assets

To see what Context Engine has produced from your code, open the Context Engine Assets page.

This page catalogs all the generated content from the Context Engine as useful structured outputs from your repositories. When you roll Context Engine out to new codebases, you can return here to confirm that new assets appear and are associated with the correct teams.

At the top of the page, you can review the metrics that show the number of 1) connected data sources, 2) generated assets, 3) existing asset types, and 4) data sources for each type.

<figure><img src="/files/jWgDfHuNhu7YbkWhPkmG" alt=""><figcaption></figcaption></figure>

To understand which kinds of assets you have, look at the “Data Sources per Type” summary. Check counts for types such as Service Summaries and OpenAPI Specs to verify that the right analyzers are active.

To narrow the asset list, use the filters under Metrics to select a data source, asset type, or team.

If you have recently enabled Context Engine and see no assets, wait for runs to complete. If assets still do not appear after successful runs, adjust the filters or review your analyzer configuration.


---

# Agent Instructions: 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:

```
GET https://docs.tabnine.com/main/administering-tabnine/managing-your-team/context-engine/assets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.