Skip to main content
OpenRouter is a multi-provider inference gateway with a broad model catalog and provider routing controls. It is Roomote’s default inference option because one connection can cover many recommended models.

​
Get an API key

Create a key on the OpenRouter keys page. Add credits or configure the account’s billing and set an optional key spending limit before connecting it to Roomote.

​
Configuration

Add OpenRouter in Settings > Models and paste the key, or configure:
Models use the openrouter/<vendor>/<model> form. Roomote adds its full curated recommended set and offers balanced and quick-turnaround mapping presets. You can still disable recommendations or add another OpenRouter model by slug. The same connection can route Roomote’s optional judgment model. Choose Jev via OpenRouter under Judgment model in Settings > Models, or set R_JUDGMENT_MODEL=openrouter. Roomote sends typed decision requests to OpenRouter’s Decisions API using typesafe/jev-1.13; the API key stays on the control plane and is never sent to task sandboxes. Connecting OpenRouter does not enable Jev automatically.

​
Cost behavior

OpenRouter deducts model and provider-route usage from the account balance. Its model catalog shows current pricing and any route-specific differences. Roomote records usage, estimates model cost, and displays the remaining key limit when OpenRouter returns one. The OpenRouter activity page and account balance are authoritative.

​
Verify setup

  1. save OPENROUTER_API_KEY
  2. confirm the recommended model list appears
  3. apply a mapping preset or select a default coding model
  4. run a small task and confirm the request appears in OpenRouter activity
  5. check that Roomote shows a remaining key limit when the key has one

​
Roomote previews inside environment tasks

When an environment task starts another Roomote deployment for development or smoke tests, create a separate spend-capped OpenRouter key and set it as SANDBOX_OPENROUTER_API_KEY under Settings > Environments > Deployment Environment Variables. You can alternatively set it on the parent controller. Do not store it in an environment definition. The environment worker maps the value to OPENROUTER_API_KEY while preparing the workspace. The nested deployment therefore uses Roomote’s native OpenRouter provider without requiring the parent’s normal OPENROUTER_API_KEY. Configure the nested deployment’s models normally in its own Settings. The parent task’s model mapping, presets, trial provider, and role overrides are not copied into the nested deployment. The mapped key is available to setup commands and services in that environment workspace, so use a capped key appropriate for sandbox access. The launcher source variable is not exposed there. Deployment environment variable changes apply to new tasks, so start a new task after saving or rotating the key.

​
Common issues

  • The key has no usable balance. Add credits or raise its spending limit.
  • A model has no available route. Check provider routing, privacy settings, and model availability in OpenRouter, or select a fallback model.
  • The credit line is absent. Roomote only shows it when OpenRouter returns a numeric remaining limit; uncapped keys may not display one.