provider=openrouter uses your org’s OpenRouter key to generate chat replies.
Setup
1
Get an OpenRouter API key
Go to openrouter.ai, sign in, and create an API key from your dashboard. Copy the key.
2
Add the key to Workspace Settings
In Hyperspeed, open Workspace Settings → OpenRouter integration and paste your API key. Hyperspeed stores it encrypted using
HS_SSH_ENCRYPTION_KEY.You need the
org.manage permission to configure integrations.3
Create an OpenRouter-backed AI staff member
Go to Workspace Settings → AI Staff and create a service account with:
- Provider:
openrouter - Model: a model ID from the OpenRouter model catalog (e.g.
openai/gpt-4o-mini,anthropic/claude-3.5-sonnet,mistralai/mistral-7b-instruct)
Environment variables
These variables tune the chat tool-calling pipeline on the API server. Set them in your.env file or deployment environment.
Reasoning tokens
For models that support extended reasoning (e.g. Anthropic Claude with thinking), setOPENROUTER_CHAT_REASONING_JSON to a JSON object. Examples:
Authentication
Hyperspeed authenticates all OpenRouter requests withAuthorization: Bearer <org key> as documented by OpenRouter. The key is stored per-organization and never exposed in API responses (only a display hint is returned).
Troubleshooting
GET /api/v1/organizations/{orgID}/integrations/openrouter returns 404 page not found
The running API binary was built before the OpenRouter routes were added. Rebuild and restart the API:
GET /api/v1/organizations/{orgId}/integrations/openrouter returns a 200 response instead of 404.