This guide explains how to configure OpenRouter in Aimogen using the unified API key system. OpenRouter acts as a meta-provider that gives access to many different AI models through a single API. As with all providers in Aimogen, there are no enable switches or provider toggles. Entering a valid API key is all that’s required.
What Is OpenRouter in Aimogen #
OpenRouter is an aggregation layer that routes requests to multiple underlying AI models from different vendors. In Aimogen, OpenRouter behaves like a normal provider, but it exposes a much wider model catalog than a single vendor would.
This makes it useful for:
- Accessing many models through one API key
- Testing and comparing different models
- Using niche or experimental models
- Centralizing billing and rate limits
Where to Configure OpenRouter #
All AI provider credentials are managed from:
Aimogen → Settings → API Keys
OpenRouter has its own dedicated API key field in this tab.
Prerequisites #
Before adding the API key, make sure you have:
- An OpenRouter account
- A valid OpenRouter API key
- Billing or credits enabled on OpenRouter
- Outbound HTTPS access from your server
Without credits or billing enabled, requests will fail even if the key is valid.
Setting Up OpenRouter (Step by Step) #
- Go to Aimogen → Settings → API Keys
- Locate the OpenRouter API Key field
- Paste your API key
- Save the settings
That’s it.
There is no provider enable toggle, no manual activation, and no model import step.
What Happens After Saving the API Key #
Once the API key is saved:
- Aimogen automatically validates the key
- OpenRouter becomes an active provider
- Available OpenRouter models are detected dynamically
- Models appear in all relevant model dropdowns
Only models compatible with the selected execution type are shown.
Model Availability and Behavior #
OpenRouter exposes a large and constantly changing model catalog.
Aimogen:
- Queries available models dynamically
- Filters models by capability (chat, text, embeddings, etc.)
- Hides models that do not support the current feature
If a model does not appear, it usually means:
- The model is not available to your OpenRouter account
- You do not have sufficient credits
- The model does not support that execution type
- The model is temporarily unavailable upstream
This is expected behavior.
Common Use Cases for OpenRouter #
OpenRouter is commonly used for:
- Accessing multiple vendors through one provider
- Trying new or experimental models
- Comparing output quality across models
- Avoiding lock-in to a single AI vendor
It is often paired with a primary provider rather than used exclusively.
Removing or Rotating the API Key #
If you remove the OpenRouter API key and save:
- OpenRouter is immediately disabled
- Its models disappear from all selection lists
- Any feature using OpenRouter will fall back or stop gracefully
- No content or settings are deleted
API keys can be rotated safely at any time.
Using OpenRouter with Other Providers #
OpenRouter integrates cleanly into mixed-provider setups.
Common combinations include:
- OpenAI or Claude for stable production content
- OpenRouter for model experimentation
- Groq for low-latency chat
- Ollama for local testing
Provider selection can be overridden per feature, chatbot, or workflow step.
Troubleshooting #
If OpenRouter does not appear or execution fails, check:
- API key correctness
- Available credits or billing status
- Model availability in your OpenRouter dashboard
- Outbound HTTPS connectivity
- Errors shown in Aimogen → Status or Logs
Most issues are related to account credits or model availability rather than plugin configuration.
Summary #
- OpenRouter is configured in Aimogen → Settings → API Keys
- Entering the API key automatically enables the provider
- Models are detected and loaded dynamically
- No enable toggles or manual activation steps exist
- Removing the key disables the provider instantly
OpenRouter gives Aimogen access to a broad and flexible model ecosystem while keeping the same execution flow used by all other providers.
