> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/vibesec/agent-ai-bom/agent-ai-bom-ai-models.md).

# Models

On the AI Models tab of the [Agent AI BOM](/vibesec/agent-ai-bom.md) page, you can see which code generation AI models the VibeSec agents in your organization are running on, how widely each model is used, and when each was last called.

Reviewing this list helps you understand which models are being used across the organization and identify unexpected or unapproved model usage.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-0eb1cac81e2be64a3a37ca17a380cb832028bfd6%2FAgent%20AI%20BOM_AI_Models%20(1).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## Table columns

| Column        | Description                                                          |
| ------------- | -------------------------------------------------------------------- |
| Model         | The model identifier, as reported by the agent.                      |
| Total Users   | The number of distinct developers whose agents have used this model. |
| Total Calls   | The total number of calls recorded against this model.               |
| First Seen    | When OX first recorded a call using this model.                      |
| Last Activity | When the most recent call was recorded.                              |

## Filters

| Filter | Description                                                                |
| ------ | -------------------------------------------------------------------------- |
| Model  | Limits the list to selected AI models by name (such as `claude-opus-4-7`). |

## Reviewing models

Review the Model column to verify that the models your developers are using are the ones your organization has approved.

Models you did not expect to see in the list are candidates for follow-up with the developer listed under Total Users.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-2b8894ecf79721c31e451220ce4682f3e26cce19%2FAgent%20AI%20BOM_AI_Models_details%20(1).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.ox.security/vibesec/agent-ai-bom/agent-ai-bom-ai-models.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.