Error messages

No endpoints found that support tool use.

No endpoints found that support tool use.

The core of it:

No endpoints found that support tool use.

OpenRouter returns it as an HTTP 404. The 2025 version, from a claude-code-router thread, ends with a link to its routing docs:

{"error":{"message":"No endpoints found that support tool use. To learn more about provider routing, visit: https://openrouter.ai/docs/provider-routing","code":404}}

Cline users in 2026 see a longer one (Cline 3.89 in June, 4.1.8 in August), with Try disabling "skills". in the middle and the link moved to /docs/guides/routing/provider-selection. We couldn't tell from the reports whether that "skills" sentence is OpenRouter's or Cline's. Across GitHub, 132 issues carry the line (our count on September 26, 2026).

What an endpoint is here

OpenRouter forwards each request to one of the providers hosting that model, and each of those hosting options is an endpoint. They don't all offer the same features. Tool use, where the model asks your app to run a function such as reading a file, is one of the things some endpoints support and others don't.

Coding agents send tools on every request, since reading and editing files is how they work. So when none of a model's endpoints left in play can take tools, the request has nowhere to go. A commenter in the claude-code-router thread put the practical side bluntly: nearly everything Claude Code does is a tool call, so a model without tools can only chat.

Why it happens with models that do support tools

OpenRouter's provider selection page describes tools as a "soft preference": if some endpoints support them, "the request is only routed to the supporting providers." The same page says that when none of a model's providers support tools, the request still goes through and the tools are ignored. So with default settings, a model that lacks tools entirely shouldn't produce this 404 today. The filters you've set are what turn it into a hard stop:

• Privacy settings. Denying providers that may store your data, or requiring zero data retention (ZDR in OpenRouter's API), can be set per request or account-wide in OpenRouter's privacy settings.
• Provider rules. An only or ignore list in your request's JSON or in the tool's config file.
• Strict parameters. With require_parameters set to true, OpenRouter skips every provider that doesn't support all the parameters in the request, tools included.

That's our best reading of why a Cline user hit it in June with gpt-5-mini on their model list, a model OpenAI serves with tools. Neither Cline issue got an explanation from the maintainers, so check your filters before assuming the model is at fault.

Finding a model that works

OpenRouter's tool calling guide gives the filter: openrouter.ai/models?supported_parameters=tools. Pick from that list. In the 2025 claude-code-router thread the model was DeepSeek R1, which had no tool-capable host there at the time, and the advice that followed was to switch to a model with tool support. (Under the routing rules OpenRouter documents now, that model would get the request with its tools dropped, which for a coding agent is barely better.)

If the model is on the list and it still fails, loosen one filter at a time, starting with account-wide privacy settings, since those apply to every request without showing up in your code.