Fine-tuned models no longer need a second integration: OpenRouter private endpoints keep your team's deployments on the same model slug
OpenRouter launched Private Endpoints, letting enterprises register fine-tuned models, dedicated deployments, or reserved capacity as endpoints visible only inside their organization, while continuing to call them through the existing API, model slug, and routing preferences. Previously such deployments meant maintaining a second integration alongside OpenRouter; now an organization's traffic prefers the endpoint by default and can fall back to public providers under existing preferences when it is rate-limited or unavailable. Endpoints must be hosted by a BYOK-supported provider and serve a model already in the catalog, and activation requires one real request that verifies the key, streaming, usage reporting, and model ID.