OpenRouter AI employee

A Superkind AI employee that checks generations, explains model errors, monitors credits, and manages API keys in OpenRouter. Message it in Teams or Outlook, it works in OpenRouter and reports back with the result. Sensitive actions wait for your approval.

  • Hosted in the EU
  • GDPR data processing agreement
  • Ready to start today
  • Works in Teams, Slack and more

What is a OpenRouter AI employee?

An OpenRouter AI employee connects to your OpenRouter account and completes work in it. It checks generations, analyses costs and errors, manages API keys, and monitors providers. Superkind builds it with your company knowledge, your rules, and your team responsibilities.

Unlike Zapier or Make, there is nothing to configure. You describe the outcome you need, the AI employee picks the right OpenRouter actions, chains them with your other systems, and asks for your approval before sensitive changes.

About OpenRouter

OpenRouter provides one API for hundreds of AI models, provider routing, central billing, and access management.

  1. You ask in Teams

    Describe what you want to know about models, costs, or errors in plain English.

  2. Superkind picks the actions

    Selects the right OpenRouter actions and connects them with your systems.

  3. OpenRouter

    Superkind works in OpenRouter

    Checks generations, credits, providers, and API keys in your real data.

  4. Superkind reports back

    Delivers the result with sources in Teams or Outlook.

Try asking

What can you ask Superkind to do in OpenRouter?

Simply write what you need, add your specifics, and Superkind takes it from there.

Check the OpenRouter alert after today’s deployment and summarise the affected models and providers.

you, to @Superkind

Explain the cause of failed generations since this morning using error codes and endpoint data.

you, to @Superkind

Create a Jira ticket with the affected models, error rate, and links to the generations.

you, to @Superkind

Let me know here as soon as new OpenRouter incidents affect more than two providers or our credit limit.

you, to @Superkind
How it works

How does Superkind work with OpenRouter?

  1. Native integrations and connectors for 1,000+ tools

    1Connect your systems

    You connect OpenRouter securely to Superkind. Add Teams and the systems where your team works. Superkind uses only the permissions you agree. You can then assign tasks directly in Teams.

  2. Lena Hoffmann9:12 AM

    @Superkind check the OpenRouter alert since the deployment and prepare a guardrail for the affected API keys.

    @SuperkindApp9:13 AM

    I am checking the OpenRouter generations and preparing the right guardrail.

    2Tell Superkind what you need

    Message Superkind in Teams with the OpenRouter generations, models, or costs you want checked. You do not need endpoint names or queries. Superkind understands the outcome and picks the right actions. Any questions stay in context in Teams.

  3. @SuperkindApp9:14 AM
    • 3 endpoint errors since deployment
    • Provider endpoint: timeout
    • Guardrail gr-prod created
    OpenRouter
    Guardrail gr-prodstill inactive · 2 rules
    Waiting for your approvalAssign guardrail to API keys?

    3Superkind operates, you approve

    Superkind runs the check in OpenRouter and delivers the results in Teams. Changes to API keys, budgets, or access wait for your approval. Superkind only runs the sensitive OpenRouter action after your confirmation. Every step is logged.

Actions

What can Superkind do in OpenRouter?

