StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

Unified model API provider connection for future workflow-owned model actions.

0 listed actions0 capability groups

Connection facts

What the OpenRouter connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
api-key
Setup
Sign in to OpenRouter, create an API key, add credits if needed, and store the key in StackOS.
Capability groups
No callable capability groups published yet.
Action boundaries
No callable actions published yet.

Action catalog

Actions listed for OpenRouter.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

This provider is available to the plugin, but it does not publish callable actions yet.

Direct answer

How does the OpenRouter integration work?

People continue using OpenRouter as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03OpenRouterDoes its bounded part
  4. 04Checked resultKeeps the proof

More from Utilities

Related integrations.

See the plugin →

Common questions

OpenRouter and StackOS.

What can the OpenRouter integration do in StackOS?

The current catalog includes the OpenRouter provider through the Utilities plugin. The exact actions used depend on the workflow and approval rules.

Does StackOS replace OpenRouter?

No. OpenRouter remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.