Other Clients

Ollama Clients

Quick answer
Prism is not an Ollama server. It listens on port 11434 — Ollama's default port — but it only serves OpenAI-compatible endpoints such as /v1/chat/completions. Clients that speak Ollama's native /api/chat or /api/tags will not work against Prism; clients that support an OpenAI-compatible base URL will.

Last updated Reviewed against Prism v0.3.26

What Prism actually serves

RouteAvailable on Prism?
/v1/chat/completionsYes — OpenAI Chat Completions.
/v1/responsesYes — OpenAI Responses.
/v1/messagesYes — Anthropic Messages, for Anthropic-protocol clients.
/v1/modelsYes — your routed catalog, no auth needed.
/api/chatNo. This route does not exist in Prism.
/api/generateNo.
/api/tagsNo. Ollama's model listing is not served.
/api/showNo.
Why the confusion exists
Port 11434 is Ollama's default, and Prism uses it too so that OpenAI-compatible tools need the least possible configuration. But sharing a port is not the same as speaking the same protocol. The old /api/chat examples in earlier Prism documentation were incorrect.

Prism does speak Ollama upstream

The reverse direction is supported: a custom provider can point at a real local Ollama server over its native API, using Ollama's own /api/chat format as the upstream. That is an outbound setting on a provider, not an inbound route on Prism. Configure it in Provider Setup.

Tools that work today

Any client with an OpenAI-compatible base URL works. Point it at http://127.0.0.1:11434/v1 with prism as the key.

ClientWhat to set
Continue.devAn OpenAI-compatible model with apiBase http://127.0.0.1:11434/v1.
Open WebUIAn OpenAI connection with the base URL above, rather than the Ollama connection.
LibreChatAn openAI-style endpoint in its config with the Prism base URL and key.
Cline, Roo and similar VS Code extensionsAn OpenAI-compatible provider with the same base URL.
Any SDK-based scriptSet OPENAI_BASE_URL and OPENAI_API_KEY.
# Confirm Prism is answering before configuring a client
curl http://127.0.0.1:11434/v1/models

Running Prism alongside a local Ollama

Both default to port 11434, so only one can hold it. If Ollama runs as a background service, move Prism to another port with PRISM_PORT.

# PowerShell
$env:PRISM_PORT = "11435"
# Prism now serves http://127.0.0.1:11435/v1

# bash
export PRISM_PORT=11435

Changing the port also moves the base URL written into every agent integration, so re-sync your agents from the Agents tab after changing it.

Keeping Ollama reachable too
A common setup is Ollama on 11434 and Prism on 11435, with Prism holding a custom provider that points at http://127.0.0.1:11434 for local models. Your agents then reach local and cloud models through one base URL.

Model names

Ollama-oriented tools often default to names like llama3 or codellama. Prism serves a request for an unknown model from your default model, or you can alias the name explicitly:

{
  "aliases": {
    "llama3": "glm-5.1:cloud",
    "codellama": "deepseek-v4-flash:cloud"
  }
}