Ask in plain English from Teams or Outlook. Superkind picks the right OpenRouter actions, completes the work, and reports back. No workflows to build.

  • Usage

    Check credits

    Shows purchased, used, and remaining OpenRouter credits.

  • Usage

    Analyse activity

    Groups OpenRouter activity by endpoint, model, or workspace.

  • Usage

    Check generation

    Reads the model, provider, tokens, cost, latency, and status of a generation.

  • Usage

    Get error content

    Retrieves stored error details from an OpenRouter generation for root cause analysis.

  • Usage

    Compare usage

    Compares tokens and costs across models, API keys, or workspaces.

  • Models and providers

    List models

    Lists available OpenRouter models with context length, modalities, and prices.

  • Models and providers

    Check model

    Reads the full properties of a model from its slug.

  • Models and providers

    Compare endpoints

    Compares a model’s provider endpoints by price, latency, and supported parameters.

  • Models and providers

    List providers

    Lists all OpenRouter providers and their current properties.

  • Models and providers

    Preview ZDR impact

    Shows which endpoints remain available with Zero Data Retention enabled.

  • API keys

    List API keys

    Lists OpenRouter API keys with name, hash, limit, and usage.

  • API keys

    Check API key

    Reads details and usage for a specific OpenRouter API key.

  • API keysNeeds approval

    Create API key

    Creates an OpenRouter API key with a name and optional credit limit.

  • API keysNeeds approval

    Limit API key

    Changes the credit limit or name of an OpenRouter API key.

  • API keysNeeds approval

    Delete API key

    Permanently deletes an existing OpenRouter API key.

  • Workspaces

    List workspaces

    Lists OpenRouter workspaces with ID, slug, and status.

  • WorkspacesNeeds approval

    Create workspace

    Creates a new OpenRouter workspace for a team or project.

  • Workspaces

    List members

    Shows members and roles in an OpenRouter workspace.

  • WorkspacesNeeds approval

    Add members

    Adds organisation members to an OpenRouter workspace with their role.

  • WorkspacesNeeds approval

    Set budget

    Sets a daily, weekly, or monthly budget for an OpenRouter workspace.

  • Guardrails and presets

    List guardrails

    Lists OpenRouter guardrails with their rules and assignments.

  • Guardrails and presetsNeeds approval

    Create guardrail

    Creates an OpenRouter guardrail for spending, models, or sensitive content.

  • Guardrails and presets

    List presets

    Lists OpenRouter presets by their latest update.

  • Guardrails and presets

    Check preset versions

    Shows every version of an OpenRouter preset in order.

  • Other

    List files

    Lists files in the OpenRouter workspace with type, size, and status.

  • Other

    Check BYOK credentials

    Lists Bring Your Own Key provider credentials in the OpenRouter workspace.

Works with your stack

Superkind uses OpenRouter together with your other systems

Ask for outcomes across tools. Superkind checks OpenRouter, matches incidents with GitHub, Jira, or Linear, and reports the result in Teams or Outlook.

Matching AI employees

Superkind AI employees that work with OpenRouter

Every role brings its expertise and uses OpenRouter as one of its tools.

Companies working with Superkind

CG Group
CG Real Estate
Ecobuilding
Nivocare
Lindenstrom
Tylrus
Lorvan
Voelpker
Voelpker
Lorvan
FAQ

Frequently asked questions

Everything you need to know about your AI employee for OpenRouter.

Yes. Superkind connects OpenRouter through a managed connector. Once connected, your team can ask the AI employee from Teams or Outlook to check generations, analyse costs, or compare models and providers. It only receives the OpenRouter permissions required for the tasks you have agreed.

An admin provides the right OpenRouter access and confirms the required permissions. Superkind configures the connection with you and tests it using one clearly scoped task. The AI employee can then use OpenRouter from Teams. Management actions use separate access with the fewest permissions possible.

It can check credits and activity, analyse generations with tokens, costs, and errors, compare models and provider endpoints, and manage API keys, workspaces, budgets, guardrails, and presets. The list above shows typical OpenRouter actions. You decide which actions the AI employee runs independently based on your processes and permissions.

No. With Zapier or Make, you build and maintain triggers, filters, and individual steps. With the AI employee, you describe the outcome in plain English. Superkind picks the right OpenRouter actions, connects them with Teams, Jira, or GitHub when needed, and asks for clarification when information is missing for safe execution.

Only with your approval. Superkind can read data, explain errors, and prepare reports independently. Creating, limiting, or deleting API keys and changing workspace budgets or memberships wait for an explicit yes from a responsible person in Teams. You decide which OpenRouter actions are sensitive and who may approve them.

Superkind is hosted in the EU and signs a GDPR data processing agreement with you. The AI employee receives minimal OpenRouter permissions and separate access for sensitive management tasks. Your data is not used for training. Every action is logged, so you can trace checks, changes, and approvals later.

OpenRouter has no flat monthly price per user. Model usage is billed through credits at each model’s price. Zapier starts at about 20 euros per month and Make at about 10 euros per month, both plus setup and maintenance time. Superkind is priced per use case, a fraction of a full-time hire.

Putting your AI to workContact ustogether