Skip to content

Use a custom endpoint

Besides Groq and OpenAI, Abe can talk to any service that works like the OpenAI API. Lots of tools do, including some that run entirely on your own computer. This page is for you if you want to:

  • Keep Voice Transform offline by running a language model on your computer with Ollama.
  • Use a gateway such as OpenRouter to pick from hundreds of chat models.
  • Run your own Whisper server, for example on a home server with a GPU.

If you just want something that works with the least effort, use Groq instead.

You give Abe three things:

Field What it is Example
Base URL The address of the service, usually ending in /v1 http://localhost:11434/v1
Model The exact model name the service expects llama3.2
API key The service’s key. Local tools that don’t check keys accept any text ollama

What the service has to support depends on the feature:

  • Dictation needs a speech-to-text endpoint (/v1/audio/transcriptions). Most chat services, including Ollama and OpenRouter, don’t offer this.
  • Voice Transform needs a chat endpoint (/v1/chat/completions). Almost every OpenAI-compatible service offers this.

So a common setup is Local transcription in Abe plus a custom endpoint for Voice Transform. Voice Transform always needs a cloud or custom provider, even when you transcribe locally.

Ollama runs language models on your own computer. Combined with Abe’s Local transcription, nothing you say or select ever leaves your machine. It’s free; you need a reasonably modern computer (8 GB of RAM or more).

  1. Download and install Ollama from ollama.com/download, then start it.

  2. Download a model. Open a terminal (on Windows, PowerShell; on a Mac, Terminal) and run:

    Terminal window
    ollama pull llama3.2

    llama3.2 is small and quick. If your computer has plenty of memory, larger models such as gpt-oss or qwen3 give better rewrites. Browse the Ollama library for others.

  3. In Abe, open Settings and set the Transform provider to Custom (OpenAI-compatible).

  4. Enter:

    • Base URL: http://localhost:11434/v1
    • Model: llama3.2 (or the model you downloaded)
    • API key: any text, such as ollama. Ollama requires a value but ignores it.
  5. Click Test. Abe confirms the connection works.

Ollama doesn’t do speech-to-text, so keep transcription on Local (or Groq/OpenAI). Details: Ollama’s OpenAI compatibility docs.

Abe says What it means What to do
“Couldn’t reach the provider. Check your connection.” Nothing answered at the base URL Make sure the server (or Ollama) is running. Check the base URL, including http:// and the /v1 at the end.
“The selected model is not available. Check Settings.” The server doesn’t know that model name Copy the name exactly. For Ollama, run ollama list to see your models.
“Your API key was rejected. Check it in Settings.” The service checks keys and yours is wrong Paste the key again, or create a new one with the service.
“Your provider account is out of credit.” A paid gateway such as OpenRouter has no credit left, or the key hit its credit limit Add credit or raise the key’s limit.
“The provider is rate limiting you. Try again in a moment.” The service is limiting requests Wait a moment and try again.
“The provider took too long to respond.” The model is slow on your hardware, or it’s still loading Try again; the first request after starting Ollama loads the model and takes longer. A smaller model helps.
“This recording is too long for the provider.” The server rejected the size of the recording Keep recordings shorter, or raise the server’s upload limit.

To stop using a custom endpoint, switch the provider back in Settings, and delete any key you created on the service’s website.