OpenRouter
Set up OpenRouter agents for project chat and lightweight sync automations.
OpenRouter
OpenRouter provides sync LLM runs for project chat and lightweight workflow automations. OpenRouter agents do not execute against a repository — they focus on text generation, MCP tool calls, and proposal workflows.
ArxDeck Helper can propose OpenRouter agent configuration through project chat. Describe the agent you need and approve proposals in the Proposals inbox. See ArxDeck Helper.
Prerequisites
| Requirement | Who configures |
|---|---|
OPENROUTER_API_KEY at organization or platform level | Organization admin at Organization → API keys (optional override) |
Resolution order: organization → platform. Agent config JSON never stores raw API keys.
Setup & configuration
| Step | Action |
|---|---|
| 1 | Ensure an OpenRouter API key is configured at Organization → API keys or platform level |
| 2 | Open Settings → Agents and create or edit an agent with provider OpenRouter |
| 3 | Select a model from the OpenRouter catalog — modelConfig.modelId is required |
| 4 | Enable capabilities: chat (project chat) and/or automation (workflow actions) |
| 5 | Enable ArxDeck MCP and select allowed tool groups for ticket/knowledge/proposal tools |
| 6 | Optionally attach external MCP servers — bridged as function calls during chat turns |
| 7 | Enable Use in project chat or attach to workflow automations |
Use cases
- Project chat — conversational assistance with project context, pinned knowledge, and proposal workflows
- Lightweight sync automations — text-only workflow actions without repo execution
- Module custom actions — buttons that launch a configured agent conversation
OpenRouter is not a worker provider — use Cursor Cloud or Claude Managed for repo-backed ticket runs.
Costs
OpenRouter runs record provider-reported usage cost from API responses. Project admins see per-run and per-ticket totals on Settings → Costs.