Immutable solution version
Nebius retires hosted models with notice, legacy ids need their own serving endpoint
Complete solution
Nebius retires hosted models with notice, legacy ids need their own serving endpoint: Do not hardcode legacy Nebius model IDs in production: check the deprecation notice page and the Token Factory model list before each deployment, since public hosted models get retired.
Do not hardcode legacy Nebius model IDs in production: check the deprecation notice page and the Token Factory model list before each deployment, since public hosted models get retired. Pin to a currently served model id and keep the model list check in your deploy script. If a legacy id is required, budget for a dedicated serving endpoint rather than assuming serverless availability.
Context: A Nebius-hosted recipe documents the model retirement pattern to watch. The public hosted model for the Cosmos3 recipe was retired under an August 2026 deprecation notice, and explicit legacy model IDs require a serving endpoint: the recipe notes that it does not establish their current availability. The current path is the Token Factory guide and its migration verification.
Matched source
Source: Published skill Original query: "Nebius retires hosted models with notice, legacy ids need their own serving endpoint" Key terms: endpoint, hosted, legacy, models, nebius, need, notice, retires, serving, their
Evidence
Source: A Nebius-hosted recipe documents the model retirement pattern to watch. The public hosted model for the Cosmos3 recipe was retired under an August 2026 deprecation notice, and explicit legacy model IDs require a serving endpoint: the recipe notes that it does not establish their current availability. The current path is the Token Factory guide and its migration verification.
Verified resolution: Do not hardcode legacy Nebius model IDs in production: check the deprecation notice page and the Token Factory model list before each deployment, since public hosted models get retired. Pin to a currently served model id and keep the model list check in your deploy script. If a legacy id is required, budget for a dedicated serving endpoint rather than assuming serverless availability.
Source URL: https://github.com/nebius/nebius-physical-ai/blob/HEAD/docs/hackathon-cosmos3-reasoner.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_CiKJjegaz3kLHkTpeU3IJg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Nebius retires hosted models with notice, legacy ids need their own serving endpoint <span>— Vectle</span></a>