> 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/ai-spm.md).

# AI-SPM

How AI Security Posture Management gives you visibility and governance over the AI assets in your code

AI Security Posture Management (AI-SPM) gives you visibility, governance, and security oversight of the AI assets in your code. It maps your assets, scores their risk, and helps you enforce governance, so you can maintain compliance and make informed decisions about your AI infrastructure.

{% hint style="info" %}
AI-SPM assets appear under **Inventory** > **Code**.
{% endhint %}

### How AI-SPM works

AI-SPM runs as three agents:

* Map assets: the **Discovery agent** maps the AI assets across your repositories and applications. To learn more, visit [AI asset visibility](/agent-security/evo-by-snyk/ai-spm/ai-asset-visibility.md).
* Assess risk: the **Risk intelligence agent** scores the models in your inventory with a Model Risk Score, and evaluates your policies to surface violations and risky usage. To learn more, visit [Risk intelligence](/agent-security/evo-by-snyk/ai-spm/risk-intelligence.md).
* Enforce governance: the **Policy agent** governs your assets through policies and issues. To learn more, visit [Policies and issues](/agent-security/evo-by-snyk/platform-surfaces/policies-and-issues.md).

### Set up AI-SPM

Enable Evo, then import the repositories you want AI-SPM to scan.

To enable Evo, visit [Access and authentication](/agent-security/evo-by-snyk/access-and-authentication.md). To import repositories, visit [AI asset visibility](/agent-security/evo-by-snyk/ai-spm/ai-asset-visibility.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 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/ai-spm.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.