OpenRouter 404 No Endpoints Found That Support Image Input — Text-Only Model Fails on Multimodal Tool Results

What this error means

HTTP 404: No endpoints found that support image input is a OpenRouter failure pattern reported for developers trying to fix openrouter rejection when sending images to text-only models (e.g., deepseek-v4-pro); need to detect modality mismatch before tool invocation. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

From NousResearch/hermes-agent PR #23411 (open, created 2026-05-10). When a multimodal tool captures images and sends them via OpenRouter with a text-only model, the API returns 404 instead of a friendly message. Recovery fallback triggers fail because error phrase doesn’t match. High commercial value for teams using multi-model routing. Category mapping: OpenRouter model routing/API compatibility → OpenAI API per SKILL.md context-dependent rules.

Common causes

• From NousResearch/hermes-agent PR #23411 (open, created 2026-05-10). When a multimodal tool captures images and sends them via OpenRouter with a text-only model, the API returns 404 instead of a friendly message. Recovery fallback triggers fail because error phrase doesn’t match. High commercial value for teams using multi-model routing. Category mapping: OpenRouter model routing/API compatibility → OpenAI API per SKILL.md context-dependent rules.

Quick fixes

1. Confirm the exact error signature matches HTTP 404: No endpoints found that support image input.
2. Check the OpenRouter account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/NousResearch/hermes-agent/pull/23411

Evidence note: From NousResearch/hermes-agent PR #23411 (open, created 2026-05-10). When a multimodal tool captures images and sends them via OpenRouter with a text-only model, the API returns 404 instead of a friendly message. Recovery fallback triggers fail because error phrase doesn’t match. High commercial value for teams using multi-model routing. Category mapping: OpenRouter model routing/API compatibility → OpenAI API per SKILL.md context-dependent rules.

Related errors

• OpenAI API

FAQ

What should I check first?

Start with the exact HTTP 404: No endpoints found that support image input text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed OpenRouter workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without HTTP 404: No endpoints found that support image input.