Skip to main content
Beta
BetaServer tools are currently in beta. The API and behavior may change.
Server tools are specialized tools operated by OpenRouter that any model can call during a request. When a model decides to use a server tool, OpenRouter executes it server-side and returns the result to the model — no client-side implementation needed.

​
Server Tools vs Plugins vs User-Defined Tools

Server ToolsPluginsUser-Defined Tools
Who decides to use itThe modelAlways runsThe model
Who executes itOpenRouterOpenRouterYour application
Call frequency0 to N times per requestOnce per request0 to N times per request
Specified viatools arrayplugins arraytools array
Type prefixopenrouter:*N/Afunction
Server tools are tools the model can invoke zero or more times during a request. OpenRouter handles execution transparently. Plugins inject or mutate a request or response to add functionality (e.g. response healing, PDF parsing). They always run once when enabled. User-defined tools are standard function-calling tools where the model suggests a call and your application executes it.

​
Available Server Tools

ToolTypeDescription
Web Searchopenrouter:web_searchSearch the web for current information
Datetimeopenrouter:datetimeGet the current date and time
Image Generationopenrouter:image_generationGenerate images from text prompts
Web Fetchopenrouter:web_fetchFetch and extract content from URLs
Apply Patchopenrouter:apply_patchPropose file edits via V4A diff patches (Responses API only)
Filesopenrouter:filesRead, write, edit, and list workspace files via the Files API
Fusionopenrouter:fusionRun a panel of models and a judge for multi-model analysis
Advisoropenrouter:advisorConsult a stronger model for guidance mid-generation
Subagentopenrouter:subagentDelegate self-contained tasks to a smaller, faster worker model

​
How Server Tools Work

  1. You include one or more server tools in the tools array of your API request.
  2. The model decides whether and when to call each server tool based on the user’s prompt.
  3. OpenRouter intercepts the tool call, executes it server-side, and returns the result to the model.
  4. The model uses the result to formulate its response. It may call the tool again if needed.
Server tools work alongside your own user-defined tools — you can include both in the same request.

​
Quick Start

Add server tools to the tools array using the openrouter: type prefix:

​
Combining with User-Defined Tools

Server tools and user-defined tools can be used in the same request: 
{
  "model": "openai/gpt-5.2",
  "messages": [...],
  "tools": [
    { "type": "openrouter:web_search", "parameters": { "max_results": 3 } },
    { "type": "openrouter:datetime" },
    {
      "type": "function",
      "function": {
        "name": "get_stock_price",
        "description": "Get the current stock price for a ticker symbol",
        "parameters": {
          "type": "object",
          "properties": {
            "ticker": { "type": "string" }
          },
          "required": ["ticker"]
        }
      }
    }
  ]
}
The model can call any combination of server tools and user-defined tools. OpenRouter executes the server tools automatically, while your application handles the user-defined tool calls as usual.

​
Usage Tracking

Server tool usage is tracked in the response usage object: 
{
  "usage": {
    "input_tokens": 105,
    "output_tokens": 250,
    "server_tool_use": {
      "web_search_requests": 2
    }
  }
}

​
Next Steps

  • Web Search — Search the web for real-time information
  • Datetime — Get the current date and time
  • Image Generation — Generate images from text prompts
  • Web Fetch — Fetch and extract content from URLs
  • Apply Patch — Propose file edits via V4A diffs
  • Files — Read, write, edit, and list workspace files
  • Fusion — Run a panel of models and a judge for multi-model analysis
  • Advisor — Consult a stronger model for guidance mid-generation
  • Subagent — Delegate self-contained tasks to a smaller, faster worker model
  • Tool Calling — Learn about user-defined tool calling