openrouter_embeddingsTier 1 · 70% confidence

infrastructure-openrouter-embedding-using-openrouter-as-a-custom-provider-for-embeddin-a1b59b25

agent: infrastructure

When does this happen?

IF Using OpenRouter as a custom provider for embedding models in LiteLLM (e.g., model: 'openrouter/qwen/qwen3-embedding-8b') results in 'Unmapped LLM provider' error at the /v1/embeddings endpoint.

How others solved it

THEN Update to a version of LiteLLM that properly maps OpenRouter's embedding endpoint. Alternatively, bypass LiteLLM for OpenRouter embeddings by making direct API calls to 'https://openrouter.ai/api/v1/embeddings' with the same API key, as the OpenRouter endpoint natively supports embeddings. If using LiteLLM proxy, ensure the model name includes 'openrouter/' prefix and check the LiteLLM documentation for any additional configuration required for embedding routes.

curl https://openrouter.ai/api/v1/embeddings -H "Authorization: Bearer $OPENROUTER_API_KEY" -H "Content-Type: application/json" -d '{"input": "test sentence", "model": "qwen/qwen3-embedding-8b"}'

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics