Skip to navigation
Inference Providers

UberLLM

UberLLM is a pay-as-you-go, OpenAI-compatible API that serves chat models such as GPT, Claude, Gemini, DeepSeek, Qwen and Kimi through one key. PrivateGPT can use its Chat Completions endpoint at https://api.uberllm.dev/v1 through the existing OpenAI-compatible integration.

UberLLM has no embeddings endpoint, so this setup sends chat requests to UberLLM and keeps embeddings on a separate local Ollama server. It does not require a new PrivateGPT backend.

Setup

1

Create a key and choose a chat model

  1. Sign up at uberllm.dev, add prepaid credit and create an API key.
  2. Set OPENAI_API_KEY in your environment or .env file. Keep the secret out of committed files.
  3. List the chat models:
curl https://api.uberllm.dev/v1/models

Model IDs use the provider/model form, for example deepseek/deepseek-v4-flash. Set UBERLLM_MODEL to the exact ID of a chat model from the response:

export UBERLLM_MODEL="deepseek/deepseek-v4-flash"
2

Start a local embeddings server

Start Ollama and pull the embeddings model:

ollama pull mxbai-embed-large

These examples use Ollama’s OpenAI-compatible API at http://localhost:11434/v1, with the separate placeholder key ollama.

3

Run PrivateGPT

OPENAI_API_BASE=https://api.uberllm.dev/v1 \
  OPENAI_EMBEDDING_API_BASE=http://localhost:11434/v1 \
  OPENAI_EMBEDDING_API_KEY=ollama \
  PGPT_LLM_DEFAULT="$UBERLLM_MODEL" \
  PGPT_EMBEDDING_DEFAULT=mxbai-embed-large \
  private-gpt serve

Follow the corresponding installation guide first, including PrivateGPT’s other required services.

Model limits and capabilities

  • GET /v1/models lists chat models only and returns context_length and max_output_tokens for each one, so model discovery sets the context window and output limit.
  • Use the model ID returned by /v1/models unchanged, including its provider/ prefix.
  • Streaming is supported. Tools, reasoning and image input depend on the model; /v1/models reports supports_tools and supports_vision for each one.
  • The examples use local embeddings. Retrieved document excerpts included in a chat prompt are still sent to the hosted API.