otari
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/mozilla-ai/otari with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/mozilla-ai/otari'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/mozilla-ai--otari)HTML
<a href="/listings/mozilla-ai--otari"><img src="/api/listings/mozilla-ai--otari/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
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 serveOn 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](docs/agent-guardrails.md) and [Use with Claude Code](docs/use-with-claude-code.md).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 18 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- {
- "name": "otari",
- "owner": {
- "name": "Mozilla AI"
- },
- "metadata": {
- "description": "Plugins that connect a coding agent to Otari, the open-source AI gateway."
- },
- "plugins": [
- {
- "name": "otari-router",
- "source": "./plugins/otari-router",
- "description": "Asks an Otari gateway which model each Claude Code subagent should run on, and starts it there.",
- "category": "productivity",
- "tags": ["otari", "model-routing", "cost", "subagents", "llm-gateway"]
- }
- ]
- }
README.md · README · 180 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <p align="center">
- <img src="assets/otari-logo.svg" width="320" alt="Otari logo"/>
- </p>
- <div align="center">
- **An AI gateway you own and run.**
- Route one endpoint to 40+ providers, issue virtual keys, enforce budgets, and
- track usage.
- [](https://github.com/mozilla-ai/otari/actions/workflows/otari-tests.yml)
- [](https://github.com/mozilla-ai/otari/actions/workflows/otari-lint.yml)
- [](https://github.com/mozilla-ai/otari/actions/workflows/otari-typecheck.yml)
- [](https://github.com/mozilla-ai/otari/actions/workflows/otari-docker.yml)
- 
- [Docs](docs/index.md) · [otari.ai](https://otari.ai) ·
- [Launch blog](https://blog.mozilla.ai/otari-own-your-ai-stack/) ·
- [Discord](https://discord.gg/ZfZPfTdtSe)
- English · [简体中文](README.zh-CN.md)
- </div>
- <p align="center">
- <img src="assets/otari-demo.gif" width="720" alt="Otari dashboard tour: spend overview, usage by model, a request rescued by a routing fallback, two models compared in the Playground, the model catalog, routing policies, API keys, members, budgets, and providers"/>
- </p>
- 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](https://github.com/mozilla-ai/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, conditional selection, traffic splitting, and spill-over past a rate limit
- - Optional code execution, web search, MCP, inference guardrails, and file understanding
- ## Quickstart
- Run Otari with Docker. It needs no configuration:
- ```bash
- docker run -v otari:/data -p 127.0.0.1:8000:8000 mzdotai/otari:latest
- ```
- On its first start, Otari prints a setup link once, and little else:
- ```text
- Otari 1.0.0 is running at http://localhost:8000
- Open this link to choose your password and finish setup:
- http://localhost:8000/setup#key=otari-mk-...
- It is shown only once and carries your master key, so treat it like one.
- ```
- Open it and choose the email and password you will sign in with. Then add a
- provider on the dashboard's **Hosted providers** page and enable default
- pricing there. The key in the link is the gateway's master key, so keep the
- link private.
- Create an API key in the dashboard, from the setup guide on the **Overview** or
- on the **API keys** page, and send a request with it:
- ```bash
- 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`.
- The `otari` volume holds the SQLite database and, beside it, the generated key
- that encrypts stored provider credentials, so a new container started with the
- same `-v otari:/data` keeps its data. Without `-v`, Docker gives each container
- a fresh anonymous volume. Use the Compose setup below to run on PostgreSQL.
- The command a developer runs next to a coding agent (`otari hook`,
- `otari import claude-code`) installs on its own, without the server:
- ```bash
- brew install mozilla-ai/tap/otari
- ```
- See [Agent Guardrails](cli/docs/agent-guardrails.md) and
- [Claude Code](docs/claude-code.md).
- ## Run the full stack
- ```bash
- 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
- and web search services:
- ```bash
- docker compose --profile code-exec --profile web-search up -d
- ```
- The dashboard is served at `http://localhost:8000/`. To store provider keys
- through the dashboard on PostgreSQL, set `OTARI_SECRET_KEY` to a Fernet key
- generated by `otari gen-secret-key`.
- ## API and dashboard
- The core completion routes are:
- - `POST /api/v1/chat/completions`
- - `POST /api/v1/messages`
- - `POST /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](docs/api-reference.md).
- 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 [Run the dashboard](docs/run-the-dashboard.md).
- ## Development
- ```bash
- 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:
- ```bash
- make test
- make lint
- make typecheck
- ```
- See [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request.
- ## Documentation
- - [Quickstart](docs/self-hosted-quickstart.md)
- - [Deployment](docs/deployment.md)
- - [Configuration](docs/configuration.md)
- - [Models](docs/models.md)
- - [Routing](docs/routing.md)
- - [Access control](docs/access-control.md)
- - [Built-in tools](docs/tools.md)
- - [Agent Guardrails](cli/docs/agent-guardrails.md)
- - [SDK and agent integrations](docs/integrations.md)
- - [Architecture](ARCHITECTURE.md)
- ## License
- Apache 2.0. See [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.