- Jev via TypeSafe, with a TypeSafe API key (this page)
- Jev via OpenRouter, with the OpenRouter key a deployment already uses for OpenRouter
- Jev via Vercel AI Gateway, with the AI Gateway key a deployment already uses for Vercel AI Gateway
Get an API key
Create an API key in your TypeSafe account.Configuration
Add TypeSafe in Settings > Models and paste the key. Roomote checks the key with a small request when you save it. Self-hosted operators can set the key in the environment instead:R_JUDGMENT_MODEL to typesafe, openrouter,
vercel, roomote, or off. The environment variable overrides the Settings
choice.
What is sent to TypeSafe
Each judgment sends only the text that decision needs, such as a channel message and its launch criteria, a request and the names and descriptions of skills, tools, or environments, a PR review event, or Memory search passages. The key stays on the control plane and is never sent to task sandboxes. Review TypeSafe’s data terms before enabling it.Verify setup
- save the key in Settings > Models and confirm TypeSafe shows as connected
- confirm Judgment model shows Jev via TypeSafe
- post a message in an auto-respond channel and confirm the launch decision in the logs names the judgment model
Common issues
- The key is rejected when saving. Confirm the key is active in your TypeSafe account.
- The judgment model is selected but unused. The selected route needs its key: a TypeSafe key for Jev via TypeSafe, an OpenRouter key for Jev via OpenRouter, or a Vercel AI Gateway key for Jev via Vercel AI Gateway. Roomote never switches routes on its own.
- Decisions look the same as before. Roomote acts on the judgment model only when it is confident; everything else keeps the existing behavior.