Openrouter
for LuumenAI
Check model availability, key limits, and credits across OpenRouter providers
Connect OpenRouter and Luumen can answer questions about the model access your team depends on. Check the credit balance, read what the current API key allows, list available models and their endpoints, and see which providers and zero-retention endpoints are in play. When credits run low, Luumen can create a Coinbase charge to top up, as an approved step.
The Openrouter toolbox
13 tools: 12 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCreate Chat CompletionGenerate a chat-style completion.
- ReadCreate Message (Anthropic Format)Create a message using Anthropic Messages API format via OpenRouter.
- ReadGet CreditsGet the current API credit balance for the authenticated user.
- ReadGet Current KeyGet information about the currently authenticated API key.
- ReadGet GenerationRetrieve a generation result by its unique ID.
- ReadGet Models CountGet the total count of available models on OpenRouter.
- ReadList Available ModelsList available models via OpenRouter API.
- ReadList Embedding ModelsList all available embeddings models via OpenRouter API.
- ReadOpenRouter List Model EndpointsList endpoints for a specific model.
- ReadOpenRouter List ProvidersList all AI model providers available through the OpenRouter API.
- ReadList User ModelsList models filtered by user provider preferences, privacy settings, and guardrails.
- ReadOpenRouter List ZDR EndpointsPreview the impact of Zero Data Retention (ZDR) on the available endpoints.
- WriteCreate Coinbase ChargeCreate a Coinbase charge for crypto payment to add credits to your OpenRouter account. Approval by default
One prompt, start to finish
What a governed Openrouter run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create coinbase charge. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Openrouter — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Openrouter to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.