Omniscio

OpenRouter (one key, hundreds of models, no Claude account)

The connect-with-one-key run path: paste a single OpenRouter key and run real sessions against hundreds of models, with no Anthropic account and no sign-in. The same key also powers the app's built-in AI helpers, and signed-in users can instead run on Omniscio's company key and draw down their prepaid credit.

On this page

What it is

Omniscio supports spawning Claude-Code-style sessions backed by OpenRouter — a gateway to hundreds of models — via its Anthropic-compatible endpoint (the "Anthropic Skin", hosted at https://openrouter.ai/api). It is the seventh member of the anthropic-compat family, alongside deepseek, kimi, glm, minimax, meta, and qwen.

What makes OpenRouter special: it is the "connect with one key, no Claude account" run path. A new user can pick OpenRouter in first-run setup, paste a single sk-or-… key, and run real agents — no Anthropic account, no sign-in, no managed pool. That same one key also powers the built-in AI helpers (session titles, suggestions, reply drafts, the daily digest), because it reuses the shared userOpenrouterApiKey slot.

Two OpenRouters — don't confuse them. OpenRouter ALSO ships as a flag-gated customOpenai preset (proxy-backed through the local CLIProxyAPI, behind the off-by-default custom-providers feature, keyed separately in customProviderKeys). That preset is a power-user "add any OpenAI-compatible endpoint" path. THIS provider (openrouter) is the no-proxy, onboarding-visible, one-key path. They coexist; most users only ever see this one.

Where to find it

First-run setup's Connect step puts OpenRouter in the provider pick list; afterwards it lives in Settings → Accounts with the rest of the providers.

How it behaves

What the user sees

An OpenRouter session looks identical in the sidebar and main pane to a Claude session — same status dots, streaming bubbles, Ctrl+Enter to send, Plan / Auto-Accept / Bypass Permissions modes, and tool-call approval UI. Tool-call behavior is identical to Claude because the same claude CLI binary is doing the talking — only the model and the upstream endpoint differ. There is no yolo / auto-approve mode; the standard Claude approval flow applies.

How to enable

Two ways lead here:

  1. First-run setup (the headline path). On the Setup v2 "Connect" step, OpenRouter appears in the provider pick list ("Run any model with one key — no account needed"). Pick it, paste your key, and setup finishes with a working, account-free run path. Saving the key auto-enables allowOpenrouterSessionSpawn AND powers the built-in helpers (one key, both jobs). A note under the key field says exactly that.
  2. Settings → Accounts. Like the other alternative providers, OpenRouter's management card lives under Settings → Accounts → Show alternative AI providers (ON by default on a fresh install). Its two gates: the Allow OpenRouter sessions toggle and the OpenRouter key field (which is the SAME "Your OpenRouter key" field under Settings → API Keys — one shared slot).

Add your own key — or run on Omniscio credits. The wiring ships complete but keyless — with no key, an OpenRouter spawn is refused up front with a clear "add a key" message (it never crashes or silently falls back to Claude). Two ways to pay, both rows of OpenRouter's supply list in Settings → Accounts → Who pays & who serves: your own sk-or-… key (below), or Omniscio's company key drawing down your prepaid balance — see the Company OpenRouter credits section below. A session connects through the first row that can serve.

Once ready you can launch an OpenRouter session three ways: the per-launch ChangeProviderButton on a fresh session, a per-project default (Edit Project → Default provider), or programmatically (provider: 'openrouter' via recipes / the CLI control API).

Company OpenRouter credits (run on Omniscio's key, draw down your credits)

Instead of pasting your own OpenRouter key, any signed-in user can run OpenRouter sessions on Omniscio's company OpenRouter key — usage draws down that user's prepaid credit balance (the same balance shown in Settings → My API Keys) and is cut off when it hits zero. It is the Omniscio credits row of OpenRouter's supply list in Settings → Accounts → Who pays & who serves — a new user's list holds it right after their own key, and moving it up makes credits pay first. See model-vendors.md.

Two things set it apart from the GLM company-credits path:

  • Ungated — no plan tier. GLM's company credits are Pro-only; OpenRouter's are open to any signed-in account with a positive prepaid balance (minTier: 'free' in the routing map). The gate is sign-in + credits, nothing more.
  • Every model, priced live. It covers every model OpenRouter serves (~400 today), not a fixed list. The gateway meters whatever vendor/model slug the session runs against OpenRouter's own price list (fetched + cached hourly), so a curated-picker model and a recipe/CLI-supplied slug both bill at their real rate. A model whose price the cache hasn't loaded yet is billed at a conservative blended floor (never under-billed) and self-corrects within the hour.

Rules (same fail-closed stance as GLM):

  • Signed-in only. The row authenticates to Omniscio's gateway with your sign-in token; signed out, it is skipped and the next row serves, and with no other row an OpenRouter spawn fails closed with a "sign in (or add your own key)" message — never a broken session.
  • The list's order decides. Whichever of your own key and the credits row comes first in OpenRouter's list pays first; the other is used when the first cannot serve.
  • Out of credits → the next row, or a clean stop. When your balance reaches zero the gateway refuses; the session moves to the next row of the list that can serve, and only when none is left does it stop with an "out of credits — top up" message, not a raw error.

How it works: the OpenRouter session runs through Omniscio's own gateway — the same service behind "My API Keys" — with your sign-in token as the bearer, so the company OpenRouter key never reaches your machine. The gateway prices the turn's real token usage from OpenRouter's live rate list, applies the standard 10% markup, and debits your prepaid credits. The routing is data-driven and shared with GLM, so the two providers differ by one row of configuration.

Choosing the model

OpenRouter is a gateway, so its model ids are vendor/model OpenRouter slugs. Omniscio curates a short list (registry-driven, MODELS_BY_PROVIDER.openrouter in provider-models.ts):

  • Qwen3 Coder (qwen/qwen3-coder, the default) — an open coding specialist (480B MoE); the low-cost open default, and the cheapest model here that could be proven to answer.
  • Qwen3.8 Flash (qwen/qwen3.8-flash) — a fast, cost-efficient multimodal MoE. Offering it here is what makes this id nameable: a reviewers entry is placed by looking the name up against the engines' pickers, so an id no picker carries resolves to nothing and silently falls back to the author's own engine. No AI Code Review entry currently names it — both review steps run glm and deepseek. Verified on this lane, not the OpenAI-compat one — a live POST https://openrouter.ai/api/v1/messages answered HTTP 200 with a well-formed Anthropic Message (the shape that deepseek/deepseek-chat failed to return), so the engine can read it. It had been on OPENROUTER_REFUSED_MODEL_IDS (src/shared/providers/custom-providers.ts) since 2026-09-25 and came off on 2026-09-27 on that measurement.
  • DeepSeek V3 (deepseek/deepseek-chat) — cheap and capable, but it could not answer as of 2026-09-25 (see the note below); it stays selectable rather than being removed, and it is no longer the default.
  • DeepSeek V4.1 Flash 1017 (deepseek/deepseek-v4.1-flash-1017) — the current DeepSeek Flash snapshot, released 2026-10-17 (1M context, vision + tool calling). DeepSeek's own API serves it under deepseek-flash, which is the id the DeepSeek engine already runs; this slug is the OpenRouter spelling, so it is offered here for sessions billed to your OpenRouter balance or Omniscio credits. Verified on this lane: a live POST https://openrouter.ai/api/v1/messages answered HTTP 200 with a well-formed Anthropic Message (a thinking block and a real usage block). Priced at DeepSeek's Flash rate — $0.30/M input, $1.20/M output, $0.006/M cached input, halved off-peak — in its own MODEL_PRICING row.
  • Kimi K3 (moonshotai/kimi-k3) and Kimi K2.7 Code (moonshotai/kimi-k2.7-code) — the same upstream models the kimi provider serves, offered here too because the two lanes bill different accounts.
  • Muse Spark Open (meta/muse-spark-open) — Meta's open-weight coding model (released 2026-10-15; 816B mixture-of-experts, 42B active, 1M context). Meta's own Model API does not serve it, so this lane — your own OpenRouter key or Omniscio credits — is how you reach it in Omniscio; the Meta engine's picker does not list it, and a Meta session pinned to this slug is refused before it starts. Billed at OpenRouter's rate, measured 2026-10-16 on every serving host: $1.25/M input, $4.25/M output, $0.15/M cached input (its own meta/muse-spark-open row in MODEL_PRICING). Every serving host lists tool calling, but it has not yet been run in a live session on this lane — if a turn comes back empty, see the warning below.
  • Claude Sonnet 4.6 (anthropic/claude-sonnet-4.6) — Claude via OpenRouter, one click away (premium, billed at OpenRouter's Claude rates).

[!WARNING] deepseek/deepseek-chat could not answer as of 2026-09-25, which is why it is no longer the default. It replies HTTP 200 with a body that is JSON but not an Anthropic Message, so the engine cannot read it and the turn ends with zero tokens and no output. Two other slugs (anthropic/claude-sonnet-4.6, moonshotai/kimi-k3) answered normally on the same key and lane in the same minute, so it is the model, not the key or the account. Nothing in OpenRouter's model list marks it — it is still listed, with a real timestamp, a real context window and non-zero pricing — so a live request is the only way to know. qwen/qwen3-coder was chosen as the replacement on an explicit live test; do not revert this default without running one.

Use default spawns qwen/qwen3-coder rather than omitting the model flag — OpenRouter's endpoint serves the model named in the slug, and the shared claude binary's built-in default is a Claude id OpenRouter can't route, so the registry pins a real slug via getProviderDefaultModel. An OpenRouter session never inherits your Claude default model.

When a turn produces no output

A vendor can reject a request in a way the claude binary cannot parse — the case above. The engine then emits a synthetic placeholder: a turn with zero tokens and no visible reply. Omniscio keeps the evidence for it rather than guessing:

  • the HTTP status the engine reported for the turn,
  • the synthetic frame's own error value when it carries one,
  • a redacted, bounded snippet of what the engine said.

The raw snippet goes to the log ([placeholder-evidence]), never into the session transcript. What you see in the session is a humanized sentence that names the engine, the model, and — when the running model is the provider's default — that Omniscio chose it. When nothing at all was reported, the message says so instead of inventing a cause. A recognized vendor rejection (out of balance, an expired key, an over-long conversation, a rate limit) is still named specifically, as before.

Error states and fixes

Two gap codes (no binary to check — same claude binary as Claude):

Gap What it means Click-to-fix lands you at…
toggle-off "Allow OpenRouter sessions" is OFF in Settings Settings → Account → Allow OpenRouter sessions toggle
key-missing OpenRouter API key not configured Settings → API Keys → Your OpenRouter key field

A retired/invalid model id, out-of-balance, context-overflow, bad key, or rate-limit is surfaced with the specific cause + fix via the shared classifyAnthropicCompatPlaceholderError / isRetiredAnthropicCompatModel guards the DeepSeek/Kimi/GLM/MiniMax/Meta/Qwen siblings use. See provider-spawn-model-availability-contract.md.

  • qwen-provider.md — the sixth anthropic-compat sibling
  • deepseek-provider.md · kimi-provider.md · glm-provider.md — the other anthropic-compat siblings
  • switching-providers.md — the unified session-provider guide
  • provider-registry-contract.md — the DeepSeek + Kimi + GLM + MiniMax + Meta + Qwen + OpenRouter (anthropic-compat) invariants
  • company-openrouter-gateway-contract.md — the invariants of OpenRouter's Omniscio credits row (ungated, gateway-routed, live-priced company credit)
  • model-vendors.md — who pays for an OpenRouter session (the supply list)
  • company-glm-gateway-contract.md — the GLM sibling of the company-credit path (Pro-gated, static-priced)
  • api-keys.md — the "My API Keys" gateway + prepaid-credit balance the company-credit path draws down

Last verified 2026-10-06