> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/agent-security/evo-by-snyk/platform-surfaces/inventory.md).

# Inventory

How Inventory presents the AI assets discovered across your environment with their assessed risk

Inventory surfaces the AI assets discovered across your environment alongside the assessed risk so you can review it in context.

* [AI-SPM](/agent-security/evo-by-snyk/ai-spm/ai-asset-visibility.md) discovers assets in your source code through a source code management (SCM) integration.
* [Agent Supply Chain Security](/agent-security/evo-by-snyk/agentic-development-security-ads/agent-supply-chain-security.md) within ADS discovers the components that agents use on end users' machines.

You can explore Inventory with Evo chat. For example, ask which assets occur most often in your code.

The **Repositories** table shows the Snyk Organization for each repository. If you import a repository into multiple Snyk Organizations, Snyk lists it once for each Organization.

{% hint style="info" %}
Inventory shows the assets you can access. If your access is restricted to specific Organizations, Inventory shows only the assets belonging to those Organizations, and counts and totals are lower than they are for a user with access to the whole Tenant. To learn more, visit [Access and authentication](/agent-security/evo-by-snyk/access-and-authentication.md).
{% endhint %}


---

# 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://docs.snyk.io/agent-security/evo-by-snyk/platform-surfaces/inventory.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.