> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/local-model.md).

# Local Model

Connect to locally hosted models for offline AI processing.

This catalog entry does not define workflow actions, event triggers, or knowledge retrieval capabilities.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector       | Authentication |
| --------------- | -------------- |
| Local LLM       | API Key        |
| Local Embedding | API Key        |
| Local Model     | API Key        |

#### Local LLM

Connect to locally hosted LLM models via OpenAI-compatible API endpoints.

**Set up in Local Model**

1. Host your language model behind an OpenAI-compatible API endpoint (for example vLLM or Ollama).
2. Note the endpoint's base URL and, if your server requires one, an API key.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Local LLM**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required                 | What to enter                                                         |
| ----------------- | ------------------------ | --------------------------------------------------------------------- |
| API Key           | Yes                      | API key for your local LLM endpoint.                                  |
| Endpoint Base URL | Yes                      | Base URL for your local LLM endpoint (e.g., <http://localhost:8080>). |
| Health Check Path | Optional / as applicable | Optional health check endpoint path (e.g., /health).                  |
| Available Models  | Optional / as applicable | List of model IDs available at this endpoint.                         |

#### Local Embedding

Connect to locally hosted embedding models via OpenAI-compatible API endpoints.

**Set up in Local Model**

1. Host your embedding model behind an OpenAI-compatible API endpoint.
2. Note the endpoint's base URL and, if your server requires one, an API key.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Local Embedding**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required                 | What to enter                                                               |
| ----------------- | ------------------------ | --------------------------------------------------------------------------- |
| API Key           | Yes                      | API key for your local embedding endpoint.                                  |
| Endpoint Base URL | Yes                      | Base URL for your local embedding endpoint (e.g., <http://localhost:8080>). |
| Health Check Path | Optional / as applicable | Optional health check endpoint path (e.g., /health).                        |
| Available Models  | Optional / as applicable | List of embedding model IDs available at this endpoint.                     |

#### Local Model

Connect to locally hosted models via API endpoints.

**Set up in Local Model**

1. Note the endpoint's base URL and, if your server requires one, an API key.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Local Model**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required | What to enter                                                           |
| ----------------- | -------- | ----------------------------------------------------------------------- |
| API Key           | Yes      | API key for your local model endpoint.                                  |
| Endpoint Base URL | Yes      | Base URL for your local model endpoint (e.g., <http://localhost:8080>). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Important behavior

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/local-model.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.
