Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

If Aider shows OpenRouter’s “No Endpoints Found” error, verify the exact model ID and whether OpenRouter currently has endpoints for it. A retired or renamed model is one possible cause, but the message alone does not prove that the model was retired. OpenRouter privacy and provider-routing settings can also prevent a listed model from being served.

What the error means—and what it does not prove

Aider sends requests to OpenRouter using a model identifier, and OpenRouter must have a provider endpoint available and allowed to handle that request. The error can point to a stale model ID or a lack of usable endpoints, but it is not enough on its own to determine which is responsible.

A historical Aider issue illustrates the stale-ID possibility: issue #2444, opened November 24, 2024, reported the related API message “No endpoints found for this model” for openrouter/deepseek/deepseek-coder. Discussion at the time mentioned openrouter/deepseek/deepseek-chat as a replacement. That is historical evidence, not a guarantee that either model ID has an endpoint now. Check OpenRouter’s current catalog before using one.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How to diagnose and fix it

  1. Record the model Aider is actually using. Check the --model command-line option, the AIDER_MODEL environment variable, or the model selected in the active Aider chat. Aider documents these options in its options reference.
  2. Compare the ID with Aider’s OpenRouter model names. Run aider --list-models openrouter/. Aider’s usual naming pattern is openrouter/<provider>/<model>; compare the complete configured string with the names Aider lists in its OpenRouter guide.
  3. Check OpenRouter’s live catalog and endpoint data. Search its model catalog API for the slug. Then check the specific model’s endpoint data using OpenRouter’s documented per-model endpoints API. A catalog record and an available endpoint are separate checks.
  4. Review routing and privacy restrictions. If the model is listed and endpoint data exists, inspect OpenRouter’s privacy settings and the provider controls described in Aider’s OpenRouter guide. Account-level provider ignores, model-level provider routing, provider order, fallback settings, and data-collection restrictions can affect which providers are eligible to serve the request.
  5. Update Aider to an exact current model ID if needed. If the old slug was renamed, retired, or has no active endpoint you can use, choose a model that is currently listed and set Aider’s --model value to its exact slug, keeping the openrouter/<provider>/<model> format. Do not rely on an old tutorial or copy the historical DeepSeek example without checking availability.
  6. Configure Aider metadata only if Aider does not recognize the replacement. Aider’s advanced configuration documentation and model metadata documentation describe ways to add local model settings, context, or cost information. These settings help Aider understand a model; they do not create an OpenRouter endpoint or make an unavailable model available.

Choose the next step based on what you find

What you find What to do
The configured slug is absent from Aider’s list or OpenRouter’s catalog. Check for a typo or stale model ID, then select an exact slug that appears in OpenRouter’s current catalog.
The slug appears in the catalog, but its endpoint data shows no usable endpoint. Select a model with an endpoint available to you, or try another provider supported by Aider.
The slug and endpoint are present, but requests still fail. Review OpenRouter privacy settings and provider ignores, ordering, fallback, and data-collection restrictions.
OpenRouter has a usable endpoint, but Aider reports an unknown model or lacks model details. Check Aider’s model support and, if necessary, configure its local settings or metadata. Do not treat that configuration as a fix for endpoint availability.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Keep the model ID and endpoint checks separate

Model names and provider endpoints can change, so verify both when the error returns. OpenRouter’s catalog can help establish whether a slug is listed; the per-model endpoint response helps establish whether providers currently serve it. Even a listed model may not be usable with a particular account’s routing or privacy settings.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.