
otari
Open-source, OpenAI-compatible LLM gateway you run yourself. One endpoint for 40+ providers, with virtual keys, budgets, and usage tracking.
Install with your AI
Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.
Install and set up otari (claude-plugin project) into my current project. Found on https://claudeers.com/otari Repo: https://github.com/mozilla-ai/otari Homepage/docs: https://otari.ai/docs/gateway Detected install method: claude-plugin → /plugin install otari@mozilla-ai/otari Category: other. Platforms: api, web, mobile. Read the repo's README for exact setup and env vars, then install it and wire it into my project. Claudeers Health Verdict: active; community-verified: false. Confirm the source before running anything.
/plugin marketplace add mozilla-ai/otari /plugin install otari@mozilla-ai/otari
git clone https://github.com/mozilla-ai/otari
// compatibility
| Platforms | api, web, mobile |
|---|---|
| Operating systems | — |
| AI compatibility | claude |
| License | Apache-2.0 |
| Pricing | open-source |
| Language | Python |
An OpenAI-compatible LLM gateway you own and run.
Route one endpoint to 40+ providers, issue virtual keys, enforce budgets, and track usage.
Docs · otari.ai · Launch blog · Discord
Otari sits between your applications and model providers. It authenticates requests, resolves provider credentials, enforces budgets before dispatch, and records usage afterwards. Provider calls go through any-llm.
Run Otari with your own database and provider keys.
Why Otari
- One OpenAI and Anthropic-compatible endpoint for many providers
- Provider credentials stay behind the gateway
- Revocable API keys with user, workspace, and model scope
- Budget checks before spend and usage records after settlement
- Local routing policies for failover, weighting, and learned selection
- Optional code execution, web search, MCP, inference guardrails, and file understanding
Quickstart
Run an ephemeral gateway with Docker:
docker run --rm -p 8000:8000 \
-e OPENAI_API_KEY=YOUR_OPENAI_KEY \
-e OTARI_CONFIG_YAML='
default_pricing: true
providers:
openai:
api_key: ${OPENAI_API_KEY}
' \
mzdotai/otari:latest \
otari serve
On the first empty database, Otari creates an API key and prints it once:
No API keys found. Created bootstrap key for first run. Save this key now:
tk-...
Send a request with that key:
curl http://localhost:8000/api/v1/chat/completions \
-H "Authorization: Bearer tk-..." \
-H "Content-Type: application/json" \
-d '{
"model": "openai:gpt-4o-mini",
"messages": [{"role": "user", "content": "Say hello."}]
}'
OpenAI clients work by setting base_url to
http://localhost:8000/api/v1.
This container uses SQLite inside the container and is deleted when it stops. Use the Compose setup below for persistent data.
The command a developer runs next to a coding agent (otari hook,
otari import claude-code) installs on its own, without the server:
brew install mozilla-ai/tap/otari
See Agent Guardrails and Use with Claude Code.
Run the full stack
git clone https://github.com/mozilla-ai/otari
cd otari
cp config.example.yml config.yml
# Set a master key, provider credentials, and pricing in config.yml.
# Provider copies of attached files are off until they have a pepper of their own. Compose reads .env.
grep -qs OTARI_PROVIDER_ACCOUNT_PEPPER .env || echo "OTARI_PROVIDER_ACCOUNT_PEPPER=$(openssl rand -base64 32)" >> .env
docker compose pull
docker compose up -d
Compose runs Otari with PostgreSQL. Optional profiles add the code sandbox, web search, and guardrail services:
docker compose --profile code-exec --profile web-search --profile guardrails up -d
The dashboard is served at http://localhost:8000/. To store provider keys
through the dashboard, set OTARI_SECRET_KEY to a Fernet key generated by
otari gen-secret-key.
A one-click deployment template is available for Railway.
API and dashboard
The core completion routes are:
POST /api/v1/chat/completionsPOST /api/v1/messagesPOST /api/v1/responses
Otari also serves the broader OpenAI-compatible and management APIs. The
running server publishes Swagger UI at /api/v1/docs and OpenAPI at
/api/v1/openapi.json. See API reference.
The dashboard manages providers, models, routing, tools, keys, members, budgets, settings, activity, and usage. Its navigation adapts to the signed-in person's authority. See Admin dashboard.
Development
git clone https://github.com/mozilla-ai/otari
cd otari
uv sync --dev
cp config.example.yml config.yml
uv run otari serve --config config.yml
For local development without PostgreSQL, change database_url to
sqlite+aiosqlite:///./otari.db.
Common checks:
make test
make lint
make typecheck
See CONTRIBUTING.md before opening a pull request.
Documentation
- Quickstart
- Deployment
- Configuration
- Models
- Routing
- Access control
- Built-in tools
- Agent Guardrails
- SDK and agent integrations
- Architecture
License
Apache 2.0. See LICENSE.
// faq
What is otari?
Open-source, OpenAI-compatible LLM gateway you run yourself. One endpoint for 40+ providers, with virtual keys, budgets, and usage tracking.. It is open-source on GitHub.
Is otari free to use?
otari is open-source under the Apache-2.0 license, so it is free to use.
What category does otari belong to?
otari is listed under other in the Claudeers registry of Claude-compatible tools.
// embed badge
[](https://claudeers.com/otari)
// retro hit counter
[](https://claudeers.com/otari)
// reviews
// guestbook
// related in Other
Anti-AI-slop design skill for Claude Code, Cursor, and Codex.
Huashu Design · HTML-native design skill for Claude Code · Claude Code 里 HTML 原生的设计 skill · 高保真原型 / 幻灯片 / 动画 + 20 设计哲学 + 5 维评审 + MP4 导出 · Agent-agnostic
Open source Ghostty-based macOS terminal with vertical tabs and notifications for AI coding agents. Built for multitasking, organization, and programmability.
// built by
1 of its contributors also build on official projects — claude-code, claude-cookbooks, claude-plugins-official
→ see how otari connects across the ecosystem