Agentic Web Tools
- Source
- openrouter.ai
- Author
- OpenRouter
- Date

Context
OpenRouter's server-side web tools let a model choose when to search the web, what to search for and which pages to fetch. OpenRouter runs those requests itself and returns the results to the model, so the application does not need to implement the search-and-fetch loop.
The difference from OpenRouter's earlier web search plugin is control: the plugin ran exactly one search per request, while the tools let the model search zero or many times. Developers can cap cumulative results to bound the material returned. The tool definition and result format are the same across models that support , which makes switching models less entangled with application-side web tooling. OpenRouter notes that identical search behavior, as opposed to an identical interface, requires specifying a search provider such as Exa or Parallel, because native search features vary by model provider. Behavior and migration details.
- tool use — A model's ability to call external functions — run code, search the web, edit files — instead of only generating text.
- agentic loop — The cycle an agent runs in: decide, call a tool, read the result, decide again — repeating until the goal is met or a stop condition fires.
Checking sign-in…
Loading comments…






