← Back to Home
OpenRouter logo

OpenRouter

AI Infrastructure

Unified API gateway for 200+ LLMs — switch models without changing your code.

About OpenRouter

OpenRouter is an API proxy that normalizes access to over 200 language models — GPT-4, Claude, Gemini, Mistral, Llama, and dozens of open-source variants — behind a single OpenAI-compatible endpoint. You use one API key, one request format, and one billing account regardless of which underlying model you choose. The operational value is model flexibility without code changes: if a model is slow, expensive, or unavailable, you swap it by changing a parameter, not by refactoring your integration. For engineering teams, the integration pattern is: Linear issue created → n8n webhook fires → OpenRouter calls the best available LLM to classify severity and suggest an assignee → result posted back to Linear as a comment. This removes the dependency on any single LLM provider and lets teams route high-stakes requests to the most capable model while sending routine classification to cheaper alternatives.

Integration Capabilities

OpenRouter has 0 native integrations in its API directory. This page focuses only on guides we publish and maintain.

How OpenRouter Integrations Usually Work

Start with the implementation model, not the connector. We map each pair by intent so you can decide if native sync is enough or if this workflow needs stronger controls.

OpenRouter Integrations

1

Focused pages with known intent and use-case data.

Direct Paths

0

Native in at least one direction.

Connector Paths

1

Usually require mapping, retries, or approval gates.

Most OpenRouter integrations are built for Complex workflow logic use cases. Open any guide below to see the recommended setup path and cost estimate.

Connector-Based Integrations (1)

These workflows usually need connector logic. Open each setup guide to confirm scope before choosing a platform. If you need a starting point, use the recommendations in the section above.