> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/ai-models.md).

# AI models

Configure bring-your-own model-provider credentials at project or organisation scope.

AI Models configures model-provider connections that Lleverage can use.

![Connecting a model provider by selecting an existing Secret or Variable rather than pasting the provider key into the AI Models page.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-ba2ac3f1f62d263868d9a3e38e07f2e8a314b529%2Fcontrol-ai-models.png?alt=media)

Current providers shown in the product include **OpenAI, Anthropic, Google, TogetherAI and Mistral**.

A model-provider connection can exist at **Project** or **organisation** scope. The setup surface shows the provider's required configuration key, such as `OPENAI_API_KEY`, and asks you to **Select secret or env var**. You do not paste the credential directly into AI Models; create the sensitive value under [Secrets](/administer-and-govern/control/secrets.md) first, or use Variables only for non-secret configuration.

### Current constraint

There can currently be only **one connection per model provider per Project**, and one per provider at organisation scope. If a Project already has an OpenAI connection, for example, you cannot add a second independent OpenAI connection to that same Project.

The optional nickname changes how the connection is presented; it does not create a second provider slot.

### Plan visibility

AI Models is **not shown** in the Control navigation on the Free plan. Treat that as current navigation behaviour rather than a promise that the underlying route is technically unavailable.


---

# 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.lleverage.ai/administer-and-govern/control/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.