aiqbench takeAI Products

OpenRouter is adding a way for Enterprise customers to route their own fine-tuned models and dedicated or reserved deployments through the same API they use for public models, with organization-only visibility. The main practical changes are routing and fallback: private endpoints can be prioritized by default and overflow to public providers, with billing going directly to the customer's provider via BYOK. Teams evaluating this should check the Enterprise add-on requirement and which providers are supported.

Source coveringOpenRouter

What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Private Endpoints: Bring Your Fine-Tuned Models and Capacity to OpenRouter

OpenRouterOctober 14, 20264 min read

Private Endpoints let Enterprise customers route their own fine-tuned models and dedicated deployments through OpenRouter, alongside the public catalog. Private endpoints are only visible within your organization, and requests go through the API your team already uses. Available by request on the Enterprise plan.

Today we’re launching Private Endpoints. OpenRouter already puts the public models your team uses behind one API. Now it can serve the deployments only your team has too. If you run a fine-tuned model, a dedicated deployment of a public model, or capacity you’ve reserved with a provider, you can route it through OpenRouter alongside everything else in the catalog. Your team keeps the API, model slug, and routing preferences they use today. Private endpoints are only…

Excerpt shown under the publisher's RSS terms · 77 words · full text and figures are on the publisher's site

Read at OpenRouter ↗Ask about this article