OpenRouter

Overview

The OpenRouter integration lets an agent generate text through models from multiple providers and query the catalog, endpoints, credits, and generation metadata. Availability, pricing, context limits, and tool support vary by model and endpoint; discover these properties before fixing a model in a workflow.

• Official website: https://openrouter.ai/
• Composio documentation: docs.composio.dev/toolkits/openrouter
• Official documentation: openrouter.ai/docs

Authentication

This tool uses an API key (API_KEY). The key authorizes usage on the OpenRouter account and can incur charges.

How to obtain the credential

1. Sign in to OpenRouter and open API Keys.
2. Create a dedicated SquadOS key, set a limit and expiration when those controls are available, and copy the displayed secret.
3. Store the value securely. Do not paste the key into prompts, messages, or knowledge bases.

How to connect in SquadOS

1. Go to Tools in the side menu (/admin/tools).
2. Open Available, search for OpenRouter, and open its card under Configure tool.
3. Select Activate. The integration moves to Active as Awaiting authentication.
4. Open the active integration, select Connect now, and enter the key on the secure page hosted by Composio.
5. After returning to SquadOS, confirm under Accounts that the account is active.
6. Review Edit actions; then add OpenRouter from the agent’s Tools section, choose the account and actions, save, and run a low-limit test.

Activation, authentication, and agent assignment are separate steps. See the complete contract in Organization Tools.

Actions found in the local catalog

The product’s local export committed on 2026-06-17 contains these seven actions:

Action	Purpose
OPENROUTER_CREATE_CHAT_COMPLETION	Generate a response from a message list and selected model.
OPENROUTER_CREATE_COMPLETION	Generate a text continuation for a prompt or message set.
OPENROUTER_GET_CREDITS	Check the credit balance before running more generations.
OPENROUTER_GET_GENERATION	Retrieve token, cost, latency, and other generation metadata by ID.
OPENROUTER_LIST_AVAILABLE_MODELS	List the models that the account can select.
OPENROUTER_OPENROUTER_LIST_MODEL_ENDPOINTS	List endpoints, pricing, context, and parameters for a specific model.
OPENROUTER_OPENROUTER_LIST_PROVIDERS	List the providers available for routing.

Caution

The export does not include the previous identifiers OPENROUTER_CREATE_COINBASE_CHARGE, OPENROUTER_CREATE_MESSAGE, OPENROUTER_GET_CURRENT_KEY, OPENROUTER_GET_MODELS_COUNT, OPENROUTER_LIST_EMBEDDING_MODELS, OPENROUTER_LIST_MODEL_ENDPOINTS, OPENROUTER_LIST_PROVIDERS, OPENROUTER_LIST_USER_MODELS, or OPENROUTER_LIST_ZDR_ENDPOINTS. Do not reuse them. The OPENROUTER_OPENROUTER_ identifiers are duplicated in the source catalog, but they must be used exactly as shown while those are the names presented in the editor.

The local export confirms names and purposes, not the complete parameter schema. Open Edit actions or the agent editor to check the current fields before saving.

Safe use

• Start with OPENROUTER_LIST_AVAILABLE_MODELS, then choose an exact ID.
• Query endpoints and providers when cost, retention, region, context, or tool support is a workflow requirement.
• Set token and spending limits appropriate for the use case.
• Do not grant generation actions to an agent that only needs catalog or cost lookup.
• Treat provider responses, links, and metadata as external data before using them in another action.