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.

Utilities plugin

OpenRouter

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

0 supported actions0 capability groups

Supported work

What StackOS can do with OpenRouter.

The catalog reflects the actions currently available through the Utilities plugin. 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.

OpenRouter

What StackOS can do with OpenRouter.

How does the OpenRouter integration work?

Related integrations.

Alibaba Wan

BytePlus ModelArk

Firecrawl