Outils serveur
Donnez aux modèles accès à la recherche web, à l’exécution de code et à d’autres fonctionnalités. Découvrez ce que fait chaque outil, comparez les fournisseurs et les tarifs, et apprenez à l’utiliser. Lire le guide des outils serveur. Les administrateurs d’espace de travail peuvent gérer les outils serveur disponibles depuis la page Outils dans les paramètres de l’espace de travail.
Tous les outils
Questions fréquentes
Server tools are built-in capabilities that OpenRouter exposes to any tool-calling model during a request, including web search, web fetch, image generation, a sandboxed shell, and orchestration tools. For hosted server tools and engines, OpenRouter executes the tool loop server-side so your application does not need to host tool backends; client-executed tools such as default bash and apply_patch return structured tool calls for your application to run locally.
Most server tools work with any tool-calling model through Chat Completions (/api/v1/chat/completions), the Responses API (/api/v1/responses), or the Anthropic Messages API (/api/v1/messages). A few tools follow one API shape, such as apply_patch on Responses and bash on Anthropic Messages, as noted on each tool page.
In-process utilities like datetime and tool search have no separate tool fee beyond normal model token usage. Orchestration and media tools such as advisor, subagent, fusion, and image generation are billed at the underlying models’ token or image prices, while hosted search, fetch, and sandbox tools list per-engine pricing on each tool page.
Yes. Workspace admins can enable, restrict, or lock allowed engines for server tools from the Tools page in workspace settings, and per-request data policies such as Zero Data Retention (ZDR) restrict engines that do not meet that policy.