Sari la conținut

Română · beta. Traducerea a fost făcută automat și este încă în curs de revizuire. Citește pagina în engleză

perspectiva aiqbenchProduse AI

analiza aiqbench

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.
Sursă care acoperăOpenRouter
Ce este aceastaLectura unui model asupra articolului și a acoperirii conexe, scrisă pentru aiqbench. Nu sunt cuvintele publicației.

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

OpenRouter4 min de cititArticolul și perspectiva sunt în engleză.

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…

Extras afișat conform termenilor RSS ai publicației · 77 cuvinte · textul integral și figurile sunt pe site-ul publicației

Subiecte conexe