OpenRouter launches Private Endpoints for fine-tuned models and reserved capacity
OpenRouter introduced Private Endpoints, letting organizations route their own fine-tuned models, dedicated deployments or reserved capacity through the same API they already use for public models. Private endpoints are visible only to approved organizations and never appear in public model lists, rankings, search, charts or benchmarks. An admin registers a deployment from the account page, and OpenRouter first sends one real request through a saved BYOK key to confirm the key works, the deployment speaks the OpenAI-compatible format, streaming and usage reporting function, and the model ID matches; only then can the endpoint be activated. The full lifecycle — registration, testing, activation, pricing updates, pausing and deletion — is also available through a Management API and a Terraform provider. It is an add-on to the Enterprise plan that must be enabled by an account representative, and each organization can have up to 10 private endpoints by default.
It folds an organization's own fine-tuned models and reserved capacity into one routing layer, removing the need to maintain a second integration alongside public model APIs.