> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/public-ai-llm-models/openrouter.md).

# OpenRouter

The **OpenRouter** node lets you use OpenRouter inside a Diaflow workflow with your own API key. It is a strong fit when your team wants access to multiple AI providers and model families through one account.

<figure><img src="/files/GIFzLPISD2jLrZCdtwKL" alt=""><figcaption></figcaption></figure>

You can use this node for tasks such as comparing models, switching providers without rebuilding a workflow, and choosing the best balance of quality, speed, and cost for a business task.

{% hint style="info" %}
Diaflow runs the workflow. OpenRouter charges usage to your own OpenRouter account.
{% endhint %}

## What this node does

The node takes your instruction, sends it through the selected OpenRouter model, and returns the result to the next step in your workflow. In most business workflows, that result is text.

You can also pass content from earlier steps into this node. For example, you can send documents, customer messages, retrieved knowledge, or business notes and ask the selected model to turn them into a useful answer.

## When to use it

Use **OpenRouter** when you want one provider connection that can expose many different model options. This is useful when your business wants flexibility, easier provider testing, or the ability to change models without changing the overall workflow.

Common use cases include:

* Compare different models for the same business task.
* Switch providers when cost, speed, or output quality changes.
* Standardize one workflow while keeping model choice flexible.

## Before you start

Make sure you have:

* An active OpenRouter account.
* A valid OpenRouter API key.
* Access to the models you want to use through that account.

## How to set it up

Set up the node in this order:

1. In **Credentials**, choose your saved OpenRouter key.
2. In **Model**, choose the provider model that fits your task.
3. In **Prompt**, describe what you want the model to do.
4. Run the node and review the result.

<figure><img src="/files/2KcLUAIUGaOny4fgSEGs" alt="" width="374"><figcaption></figcaption></figure>

If you want the model to work from earlier workflow data, insert that data into the prompt with `@`.

## What each field means

### Credentials

This is where you select the OpenRouter API key your team wants to use. If the correct key is not listed, add it first, then refresh the list if needed.

### Model

This is where you choose the model exposed through OpenRouter. The list depends on the key and account you connected.

For most business users, the choice is simple:

* Choose a general text model for writing, summaries, and Q\&A.
* Choose a stronger model when quality matters more than speed or cost.
* Use model comparison when you need to evaluate output across providers.

If you are unsure, start with one general-purpose model, test it on a real business task, then compare alternatives only if needed.

### Prompt

This is the instruction you give the model. Write it in plain language and focus on the result you want.

A strong prompt usually includes:

* the task
* the context
* the expected format

For example:

```
Read this customer request and draft a professional reply.
Keep the message clear and concise.
Return 1 email draft and 3 short subject line options.
```

If your workflow already has data from previous steps, insert that data into the prompt with `@` so the model uses that content directly.

## Advanced configurations

Open **Show advanced configurations** when you need more control.

### Enable caching

Caching reuses a previous result when the same input runs again. This can help save time and reduce repeated calls.

Use caching when the same request is likely to run more than once and the answer does not need to change every time.

### Caching time

This controls how long the cached result stays available. Use a shorter time when the source content changes often. Use a longer time when the same request repeats across multiple runs.

### Max token

This limits how long the model response can be. Use a lower value for short answers. Increase it when you need fuller summaries, longer drafts, or more detailed output.

## What you get back

The node returns the model’s result to the next step in your workflow. In most cases, that result is text. You can send it to an output node, store it, transform it, or pass it into another business step.

## Tips for business users

* Start with one clear task per prompt.
* Use OpenRouter when comparing providers matters to your team.
* Ask for a specific output format such as bullets, summary, or draft message.
* Test one model first, then compare only when there is a business reason.

### Next steps

* Compare other providers in [Public AI/LLM Models](/workflow-builder/nodes/public-ai-llm-models.md).
* Learn the workflow basics in [Overview](/workflow-builder/overview.md).
* Browse more nodes in [Component List](/workflow-builder/component-list.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.diaflow.io/workflow-builder/nodes/public-ai-llm-models/openrouter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
