Connect your apps
Use AnonRouter with the chat clients, coding tools, self-hosted interfaces, and personal agents you already use.
AnonRouter plugs into many existing AI tools through their custom OpenAI-compatible provider setting. In most cases, you only need an API base URL, a compatibility-enabled AnonRouter key, and a model id.
The common connection values
API base URL: https://api.anonrouter.ai/v1
API key: a compatibility-enabled AnonRouter inference key beginning with
ar_
Model: /auto or an exact id from the model catalog
Some apps ask for the full Chat Completions URL instead of a base URL, store credentials differently, or require extra model capability settings. Use the app-specific guides below for the exact field names and paths.
Create an API keyHow the plug-and-play setup works
Most integrations use compatibility mode: the app sends a standard OpenAI Chat Completions request with your AnonRouter key, and AnonRouter routes it to the model you selected. Streaming responses and tool calls return in the OpenAI-compatible format the client expects.
This makes AnonRouter work with clients that cannot perform a custom authentication exchange. It also means the compatibility broker temporarily receives the stable key identity and request content together in memory. Use a dedicated key, give it an appropriate credit limit, and read the privacy model before sending sensitive content.
Clients or plugins that can make two coordinated requests may instead use the native private ticket flow. The stable key stays on the control plane, while the content request carries only a single-use ticket. Each integration guide identifies which connection path it uses.
Choose a model
Use /auto when you want AnonRouter to select a suitable route within your
allowed privacy and capability constraints. Use an exact model id when you
need predictable behavior or a specific model provider.
Before using tools, file access, or unattended agent workflows, confirm that the selected route supports tool calling and has enough context for the app's prompts and tool output. See models and privacy labels and intelligent routing for the selection rules.
Developer tools
Chat clients and interfaces
Janitor AI
Import a ready-made proxy JSON configuration for roleplay and character chat.
SillyTavern
Connect a custom OpenAI-compatible source and select an AnonRouter model.
Open WebUI
Add an OpenAI connection, discover models, or configure a Docker deployment.
RisuAI
Use the native ticket-flow plugin and understand its browser and credential-storage boundaries.
Chub AI
Connect AnonRouter through Chub's OpenAI reverse-proxy settings.
LibreChat
Add a custom endpoint with ready-made YAML and optional user-provided keys.
Jan Desktop
Add AnonRouter as a remote model provider in the local desktop client.
Personal agents
What generally carries across apps
| Capability | What to expect |
|---|---|
| Model discovery | Available when the app calls AnonRouter's authenticated GET /v1/models endpoint |
| Streaming chat | Supported through OpenAI-compatible Chat Completions |
| Tool calling | Requires support from both the client and the selected model route |
| Automatic routing | Select /auto when the app accepts a custom model id |
| Embeddings | Available to clients that expose a compatible embedding-provider setting |
| Key limits | Use a dedicated key and set a credit ceiling appropriate for the app |
Using a tool that is not listed
If a tool supports a custom OpenAI-compatible provider, start with the common
base URL, key, and model values above. Check whether its URL field expects the
/v1 base or the full /v1/chat/completions path, and whether it requires
native tool calling or the Responses API.
AnonRouter implements a deliberate subset of the OpenAI API. A configurable base URL does not guarantee every app feature will work, so test ordinary text chat first and then enable tools, files, retrieval, or agent actions one at a time.