Plugins

OpenRouter plugins extend the capabilities of any model by adding features like real-time web search, PDF processing, and automatic JSON repair. Plugins can be enabled per-request via the API or configured as defaults for all your API requests through the Plugins settings page.

Available Plugins

OpenRouter currently supports the following plugins:

Enabling Plugins via API

Plugins are enabled by adding a plugins array to your chat completions request. Each plugin is identified by its id and can include optional configuration parameters.

1
const response = await fetch('https://openrouter.ai/api/v1/chat/completions', {
2
  method: 'POST',
3
  headers: {
4
    Authorization: 'Bearer {{API_KEY_REF}}',
5
    'Content-Type': 'application/json',
6
  },
7
  body: JSON.stringify({
8
    model: '{{MODEL}}',
9
    messages: [
10
      {
11
        role: 'user',
12
        content: 'What are the latest developments in AI?'
13
      }
14
    ],
15
    plugins: [
16
      { id: 'web' }
17
    ]
18
  }),
19
});
20
21
const data = await response.json();
22
console.log(data.choices[0].message.content);

Using Multiple Plugins

You can enable multiple plugins in a single request:

1
{
2
  "model": "openai/gpt-4o",
3
  "messages": [...],
4
  "plugins": [
5
    { "id": "web", "max_results": 3 },
6
    { "id": "response-healing" }
7
  ],
8
  "response_format": {
9
    "type": "json_schema",
10
    "json_schema": { ... }
11
  }
12
}

Default Plugin Settings

Organization admins and individual users can configure default plugin settings that apply to all API requests. This is useful for:

• Enabling plugins like web search or response healing by default across all requests
• Setting consistent plugin configurations without modifying application code
• Enforcing plugin settings that cannot be overridden by individual requests

To configure default plugin settings:

1. Navigate to Settings > Plugins
2. Toggle plugins on/off to enable them by default
3. Click the configure button to customize plugin settings
4. Optionally enable “Prevent overrides” to enforce settings across all requests

Plugin precedence

Plugin settings are applied in the following order of precedence:

1. Request-level settings: Plugin configurations in the plugins array of individual requests
2. Account defaults: Settings configured in the Plugins settings page

If a plugin is enabled in your account defaults but not specified in a request, the default configuration will be applied. If you specify a plugin in your request, those settings will override the defaults.

If you want the account setting to take precedence, toggle on “Prevent overrides” in the config for the plugin. It will then be impossible for generations to override the config.

Disabling a default plugin

If a plugin is enabled by default in your account settings, you can disable it for a specific request by passing "enabled": false in the plugins array:

1
{
2
  "model": "openai/gpt-4o",
3
  "messages": [...],
4
  "plugins": [
5
    { "id": "web", "enabled": false }
6
  ]
7
}

This will turn off the web search plugin for that particular request, even if it’s enabled in your account defaults.

Model Variants as Plugin Shortcuts

Some plugins have convenient model variant shortcuts. For example, appending :online to any model ID enables web search:

1
{
2
  "model": "openai/gpt-4o:online"
3
}

This is equivalent to:

1
{
2
  "model": "openai/gpt-4o",
3
  "plugins": [{ "id": "web" }]
4
}

See Model Variants for more information about available shortcuts.