Custom Endpoints
Add custom AI providers like OpenRouter, Ollama, and Anthropic-compatible gateways to IntelliAsk using intelliask.yaml
IntelliAsk supports OpenAI API-compatible services as custom endpoints. It also supports Anthropic-compatible custom endpoints with provider: "anthropic". In the stack deployment you configure endpoints in config/intelliask.yaml and store API keys in config/.env (referenced with ${VAR_NAME} syntax).
Which File Does What?
Custom endpoint setup involves two configuration files:
config/intelliask.yaml-- Defines your custom endpoints (name, API URL, models, display settings). It is already mounted into the IntelliAsk container byintelliask.compose.yml.config/.env-- Stores sensitive values like API keys (referenced fromintelliask.yamlusing${VAR_NAME}syntax).
For a full overview of how configuration is organised, see Configuration & secrets.
Before You Start
This guide assumes you have a provisioned IntelliAsk stack running. If not, complete Installation first.
Step 1. Open the mounted config
The stack already mounts config/intelliask.yaml into the container, so there's nothing extra to wire up — just edit that file on the host.
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 intelliask.yaml to config/.env:
Each ${VARIABLE_NAME} in intelliask.yaml must have a matching entry in config/.env.
Step 4. Restart and Verify
After editing the config or .env, restart IntelliAsk for changes to take effect:
Open IntelliAsk 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 or missing env vars. Validate your YAML with the YAML Validator.
OpenRouter Still Does Not Show Up
For OpenRouter specifically, verify the chain:
config/.envhasOPENROUTER_KEY=...intelliask.yamlhasapiKey: "${OPENROUTER_KEY}"under the OpenRouter custom endpoint
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
Last updated on