Custom Endpoints
Add custom AI providers like OpenRouter, Ollama, and Anthropic-compatible gateways to LibreChat using librechat.yaml
LibreChat supports OpenAI API-compatible services as custom endpoints. It also supports Anthropic-compatible custom endpoints with provider: "anthropic". You configure endpoints in librechat.yaml, store API keys in .env, and mount the config via docker-compose.override.yml for Docker deployments.
Which File Does What?
Custom endpoint setup involves three files, each with a specific role:
librechat.yaml-- Defines your custom endpoints (name, API URL, models, display settings).env-- Stores sensitive values like API keys (referenced from librechat.yaml using${VAR_NAME}syntax)docker-compose.override.yml-- Mountslibrechat.yamlinto the Docker container (Docker users only)
For a full overview of how these files work together, see the Configuration Overview.
Before You Start
This guide assumes you have LibreChat installed and running. If not, complete the Docker setup first.
Step 1. Mount librechat.yaml (Docker Only)
Docker users need to mount librechat.yaml as a volume so the container can read it. Skip this step if you are running LibreChat locally without Docker.
Edit docker-compose.override.yml and ensure the volume mount is uncommented:
Learn more: Docker Override Guide
Step 2. Configure librechat.yaml
Create a librechat.yaml file in the project root (if it does not exist) and add your endpoint configuration. See the librechat.yaml guide for detailed setup instructions.
Here is an example with OpenRouter, Ollama, and an Anthropic-compatible gateway:
Browse all compatible providers in the AI Endpoints section. For the full field reference, see Custom Endpoint Object Structure.
Anthropic-Compatible Endpoints
Use provider: "anthropic" only for endpoints that speak the native Anthropic Messages API. For OpenAI-compatible gateways that merely expose Anthropic models, omit provider and use the regular OpenAI-compatible custom endpoint shape.
API Key Configuration
When configuring API keys in custom endpoints, you have three options:
- Environment variable (recommended):
apiKey: "${OPENROUTER_KEY}"-- reads from.env - User provided:
apiKey: "user_provided"-- users enter their own key in the UI - Direct value (not recommended):
apiKey: "sk-your-actual-key"-- stored in plain text
Step 3. Set Environment Variables
Add the API keys referenced in your librechat.yaml to the .env file:
Each ${VARIABLE_NAME} in librechat.yaml must have a matching entry in .env.
Step 4. Restart and Verify
After editing configuration files, you must restart LibreChat for changes to take effect.
Open LibreChat in your browser. Your custom endpoints should appear in the endpoint selector dropdown.
Not Seeing Your Endpoint?
Check the server logs for configuration errors:
Common issues: YAML syntax errors, missing env vars, or librechat.yaml not mounted in Docker. Validate your YAML with the YAML Validator.
OpenRouter Still Does Not Show Up
For OpenRouter specifically, verify the three-file chain:
.envhasOPENROUTER_KEY=...librechat.yamlhasapiKey: "${OPENROUTER_KEY}"under the OpenRouter custom endpoint- Docker users mounted
librechat.yamlindocker-compose.override.yml
Then restart with:
If the endpoint appears but returns 402 Payment Required, the request reached OpenRouter successfully and the issue is usually account credits, billing, or model availability on OpenRouter.
Next Steps
How is this guide?